18. Apr 2024 at 19:53
 Choose Language:
  Phoner(Lite) Forum › Allgemein / General › Fehlermeldungen / Error Messages › SIP-Kommunikation mit linphone
‹ Previous Topic | Next Topic ›
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic SIP-Kommunikation mit linphone (Read 5727 times)
Pythagoras1
YaBB Newbies
*
Offline


Phoner is great!

Posts: 5
Joined: 04. Jun 2005
SIP-Kommunikation mit linphone
04. Jun 2005 at 21:43
Print Post  
hi, ich habe es gewagt einen versuch mit sip durchzuführen und bin kläglich gescheitert.
es ist ein einfaches netzwerk: zwei pcs einer linux mit linphone (192.168.0.225) der andere windows mit phoner (192.168.0.1). beide rechner sind mit einem gekreuzten ethernetkabel verbunden (100 Mbit/s). gleichzeitig steht auf dem windows-rechner eine isdn-verbindung (62.46.weiss.net). in den sip-einstellungen von phoner habe ich 192.168.0.1 ausgewählt, weil ich nur diese direktverbindung testen will.

versuch 1: anruf von phoner nach linphone mit der adresse mayly@192.168.0.225
es läutet das log gibt aus

Code
Select All
21:16:56,040: Connect Request:  to mayly@192.168.0.225
21:16:56,050: Connect Confirm
21:16:56,140: Info Indication: alerting
21:16:56,451: Info Response


sip-log:
Code
Select All
-------------------------------------------
21:16:56,100: T: 192.168.0.225:5060
INVITE sip:mayly@192.168.0.225 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK004458e29ad3d911bc9b004f4e05e581
From: <sip:192.168.0.1>;tag=5170
To: <sip:mayly@192.168.0.225>
Call-ID: 004458E2-9AD3-D911-BC9A-004F4E05E581@192.168.0.1
CSeq: 1 INVITE
Contact: <sip:192.168.0.1>
Max-Forwards: 70
User-Agent: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Type: application/sdp
Content-Length:   241

v=0
o=root 0 0 IN IP4 192.168.0.1
s=SIPPER for phoner
c=IN IP4 192.168.0.1
t=1117912616 1117916216
m=audio 5062 RTP/AVP 2 3 97 101
a=rtpmap:2 G726-32/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:101 telephone-event/8000
-------------------------------------------
21:16:56,120: R: 192.168.0.225:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK004458e29ad3d911bc9b004f4e05e581
From: <sip:192.168.0.1>;tag=5170
To: <sip:mayly@192.168.0.225>
Call-ID: 004458E2-9AD3-D911-BC9A-004F4E05E581@192.168.0.1
CSeq: 1 INVITE
Content-Length: 0

-------------------------------------------
21:16:56,130: R: 192.168.0.225:5060
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK004458e29ad3d911bc9b004f4e05e581
From: <sip:192.168.0.1>;tag=5170
To: <sip:mayly@192.168.0.225>;tag=2605303791
Call-ID: 004458E2-9AD3-D911-BC9A-004F4E05E581@192.168.0.1
CSeq: 1 INVITE
Contact: <sip:mayly@192.168.0.1>
Content-Length: 0
  
Back to top
 
IP Logged
 
Pythagoras1
YaBB Newbies
*
Offline


Phoner is great!

Posts: 5
Joined: 04. Jun 2005
Re: SIP-Kommunikation mit linphone
Reply #1 - 04. Jun 2005 at 21:45
Print Post  
ich wähle in linphone "entgegennehmen". in phoner wird darauf einige sekunden lang "trennen" und "in:GSM, out:GSM" angezeigt, danach "protocol error, layer 2". "in:GSM, out:GSM" steht weiterhin dort, obwohl keine verbindung besteht. hier das log:

Code
Select All
21:17:20,145: Connect Active Indication:
21:17:20,155: Connect B3 Request
21:17:20,195: Connect Active Response
21:17:20,205: Connect B3 Confirm
21:17:20,215: Connect B3 Active Indication
21:17:20,255: WaveOut (0): open
21:17:20,275: WaveIn (0): open
21:17:20,285: Connect B3 Active Response
21:17:20,666: Disconnect B3 Indication
21:17:20,986: WaveIn (0): close
21:17:21,166: WaveOut (0): close
21:17:21,176: Disconnect B3 Response
21:17:21,186: Disconnect Indication: protocol error, layer 2
21:17:23,109: Disconnect Response
21:17:23,169: waveOut opened
21:17:23,370: waveIn opened
21:17:23,580: waveIn closed
21:17:23,600: waveOut closed


