Verbindungsprobleme zwischen Fritzbox und 1722 (Gelöst)

rubinho · Beitrag von **rubinho** » 17 Feb 2006, 15:40

Hallo

Da ich mehrere Probleme in meinen ersten Tread reingeschrieben hab und ich so gut wie keinen Feedback bekommen habe, versuch ich es mal die Probleme zu splitten.

Meine Fritzbox lässt sich an und für sich ohne Probleme an der 1722 registrieren. Doch ein und ausgehende Gespäche sind nicht möglich.

Den Grund schein ich mittlerweile gefunden zu haben.
Und zwar scheint es so das bei dem Registrationsprozess die Ip-Adresse der FB nicht richtig an den 1722 übermittelt wird.

Hier den Registrationstrace der Fritzbox

Code: Alles auswählen

#
# voipd -R
Feb 17 12:38:10 voipd[409]: Signal: hangup
Feb 17 12:38:10 voipd[409]: sighup - NOT running (voip=0)
Feb 17 12:38:10 voipd[409]: 0: connected    vcc 0/0/RBE/14 stay online 1
Feb 17 12:38:10 voipd[409]: 13@home.local: REGISTER starting
Feb 17 12:38:10 voipd[409]: query_local_ipaddress - NOT running (voip=0)
Feb 17 12:38:10 voipd[409]: 0: connected    vcc 0/0/RBE/14 stay online 1
Feb 17 12:38:10 voipd[409]: query_local_ipaddress: 0.0.0.0
Feb 17 12:38:10 voipd[409]: >>>udp Request: REGISTER sip:home.local
Feb 17 12:38:10 voipd[409]: <<<udp Status: 401 Unauthorized
Feb 17 12:38:10 voipd[409]: query_local_ipaddress - NOT running (voip=0)
Feb 17 12:38:10 voipd[409]: 0: connected    vcc 0/0/RBE/14 stay online 1
Feb 17 12:38:10 voipd[409]: query_local_ipaddress: 0.0.0.0
Feb 17 12:38:10 voipd[409]: >>>udp Request: REGISTER sip:home.local
Feb 17 12:38:10 voipd[409]: <<<udp Status: 200 OK
Feb 17 12:38:10 voipd[409]: >>>udp Request: REGISTER sip:home.local
Feb 17 12:38:10 voipd[409]: <<<udp Status: 401 Unauthorized
Feb 17 12:38:10 voipd[409]: >>>udp Request: REGISTER sip:home.local
Feb 17 12:38:10 voipd[409]: <<<udp Status: 200 OK
Feb 17 12:38:10 voipd[409]: 13@home.local: REGISTER end
Feb 17 12:38:10 voipd[409]: 13@home.local: REGISTER (sip:13@255.255.255.255) complete (next in 1629 seconds)
Feb 17 12:38:10 voipd[409]: >>>udp Request: SUBSCRIBE sip:13@home.local
#
# Feb 17 12:38:11 voipd[409]: >>>udp Request: SUBSCRIBE sip:13@home.local
Feb 17 12:38:12 voipd[409]: >>>udp Request: SUBSCRIBE sip:13@home.local
Feb 17 12:38:14 voipd[409]: >>>udp Request: SUBSCRIBE sip:13@home.local
Feb 17 12:38:18 voipd[409]: >>>udp Request: SUBSCRIBE sip:13@home.local
Feb 17 12:38:22 voipd[409]: >>>udp Request: SUBSCRIBE sip:13@home.local
Feb 17 12:38:26 voipd[409]: >>>udp Request: SUBSCRIBE sip:13@home.local
Feb 17 12:38:30 voipd[409]: >>>udp Request: SUBSCRIBE sip:13@home.local
Feb 17 12:38:34 voipd[409]: >>>udp Request: SUBSCRIBE sip:13@home.local
Feb 17 12:38:38 voipd[409]: >>>udp Request: SUBSCRIBE sip:13@home.local
Feb 17 12:38:42 voipd[409]: >>>udp Request: SUBSCRIBE sip:13@home.local
Feb 17 12:38:42 voipd[409]: SUBSCRIBED: message-summary sip:13@home.local 5.0

#

Hier den Registrationstrace der 1722

Code: Alles auswählen

root@LC1722Voip:/
> trace # call sip
Callmanager     ON
SIP-Packet      ON

