Gesprächsvermittlung via VCM wird von Telekom mit 403 Forbidden abgelehnt

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

Moderator: Lancom-Systems Moderatoren

Antworten
CyberT
Beiträge: 281
Registriert: 17 Apr 2005, 14:36

Gesprächsvermittlung via VCM wird von Telekom mit 403 Forbidden abgelehnt

Beitrag von CyberT »

Hallo liebe VCM-/VoIP-Experten,

Ausgangssituation
- LANCOM 1781VAW mit All-IP
- Einrichtung der internen SIP-User und externen Leitungen (im wesentlichen) mit dem Setup-Assistenten
- Test und diverses Traces mit LCOS 10.34 RU2 und 10.40 RU3
- Standard Telekom Business-Anschluss (DeutschlandLAN IP Voice/Data S Premium mit VDSL 100 und fester IP-Adresse) mit 2 zusätzlichen Business-Sprachkanälen
- Bezugnahme zu Thread Gesprächsvermittlung zwischen Gigaset-Mobilteilen via VCM

Die Erstanalyse des LANCOM Support hat folgendes ergeben:
- Ein externes Gespräch wird intern von **17 zu **18 weiterverbunden. Für den Provider ist dies ein Halten -> Fortsetzen.
- Der Ruf wird vom Voice Call Manager korrekt verbunden.
- Der Dialog wird von der **17 und dem Voice Call Manager "geparkt" (a=inactive).
- Anschließend sendet dieser ein INVITE Richtung Telekom, um die **18 mit der externen Nummer zu verbinden.
- Die Telekom lehnt den Ruf aber mit 403 Forbidden ab.
(Dadurch entsteht der Eindruck, also würde keine keine Audio-Übertragung mehr stattfinden, siehe anderer Thread.)
- Warum der Ruf von der Telekom mit 403 Forbidden abgelehnt wird, ist unklar.

Davon ausgehend bedeutet dies ja, dass am vorliegenden Anschluss mit jeglichen internen Endgeräten (also auch bei analogen, ISDN- und anderen IP-Telefonen), das Vermitteln von Gesprächen via VCM (mittels **XY) nie gelingen würde. Und das verwundert mich doch ehrlich gesagt sehr! :-o

Hier handelt es sich um einen Standard Telekom Business-Anschluss, der als Neuanschluss erst im Sommer 2019 geschaltet wurde. Hier wurde nichts speziell konfiguriert, lediglich 2 zusätzliche Business-Sprachkanäle wurden hinzu gebucht. Vor diesem Hintergrund ist es für mich derzeit schwer nachvollziehbar, dass ausgerechnet an diesem Anschluss spezifisch etwas nicht funktionieren sollte.

Hat jemand eine Idee, wie und wo ich hier jetzt noch ansetzen kann?

Vielen Dank vorab und
Gruß.
Nach oben
CyberT
Beiträge: 281
Registriert: 17 Apr 2005, 14:36

Re: Gesprächsvermittlung via VCM wird von Telekom mit 403 Forbidden abgelehnt

Beitrag von CyberT »

Hallo nochmal,

nachfolgend noch ergänzende (teils anonymisierten) Informationen und der relevante Ausschnitt aus dem SIP-Packet-Trace (in dem nachvollziehbar ist, dass die Telekom den Ruf mit 403 Forbidden ablehnt):

Telekom Business-Anschluss
Feste IP-Adresse: 12.345.67.89

Quell-Rufnummer (extern): +491721234567
Ziel-Rufnummer (extern): +496912345629

Rufannahme (intern): **17
Gesprächsübergabe an (intern): **18

Code: Alles auswählen