sip-log:
Code
Select All
-------------------------------------------
21:17:20,135: R: 192.168.0.225:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK004458e29ad3d911bc9b004f4e05e581
From: <sip:192.168.0.1>;tag=5170
To: <sip:mayly@192.168.0.225>;tag=2605303791
Call-ID: 004458E2-9AD3-D911-BC9A-004F4E05E581@192.168.0.1
CSeq: 1 INVITE
Contact: <sip:mayly@192.168.0.1>
Content-Type: application/sdp
Content-Length:   178

v=0
o=mayly 123456 654321 IN IP4 192.168.0.1
s=A conversation
c=IN IP4 192.168.0.1
t=0 0
m=audio 7078 RTP/AVP 3 101
a=rtpmap:3 GSM/8000
a=rtpmap:101 telephone-event/8000
-------------------------------------------
21:17:20,365: R: 192.168.0.1:5060
ACK sip:mayly@192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK0060a6f09ad3d911bc9b004f4e05e581
From: <sip:192.168.0.1>;tag=5170
To: <sip:mayly@192.168.0.225>;tag=2605303791
Call-ID: 004458E2-9AD3-D911-BC9A-004F4E05E581@192.168.0.1
CSeq: 1 ACK
Contact: <sip:192.168.0.1>
Max-Forwards: 70
Content-Length: 0

-------------------------------------------
21:17:20,546: T: 192.168.0.1:5060
ACK sip:mayly@192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK0060a6f09ad3d911bc9b004f4e05e581
From: <sip:192.168.0.1>;tag=5170
To: <sip:mayly@192.168.0.225>;tag=2605303791
Call-ID: 004458E2-9AD3-D911-BC9A-004F4E05E581@192.168.0.1
CSeq: 1 ACK
Contact: <sip:192.168.0.1>
Max-Forwards: 70
Content-Length: 0

-------------------------------------------
21:17:23,119: R: 192.168.0.1:5060
BYE sip:mayly@192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK0060a6f09ad3d911bc9c004f4e05e581
From: <sip:192.168.0.1>;tag=5170
To: <sip:mayly@192.168.0.225>;tag=2605303791
Call-ID: 004458E2-9AD3-D911-BC9A-004F4E05E581@192.168.0.1
CSeq: 2 BYE
Max-Forwards: 70
User-Agent: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0

-------------------------------------------
21:17:23,129: T: 192.168.0.1:5060
BYE sip:mayly@192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK0060a6f09ad3d911bc9c004f4e05e581
From: <sip:192.168.0.1>;tag=5170
To: <sip:mayly@192.168.0.225>;tag=2605303791
Call-ID: 004458E2-9AD3-D911-BC9A-004F4E05E581@192.168.0.1
CSeq: 2 BYE
Max-Forwards: 70
User-Agent: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0

-------------------------------------------
21:17:23,139: R: 192.168.0.1:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK0060a6f09ad3d911bc9c004f4e05e581
From: <sip:192.168.0.1>;tag=5170
To: <sip:mayly@192.168.0.225>;tag=2605303791
Call-ID: 004458E2-9AD3-D911-BC9A-004F4E05E581@192.168.0.1
CSeq: 2 BYE
Contact: <sip:192.168.0.1>
Max-Forwards: 70
Server: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0

-------------------------------------------
21:17:23,149: T: 192.168.0.1:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK0060a6f09ad3d911bc9c004f4e05e581
From: <sip:192.168.0.1>;tag=5170
To: <sip:mayly@192.168.0.225>;tag=2605303791
Call-ID: 004458E2-9AD3-D911-BC9A-004F4E05E581@192.168.0.1
CSeq: 2 BYE
Contact: <sip:192.168.0.1>
Max-Forwards: 70
Server: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0


in linphone wird dennoch derstatus "verbunden" angezeigt obwohl ich nichts höre. sobald ich in linphone auflege kommt im phoner-sip-log:

Code
Select All
21:19:06,648: R: TEI management(00): FE FF 03 0F 00 00 04 FF
21:19:06,658: T: TEI management(00): FC FF 03 0F 8A 06 05 8B
21:19:07,650: R: TEI management(00): FE FF 03 0F 00 00 04 FF
21:19:07,660: T: TEI management(00): FC FF 03 0F 8D F1 05 8B
-------------------------------------------
21:19:24,654: R: 192.168.0.225:5060
BYE sip:192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK671738760
From: <sip:mayly@192.168.0.225>;tag=2605303791
To: <sip:192.168.0.1>;tag=5170
Call-ID: 004458E2-9AD3-D911-BC9A-004F4E05E581@192.168.0.1
CSeq: 0 BYE
max-forwards: 10
user-agent: oSIP/Linphone-0.12.1
Content-Length: 0