root@LC1722Voip:/
>
[SIP-Packet] 2006/02/17 12:44:42,380
Receiving Datagram with length 805 from 192.168.111.8:5060:
REGISTER sip:home.local SIP/2.0
Via: SIP/2.0/UDP 255.255.255.255:5060;branch=z9hG4bKAA61D11C86C42B9AD82FB5AD9512C
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=3168772918
To: <sip:13@home.local>
Call-ID: 2413B501329D942607FB2762C66C6@192.168.178.254
CSeq: 14 REGISTER
Authorization: Digest username="13", realm="home.local", nonce="36c9c4d7f6dc614b96d6b385a6d3dae2", uri="sip:home.local", response="dbd15627581489997ccb8c0fed631e97", algorithm=md5
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Supported: 100rel, replaces
Allow-Events: telephone-event, refer
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, PRACK, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:42,380
Sending Datagram with length 529 to 192.168.111.8:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 255.255.255.255:5060;received=192.168.111.8:5060;branch=z9hG4bKAA61D11C86C42B9AD82FB5AD9512C
From: <sip:13@home.local>;tag=3168772918
To: <sip:13@home.local>;tag=666012970-333006485
Call-ID: 2413B501329D942607FB2762C66C6@192.168.178.254
CSeq: 14 REGISTER
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: LC1722Voip
Allow: INVITE, ACK, CANCEL, BYE
WWW-Authenticate: Digest realm="home.local",nonce="d4ad8b3a6a56c59dd893e1ee6c49f0f7",opaque="",algorithm=md5
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:42,400
Receiving Datagram with length 805 from 192.168.111.8:5060:
REGISTER sip:home.local SIP/2.0
Via: SIP/2.0/UDP 255.255.255.255:5060;branch=z9hG4bK70C22CF5A64823F12E0F1520FC89A
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=3168772918
To: <sip:13@home.local>
Call-ID: 2413B501329D942607FB2762C66C6@192.168.178.254
CSeq: 15 REGISTER
Authorization: Digest username="13", realm="home.local", nonce="d4ad8b3a6a56c59dd893e1ee6c49f0f7", uri="sip:home.local", response="b38df2865f142518697ef9a90d722039", algorithm=md5
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Supported: 100rel, replaces
Allow-Events: telephone-event, refer
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, PRACK, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:42,410
Sending Datagram with length 457 to 192.168.111.8:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 255.255.255.255:5060;received=192.168.111.8:5060;branch=z9hG4bK70C22CF5A64823F12E0F1520FC89A
From: <sip:13@home.local>;tag=3168772918
To: <sip:13@home.local>;tag=666012970-333006485
Call-ID: 2413B501329D942607FB2762C66C6@192.168.178.254
CSeq: 15 REGISTER
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: LC1722Voip
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:13@255.255.255.255>;expires=1722
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:42,420
Receiving Datagram with length 890 from 192.168.111.8:5060:
REGISTER sip:home.local SIP/2.0
Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bKF779A177143D9D0A4AF89212CFAA4
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=3168772918
To: <sip:13@home.local>
Call-ID: 2413B501329D942607FB2762C66C6@192.168.178.254
CSeq: 16 REGISTER
Contact: <sip:13@255.255.255.255;uniq=A3C2EA0CF6E710DD02C173D041C0F>
Authorization: Digest username="13", realm="home.local", nonce="d4ad8b3a6a56c59dd893e1ee6c49f0f7", uri="sip:home.local", response="b38df2865f142518697ef9a90d722039", algorithm=md5
Expires: 1800
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Supported: 100rel, replaces
Allow-Events: telephone-event, refer
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, PRACK, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:42,420
Sending Datagram with length 545 to 192.168.111.8:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 255.255.255.255:5060;received=192.168.111.8:5060;branch=z9hG4bKF779A177143D9D0A4AF89212CFAA4
From: <sip:13@home.local>;tag=3168772918
To: <sip:13@home.local>;tag=401658911-3863013679
Call-ID: 2413B501329D942607FB2762C66C6@192.168.178.254
CSeq: 16 REGISTER
Expires: 1800
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: LC1722Voip
Allow: INVITE, ACK, CANCEL, BYE
WWW-Authenticate: Digest realm="home.local",nonce="bcc2ff5db3d9fc8e59ecfe47c14efc03",opaque="",algorithm=md5
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:42,440
Receiving Datagram with length 890 from 192.168.111.8:5060:
REGISTER sip:home.local SIP/2.0
Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK40D452020DC5A1012B6BE57BBDD24
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=3168772918
To: <sip:13@home.local>
Call-ID: 2413B501329D942607FB2762C66C6@192.168.178.254
CSeq: 17 REGISTER
Contact: <sip:13@255.255.255.255;uniq=A3C2EA0CF6E710DD02C173D041C0F>
Authorization: Digest username="13", realm="home.local", nonce="bcc2ff5db3d9fc8e59ecfe47c14efc03", uri="sip:home.local", response="17da0ac2870ebc4fece5e3c26db3861e", algorithm=md5
Expires: 1800
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Supported: 100rel, replaces
Allow-Events: telephone-event, refer
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, PRACK, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:42,440
Sending Datagram with length 473 to 192.168.111.8:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 255.255.255.255:5060;received=192.168.111.8:5060;branch=z9hG4bK40D452020DC5A1012B6BE57BBDD24
From: <sip:13@home.local>;tag=3168772918
To: <sip:13@home.local>;tag=401658911-3863013679
Call-ID: 2413B501329D942607FB2762C66C6@192.168.178.254
CSeq: 17 REGISTER
Expires: 1800
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: LC1722Voip
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:13@255.255.255.255>;expires=1810
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:42,460
Receiving Datagram with length 563 from 192.168.111.8:5060:
SUBSCRIBE sip:13@home.local SIP/2.0
Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK6891C33800E2E2C8EDA879F0042FA
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=2689145781
To: <sip:13@home.local>
Call-ID: 71DA205E4D6749B4030271412227D@255.255.255.255
CSeq: 18 SUBSCRIBE
Contact: <sip:13@255.255.255.255;uniq=A3C2EA0CF6E710DD02C173D041C0F>
Event: message-summary
Expires: 3600
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Allow: NOTIFY
Accept: application/simple-message-summary
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:42,970
Receiving Datagram with length 563 from 192.168.111.8:5060:
SUBSCRIBE sip:13@home.local SIP/2.0
Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK6891C33800E2E2C8EDA879F0042FA
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=2689145781
To: <sip:13@home.local>
Call-ID: 71DA205E4D6749B4030271412227D@255.255.255.255
CSeq: 18 SUBSCRIBE
Contact: <sip:13@255.255.255.255;uniq=A3C2EA0CF6E710DD02C173D041C0F>
Event: message-summary
Expires: 3600
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Allow: NOTIFY
Accept: application/simple-message-summary
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:43,980
Receiving Datagram with length 563 from 192.168.111.8:5060:
SUBSCRIBE sip:13@home.local SIP/2.0
Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK6891C33800E2E2C8EDA879F0042FA
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=2689145781
To: <sip:13@home.local>
Call-ID: 71DA205E4D6749B4030271412227D@255.255.255.255
CSeq: 18 SUBSCRIBE
Contact: <sip:13@255.255.255.255;uniq=A3C2EA0CF6E710DD02C173D041C0F>
Event: message-summary
Expires: 3600
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Allow: NOTIFY
Accept: application/simple-message-summary
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:45,990
Receiving Datagram with length 563 from 192.168.111.8:5060:
SUBSCRIBE sip:13@home.local SIP/2.0
Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK6891C33800E2E2C8EDA879F0042FA
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=2689145781
To: <sip:13@home.local>
Call-ID: 71DA205E4D6749B4030271412227D@255.255.255.255
CSeq: 18 SUBSCRIBE
Contact: <sip:13@255.255.255.255;uniq=A3C2EA0CF6E710DD02C173D041C0F>
Event: message-summary
Expires: 3600
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Allow: NOTIFY
Accept: application/simple-message-summary
Content-Length: 0