[SIP-Packet] 2021/01/09 17:31:00,276  Devicetime: 2021/01/09 17:31:00,395 [Packet]: 
Receiving datagram (1689 Bytes) at 12.345.67.89:13430 from 217.0.28.32:5060 using UDP (RtgTag 0):
INVITE sip:+496912345629@12.345.67.89:13430;transport=udp SIP/2.0\r\n
Max-Forwards: 56\r\n
Via: SIP/2.0/UDP 217.0.28.32:5060;branch=z9hG4bKg3Zqkv7ihz83zwj6xdxrymfg53qredcbc\r\n
To: <sip:+496912345629@telekom.de;user=phone>\r\n
From: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 1 INVITE\r\n
Contact: <sip:sgc_c@217.0.28.32;transport=udp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"\r\n
Record-Route: <sip:217.0.28.32;transport=udp;lr>\r\n
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"\r\n
Min-Se: 900\r\n
P-Asserted-Identity: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>\r\n
P-Asserted-Identity: <tel:+491721234567>\r\n
Session-Expires: 1800\r\n
Supported: timer\r\n
Supported: 100rel\r\n
Supported: precondition\r\n
Supported: histinfo\r\n
Supported: norefersub\r\n
Supported: 199\r\n
Content-Type: application/sdp\r\n
Content-Length: 548\r\n
Session-ID: 8ab35300a1c4f30d7603f15fe9661cc1\r\n
Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, INFO, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE\r\n
\r\n
v=0\r\n
o=- 776270784 851991554 IN IP4 217.0.28.32\r\n
s=-\r\n
c=IN IP4 217.0.6.244\r\n
t=0 0\r\n
m=audio 25228 RTP/AVP 96 9 97 8 98 99\r\n
b=AS:80\r\n
a=rtpmap:96 AMR-WB/16000\r\n
a=fmtp:96 mode-change-capability=2; max-red=0\r\n
a=rtpmap:9 G722/8000\r\n
a=rtpmap:97 AMR/8000\r\n
a=fmtp:97 mode-change-period=2; mode-change-neighbor=1; max-red=0\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:98 telephone-event/8000\r\n
a=rtpmap:99 telephone-event/16000\r\n
a=ptime:20\r\n
a=maxptime:30\r\n
a=curr:qos local none\r\n
a=curr:qos remote none\r\n
a=des:qos mandatory local sendrecv\r\n
a=des:qos none remote sendrecv\r\n

[SIP-Packet] 2021/01/09 17:31:00,338  Devicetime: 2021/01/09 17:31:00,411 [Packet]: 
Sending datagram (564 Bytes) from 12.345.67.89:13430 to 217.0.28.32:5060 using UDP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 217.0.28.32:5060;branch=z9hG4bKg3Zqkv7ihz83zwj6xdxrymfg53qredcbc;received=217.0.28.32\r\n
Record-Route: <sip:217.0.28.32;transport=udp;lr>\r\n
From: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
To: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 1 INVITE\r\n
User-Agent: LANCOM 1781VAW (over ISDN) 10.40.0414\r\n
Server: Lancom\r\n
Supported: replaces,timer\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2021/01/09 17:31:00,950  Devicetime: 2021/01/09 17:31:01,037 [Packet]: 
Sending datagram (717 Bytes) from 12.345.67.89:13430 to 217.0.28.32:5060 using UDP (RtgTag 0):
SIP/2.0 180 Ringing\r\n
Via: SIP/2.0/UDP 217.0.28.32:5060;branch=z9hG4bKg3Zqkv7ihz83zwj6xdxrymfg53qredcbc;received=217.0.28.32\r\n
Record-Route: <sip:217.0.28.32;transport=udp;lr>\r\n
From: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
To: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 1 INVITE\r\n
User-Agent: LANCOM 1781VAW (over ISDN) 10.40.0414\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, REFER, INFO, OPTIONS, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK\r\n
Supported: replaces,timer\r\n
Contact: <sip:+496912345629@12.345.67.89:13430;transport=UDP>\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2021/01/09 17:31:09,739  Devicetime: 2021/01/09 17:31:09,787 [Packet]: 
Sending datagram (1008 Bytes) from 12.345.67.89:13430 to 217.0.28.32:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 217.0.28.32:5060;branch=z9hG4bKg3Zqkv7ihz83zwj6xdxrymfg53qredcbc;received=217.0.28.32\r\n
Record-Route: <sip:217.0.28.32;transport=udp;lr>\r\n
From: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
To: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 1 INVITE\r\n
User-Agent: LANCOM 1781VAW (over ISDN) 10.40.0414\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, REFER, INFO, OPTIONS, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK\r\n
Supported: replaces,timer\r\n
Contact: <sip:+496912345629@12.345.67.89:13430;transport=UDP>\r\n
Session-Expires: 1800;refresher=uac\r\n
Require: timer\r\n
Content-Type: application/sdp\r\n
Content-Length: 210\r\n
\r\n
v=0\r\n
o=- 0 0 IN IP4 12.345.67.89\r\n
s=call\r\n
c=IN IP4 12.345.67.89\r\n
t=0 0\r\n
m=audio 14146 RTP/AVP 8 98\r\n
b=TIAS:64000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:98 telephone-event/8000\r\n
a=fmtp:98 0-15\r\n
a=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2021/01/09 17:31:09,846  Devicetime: 2021/01/09 17:31:09,988 [Packet]: 
Receiving datagram (567 Bytes) at 12.345.67.89:13430 from 217.0.28.32:5060 using UDP (RtgTag 0):
ACK sip:+496912345629@12.345.67.89:13430;transport=udp SIP/2.0\r\n
Max-Forwards: 64\r\n
Via: SIP/2.0/UDP 217.0.28.32:5060;branch=z9hG4bKg3Zqkv7itprzgl9wlh26gxcrx1lg1sho4\r\n
To: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
From: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 1 ACK\r\n
Contact: <sip:sgc_c@217.0.28.32;transport=udp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2021/01/09 17:31:19,504  Devicetime: 2021/01/09 17:31:19,600 [Packet]: 
Sending datagram (1086 Bytes) from 12.345.67.89:13430 to 217.0.28.32:5060 using UDP (RtgTag 0):
INVITE sip:sgc_c@217.0.28.32;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 12.345.67.89:13430;branch=z9hG4bK-1909d454-2112c81a;rport\r\n
Route: <sip:217.0.28.32;transport=udp;lr>\r\n
From: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
To: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 1 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781VAW (over ISDN) 10.40.0414\r\n
Allow: SUBSCRIBE, NOTIFY, REFER, INFO, OPTIONS, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK\r\n
Supported: timer\r\n
Contact: <sip:+496912345629@12.345.67.89:13430;transport=UDP>\r\n
Session-Expires: 1800;refresher=uac\r\n
P-Early-Media: supported\r\n
Content-Type: application/sdp\r\n
Content-Length: 284\r\n
\r\n
v=0\r\n
o=- 0 1 IN IP4 12.345.67.89\r\n
s=call\r\n
c=IN IP4 12.345.67.89\r\n
t=0 0\r\n
m=audio 14146 RTP/AVP 8 0 18 101\r\n
b=TIAS:64000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:18 annexb=no\r\n
a=fmtp:101 0-15\r\n
a=inactive\r\n
a=ptime:20\r\n