-------------------------------------------
21:19:24,674: T: 192.168.0.225:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK671738760;received=192.168.0.225
From: <sip:mayly@192.168.0.225>;tag=2605303791
To: <sip:192.168.0.1>;tag=5170
Call-ID: 004458E2-9AD3-D911-BC9A-004F4E05E581@192.168.0.1
CSeq: 0 BYE
Contact: <sip:192.168.0.1>
Max-Forwards: 10
Server: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0
  
Back to top
 
IP Logged
 
Pythagoras1
YaBB Newbies
*
Offline


Phoner is great!

Posts: 5
Joined: 04. Jun 2005
Re: SIP-Kommunikation mit linphone
Reply #2 - 04. Jun 2005 at 21:46
Print Post  
versuch 2: anruf von linphone an phoner mit adresse 192.168.0.1

Code
Select All
21:20:37,248: Connect Indication
21:20:37,258:  CIP: 1 (speech)
21:20:37,258:  CalledPartyNumber:
21:20:37,268:  CallingPartyNumber: mayly
21:20:37,268: phone book lookup for mayly: mayly [mayly]
21:20:37,278: Alert Request
21:20:38,240: Alert Confirm


sip-log:
Code
Select All
-------------------------------------------
21:20:37,228: R: 192.168.0.225:5060
INVITE sip:192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK3380752755
From: <sip:mayly@ospranzn>;tag=140370001
To: <sip:192.168.0.1>
Call-ID: 1592915786@192.168.0.1
CSeq: 20 INVITE
Contact: <sip:mayly@192.168.0.1>
max-forwards: 10
user-agent: oSIP/Linphone-0.12.1
Content-Type: application/sdp
Content-Length:   316

v=0
o=mayly 123456 654321 IN IP4 192.168.0.1
s=A conversation
c=IN IP4 192.168.0.1
t=0 0
m=audio 7078 RTP/AVP 3 110 111 115 101
b=AS:110 20
b=AS:111 28
a=rtpmap:3 GSM/8000/1
a=rtpmap:110 speex/8000/1
a=rtpmap:111 speex/16000/1
a=rtpmap:115 1015/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-11
-------------------------------------------
21:20:38,270: T: 192.168.0.225:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK3380752755;received=192.168.0.225
From: <sip:mayly@ospranzn>;tag=140370001
To: <sip:192.168.0.1>
Call-ID: 1592915786@192.168.0.1
CSeq: 20 INVITE
Contact: <sip:192.168.0.1>
Max-Forwards: 10
Server: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0

-------------------------------------------
21:20:38,280: T: 192.168.0.225:5060
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK3380752755;received=192.168.0.225
From: <sip:mayly@ospranzn>;tag=140370001
To: <sip:192.168.0.1>;tag=803012669bd3d911bc9c004f4e05e581
Call-ID: 1592915786@192.168.0.1
CSeq: 20 INVITE
Contact: <sip:192.168.0.1>
Max-Forwards: 10
Server: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0


ich nehme diesen anruf mit "Ja" an und die verbindung besteht:

Code
Select All
21:21:06,861: Connect Response: accept call
21:21:06,881: Connect Active Indication:
21:21:06,901: Connect Active Response
21:21:06,911: Connect B3 Indication
21:21:06,921: Connect B3 Response: accept call
21:21:06,931: Connect B3 Active Indication
21:21:06,961: WaveOut (0): open
21:21:07,001: WaveIn (0): open
21:21:07,061: Connect B3 Active Response
21:21:07,622: waveOut opened
21:21:08,053: waveIn opened


sip-log:
Code
Select All
-------------------------------------------
21:21:07,081: T: 192.168.0.225:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK3380752755;received=192.168.0.225
From: <sip:mayly@ospranzn>;tag=140370001
To: <sip:192.168.0.1>;tag=003d5b779bd3d911bc9c004f4e05e581
Call-ID: 1592915786@192.168.0.1
CSeq: 20 INVITE
Contact: <sip:192.168.0.1>
Max-Forwards: 10
Server: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Type: application/sdp
Content-Length:   170