[SIP-Packet] 2006/02/17 12:44:48,510
Sending Datagram with length 421 to 212.227.15.197:5060:
REGISTER sip:sip-gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.165.24.116:36731;branch=z9hG4bK-59e56bee-2cf2b5f7
From: <sip:xxxxxxxxxxx@sip-gmx.net>;tag=3169102329-3016415196
To: <sip:xxxxxxxxxxxx@sip-gmx.net>
Call-ID: 2729989555@00:a0:57:11:a5:44
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:xxxxxxxxxxxx@84.165.24.116:36731>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:48,510
Sending Datagram with length 415 to 212.227.15.197:5060:
REGISTER sip:sip.gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.165.24.116:38631;branch=z9hG4bK-52ca5a63-c4ddae11
From: <sip:xxxxxxxxxx@sip.gmx.net>;tag=2421714893-2777986246
To: <sip:xxxxxxxxxxx@sip.gmx.net>
Call-ID: 4223785435@00:a0:57:11:a5:44
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:xxxxxxxxxxxx@84.165.24.116:38631>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:48,740
Receiving Datagram with length 451 from 212.227.15.197:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 84.165.24.116:36731;branch=z9hG4bK-59e56bee-2cf2b5f7
From: <sip:496825898349@sip-gmx.net>;tag=3169102329-3016415196
To: <sip:xxxxxxxxxxxxxx@sip-gmx.net>;tag=329cfeaa6ded039da25ff8cbb8668bd2.4f37
Call-ID: 2729989555@00:a0:57:11:a5:44
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sip-gmx.net", nonce="43f5b85c9a8a2e2eb88a9402ec58cf0a5aad2b38"
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:48,740
Sending Datagram with length 617 to 212.227.15.197:5060:
REGISTER sip:sip-gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.165.24.116:36731;branch=z9hG4bK-11faca85-e545e662
From: <sip:xxxxxxxxxxxxxx@sip-gmx.net>;tag=3169102329-3016415196
To: <sip:xxxxxxxxxxxxx@sip-gmx.net>
Call-ID: 2729989555@00:a0:57:11:a5:44
CSeq: 2 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:xxxxxxxxxxxxx@84.165.24.116:36731>
Expires: 240
User-Agent: LANCOM PBX
Authorization: Digest username="xxxxxxxxxxxxxxx",realm="sip-gmx.net",algorithm=MD5,uri="sip:sip-gmx.net",nonce="43f5b85c9a8a2e2eb88a9402ec58cf0a5aad2b38",response="60ea9882c806f89f691bd70ef63c6b0b"
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:48,850
Receiving Datagram with length 407 from 212.227.15.197:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 84.165.24.116:36731;branch=z9hG4bK-11faca85-e545e662
From: <sip:xxxxxxxxxxxxxx@sip-gmx.net>;tag=3169102329-3016415196
To: <sip:xxxxxxxxxxxxxxxx@sip-gmx.net>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-9751
Call-ID: 2729989555@00:a0:57:11:a5:44
CSeq: 2 REGISTER
Contact: <sip:xxxxxxxxxxxx@84.165.24.116:36731>;expires=3221
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:50,000
Receiving Datagram with length 563 from 192.168.111.8:5060:
SUBSCRIBE sip:13@home.local SIP/2.0
Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK6891C33800E2E2C8EDA879F0042FA
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=2689145781
To: <sip:13@home.local>
Call-ID: 71DA205E4D6749B4030271412227D@255.255.255.255
CSeq: 18 SUBSCRIBE
Contact: <sip:13@255.255.255.255;uniq=A3C2EA0CF6E710DD02C173D041C0F>
Event: message-summary
Expires: 3600
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Allow: NOTIFY
Accept: application/simple-message-summary
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:54,010
Receiving Datagram with length 563 from 192.168.111.8:5060:
SUBSCRIBE sip:13@home.local SIP/2.0
Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK6891C33800E2E2C8EDA879F0042FA
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=2689145781
To: <sip:13@home.local>
Call-ID: 71DA205E4D6749B4030271412227D@255.255.255.255
CSeq: 18 SUBSCRIBE
Contact: <sip:13@255.255.255.255;uniq=A3C2EA0CF6E710DD02C173D041C0F>
Event: message-summary
Expires: 3600
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Allow: NOTIFY
Accept: application/simple-message-summary
Content-Length: 0