[SIP-Packet] 2021/01/09 17:31:19,516  Devicetime: 2021/01/09 17:31:19,655 [Packet]: 
Receiving datagram (582 Bytes) at 12.345.67.89:13430 from 217.0.28.32:5060 using UDP (RtgTag 0):
SIP/2.0 407 Proxy Authentication Required 02035034C\r\n
Via: SIP/2.0/UDP 12.345.67.89:13430;received=12.345.67.89;rport=13430;branch=z9hG4bK-1909d454-2112c81a\r\n
To: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
From: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 1 INVITE\r\n
Content-Length: 0\r\n
Proxy-Authenticate: Digest nonce="A527E56764DAF95F00000000D21CA900",realm="tel.t-online.de",algorithm=MD5,qop="auth",stale=true\r\n
\r\n

[SIP-Packet] 2021/01/09 17:31:19,516  Devicetime: 2021/01/09 17:31:19,656 [Packet]: 
Sending datagram (530 Bytes) from 12.345.67.89:13430 to 217.0.28.32:5060 using UDP (RtgTag 0):
ACK sip:sgc_c@217.0.28.32;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 12.345.67.89:13430;branch=z9hG4bK-1909d454-2112c81a;rport\r\n
Route: <sip:217.0.28.32;transport=udp;lr>\r\n
From: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
To: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 1 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781VAW (over ISDN) 10.40.0414\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2021/01/09 17:31:19,532  Devicetime: 2021/01/09 17:31:19,658 [Packet]: 
Sending datagram (1358 Bytes) from 12.345.67.89:13430 to 217.0.28.32:5060 using UDP (RtgTag 0):
INVITE sip:sgc_c@217.0.28.32;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 12.345.67.89:13430;branch=z9hG4bK-3b478380-1ab66d4b;rport\r\n
Route: <sip:217.0.28.32;transport=udp;lr>\r\n
From: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
To: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 2 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781VAW (over ISDN) 10.40.0414\r\n
Allow: SUBSCRIBE, NOTIFY, REFER, INFO, OPTIONS, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK\r\n
Supported: timer\r\n
Proxy-Authorization: Digest username="anonymous@t-online.de", realm="tel.t-online.de", algorithm=MD5, uri="sip:sgc_c@217.0.28.32:5060", nonce="A527E56764DAF95F00000000D21CA900",qop=auth, cnonce="4f9ae5f1ca75f1d8", nc=00000001, response="ac3d0020133e894076a4258e7bbef2ae"\r\n
Contact: <sip:+496912345629@12.345.67.89:13430;transport=UDP>\r\n
Session-Expires: 1800;refresher=uac\r\n
P-Early-Media: supported\r\n
Content-Type: application/sdp\r\n
Content-Length: 284\r\n
\r\n
v=0\r\n
o=- 0 1 IN IP4 12.345.67.89\r\n
s=call\r\n
c=IN IP4 12.345.67.89\r\n
t=0 0\r\n
m=audio 14146 RTP/AVP 8 0 18 101\r\n
b=TIAS:64000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:18 annexb=no\r\n
a=fmtp:101 0-15\r\n
a=inactive\r\n
a=ptime:20\r\n