v=0
o=root 0 0 IN IP4 192.168.0.1
s=SIPPER for phoner
c=IN IP4 192.168.0.1
t=0 0
m=audio 5062 RTP/AVP 3 101
a=rtpmap:3 GSM/8000
a=rtpmap:101 telephone-event/8000
-------------------------------------------
21:21:07,101: R: 192.168.0.225:5060
ACK sip:192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK1680031692
From: <sip:mayly@ospranzn>;tag=140370001
To: <sip:192.168.0.1>;tag=003d5b779bd3d911bc9c004f4e05e581
Call-ID: 1592915786@192.168.0.1
CSeq: 20 ACK
max-forwards: 10
user-agent: oSIP/Linphone-0.12.1
Content-Length: 0
  
Back to top
 
IP Logged
 
Pythagoras1
YaBB Newbies
*
Offline


Phoner is great!

Posts: 5
Joined: 04. Jun 2005
Re: SIP-Kommunikation mit linphone
Reply #3 - 04. Jun 2005 at 21:46
Print Post  
In beiden Programmen steht nun "verbunden", sowie "in:GSM, out:---". Die Audioverbindung funktioniert nur in eine Richtung und zwar von linphone zu phoner. nachfolgend die meldungen, nachdem ich mit linphone auflege:

Code
Select All
21:22:30,481: Disconnect B3 Indication
21:22:30,661: WaveIn (0): close
21:22:30,762: WaveOut (0): close
21:22:30,772: Disconnect B3 Response
21:22:30,782: Disconnect Indication: Normal call clearing
21:22:31,292: OpenDevice (sipper.dll)
21:22:31,302: SIPPER: 2.0 (0.8)
21:22:31,312: Register: 1024 bytes blocksize
21:22:31,372: Listen Request
21:22:31,382: CAPI thread created: 0x0390
21:22:31,392: Listen Request
21:22:33,065: Disconnect Response
21:22:33,085: waveIn closed
21:22:33,105: waveOut closed
21:22:33,125: Listen Confirm
21:22:33,135: Listen Confirm


sip-log:
Code
Select All
-------------------------------------------
21:22:30,461: R: 192.168.0.225:5060
BYE sip:192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK3871048533
From: <sip:mayly@ospranzn>;tag=140370001
To: <sip:192.168.0.1>;tag=003d5b779bd3d911bc9c004f4e05e581
Call-ID: 1592915786@192.168.0.1
CSeq: 21 BYE
max-forwards: 10
user-agent: oSIP/Linphone-0.12.1
Content-Length: 0

-------------------------------------------
21:22:33,075: T: 192.168.0.225:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK3871048533;received=192.168.0.225
From: <sip:mayly@ospranzn>;tag=140370001
To: <sip:192.168.0.1>;tag=003d5b779bd3d911bc9c004f4e05e581
Call-ID: 1592915786@192.168.0.1
CSeq: 21 BYE
Contact: <sip:192.168.0.1>
Max-Forwards: 10
Server: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0


die verbindung wird daraufhin erfolgreich abgebaut.

sobald ich eine gleiche verbindung aber mit phoner trenne:

Code
Select All
21:34:00,373: Disconnect B3 Request
21:34:00,393: Disconnect B3 Confirm
21:34:00,774: Disconnect B3 Indication
21:34:01,084: WaveIn (0): close
21:34:01,104: WaveOut (0): close
21:34:01,114: Disconnect Request
21:34:01,124: Disconnect B3 Response
21:34:01,124: Disconnect Indication: Normal call clearing
21:34:03,247: Disconnect Response
21:34:03,287: Disconnect Confirm
21:34:03,297: waveIn closed
21:34:03,307: waveOut closed


sip-log:
Code
Select All
-------------------------------------------
21:34:00,553: R: 192.168.0.1:5060
BYE sip:mayly@192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK0044b2449dd3d911bca1004f4e05e581
From: <sip:192.168.0.1>;tag=005595379dd3d911bca1004f4e05e581
To: <sip:mayly@ospranzn>;tag=1545502719
Call-ID: 187608728@192.168.0.1
CSeq: 21 BYE
Max-Forwards: 70
User-Agent: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0

-------------------------------------------
21:34:00,573: T: 192.168.0.1:5060
BYE sip:mayly@192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK0044b2449dd3d911bca1004f4e05e581
From: <sip:192.168.0.1>;tag=005595379dd3d911bca1004f4e05e581
To: <sip:mayly@ospranzn>;tag=1545502719
Call-ID: 187608728@192.168.0.1
CSeq: 21 BYE
Max-Forwards: 70
User-Agent: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0