[SIP-Packet] 2006/02/17 12:44:58,020
Receiving Datagram with length 563 from 192.168.111.8:5060:
SUBSCRIBE sip:13@home.local SIP/2.0
Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK6891C33800E2E2C8EDA879F0042FA
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=2689145781
To: <sip:13@home.local>
Call-ID: 71DA205E4D6749B4030271412227D@255.255.255.255
CSeq: 18 SUBSCRIBE
Contact: <sip:13@255.255.255.255;uniq=A3C2EA0CF6E710DD02C173D041C0F>
Event: message-summary
Expires: 3600
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Allow: NOTIFY
Accept: application/simple-message-summary
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:58,510
Sending Datagram with length 415 to 212.227.15.197:5060:
REGISTER sip:sip.gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.165.24.116:38631;branch=z9hG4bK-cfb04df5-8a60a5da
From: <sip:xxxxxxxxxxxx@sip.gmx.net>;tag=2284010326-1142005163
To: <sip:xxxxxxxxxxx@sip.gmx.net>
Call-ID: 3409408237@00:a0:57:11:a5:44
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:xxxxxxxxxxxx@84.165.24.116:38631>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:58,590
Receiving Datagram with length 447 from 212.227.15.197:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 84.165.24.116:38631;branch=z9hG4bK-cfb04df5-8a60a5da
From: <sip:xxxxxxxxxx@sip.gmx.net>;tag=2284010326-1142005163
To: <sip:xxxxxxxxxxxxxxx@sip.gmx.net>;tag=329cfeaa6ded039da25ff8cbb8668bd2.5219
Call-ID: 3409408237@00:a0:57:11:a5:44
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sip-gmx.net", nonce="43f5b865c4351269ce566a5595ee672159c4555d"
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:58,590
Sending Datagram with length 609 to 212.227.15.197:5060:
REGISTER sip:sip.gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.165.24.116:38631;branch=z9hG4bK-41406bfd-cd18b6de
From: <sip:xxxxxxxxxxxxx@sip.gmx.net>;tag=2284010326-1142005163
To: <sip:xxxxxxxxxxxxxxxxx@sip.gmx.net>
Call-ID: 3409408237@00:a0:57:11:a5:44
CSeq: 2 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:xxxxxxxxxxxxxxx@84.165.24.116:38631>
Expires: 240
User-Agent: LANCOM PBX
Authorization: Digest username="xxxxxxxxxxx",realm="sip-gmx.net",algorithm=MD5,uri="sip:sip.gmx.net",nonce="43f5b865c4351269ce566a5595ee672159c4555d",response="9984332f53b4c6a30bdfe1333af5fd33"
Content-Length: 0



[SIP-Packet] 2006/02/17 12:44:58,700
Receiving Datagram with length 401 from 212.227.15.197:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 84.165.24.116:38631;branch=z9hG4bK-41406bfd-cd18b6de
From: <sip:xxxxxxxxxx@sip.gmx.net>;tag=2284010326-1142005163
To: <sip:4xxxxxxxxxxxx@sip.gmx.net>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-90cb
Call-ID: 3409408237@00:a0:57:11:a5:44
CSeq: 2 REGISTER
Contact: <sip:4968252061@84.165.24.116:38631>;expires=3464
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0



[SIP-Packet] 2006/02/17 12:45:02,030
Receiving Datagram with length 563 from 192.168.111.8:5060:
SUBSCRIBE sip:13@home.local SIP/2.0
Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK6891C33800E2E2C8EDA879F0042FA
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=2689145781
To: <sip:13@home.local>
Call-ID: 71DA205E4D6749B4030271412227D@255.255.255.255
CSeq: 18 SUBSCRIBE
Contact: <sip:13@255.255.255.255;uniq=A3C2EA0CF6E710DD02C173D041C0F>
Event: message-summary
Expires: 3600
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Allow: NOTIFY
Accept: application/simple-message-summary
Content-Length: 0



[SIP-Packet] 2006/02/17 12:45:06,040
Receiving Datagram with length 563 from 192.168.111.8:5060:
SUBSCRIBE sip:13@home.local SIP/2.0
Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK6891C33800E2E2C8EDA879F0042FA
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=2689145781
To: <sip:13@home.local>
Call-ID: 71DA205E4D6749B4030271412227D@255.255.255.255
CSeq: 18 SUBSCRIBE
Contact: <sip:13@255.255.255.255;uniq=A3C2EA0CF6E710DD02C173D041C0F>
Event: message-summary
Expires: 3600
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Allow: NOTIFY
Accept: application/simple-message-summary
Content-Length: 0



[SIP-Packet] 2006/02/17 12:45:10,050
Receiving Datagram with length 563 from 192.168.111.8:5060:
SUBSCRIBE sip:13@home.local SIP/2.0
Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK6891C33800E2E2C8EDA879F0042FA
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=2689145781
To: <sip:13@home.local>
Call-ID: 71DA205E4D6749B4030271412227D@255.255.255.255
CSeq: 18 SUBSCRIBE
Contact: <sip:13@255.255.255.255;uniq=A3C2EA0CF6E710DD02C173D041C0F>
Event: message-summary
Expires: 3600
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Allow: NOTIFY
Accept: application/simple-message-summary
Content-Length: 0



[SIP-Packet] 2006/02/17 12:45:14,060
Receiving Datagram with length 563 from 192.168.111.8:5060:
SUBSCRIBE sip:13@home.local SIP/2.0
Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK6891C33800E2E2C8EDA879F0042FA
Route: <sip:192.168.0.1;lr>
From: <sip:13@home.local>;tag=2689145781
To: <sip:13@home.local>
Call-ID: 71DA205E4D6749B4030271412227D@255.255.255.255
CSeq: 18 SUBSCRIBE
Contact: <sip:13@255.255.255.255;uniq=A3C2EA0CF6E710DD02C173D041C0F>
Event: message-summary
Expires: 3600
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7050 14.04.01 (Jan 25 2006)
Allow: NOTIFY
Accept: application/simple-message-summary
Content-Length: 0

Wenn jetzt zB. ein Anruf von Extern kommt geht der natürlich dann ins leere

Siehe hier

Code: Alles auswählen


root@LC1722Voip:/
> trace # call sip
Callmanager     ON
SIP-Packet      ON

root@LC1722Voip:/
>
[SIP-Packet] 2006/02/17 13:07:03,150
Receiving Datagram with length 1347 from 212.227.15.197:5060:
INVITE sip:xyz@84.165.24.116:46458 SIP/2.0
Record-Route: <sip:212.227.15.225;ftag=2074493544;lr=on>
Via: SIP/2.0/UDP 212.227.15.197;branch=z9hG4bK66961aeb1db56896d690c6e9876582bc
Via: SIP/2.0/UDP 212.227.15.225;branch=z9hG4bKfac8.c8a42576.0
Via: SIP/2.0/UDP 212.227.15.197;branch=z9hG4bK8999ce33dd7fc6b4024c21ccaf869083
Via: SIP/2.0/UDP sipgw01.bmcag.com:5060 ;received=62.206.6.140;branch=z9hG4bKter
m-3590fa-491755814471-+496825898349
From: Handy <sip:Handy@sipgw01.bmcag.com;user=phone>;tag=207449354
4
To: xyz <sip:xyz@212.227.15.197;user=phone>
Call-ID: 8e3efe3-6a59bd57-22541334-4e81@sipgw01.bmcag.com
CSeq: 1 INVITE
Supported: timer
Session-Expires: 1800
Min-SE: 1800
Contact:  <sip:Handy@sipgw01.bmcag.com:5060>
Allow: INVITE,ACK,PRACK,SUBSCRIBE,BYE,CANCEL,NOTIFY,INFO,REFER,UPDATE
Max-Forwards: 14
Content-Type: application/sdp
Content-Length: 345
Diversion: <sip:xyz@sip2.schlund.de;user=phone>;reason=additional