[SIP-Packet] 2021/01/09 17:31:19,685  Devicetime: 2021/01/09 17:31:19,804 [Packet]: 
Receiving datagram (1136 Bytes) at 12.345.67.89:13430 from 217.0.28.32:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 12.345.67.89:13430;received=12.345.67.89;rport=13430;branch=z9hG4bK-3b478380-1ab66d4b\r\n
To: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
From: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 2 INVITE\r\n
Contact: <sip:sgc_c@217.0.28.32;transport=udp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"\r\n
Require: timer\r\n
Session-Expires: 1800;refresher=uac\r\n
Supported: timer\r\n
Supported: 100rel\r\n
Supported: histinfo\r\n
Supported: norefersub\r\n
Supported: 199\r\n
Content-Type: application/sdp\r\n
Content-Length: 217\r\n
Authentication-Info: qop=auth,rspauth="b6e456f0e16ea94b1f5370fe14f6a014",cnonce="4f9ae5f1ca75f1d8",nc=00000001\r\n
Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, INFO, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE\r\n
\r\n
v=0\r\n
o=- 776270784 851991555 IN IP4 217.0.28.32\r\n
s=-\r\n
c=IN IP4 217.0.6.244\r\n
t=0 0\r\n
m=audio 25228 RTP/AVP 8 101\r\n
b=AS:80\r\n
a=inactive\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=ptime:20\r\n
a=maxptime:30\r\n