-------------------------------------------
21:34:03,247: R: 192.168.0.1:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK0044b2449dd3d911bca1004f4e05e581
From: <sip:192.168.0.1>;tag=005595379dd3d911bca1004f4e05e581
To: <sip:mayly@ospranzn>;tag=1545502719
Call-ID: 187608728@192.168.0.1
CSeq: 21 BYE
Contact: <sip:192.168.0.1>
Max-Forwards: 70
Server: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0

-------------------------------------------
21:34:03,267: T: 192.168.0.1:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK0044b2449dd3d911bca1004f4e05e581
From: <sip:192.168.0.1>;tag=005595379dd3d911bca1004f4e05e581
To: <sip:mayly@ospranzn>;tag=1545502719
Call-ID: 187608728@192.168.0.1
CSeq: 21 BYE
Contact: <sip:192.168.0.1>
Max-Forwards: 70
Server: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0


diesmal wird in linphone die verbindung weiterhin als verbunden angezeigt, in phoner ist sie nicht mehr präsent. wenn ich jetzt mit linphone die verbindung trenne erhält phoner trotzdem noch sip-meldungen:

Code
Select All
-------------------------------------------
21:34:59,929: R: 192.168.0.225:5060
BYE sip:192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK701527427
From: <sip:mayly@ospranzn>;tag=1545502719
To: <sip:192.168.0.1>;tag=80185f399dd3d911bca1004f4e05e581
Call-ID: 187608728@192.168.0.1
CSeq: 21 BYE
max-forwards: 10
user-agent: oSIP/Linphone-0.12.1
Content-Length: 0

-------------------------------------------
21:34:59,959: T: 192.168.0.225:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK701527427;received=192.168.0.225
From: <sip:mayly@ospranzn>;tag=1545502719
To: <sip:192.168.0.1>;tag=80185f399dd3d911bca1004f4e05e581
Call-ID: 187608728@192.168.0.1
CSeq: 21 BYE
Contact: <sip:192.168.0.1>
Max-Forwards: 10
Server: SIPPER for phoner
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0


ich hoffe diese details können zur behebung dieser probleme helfen. ich kann leider nicht sagen, ob die fehler von linphone oder phoner ausgelöst werden.
  
Back to top
 
IP Logged
 
Phoner Admin
YaBB Administrator
*****
Offline



Posts: 11408
Location: Germany
Joined: 12. Oct 2003
Gender: Male
Re: SIP-Kommunikation mit linphone
Reply #4 - 05. Jun 2005 at 12:48
Print Post  
Die Media-Addresse, welche LinPhone mitliefert, stimmt nicht. Schau dir in den SDP-Nachrichten die Zeile "c=IN IP4 192.168.0.1" an. An diese IP-Adresse schickt Phoner dann seine RTP-Daten - jedoch kommen die so bei deinem Linux-Rechner niemals an. Können die RTP-Daten nicht zugestellt werden, beendet Phoner den Ruf mit eben dieser Meldung (Disconnect Indication: protocol error, layer 2).

Du solltest also mal schauen, ob man bei LinPhone (mit welchem ich mich gar nicht auskenne) eine andere IP-Adresse angeben kann.
  
Back to top
WWW  
IP Logged
 
Pythagoras1
YaBB Newbies
*
Offline


Phoner is great!

Posts: 5
Joined: 04. Jun 2005
Re: SIP-Kommunikation mit linphone
Reply #5 - 06. Jun 2005 at 15:01
Print Post  
danke für den hinweis, ich glaub jetzt weiß ich was nicht passt: ich hab den windows-rechner als nat angegeben, was eigentlich richtig ist, aber innerhalb des netzwerkes logischerweise nicht funktionieren kann:

ich werd das bei gelegenheit ausschalten und nochmals versuchen. das scheint wohl ein bug in linphone zu sein, schließlich müsste er die nat/pat-unterstützung deaktivieren, wenn die verbindung von innerhalb des netzwerkes stammt.
  
Back to top
 
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint
‹ Previous Topic | Next Topic ›
 
  « Board Index ‹ Board Top  

Phoner(Lite) Forum » Powered by YaBB 2.6.11!
YaBB Forum Software © 2000-2024. All Rights Reserved.

Valid RSS Valid XHTML Valid CSS Powered by Perl Source Forge