v=0
o=- 3079023 0 IN IP4 62.206.64.18
s=Cisco SDP 0
c=IN IP4 62.206.64.18
t=0 0
m=audio 17012 RTP/AVP 8 0 2 99 18 110
a=rtpmap:99 G726-24/8000
a=rtpmap:110 X-NSE/8000
a=fmtp:110 192-194,200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 110
a=X-cpar: a=rtpmap:110 X-NSE/8000
a=X-cpar: a=fmtp:110 192-194,200-202
a=X-cap: 2 image udptl t38


[Callmanager] 2006/02/17 13:07:03,160
From: Handy@sipgw01.bmcag.com    Line: 'GMX2'
To  : 13@212.227.15.197 <Number is complete>
        Info: Parse call routing table for active entries
        Info: Search in the local user database
        Info: User '13@212.227.15.197' not found
        Info: Ignore domain
        Add ClnLine-Prefix: '0'
        Add ExtSIP-Prefix '*' to ClnNumber
==> From: *0491755814471@sipgw01.bmcag.com      Line: 'GMX2'
    To  : 13@home.local Line: 'USER.SIP'
InitiateCall:  13@home.local    Line: 'USER.SIP'

[SIP-Packet] 2006/02/17 13:07:03,160
Sending Datagram with length 858 to 0.0.0.0:5060:
INVITE sip:13@home.local SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-35512e35-f710143a
From: "Handy" <sip:*Handy@sipgw01.bmcag.com>;tag=3578050772-17890
25386
To: <sip:13@home.local>
Call-ID: 1912109033@00:a0:57:11:a5:44
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: LC1722Voip
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:*Handy@192.168.0.1:5060>
Content-Type: application/sdp
Content-Length: 392

v=0
o=- 3079023 0 IN IP4 62.206.64.18
s=Cisco SDP 0
c=IN IP4 62.206.64.18
t=0 0
m=audio 17012 RTP/AVP 8 0 2 104 18 255
a=X-sqn
a=X-cap
a=X-cpar
a=X-cpar
a=X-cap
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:104 G726-24/8000
a=rtpmap:18 G729/8000
a=rtpmap:255 X-NSE/8000
a=fmtp:255 192-194,200-202
a=X-sqn
a=X-cap
a=X-cpar
a=X-cpar
a=X-cap


[SIP-Packet] 2006/02/17 13:07:03,170
Sending Datagram with length 730 to 212.227.15.197:5060:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 212.227.15.197;received=212.227.15.197:5060;branch=z9hG4bK66961
aeb1db56896d690c6e9876582bc
Via: SIP/2.0/UDP 212.227.15.225;branch=z9hG4bKfac8.c8a42576.0
Via: SIP/2.0/UDP 212.227.15.197;branch=z9hG4bK8999ce33dd7fc6b4024c21ccaf869083
Via: SIP/2.0/UDP sipgw01.bmcag.com:5060;received=62.206.6.140;branch=z9hG4bKterm
-3590fa-Handy-xyz
From: "Hansdy" <sip:Handy@sipgw01.bmcag.com>;tag=2074493544
To: "Xyz" <sip:Xyz@sip-gmx.net>;tag=1917020052-958510026
Call-ID: 8e3efe3-6a59bd57-22541334-4e81@sipgw01.bmcag.com
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: LC1722Voip
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0



[SIP-Packet] 2006/02/17 13:07:03,510
Sending Datagram with length 420 to 212.227.15.197:5060:
REGISTER sip:sip-gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.165.24.116:46458;branch=z9hG4bK-fdcff450-7ee7fa28
From: <sip:xyz@sip-gmx.net>;tag=1105059266-552529633
To: <sip:xyz@sip-gmx.net>
Call-ID: 2210118532@00:a0:57:11:a5:44
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:xyz@84.165.24.116:46458>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 2006/02/17 13:07:03,590
Receiving Datagram with length 450 from 212.227.15.197:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 84.165.24.116:46458;branch=z9hG4bK-fdcff450-7ee7fa28
From: <sip:xyz@sip-gmx.net>;tag=1105059266-552529633
To: <sip:xyz@sip-gmx.net>;tag=329cfeaa6ded039da25ff8cbb8668bd2.03f9
Call-ID: 2210118532@00:a0:57:11:a5:44
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sip-gmx.net", nonce="43f5bd927c1117833d58ca6fbe5
878afaf5caeef"
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0



[SIP-Packet] 2006/02/17 13:07:03,590
Sending Datagram with length 616 to 212.227.15.197:5060:
REGISTER sip:sip-gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.165.24.116:46458;branch=z9hG4bK-752b7e41-d72d3c00
From: <sip:xyz@sip-gmx.net>;tag=1105059266-552529633
To: <sip:xyz@sip-gmx.net>
Call-ID: 2210118532@00:a0:57:11:a5:44
CSeq: 2 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:xyz@84.165.24.116:46458>
Expires: 240
User-Agent: LANCOM PBX
Authorization: Digest username="xyz",realm="sip-gmx.net",algorithm=MD5,
uri="sip:sip-gmx.net",nonce="43f5bd927c1117833d58ca6fbe5878afaf5caeef",response=
"7df174d0141f73546a8b804f6bad3b9e"
Content-Length: 0