[SIP-Packet] 2021/01/09 17:31:19,828  Devicetime: 2021/01/09 17:31:19,831 [Packet]: 
Sending datagram (802 Bytes) from 12.345.67.89:13430 to 217.0.28.32:5060 using UDP (RtgTag 0):
ACK sip:sgc_c@217.0.28.32;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 12.345.67.89:13430;branch=z9hG4bK-64da64c7-4876d0b8;rport\r\n
Route: <sip:217.0.28.32;transport=udp;lr>\r\n
From: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
To: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 2 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781VAW (over ISDN) 10.40.0414\r\n
Proxy-Authorization: Digest username="anonymous@t-online.de", realm="tel.t-online.de", algorithm=MD5, uri="sip:sgc_c@217.0.28.32:5060", nonce="A527E56764DAF95F00000000D21CA900",qop=auth, cnonce="4f9ae5f1ca75f1d8", nc=00000001, response="ac3d0020133e894076a4258e7bbef2ae"\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2021/01/09 17:31:41,261  Devicetime: 2021/01/09 17:31:41,232 [Packet]: 
Sending datagram (1015 Bytes) from 12.345.67.89:13430 to 217.0.28.32:5060 using UDP (RtgTag 0):
INVITE sip:sgc_c@217.0.28.32;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 12.345.67.89:13430;branch=z9hG4bK-5d989f11-536f8f61;rport\r\n
Route: <sip:217.0.28.32;transport=udp;lr>\r\n
From: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
To: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 3 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781VAW (over ISDN) 10.40.0414\r\n
Allow: SUBSCRIBE, NOTIFY, REFER, INFO, OPTIONS, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK\r\n
Supported: timer\r\n
Contact: <sip:+496912345629@12.345.67.89:13430;transport=UDP>\r\n
Session-Expires: 1800;refresher=uac\r\n
P-Early-Media: supported\r\n
Content-Type: application/sdp\r\n
Content-Length: 213\r\n
\r\n
v=0\r\n
o=- 0 2 IN IP4 12.345.67.89\r\n
s=call\r\n
c=IN IP4 12.345.67.89\r\n
t=0 0\r\n
m=audio 14146 RTP/AVP 8 101\r\n
b=TIAS:64000\r\n
a=rtpmap:8 PCMA/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] 2021/01/09 17:31:41,371  Devicetime: 2021/01/09 17:31:41,309 [Packet]: 
Receiving datagram (582 Bytes) at 12.345.67.89:13430 from 217.0.28.32:5060 using UDP (RtgTag 0):
SIP/2.0 407 Proxy Authentication Required 02035034C\r\n
Via: SIP/2.0/UDP 12.345.67.89:13430;received=12.345.67.89;rport=13430;branch=z9hG4bK-5d989f11-536f8f61\r\n
To: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
From: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 3 INVITE\r\n
Content-Length: 0\r\n
Proxy-Authenticate: Digest nonce="19E27A8C79DAF95F00000000808A3D26",realm="tel.t-online.de",algorithm=MD5,qop="auth",stale=true\r\n
\r\n

[SIP-Packet] 2021/01/09 17:31:41,371  Devicetime: 2021/01/09 17:31:41,310 [Packet]: 
Sending datagram (530 Bytes) from 12.345.67.89:13430 to 217.0.28.32:5060 using UDP (RtgTag 0):
ACK sip:sgc_c@217.0.28.32;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 12.345.67.89:13430;branch=z9hG4bK-5d989f11-536f8f61;rport\r\n
Route: <sip:217.0.28.32;transport=udp;lr>\r\n
From: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
To: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 3 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781VAW (over ISDN) 10.40.0414\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2021/01/09 17:31:41,384  Devicetime: 2021/01/09 17:31:41,312 [Packet]: 
Sending datagram (1287 Bytes) from 12.345.67.89:13430 to 217.0.28.32:5060 using UDP (RtgTag 0):
INVITE sip:sgc_c@217.0.28.32;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 12.345.67.89:13430;branch=z9hG4bK-1049e23f-c06310c5;rport\r\n
Route: <sip:217.0.28.32;transport=udp;lr>\r\n
From: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
To: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 4 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781VAW (over ISDN) 10.40.0414\r\n
Allow: SUBSCRIBE, NOTIFY, REFER, INFO, OPTIONS, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK\r\n
Supported: timer\r\n
Proxy-Authorization: Digest username="anonymous@t-online.de", realm="tel.t-online.de", algorithm=MD5, uri="sip:sgc_c@217.0.28.32:5060", nonce="19E27A8C79DAF95F00000000808A3D26",qop=auth, cnonce="1f87cba3e27b66f1", nc=00000001, response="abe1e0db261d044fd34ee34dd44d95f7"\r\n
Contact: <sip:+496912345629@12.345.67.89:13430;transport=UDP>\r\n
Session-Expires: 1800;refresher=uac\r\n
P-Early-Media: supported\r\n
Content-Type: application/sdp\r\n
Content-Length: 213\r\n
\r\n
v=0\r\n
o=- 0 2 IN IP4 12.345.67.89\r\n
s=call\r\n
c=IN IP4 12.345.67.89\r\n
t=0 0\r\n
m=audio 14146 RTP/AVP 8 101\r\n
b=TIAS:64000\r\n
a=rtpmap:8 PCMA/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] 2021/01/09 17:31:41,384  Devicetime: 2021/01/09 17:31:41,386 [Packet]: 
Receiving datagram (550 Bytes) at 12.345.67.89:13430 from 217.0.28.32:5060 using UDP (RtgTag 0):
SIP/2.0 403 Forbidden\r\n
Via: SIP/2.0/UDP 12.345.67.89:13430;received=12.345.67.89;rport=13430;branch=z9hG4bK-1049e23f-c06310c5\r\n
To: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
From: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 4 INVITE\r\n
Contact: <sip:sgc_c@217.0.28.32;transport=udp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"\r\n
Supported: timer\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2021/01/09 17:31:41,384  Devicetime: 2021/01/09 17:31:41,387 [Packet]: 
Sending datagram (530 Bytes) from 12.345.67.89:13430 to 217.0.28.32:5060 using UDP (RtgTag 0):
ACK sip:sgc_c@217.0.28.32;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 12.345.67.89:13430;branch=z9hG4bK-1049e23f-c06310c5;rport\r\n
Route: <sip:217.0.28.32;transport=udp;lr>\r\n
From: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
To: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 4 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781VAW (over ISDN) 10.40.0414\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2021/01/09 17:32:20,851  Devicetime: 2021/01/09 17:32:21,002 [Packet]: 
Receiving datagram (656 Bytes) at 12.345.67.89:13430 from 217.0.28.32:5060 using UDP (RtgTag 0):
BYE sip:+496912345629@12.345.67.89:13430;transport=udp SIP/2.0\r\n
Max-Forwards: 64\r\n
Via: SIP/2.0/UDP 217.0.28.32:5060;branch=z9hG4bKg3Zqkv7iickg7qs4qfcvzbepdz81gnu8c\r\n
To: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
From: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 2 BYE\r\n
Reason: X.int;text="0x00000000";add-info=05CC.0001.0001\r\n
Reason: Q.850;cause=16\r\n
Supported: timer\r\n
Content-Length: 0\r\n
Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, INFO, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE\r\n
\r\n

