All-IP/VoIP: SIP-Methode UPDATE not allowed?! (10.12)

Forum zu LANCOM Systems VoIP Router/Gateways und zur LANCOM VoIP Option

Moderator: Lancom-Systems Moderatoren

Antworten
Benutzeravatar
Jirka
Beiträge: 5225
Registriert: 03 Jan 2005, 13:39
Wohnort: Ex-OPAL-Gebiet
Kontaktdaten:

All-IP/VoIP: SIP-Methode UPDATE not allowed?! (10.12)

Beitrag von Jirka »

Hallo zusammen,

Cpuprofi hat ein neues Gigaset Maxwell 3 PRO und hat damit bei etwas längeren Telefonaten immer Gesprächsabbrüche - genaugenommen nach 30 Min. Wir hatten jetzt davon mal ein Trace gemacht und und diesen kurz analysiert. Demnach scheint der LANCOM-Router ein Problem mit der SIP-Methode UPDATE zu haben. Siehe nachfolgender Trace:

Firmware ist 10.12-RU6

Das Telefonat beginnt ganz normal:

Code: Alles auswählen

[SIP-Packet] 2018/04/09 19:49:12,429 [Packet]:
Receiving datagram (984 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
INVITE sip:03022222222@192.168.3.1 SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjc3e2ff0f-d28c-47f0-99d2-46da973c25d0\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1\r\n
Contact: <sip:21@192.168.3.39:5060>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12053 INVITE\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, OPTIONS, PRACK, REFER, MESSAGE\r\n
Supported: 100rel, replaces, timer, eventlist\r\n
Session-Expires: 3600\r\n
Min-SE: 90\r\n
User-Agent: Maxwell 3 PRO/82.2.22.7-release;7C2F80DE5644\r\n
Content-Type: application/sdp\r\n
Content-Length:   310\r\n
\r\n
v=0\r\n
o=- 3732284953 3732284953 IN IP4 192.168.3.39\r\n
s=Maxwell 3 PRO/82.2.22.7-release;7C2F80DE5644\r\n
t=0 0\r\n
m=audio 8000 RTP/AVP 9 8 0 101\r\n
c=IN IP4 192.168.3.39\r\n
b=TIAS:64000\r\n
a=sendrecv\r\n
a=rtpmap:9 G722/8000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-16\r\n

[SIP-Packet] 2018/04/09 19:49:12,437 [Packet]:
Sending datagram (522 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;branch=z9hG4bKPjc3e2ff0f-d28c-47f0-99d2-46da973c25d0;received=192.168.3.39;rport=5060\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12053 INVITE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 19:49:12,438 [Packet]:
Sending datagram (686 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 407 Proxy Authentication Required\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;branch=z9hG4bKPjc3e2ff0f-d28c-47f0-99d2-46da973c25d0;received=192.168.3.39;rport=5060\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12053 INVITE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Proxy-Authenticate: Digest realm="192.168.3.1",nonce="c7e6c0958e4be36a4725f1b5ce2a7bfa",opaque="",algorithm=MD5\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 19:49:12,444 [Packet]:
Receiving datagram (383 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
ACK sip:03022222222@192.168.3.1 SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjc3e2ff0f-d28c-47f0-99d2-46da973c25d0\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12053 ACK\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 19:49:12,449 [Packet]:
Receiving datagram (1189 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
INVITE sip:03022222222@192.168.3.1 SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjff88f49c-5c2d-40be-8fef-f23c4a05df36\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1\r\n
Contact: <sip:21@192.168.3.39:5060>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 INVITE\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, OPTIONS, PRACK, REFER, MESSAGE\r\n
Supported: 100rel, replaces, timer, eventlist\r\n
Session-Expires: 3600\r\n
Min-SE: 90\r\n
User-Agent: Maxwell 3 PRO/82.2.22.7-release;7C2F80DE5644\r\n
Proxy-Authorization: Digest username="21", realm="192.168.3.1", nonce="c7e6c0958e4be36a4725f1b5ce2a7bfa", uri="sip:03022222222@192.168.3.1", response="9b5296a4293c6c0d0894b21a5ebbd1e8", algorithm=MD5\r\n
Content-Type: application/sdp\r\n
Content-Length:   310\r\n
\r\n
v=0\r\n
o=- 3732284953 3732284953 IN IP4 192.168.3.39\r\n
s=Maxwell 3 PRO/82.2.22.7-release;7C2F80DE5644\r\n
t=0 0\r\n
m=audio 8000 RTP/AVP 9 8 0 101\r\n
c=IN IP4 192.168.3.39\r\n
b=TIAS:64000\r\n
a=sendrecv\r\n
a=rtpmap:9 G722/8000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-16\r\n

[SIP-Packet] 2018/04/09 19:49:12,450 [Packet]:
Sending datagram (522 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;branch=z9hG4bKPjff88f49c-5c2d-40be-8fef-f23c4a05df36;received=192.168.3.39;rport=5060\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 INVITE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 19:49:13,218 [Packet]:
Sending datagram (1213 Bytes) from [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335 to [2001:ab7::1]:5060 using UDP (RtgTag 0):
INVITE sip:03022222222@sipgate.de SIP/2.0\r\n
Via: SIP/2.0/UDP [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335;branch=z9hG4bK-378a1947-afd36f06;rport\r\n
From: "03088888888"<sip:2666666@sipgate.de;user=phone>;tag=1055621788-1659582999\r\n
To: <sip:03022222222@sipgate.de>\r\n
Call-ID: 3727826398@00a0571ba94a\r\n
CSeq: 100 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER\r\n
Supported: 100rel\r\n
Contact: <sip:2666666@[2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335;transport=UDP>\r\n
P-Preferred-Identity: <sip:2666666@sipgate.de;user=phone>\r\n
Proxy-Authorization: Digest username="2666666", realm="sipgate.de", algorithm=MD5, uri="sip:03022222222@sipgate.de", nonce="WsuoElrLpua8XUJL92h0s7tG1yhMK4R8", response="d612153bc9dd6eb6aab6f122ca99b630"\r\n
Content-Type: application/sdp\r\n
Content-Length: 321\r\n
\r\n
v=0\r\n
o=- 1863913199 1863913199 IN IP6 2003:c1:7ff:b2b:a0:57ff:fe1b:a94a\r\n
s=call\r\n
c=IN IP6 2003:c1:7ff:b2b:a0:57ff:fe1b:a94a\r\n
t=0 0\r\n
m=audio 65294 RTP/AVP 9 8 0 101\r\n
b=TIAS:64000\r\n
a=rtpmap:9 G722/8000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n
a=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2018/04/09 19:49:13,261 [Packet]:
Receiving datagram (389 Bytes) at [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335 from [2001:ab7::1]:5060 using UDP (RtgTag 0):
SIP/2.0 100 trying -- your call is important to us\r\n
Via: SIP/2.0/UDP [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335;received=2003:c1:7ff:b2b:a0:57ff:fe1b:a94a;branch=z9hG4bK-378a1947-afd36f06;rport=65335\r\n
From: "03088888888"<sip:2666666@sipgate.de;user=phone>;tag=1055621788-1659582999\r\n
To: <sip:03022222222@sipgate.de>\r\n
Call-ID: 3727826398@00a0571ba94a\r\n
CSeq: 100 INVITE\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 19:49:14,700 [Packet]:
Receiving datagram (718 Bytes) at [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335 from [2001:ab7::1]:5060 using UDP (RtgTag 0):
SIP/2.0 180 Ringing\r\n
Via: SIP/2.0/UDP [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335;received=2003:c1:7ff:b2b:a0:57ff:fe1b:a94a;branch=z9hG4bK-378a1947-afd36f06;rport=65335\r\n
Record-Route: <sip:172.20.40.6;lr>\r\n
Record-Route: <sip:217.116.119.66;r2=on;lr;ftag=1055621788-1659582999>\r\n
Record-Route: <sip:[2001:AB7:0:0:0:0:0:1];r2=on;lr;ftag=1055621788-1659582999>\r\n
From: "03088888888"<sip:2666666@sipgate.de;user=phone>;tag=1055621788-1659582999\r\n
To: <sip:03022222222@sipgate.de>;tag=as3d2884b8\r\n
Call-ID: 3727826398@00a0571ba94a\r\n
CSeq: 100 INVITE\r\n
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE\r\n
Supported: replaces\r\n
Contact: <sip:6318338p0@212.9.44.137:5060>\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 19:49:14,707 [Packet]:
Sending datagram (549 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 180 Ringing\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;branch=z9hG4bKPjff88f49c-5c2d-40be-8fef-f23c4a05df36;received=192.168.3.39;rport=5060\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 INVITE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 19:49:16,604 [Packet]:
Receiving datagram (1018 Bytes) at [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335 from [2001:ab7::1]:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335;received=2003:c1:7ff:b2b:a0:57ff:fe1b:a94a;branch=z9hG4bK-378a1947-afd36f06;rport=65335\r\n
Record-Route: <sip:172.20.40.6;lr>\r\n
Record-Route: <sip:217.116.119.66;r2=on;lr;ftag=1055621788-1659582999>\r\n
Record-Route: <sip:[2001:AB7:0:0:0:0:0:1];r2=on;lr;ftag=1055621788-1659582999>\r\n
From: "03088888888"<sip:2666666@sipgate.de;user=phone>;tag=1055621788-1659582999\r\n
To: <sip:03022222222@sipgate.de>;tag=as3d2884b8\r\n
Call-ID: 3727826398@00a0571ba94a\r\n
CSeq: 100 INVITE\r\n
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE\r\n
Supported: replaces\r\n
Contact: <sip:6318338p0@212.9.44.137:5060>\r\n
Content-Type: application/sdp\r\n
Content-Length: 272\r\n
\r\n
v=0\r\n
o=root 748674360 748674360 IN IP4 212.9.44.137\r\n
s=sipgate VoIP GW\r\n
c=IN IP6 2001:ab7:2000::12\r\n
t=0 0\r\n
m=audio 28380 RTP/AVP 8 0 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-16\r\n
a=ptime:20\r\n
a=sendrecv\r\n
a=rtcp:28381\r\n

[SIP-Packet] 2018/04/09 19:49:16,615 [Packet]:
Sending datagram (854 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;branch=z9hG4bKPjff88f49c-5c2d-40be-8fef-f23c4a05df36;received=192.168.3.39;rport=5060\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 INVITE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Contact: <sip:21@192.168.3.1:5060;transport=UDP>\r\n
Content-Type: application/sdp\r\n
Content-Length: 225\r\n
\r\n
v=0\r\n
o=- 0 0 IN IP4 192.168.3.1\r\n
s=call\r\n
c=IN IP4 192.168.3.1\r\n
t=0 0\r\n
m=audio 12670 RTP/AVP 8 0 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n
a=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2018/04/09 19:49:16,645 [Packet]:
Receiving datagram (393 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
ACK sip:21@192.168.3.1:5060;transport=UDP SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPj699fe926-dc70-4b56-afbb-bd4442146e7a\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 ACK\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 19:49:16,654 [Packet]:
Sending datagram (882 Bytes) from [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335 to [2001:ab7::1]:5060 using UDP (RtgTag 0):
ACK sip:6318338p0@212.9.44.137:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335;branch=z9hG4bK-343816bd-de5a0b7d;rport\r\n
Route: <sip:[2001:AB7:0:0:0:0:0:1];r2=on;lr;ftag=1055621788-1659582999>\r\n
Route: <sip:217.116.119.66;r2=on;lr;ftag=1055621788-1659582999>\r\n
Route: <sip:172.20.40.6;lr>\r\n
From: "03088888888"<sip:2666666@sipgate.de;user=phone>;tag=1055621788-1659582999\r\n
To: <sip:03022222222@sipgate.de>;tag=as3d2884b8\r\n
Call-ID: 3727826398@00a0571ba94a\r\n
CSeq: 100 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER\r\n
Proxy-Authorization: Digest username="2666666", realm="sipgate.de", algorithm=MD5, uri="sip:03022222222@sipgate.de", nonce="WsuoElrLpua8XUJL92h0s7tG1yhMK4R8", response="d612153bc9dd6eb6aab6f122ca99b630"\r\n
Content-Length: 0\r\n
\r\n
Bis hierhin ist alles gut. Jetzt kommt vom Gigaset ein UPDATE-Paket, was der LANCOM mit Method not allowed beantwortet:

Code: Alles auswählen

[SIP-Packet] 2018/04/09 20:19:16,741 [Packet]:
Receiving datagram (534 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
UPDATE sip:21@192.168.3.1:5060;transport=UDP SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjda77c023-cd80-4b33-9e18-21ca38ca37d5\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Contact: <sip:21@192.168.3.39:5060>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12055 UPDATE\r\n
Supported: 100rel, replaces, timer, eventlist\r\n
Session-Expires: 3600;refresher=uac\r\n
Min-SE: 90\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:16,741 [Packet]:
Sending datagram (434 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 405 Method Not Allowed\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 UPDATE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Content-Length: 0\r\n
\r\n
Frage 1: Warum weist der LANCOM das Paket mit "405 Method Not Allowed" ab? (Er schreibt sogar im selben Paket unten "Allow: ... UPDATE, ...".)
Frage 2: Warum beantwortet der LANCOM das Paket mit "CSeq: 12054 UPDATE"? Müsste da nicht die 12055 hin?

Das Gigaset versucht jetzt noch sehr ausgiebig den LANCOM zu einem UPDATE zu bewegen, aber erfolglos, womit dann das Telefongespräch beendet wird.

Code: Alles auswählen

[SIP-Packet] 2018/04/09 20:19:17,242 [Packet]:
Receiving datagram (534 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
UPDATE sip:21@192.168.3.1:5060;transport=UDP SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjda77c023-cd80-4b33-9e18-21ca38ca37d5\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Contact: <sip:21@192.168.3.39:5060>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12055 UPDATE\r\n
Supported: 100rel, replaces, timer, eventlist\r\n
Session-Expires: 3600;refresher=uac\r\n
Min-SE: 90\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:17,243 [Packet]:
Sending datagram (434 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 405 Method Not Allowed\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 UPDATE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:18,242 [Packet]:
Receiving datagram (534 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
UPDATE sip:21@192.168.3.1:5060;transport=UDP SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjda77c023-cd80-4b33-9e18-21ca38ca37d5\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Contact: <sip:21@192.168.3.39:5060>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12055 UPDATE\r\n
Supported: 100rel, replaces, timer, eventlist\r\n
Session-Expires: 3600;refresher=uac\r\n
Min-SE: 90\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:18,243 [Packet]:
Sending datagram (434 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 405 Method Not Allowed\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 UPDATE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:20,243 [Packet]:
Receiving datagram (534 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
UPDATE sip:21@192.168.3.1:5060;transport=UDP SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjda77c023-cd80-4b33-9e18-21ca38ca37d5\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Contact: <sip:21@192.168.3.39:5060>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12055 UPDATE\r\n
Supported: 100rel, replaces, timer, eventlist\r\n
Session-Expires: 3600;refresher=uac\r\n
Min-SE: 90\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:20,244 [Packet]:
Sending datagram (434 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 405 Method Not Allowed\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 UPDATE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:24,244 [Packet]:
Receiving datagram (534 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
UPDATE sip:21@192.168.3.1:5060;transport=UDP SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjda77c023-cd80-4b33-9e18-21ca38ca37d5\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Contact: <sip:21@192.168.3.39:5060>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12055 UPDATE\r\n
Supported: 100rel, replaces, timer, eventlist\r\n
Session-Expires: 3600;refresher=uac\r\n
Min-SE: 90\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:24,244 [Packet]:
Sending datagram (434 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 405 Method Not Allowed\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 UPDATE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:28,243 [Packet]:
Receiving datagram (534 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
UPDATE sip:21@192.168.3.1:5060;transport=UDP SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjda77c023-cd80-4b33-9e18-21ca38ca37d5\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Contact: <sip:21@192.168.3.39:5060>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12055 UPDATE\r\n
Supported: 100rel, replaces, timer, eventlist\r\n
Session-Expires: 3600;refresher=uac\r\n
Min-SE: 90\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:28,244 [Packet]:
Sending datagram (434 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 405 Method Not Allowed\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 UPDATE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:32,245 [Packet]:
Receiving datagram (534 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
UPDATE sip:21@192.168.3.1:5060;transport=UDP SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjda77c023-cd80-4b33-9e18-21ca38ca37d5\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Contact: <sip:21@192.168.3.39:5060>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12055 UPDATE\r\n
Supported: 100rel, replaces, timer, eventlist\r\n
Session-Expires: 3600;refresher=uac\r\n
Min-SE: 90\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:32,245 [Packet]:
Sending datagram (434 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 405 Method Not Allowed\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 UPDATE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:36,244 [Packet]:
Receiving datagram (534 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
UPDATE sip:21@192.168.3.1:5060;transport=UDP SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjda77c023-cd80-4b33-9e18-21ca38ca37d5\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Contact: <sip:21@192.168.3.39:5060>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12055 UPDATE\r\n
Supported: 100rel, replaces, timer, eventlist\r\n
Session-Expires: 3600;refresher=uac\r\n
Min-SE: 90\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:36,245 [Packet]:
Sending datagram (434 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 405 Method Not Allowed\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 UPDATE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:40,245 [Packet]:
Receiving datagram (534 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
UPDATE sip:21@192.168.3.1:5060;transport=UDP SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjda77c023-cd80-4b33-9e18-21ca38ca37d5\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Contact: <sip:21@192.168.3.39:5060>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12055 UPDATE\r\n
Supported: 100rel, replaces, timer, eventlist\r\n
Session-Expires: 3600;refresher=uac\r\n
Min-SE: 90\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:40,246 [Packet]:
Sending datagram (434 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 405 Method Not Allowed\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 UPDATE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:44,246 [Packet]:
Receiving datagram (534 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
UPDATE sip:21@192.168.3.1:5060;transport=UDP SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjda77c023-cd80-4b33-9e18-21ca38ca37d5\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Contact: <sip:21@192.168.3.39:5060>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12055 UPDATE\r\n
Supported: 100rel, replaces, timer, eventlist\r\n
Session-Expires: 3600;refresher=uac\r\n
Min-SE: 90\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:44,247 [Packet]:
Sending datagram (434 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 405 Method Not Allowed\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 UPDATE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:48,247 [Packet]:
Receiving datagram (534 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
UPDATE sip:21@192.168.3.1:5060;transport=UDP SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPjda77c023-cd80-4b33-9e18-21ca38ca37d5\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Contact: <sip:21@192.168.3.39:5060>\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12055 UPDATE\r\n
Supported: 100rel, replaces, timer, eventlist\r\n
Session-Expires: 3600;refresher=uac\r\n
Min-SE: 90\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:48,248 [Packet]:
Sending datagram (434 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 405 Method Not Allowed\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12054 UPDATE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:48,768 [Packet]:
Receiving datagram (393 Bytes) at 192.168.3.1:5060 from 192.168.3.39:5060 using UDP (RtgTag 0):
BYE sip:21@192.168.3.1:5060;transport=UDP SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;rport;branch=z9hG4bKPj00b116a2-28e6-4c64-8dc9-2a50d2eb99cb\r\n
Max-Forwards: 70\r\n
From: "03088888888" <sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: sip:03022222222@192.168.3.1;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12056 BYE\r\n
Content-Length:  0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:48,776 [Packet]:
Sending datagram (678 Bytes) from [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335 to [2001:ab7::1]:5060 using UDP (RtgTag 0):
BYE sip:6318338p0@212.9.44.137:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335;branch=z9hG4bK-6cf94775-c130e38f;rport\r\n
Route: <sip:[2001:AB7:0:0:0:0:0:1];r2=on;lr;ftag=1055621788-1659582999>\r\n
Route: <sip:217.116.119.66;r2=on;lr;ftag=1055621788-1659582999>\r\n
Route: <sip:172.20.40.6;lr>\r\n
From: "03088888888"<sip:2666666@sipgate.de;user=phone>;tag=1055621788-1659582999\r\n
To: <sip:03022222222@sipgate.de>;tag=as3d2884b8\r\n
Call-ID: 3727826398@00a0571ba94a\r\n
CSeq: 101 BYE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:48,810 [Packet]:
Receiving datagram (478 Bytes) at [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335 from [2001:ab7::1]:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP [2003:c1:7ff:b2b:a0:57ff:fe1b:a94a]:65335;received=2003:c1:7ff:b2b:a0:57ff:fe1b:a94a;branch=z9hG4bK-6cf94775-c130e38f;rport=65335\r\n
From: "03088888888"<sip:2666666@sipgate.de;user=phone>;tag=1055621788-1659582999\r\n
To: <sip:03022222222@sipgate.de>;tag=as3d2884b8\r\n
Call-ID: 3727826398@00a0571ba94a\r\n
CSeq: 101 BYE\r\n
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE\r\n
Supported: replaces\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 20:19:48,811 [Packet]:
Sending datagram (541 Bytes) from 192.168.3.1:5060 to 192.168.3.39:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 192.168.3.39:5060;branch=z9hG4bKPj00b116a2-28e6-4c64-8dc9-2a50d2eb99cb;received=192.168.3.39;rport=5060\r\n
From: "03088888888"<sip:21@intern>;tag=9813f538-3c71-4d94-a265-a8b2e6da6c6e\r\n
To: <sip:03022222222@192.168.3.1>;tag=925633541--1715083756\r\n
Call-ID: 15a30da0-1754-4a36-af2e-dc382c7b2adf\r\n
CSeq: 12056 BYE\r\n
User-Agent: LANCOM 1781VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, OPTIONS, PRACK, REFER, REGISTER\r\n
Content-Length: 0\r\n
\r\n
Vielen Dank und viele Grüße,
Cpuprofi und Jirka
awi
Beiträge: 61
Registriert: 19 Jun 2013, 15:22

Re: All-IP/VoIP: SIP-Methode UPDATE not allowed?! (10.12)

Beitrag von awi »

Hi,

zunächst einmal unterstützt der VCM die UPDATE Methode derzeit als Empfänger nur vom Provider.
Von einem SIP-Client kann der VCM das UPDATE nicht verarbeiten.

Natürlich sind hier tatsächlich zwei Fehler enthalten. Zum einen sollte die UPDATE Methode nicht im Allow-Header enthalten sein und zum
anderen ist in der Response natürlich das CSeq falsch.
Mal schauen woran das liegt.

Gruß
Awi
cpuprofi
Beiträge: 1330
Registriert: 12 Jun 2009, 12:44
Wohnort: Bremen

Re: All-IP/VoIP: SIP-Methode UPDATE not allowed?! (10.12)

Beitrag von cpuprofi »

Hallo Awi,

danke erst mal für die schnelle Rückmeldung. Hoffen wir, daß Du die Fehler beheben kannst.

Grüße
Cpuprofi
cpuprofi
Beiträge: 1330
Registriert: 12 Jun 2009, 12:44
Wohnort: Bremen

Re: All-IP/VoIP: SIP-Methode UPDATE not allowed?! (10.12)

Beitrag von cpuprofi »

Hallo Awi,

der Fehler ist ja schon in der FW 10.12.0355 von Dir beseitigt worden (der Lancom zeigt bei der internen Kommunikation nicht mehr UPDATE als Methode an). Danke.

Grüße
Cpuprofi
Antworten