[SIP-Packet] 2006/02/17 13:07:03,700
Receiving Datagram with length 406 from 212.227.15.197:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 84.165.24.116:46458;branch=z9hG4bK-752b7e41-d72d3c00
From: <sip:xyz@sip-gmx.net>;tag=1105059266-552529633
To: <sip:xyz@sip-gmx.net>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-8ae2
Call-ID: 2210118532@00:a0:57:11:a5:44
CSeq: 2 REGISTER
Contact: <sip:xyz@84.165.24.116:46458>;expires=3168
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0

trace # call sip
Callmanager     OFF
SIP-Packet      OFF

root@LC1722Voip:/

Ich hab sogar eine Anleitung von LAncom belommen wie man die Fritzbox erfolgreich mit der 1722 paart.
Aber es will einfach nicht.

Woran kann das mit der falschen IP liegen ?

Gruß
Rubinho

DirkK · Beitrag von **DirkK** » 17 Feb 2006, 16:02

rubinho hat geschrieben:Ich hab sogar eine Anleitung von LAncom belommen wie man die Fritzbox erfolgreich mit der 1722 paart.

Kannst Du die mal bitte posten, idealerweise als Link.

rubinho · Beitrag von **rubinho** » 17 Feb 2006, 16:22

Naja will mal nicht so sein

http://rapidshare.de/files/13474352/Fri ... _.pdf.html

Gruß
Rubinho

REPTILE · Beitrag von **REPTILE** » 20 Feb 2006, 15:35

hi,

hat das jetzt schon einer hinbekommen???
habe hier auch eine Fritzbox 5012 und die will auch nicht mit dem 1722, als IP steht immer 255.255.255.255 da???....

irgendwie funktioniert da garnix.... am 1722.... liegt seit 2 wochen hier rum und man kann nix mit anfangen.... grumel... ein glück hat der ja nur 9euro gekostet... grrrr

Beitrag von **LoUiS** » 20 Feb 2006, 15:44

Hi,

ich habe hier eine Fritz!Box Fon am LANCOM im Einsatz. Funktioniert einwandfrei als ATA. Vieleicht solltetst Du mal anstatt der Domaene die LAN IP des 1722 konfigurieren, aus dem Trace geht ja hervor, das die Domaene nicht aufgeloest werden kann.

REGISTER sip:home.local SIP/2.0
Via: SIP/2.0/UDP 255.255.255.255:5060;branch=z9hG4bKAA61D11C86C42B9AD82FB5AD9512C

Ciao
LoUiS

rubinho · Beitrag von **rubinho** » 20 Feb 2006, 15:53

REPTILE hat geschrieben: irgendwie funktioniert da garnix.... am 1722.... liegt seit 2 wochen hier rum und man kann nix mit anfangen.... grumel... ein glück hat der ja nur 9euro gekostet... grrrr

Wenigstens habe ich einen Leidensgenosse.

Ich dachte schon ich wär der Einzigste bei dem die Voip-Funktion überhaupt nicht zu nutzen ist.

Aber das mit den 9€ war doch ironisch gemeint oder ?

Gruß
Rubinho

REPTILE · Beitrag von **REPTILE** » 20 Feb 2006, 15:59

geht irgendwie trotzdem net..

hier mal screenshots von der config und ein trace, der da oben war ja nicht von mir....

bald knüppel ich die teile aufm müll... über sip raus zu telefoniern geht ja auch noch net... grumel.....

Code: Alles auswählen

[SIP-Packet] 2006/02/20 15:57:12,490
Receiving Datagram with length 627 from 192.168.1.51:5060:
REGISTER sip:192.168.1.50 SIP/2.0

Via: SIP/2.0/udp 192.168.1.51:5060;branch=z9hG4bK671B3BC7E8F73416BE69154564349

Route: <sip:192.168.1.50;lr>

From: <sip:9290@192.168.1.50>;tag=339661205

To: <sip:9290@192.168.1.50>

Call-ID: 52FD6FA29E0F85CDB3F55768F4E14@192.168.1.51

CSeq: 1 REGISTER

Max-Forwards: 70

User-Agent: AVM FRITZ!Box Fon 5012 (UI) 25.04.01 (Jan 25 2006)

Supported: 100rel, replaces

Allow-Events: telephone-event, refer

Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, PRACK, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE

Accept: application/sdp, multipart/mixed

Accept-Encoding: identity

Content-Length: 0





[SIP-Packet] 2006/02/20 15:57:12,490
Sending Datagram with length 527 to 192.168.1.51:5060:
SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 192.168.1.51:5060;received=192.168.1.51:5060;branch=z9hG4bK671B3BC7E8F73416BE69154564349

From: <sip:9290@192.168.1.50>;tag=339661205

To: <sip:9290@192.168.1.50>;tag=4286030198-2143015099

Call-ID: 52FD6FA29E0F85CDB3F55768F4E14@192.168.1.51

CSeq: 1 REGISTER

Max-Forwards: 70

User-Agent: LANCOM PBX

Server: jack_uplink_de

Allow: INVITE, ACK, CANCEL, BYE

WWW-Authenticate: Digest realm="FPS",nonce="42451b4fcc9a0e878bf58463a8424111",opaque="",algorithm=md5

Content-Length: 0





[SIP-Packet] 2006/02/20 15:57:12,520
Receiving Datagram with length 808 from 192.168.1.51:5060:
REGISTER sip:192.168.1.50 SIP/2.0

Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK6129EDB21E40314B634E7EDDCF70B

Route: <sip:192.168.1.50;lr>

From: <sip:9290@192.168.1.50>;tag=339661205

To: <sip:9290@192.168.1.50>

Call-ID: 52FD6FA29E0F85CDB3F55768F4E14@192.168.1.51

CSeq: 2 REGISTER

Authorization: Digest username="9290", realm="FPS", nonce="42451b4fcc9a0e878bf58463a8424111", uri="sip:192.168.1.50", response="714c24079f294bfade150a60b79703fa", algorithm=md5

Max-Forwards: 70