[SIP-Packet] 2021/01/09 17:32:20,852  Devicetime: 2021/01/09 17:32:21,005 [Packet]: 
Sending datagram (637 Bytes) from 12.345.67.89:13430 to 217.0.28.32:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 217.0.28.32:5060;branch=z9hG4bKg3Zqkv7iickg7qs4qfcvzbepdz81gnu8c;received=217.0.28.32\r\n
Record-Route: <sip:217.0.28.32;transport=udp;lr>\r\n
From: <sip:+491721234567@ims.mnc002.mcc262.3gppnetwork.org;user=phone>;tag=h7g4Esbg_p65553t1610209861m56799c12987073s1_851991794-109366585\r\n
To: <sip:+496912345629@telekom.de;user=phone>;tag=-856792362--1155142242\r\n
Call-ID: p65553t1610209861m56799c12987073s2\r\n
CSeq: 2 BYE\r\n
User-Agent: LANCOM 1781VAW (over ISDN) 10.40.0414\r\n
Server: Lancom\r\n
Allow: SUBSCRIBE, NOTIFY, REFER, INFO, OPTIONS, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK\r\n
Supported: timer\r\n
Content-Length: 0\r\n
\r\n

Was wäre der beste nächste Schritt, um das Problem lösen zu können?

Vielen Dank vorab und
Gruß.
Nach oben
CyberT
Beiträge: 281
Registriert: 17 Apr 2005, 14:36

Re: Gesprächsvermittlung via VCM wird von Telekom mit 403 Forbidden abgelehnt

Beitrag von CyberT »

Hallo zusammen,

in den Release-Notes zu LCOS 10.42 RU1 findet sich folgender Hinweis:

VoIP
Es wurden Probleme beim Vermitteln von Telefonaten mit den Methoden RE-INVITE, REFER und der damit verbundenen Voice-Codec-Aushandlung in Szenarien mit Swyx-TK-Anlagen behoben.

Ich hatte zwar keine echte Hoffnung, dass mein Problem damit auch gelöst wurde, aber ich habe zwischenzeitlich LCOS 10.42 RU1 auf dem betreffenden LANCOM installiert. Das Release läuft soweit stabil, allerdings ist das vorliegende Problem (Gesprächsvermittlung via VCM wird von Telekom mit 403 Forbidden abgelehnt) damit nicht gelöst worden.

So bleibt mir wohl in Ermangelung weiterer Alternativen jetzt tatsächlich nur noch beim Telekom Business Support hierzu ein Ticket zu öffnen...

Gruß.
Nach oben
Antworten

Zurück zu „Fragen zu LANCOM Systems VoIP Router“