User-Agent: AVM FRITZ!Box Fon 5012 (UI) 25.04.01 (Jan 25 2006)

Supported: 100rel, replaces

Allow-Events: telephone-event, refer

Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, PRACK, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE

Accept: application/sdp, multipart/mixed

Accept-Encoding: identity

Content-Length: 0





[SIP-Packet] 2006/02/20 15:57:12,520
Sending Datagram with length 467 to 192.168.1.51:5060:
SIP/2.0 200 OK

Via: SIP/2.0/UDP 255.255.255.255:5060;received=192.168.1.51:5060;branch=z9hG4bK6129EDB21E40314B634E7EDDCF70B

From: <sip:9290@192.168.1.50>;tag=339661205

To: <sip:9290@192.168.1.50>;tag=4286030198-2143015099

Call-ID: 52FD6FA29E0F85CDB3F55768F4E14@192.168.1.51

CSeq: 2 REGISTER

Max-Forwards: 70

User-Agent: LANCOM PBX

Server: jack_uplink_de

Allow: INVITE, ACK, CANCEL, BYE

Contact: <sip:9290@255.255.255.255>;expires=1709

Content-Length: 0





[SIP-Packet] 2006/02/20 15:57:12,540
Receiving Datagram with length 895 from 192.168.1.51:5060:
REGISTER sip:192.168.1.50 SIP/2.0

Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK16E3F605EB9C0D3E7826DEE88E11A

Route: <sip:192.168.1.50;lr>

From: <sip:9290@192.168.1.50>;tag=339661205

To: <sip:9290@192.168.1.50>

Call-ID: 52FD6FA29E0F85CDB3F55768F4E14@192.168.1.51

CSeq: 3 REGISTER

Contact: <sip:9290@255.255.255.255;uniq=023999DAF926CE76E84B88969A9E5>

Authorization: Digest username="9290", realm="FPS", nonce="42451b4fcc9a0e878bf58463a8424111", uri="sip:192.168.1.50", response="714c24079f294bfade150a60b79703fa", algorithm=md5

Expires: 1800

Max-Forwards: 70

User-Agent: AVM FRITZ!Box Fon 5012 (UI) 25.04.01 (Jan 25 2006)

Supported: 100rel, replaces

Allow-Events: telephone-event, refer

Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, PRACK, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE

Accept: application/sdp, multipart/mixed

Accept-Encoding: identity

Content-Length: 0





[SIP-Packet] 2006/02/20 15:57:12,540
Sending Datagram with length 545 to 192.168.1.51:5060:
SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 255.255.255.255:5060;received=192.168.1.51:5060;branch=z9hG4bK16E3F605EB9C0D3E7826DEE88E11A

From: <sip:9290@192.168.1.50>;tag=339661205

To: <sip:9290@192.168.1.50>;tag=3635720825-2179127836

Call-ID: 52FD6FA29E0F85CDB3F55768F4E14@192.168.1.51

CSeq: 3 REGISTER

Expires: 1800

Max-Forwards: 70

User-Agent: LANCOM PBX

Server: jack_uplink_de

Allow: INVITE, ACK, CANCEL, BYE

WWW-Authenticate: Digest realm="FPS",nonce="fd84d863937aef11a405f4a85202fa54",opaque="",algorithm=md5

Content-Length: 0






[SIP-Packet] 2006/02/20 15:57:12,560
Receiving Datagram with length 895 from 192.168.1.51:5060:
REGISTER sip:192.168.1.50 SIP/2.0

Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bKC6CCBCB04644F096A7C822E6E357F

Route: <sip:192.168.1.50;lr>

From: <sip:9290@192.168.1.50>;tag=339661205

To: <sip:9290@192.168.1.50>

Call-ID: 52FD6FA29E0F85CDB3F55768F4E14@192.168.1.51

CSeq: 4 REGISTER

Contact: <sip:9290@255.255.255.255;uniq=023999DAF926CE76E84B88969A9E5>

Authorization: Digest username="9290", realm="FPS", nonce="fd84d863937aef11a405f4a85202fa54", uri="sip:192.168.1.50", response="b9f30c68bf561c460e2c80e91aed199b", algorithm=md5

Expires: 1800

Max-Forwards: 70

User-Agent: AVM FRITZ!Box Fon 5012 (UI) 25.04.01 (Jan 25 2006)

Supported: 100rel, replaces

Allow-Events: telephone-event, refer

Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, PRACK, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE

Accept: application/sdp, multipart/mixed

Accept-Encoding: identity

Content-Length: 0





[SIP-Packet] 2006/02/20 15:57:12,560
Sending Datagram with length 482 to 192.168.1.51:5060:
SIP/2.0 200 OK

Via: SIP/2.0/UDP 255.255.255.255:5060;received=192.168.1.51:5060;branch=z9hG4bKC6CCBCB04644F096A7C822E6E357F

From: <sip:9290@192.168.1.50>;tag=339661205

To: <sip:9290@192.168.1.50>;tag=3635720825-2179127836

Call-ID: 52FD6FA29E0F85CDB3F55768F4E14@192.168.1.51

CSeq: 4 REGISTER

Expires: 1800

Max-Forwards: 70

User-Agent: LANCOM PBX

Server: jack_uplink_de

Allow: INVITE, ACK, CANCEL, BYE

Contact: <sip:9290@255.255.255.255>;expires=1810

Content-Length: 0





[SIP-Packet] 2006/02/20 15:57:12,580
Receiving Datagram with length 577 from 192.168.1.51:5060:
SUBSCRIBE sip:9290@192.168.1.50 SIP/2.0

Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK64EB9D12EE8E0AAA7F6C0797F08AE

Route: <sip:192.168.1.50;lr>

From: <sip:9290@192.168.1.50>;tag=3704454168

To: <sip:9290@192.168.1.50>

Call-ID: C036D2DF54FF1DB58E04B68A7EF1E@255.255.255.255

CSeq: 5 SUBSCRIBE

Contact: <sip:9290@255.255.255.255;uniq=023999DAF926CE76E84B88969A9E5>

Event: message-summary

Expires: 3600

Max-Forwards: 70

User-Agent: AVM FRITZ!Box Fon 5012 (UI) 25.04.01 (Jan 25 2006)

Allow: NOTIFY

Accept: application/simple-message-summary

Content-Length: 0





[SIP-Packet] 2006/02/20 15:57:13,080
Receiving Datagram with length 577 from 192.168.1.51:5060:
SUBSCRIBE sip:9290@192.168.1.50 SIP/2.0

Via: SIP/2.0/udp 255.255.255.255:5060;branch=z9hG4bK64EB9D12EE8E0AAA7F6C0797F08AE

Route: <sip:192.168.1.50;lr>

From: <sip:9290@192.168.1.50>;tag=3704454168

To: <sip:9290@192.168.1.50>

Call-ID: C036D2DF54FF1DB58E04B68A7EF1E@255.255.255.255

CSeq: 5 SUBSCRIBE

Contact: <sip:9290@255.255.255.255;uniq=023999DAF926CE76E84B88969A9E5>

Event: message-summary

Expires: 3600

Max-Forwards: 70

User-Agent: AVM FRITZ!Box Fon 5012 (UI) 25.04.01 (Jan 25 2006)

Allow: NOTIFY

Accept: application/simple-message-summary

Content-Length: 0

rubinho · Beitrag von **rubinho** » 20 Feb 2006, 16:09

@REPTILE

Du solltest an der Fritzbox als DNS-Server die IP des 1722 angeben (192.168.1.50)

Den Stun-Server kannst Du auch rausnehmen.

Gruß
Rubinho

REPTILE · Beitrag von **REPTILE** » 20 Feb 2006, 16:16

mhh ok habe ich gemacht... (PS: der lancom ist aber kein DNS server)

aber hat sich nix geändert im verhalten... steht immer noch 255........

rubinho · Beitrag von **rubinho** » 20 Feb 2006, 16:17

LoUiS hat geschrieben:Hi,

ich habe hier eine Fritz!Box Fon am LANCOM im Einsatz. Funktioniert einwandfrei als ATA. Vieleicht solltetst Du mal anstatt der Domaene die LAN IP des 1722 konfigurieren, aus dem Trace geht ja hervor, das die Domaene nicht aufgeloest werden kann.

REGISTER sip:home.local SIP/2.0
Via: SIP/2.0/UDP 255.255.255.255:5060;branch=z9hG4bKAA61D11C86C42B9AD82FB5AD9512C

Ciao
LoUiS

Ich hab glaub ich jetzt schon alle Variationen an der Fritzbox ausprobiert (So viele gibt es ja nicht)

Aber der 1722 weiss nicht zu welcher IP er den Anruf leiten soll.

Welche Firmware hast Du au Deiner Fritzbox? Vielleicht liegt es daran ?

Gruß
Rubinho

MoinMoin · Beitrag von **MoinMoin** » 20 Feb 2006, 16:24

Moin, moin!

Irgendwie scheint das Teil probleme mit seiner eigenen IP-Addresse zu haben. Interessanterweise war sie im ersten Paket noch richtig. Kann es sein, daß das ein Problem mit dem STUN ist? Da das LANCOM (bisher) keinen STUN-Server enthält, wird eine STUN-Anfrage auch nicht beantwortet werden. Möglicherweise setzt die AVM-Box dann die 255.255.255.255 als maskierte Adresse ein.

Ciao, Georg

MoinMoin · Beitrag von **MoinMoin** » 20 Feb 2006, 16:31

Moin, moin!

REPTILE hat geschrieben:(PS: der lancom ist aber kein DNS server)

Aber das LANCOM ist derjenige, der die SRV-Anfragen für die VoIP-Domänen auflösen kann. Für die konfigurierten SIP-Domänen erzeugt das LANCOM automatisch passende DNS-Einträge. Ist durchaus empfehlenswert, den DNS-Server dafür mit dem SIP-Proxy zusammenzulegen. LANCOM kann ja auch noch passend weiterleiten, wenn du noch einen richtigen DNS-Server betreibst.

Ciao, Georg

REPTILE · Beitrag von **REPTILE** » 20 Feb 2006, 16:32

najo klar, habs auch jetzt mal eingetragen, was aber nichts gebracht hat...

rubinho · Beitrag von **rubinho** » 20 Feb 2006, 16:33

REPTILE hat geschrieben:(PS: der lancom ist aber kein DNS server)

Mmmh, das ist mir aber jetzt neu. Sogar mein alter DSL-I/10 hatte schon einen mini DNS-Server)

@MoinMoin
Das hatte ich auch gedacht das es was mit Stun oder Nat zutun hat, aber ich habe weder einen Stun-Server aktiviert noch habe ich in der Voip.cfg den Parameter is_Nat_aware enabled.

Ausserdem hab ich die Fritzbox schon erfolgreich an meinem lokalen Asterisk-Server gekoppelt und sogar an der Soft-PBX Sippstar von Ahead.

Gruß
Rubinho

REPTILE · Beitrag von **REPTILE** » 20 Feb 2006, 17:48

naja net ganz... ISDN zu ISDN klappt ja... naja ok hat dann zwar auch weniger mit VoIP zu tun, aber wenigstens gehts durch den 1722.... da ist aber auch das einzige was geht.....

aber schonmal gut das noch einer die probleme hat, dachte schon bin zu blöd dazu *gg* oder das gerät hat nen schuss....

rubinho hat geschrieben: Wenigstens habe ich einen Leidensgenosse.

Ich dachte schon ich wär der Einzigste bei dem die Voip-Funktion überhaupt nicht zu nutzen ist.

Aber das mit den 9€ war doch ironisch gemeint oder ?

Gruß
Rubinho

LANCOM-Forum.de

Verbindungsprobleme zwischen Fritzbox und 1722 (Gelöst)

Verbindungsprobleme zwischen Fritzbox und 1722 (Gelöst)

Re: Verbindungsprobleme zwischen Fritzbox und 1722