M-Net, abgehende Gespräche schlagen fehl

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

Moderator: Lancom-Systems Moderatoren

Antworten
booker
Beiträge: 100
Registriert: 01 Aug 2005, 16:05

M-Net, abgehende Gespräche schlagen fehl

Beitrag von booker »

Hallo zusammen,

ich versuche seit geraumer Zeit meine M-Net Leitungen mit meinem 1781EF+ zu registrieren. Nachdem das anfänglich nicht funktionierte habe ich es zunächst darauf geschoben, dass M-Net in der Schnittstellenbeschreibung explizit schreibt, dass die Registrierung per IPv6 erfolgen muss. Der VCM bis zur LCOS 10 aber kein IPv6 konnte. Nach update auf die aktuelle Version scheidet das aber als Fehlerursache aus, das Problem ist unverändert.

Ich habe die Zugangsdaten als SIP-Leitung konfiguriert und die Registrierung scheint auch zu klappen. Die Leitung wird als registriert angezeigt. Ankommende Gespräche klappen! Das Problem sind abgehende Verbindungen. Wenn ich wähle, dann kommt kurz danach das Belegtzeichen obwohl die Zielrufnummer nicht belegt ist. Ich lege dann wieder auf und kurz danach klinget die Zielrufnummer! Ich füge hier mal einen (anonymisierten) SIP-Packet Trace ein.

Code: Alles auswählen

[SIP-Packet] 2017/04/23 16:55:22,094  Devicetime: 2017/04/23 16:55:25,052 [Packet]: 
Sending datagram (1306 Bytes) from [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 to [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
INVITE sip:<Ziel-Rufnummer>@phone.mnet-voip.de SIP/2.0\r\n
Via: SIP/2.0/TCP [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769;branch=z9hG4bK-8b50bc30-5465b113;rport\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 100 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: Yealink SIP-T26P 6.70.13.9\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE\r\n
Supported: 100rel\r\n
Contact: <sip:<M-Net-Nummer>@[2001:a61:1003:f900:a0:57ff:fe24:898a]:13769;transport=TCP>\r\n
Authorization: Digest username="<M-Net-Nummer>", realm="phone.mnet-voip.de", algorithm=MD5, uri="sip:<Ziel-Rufnummer>@phone.mnet-voip.de", nonce="b23daff265b8",qop=auth, cnonce="fe1632ad92b39a76", nc=00000002, response="a05dc4d5e5a0bf10f754f24b61dc1f66"\r\n
Content-Type: application/sdp\r\n
Content-Length: 413\r\n
\r\n
v=0\r\n
o=- 660431643 660431643 IN IP6 2001:a61:1003:f900:a0:57ff:fe24:898a\r\n
s=call\r\n
c=IN IP6 2001:a61:1003:f900:a0:57ff:fe24:898a\r\n
t=0 0\r\n
m=audio 64238 RTP/AVP 9 8 18 4 112 0 101\r\n
a=rtpmap:9 G722/8000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=rtpmap:4 G723/8000\r\n
a=rtpmap:112 G726-16/8000\r\n
a=rtpmap:0 PCMU/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=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2017/04/23 16:55:22,277  Devicetime: 2017/04/23 16:55:25,069 [Packet]: 
Receiving datagram (418 Bytes) at [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 from [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 100 INVITE\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+1dec0006+9596a42a\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-8b50bc30-5465b113\r\n
Server: SIP/2.0\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2017/04/23 16:55:22,349  Devicetime: 2017/04/23 16:55:25,234 [Packet]: 
Receiving datagram (637 Bytes) at [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 from [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
SIP/2.0 401 Unauthorized\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 100 INVITE\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+1dec0006+9596a42a\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-8b50bc30-5465b113\r\n
Content-Length: 0\r\n
Supported: resource-priority, siprec, 100rel\r\n
Contact: <sip:[2001:A60:1:8::10]:5060;transport=tcp>\r\n
WWW-Authenticate: Digest realm="phone.mnet-voip.de",nonce="b23db3406906",stale=true,algorithm=MD5,qop="auth"\r\n
Server: DC-SIP/2.0\r\n
\r\n

[SIP-Packet] 2017/04/23 16:55:22,349  Devicetime: 2017/04/23 16:55:25,234 [Packet]: 
Sending datagram (432 Bytes) from [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 to [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
ACK sip:<Ziel-Rufnummer>@phone.mnet-voip.de SIP/2.0\r\n
Via: SIP/2.0/TCP [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769;branch=z9hG4bK-8b50bc30-5465b113;rport\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+1dec0006+9596a42a\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 100 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: Yealink SIP-T26P 6.70.13.9\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2017/04/23 16:55:22,349  Devicetime: 2017/04/23 16:55:25,235 [Packet]: 
Sending datagram (1306 Bytes) from [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 to [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
INVITE sip:<Ziel-Rufnummer>@phone.mnet-voip.de SIP/2.0\r\n
Via: SIP/2.0/TCP [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769;branch=z9hG4bK-b87b9798-5997cf53;rport\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 101 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: Yealink SIP-T26P 6.70.13.9\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE\r\n
Supported: 100rel\r\n
Authorization: Digest username="<M-Net-Nummer>", realm="phone.mnet-voip.de", algorithm=MD5, uri="sip:<Ziel-Rufnummer>@phone.mnet-voip.de", nonce="b23db3406906",qop=auth, cnonce="c91465bd8932b1fe", nc=00000001, response="52d2ad429a705e7c0dbbf51b857e0db5"\r\n
Contact: <sip:<M-Net-Nummer>@[2001:a61:1003:f900:a0:57ff:fe24:898a]:13769;transport=TCP>\r\n
Content-Type: application/sdp\r\n
Content-Length: 413\r\n
\r\n
v=0\r\n
o=- 660431643 660431643 IN IP6 2001:a61:1003:f900:a0:57ff:fe24:898a\r\n
s=call\r\n
c=IN IP6 2001:a61:1003:f900:a0:57ff:fe24:898a\r\n
t=0 0\r\n
m=audio 64238 RTP/AVP 9 8 18 4 112 0 101\r\n
a=rtpmap:9 G722/8000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=rtpmap:4 G723/8000\r\n
a=rtpmap:112 G726-16/8000\r\n
a=rtpmap:0 PCMU/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=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2017/04/23 16:55:22,350  Devicetime: 2017/04/23 16:55:25,309 [Packet]: 
Receiving datagram (418 Bytes) at [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 from [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 101 INVITE\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+536e713b\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-b87b9798-5997cf53\r\n
Server: SIP/2.0\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2017/04/23 16:55:24,370  Devicetime: 2017/04/23 16:55:27,327 [Packet]: 
Receiving datagram (860 Bytes) at [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 from [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
SIP/2.0 183 Session Progress\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 101 INVITE\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+536e713b\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-b87b9798-5997cf53\r\n
Require: 100rel\r\n
RSeq: 184911263\r\n
Content-Length: 264\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp;user=phone>\r\n
Content-Type: application/sdp\r\n
Server: DC-SIP/2.0\r\n
\r\n
v=0\r\n
o=- 90821698094207 90821698094207 IN IP6 2001:A60:1:108::10\r\n
s=-\r\n
c=IN IP6 2001:A60:1:108::10\r\n
t=0 0\r\n
m=audio 24454 RTP/AVP 8 18 101\r\n
a=sendrecv\r\n
a=rtpmap:8 PCMA/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=ptime:20\r\n

[SIP-Packet] 2017/04/23 16:55:24,371  Devicetime: 2017/04/23 16:55:27,327 [Packet]: 
Sending datagram (608 Bytes) from [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 to [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
PRACK sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp;user=phone SIP/2.0\r\n
Via: SIP/2.0/TCP [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769;branch=z9hG4bK-653de24d-2e1ddfaf;rport\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+536e713b\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 102 PRACK\r\n
Max-Forwards: 70\r\n
User-Agent: Yealink SIP-T26P 6.70.13.9\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE\r\n
RAck: 184911263 101 INVITE\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2017/04/23 16:55:24,591  Devicetime: 2017/04/23 16:55:27,349 [Packet]: 
Receiving datagram (670 Bytes) at [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 from [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
SIP/2.0 401 Unauthorized\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 102 PRACK\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+536e713b\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-653de24d-2e1ddfaf\r\n
Content-Length: 0\r\n
Supported: resource-priority, siprec, 100rel\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp>\r\n
WWW-Authenticate: Digest realm="phone.mnet-voip.de",nonce="b23db34b6911",stale=false,algorithm=MD5,qop="auth"\r\n
Server: DC-SIP/2.0\r\n
\r\n

[SIP-Packet] 2017/04/23 16:55:24,592  Devicetime: 2017/04/23 16:55:27,350 [Packet]: 
Sending datagram (483 Bytes) from [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 to [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
ACK sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp;user=phone SIP/2.0\r\n
Via: SIP/2.0/TCP [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769;branch=z9hG4bK-b87b9798-5997cf53;rport\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+536e713b\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 101 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: Yealink SIP-T26P 6.70.13.9\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2017/04/23 16:55:24,592  Devicetime: 2017/04/23 16:55:27,351 [Packet]: 
Sending datagram (1383 Bytes) from [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 to [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
INVITE sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp;user=phone SIP/2.0\r\n
Via: SIP/2.0/TCP [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769;branch=z9hG4bK-cdf029fa-fb224c4a;rport\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 103 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: Yealink SIP-T26P 6.70.13.9\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE\r\n
Supported: 100rel\r\n
Authorization: Digest username="<M-Net-Nummer>", realm="phone.mnet-voip.de", algorithm=MD5, uri="sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060", nonce="b23db34b6911",qop=auth, cnonce="a899c967b9f46793", nc=00000001, response="562105a953565e7a29b18ba403b9b0cf"\r\n
Contact: <sip:<M-Net-Nummer>@[2001:a61:1003:f900:a0:57ff:fe24:898a]:13769;transport=TCP>\r\n
Content-Type: application/sdp\r\n
Content-Length: 413\r\n
\r\n
v=0\r\n
o=- 660431643 660431643 IN IP6 2001:a61:1003:f900:a0:57ff:fe24:898a\r\n
s=call\r\n
c=IN IP6 2001:a61:1003:f900:a0:57ff:fe24:898a\r\n
t=0 0\r\n
m=audio 64238 RTP/AVP 9 8 18 4 112 0 101\r\n
a=rtpmap:9 G722/8000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=rtpmap:4 G723/8000\r\n
a=rtpmap:112 G726-16/8000\r\n
a=rtpmap:0 PCMU/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=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2017/04/23 16:55:24,592  Devicetime: 2017/04/23 16:55:27,424 [Packet]: 
Receiving datagram (418 Bytes) at [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 from [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 103 INVITE\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+85095e27\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-cdf029fa-fb224c4a\r\n
Server: SIP/2.0\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2017/04/23 16:55:24,631  Devicetime: 2017/04/23 16:55:27,589 [Packet]: 
Receiving datagram (478 Bytes) at [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 from [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
SIP/2.0 403 Forbidden\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 103 INVITE\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+85095e27\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-cdf029fa-fb224c4a\r\n
Content-Length: 0\r\n
Contact: <sip:[2001:A60:1:8::10]:5060;transport=tcp>\r\n
Server: DC-SIP/2.0\r\n
\r\n

[SIP-Packet] 2017/04/23 16:55:24,632  Devicetime: 2017/04/23 16:55:27,590 [Packet]: 
Sending datagram (483 Bytes) from [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 to [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
ACK sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp;user=phone SIP/2.0\r\n
Via: SIP/2.0/TCP [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769;branch=z9hG4bK-cdf029fa-fb224c4a;rport\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+85095e27\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 103 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: Yealink SIP-T26P 6.70.13.9\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2017/04/23 16:55:25,066  Devicetime: 2017/04/23 16:55:27,826 [Packet]: 
Receiving datagram (860 Bytes) at [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 from [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
SIP/2.0 183 Session Progress\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 101 INVITE\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+536e713b\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-b87b9798-5997cf53\r\n
Require: 100rel\r\n
RSeq: 184911263\r\n
Content-Length: 264\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp;user=phone>\r\n
Content-Type: application/sdp\r\n
Server: DC-SIP/2.0\r\n
\r\n
v=0\r\n
o=- 90821698094207 90821698094207 IN IP6 2001:A60:1:108::10\r\n
s=-\r\n
c=IN IP6 2001:A60:1:108::10\r\n
t=0 0\r\n
m=audio 24454 RTP/AVP 8 18 101\r\n
a=sendrecv\r\n
a=rtpmap:8 PCMA/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=ptime:20\r\n

[SIP-Packet] 2017/04/23 16:55:26,076  Devicetime: 2017/04/23 16:55:28,826 [Packet]: 
Receiving datagram (860 Bytes) at [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 from [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
SIP/2.0 183 Session Progress\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 101 INVITE\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+536e713b\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-b87b9798-5997cf53\r\n
Require: 100rel\r\n
RSeq: 184911263\r\n
Content-Length: 264\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp;user=phone>\r\n
Content-Type: application/sdp\r\n
Server: DC-SIP/2.0\r\n
\r\n
v=0\r\n
o=- 90821698094207 90821698094207 IN IP6 2001:A60:1:108::10\r\n
s=-\r\n
c=IN IP6 2001:A60:1:108::10\r\n
t=0 0\r\n
m=audio 24454 RTP/AVP 8 18 101\r\n
a=sendrecv\r\n
a=rtpmap:8 PCMA/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=ptime:20\r\n

[SIP-Packet] 2017/04/23 16:55:28,076  Devicetime: 2017/04/23 16:55:30,826 [Packet]: 
Receiving datagram (860 Bytes) at [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 from [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
SIP/2.0 183 Session Progress\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 101 INVITE\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+536e713b\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-b87b9798-5997cf53\r\n
Require: 100rel\r\n
RSeq: 184911263\r\n
Content-Length: 264\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp;user=phone>\r\n
Content-Type: application/sdp\r\n
Server: DC-SIP/2.0\r\n
\r\n
v=0\r\n
o=- 90821698094207 90821698094207 IN IP6 2001:A60:1:108::10\r\n
s=-\r\n
c=IN IP6 2001:A60:1:108::10\r\n
t=0 0\r\n
m=audio 24454 RTP/AVP 8 18 101\r\n
a=sendrecv\r\n
a=rtpmap:8 PCMA/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=ptime:20\r\n


[SIP-Packet] 2017/04/23 16:55:32,033  Devicetime: 2017/04/23 16:55:34,827 [Packet]: 
Receiving datagram (860 Bytes) at [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 from [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
SIP/2.0 183 Session Progress\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 101 INVITE\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+536e713b\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-b87b9798-5997cf53\r\n
Require: 100rel\r\n
RSeq: 184911263\r\n
Content-Length: 264\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp;user=phone>\r\n
Content-Type: application/sdp\r\n
Server: DC-SIP/2.0\r\n
\r\n
v=0\r\n
o=- 90821698094207 90821698094207 IN IP6 2001:A60:1:108::10\r\n
s=-\r\n
c=IN IP6 2001:A60:1:108::10\r\n
t=0 0\r\n
m=audio 24454 RTP/AVP 8 18 101\r\n
a=sendrecv\r\n
a=rtpmap:8 PCMA/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=ptime:20\r\n

[SIP-Packet] 2017/04/23 16:55:32,034  Devicetime: 2017/04/23 16:55:34,992 [Packet]: 
Receiving datagram (572 Bytes) at [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 from [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
SIP/2.0 486 Busy Here\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 101 INVITE\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+536e713b\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-b87b9798-5997cf53\r\n
Content-Length: 0\r\n
Supported: from-change, resource-priority, histinfo, 100rel\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp>\r\n
Server: DC-SIP/2.0\r\n
\r\n

[SIP-Packet] 2017/04/23 16:55:32,035  Devicetime: 2017/04/23 16:55:34,993 [Packet]: 
Sending datagram (504 Bytes) from [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 to [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
ACK sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp SIP/2.0\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-b87b9798-5997cf53\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+536e713b\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 101 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: Lancom\r\n
Content-Length: 0\r\n
\r\n
Gerade ist mir auch noch aufgefallen, dass wohl während meiner Tests ein Watchdog im VCM zuschlug. Den packe ich mal in den passenden Thread.

Ich bin für jegliche Hinweise dankbar.

Grüße
booker
Nach oben
Benutzeravatar
MoinMoin
Moderator
Moderator
Beiträge: 1979
Registriert: 12 Nov 2004, 16:04

Re: M-Net, abgehende Gespräche schlagen fehl

Beitrag von MoinMoin »

Moin, moin!

Da möchte M-Net offenbar auch eine Authorisierung für das PrAck:

Code: Alles auswählen

[SIP-Packet] 2017/04/23 16:55:24,371  Devicetime: 2017/04/23 16:55:27,327 [Packet]:
Sending datagram (608 Bytes) from [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 to [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
PRACK sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp;user=phone SIP/2.0\r\n
Via: SIP/2.0/TCP [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769;branch=z9hG4bK-653de24d-2e1ddfaf;rport\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+536e713b\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 102 PRACK\r\n
Max-Forwards: 70\r\n
User-Agent: Yealink SIP-T26P 6.70.13.9\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE\r\n
RAck: 184911263 101 INVITE\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2017/04/23 16:55:24,591  Devicetime: 2017/04/23 16:55:27,349 [Packet]:
Receiving datagram (670 Bytes) at [2001:a61:1003:f900:a0:57ff:fe24:898a]:13769 from [2001:a60:1:8::10]:5060 using TCP (RtgTag 0):
SIP/2.0 401 Unauthorized\r\n
Call-ID: 1320863286@00a05724898a\r\n
CSeq: 102 PRACK\r\n
From: <sip:<M-Net-Nummer>@phone.mnet-voip.de;user=phone>;tag=1614457766--2005739083\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+1+18780006+536e713b\r\n
Via: SIP/2.0/TCP [2001:A61:1003:F900:A0:57FF:FE24:898A]:13769;received=2001:A61:1003:F900:A0:57FF:FE24:898A;rport=13769;branch=z9hG4bK-653de24d-2e1ddfaf\r\n
Content-Length: 0\r\n
Supported: resource-priority, siprec, 100rel\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:8::10]:5060;transport=tcp>\r\n
WWW-Authenticate: Digest realm="phone.mnet-voip.de",nonce="b23db34b6911",stale=false,algorithm=MD5,qop="auth"\r\n
Server: DC-SIP/2.0\r\n
\r\n
Macht das LANCOM aber nicht. Danach kommt dann alles durcheinander.

Ciao, Georg
Nach oben
Benutzeravatar
MoinMoin
Moderator
Moderator
Beiträge: 1979
Registriert: 12 Nov 2004, 16:04

Re: M-Net, abgehende Gespräche schlagen fehl

Beitrag von MoinMoin »

Moin, moin!

Sollte mit der aktuellen Beta behoben sein.

Ciao, Georg
Nach oben
booker
Beiträge: 100
Registriert: 01 Aug 2005, 16:05

Re: M-Net, abgehende Gespräche schlagen fehl

Beitrag von booker »

Hallo Georg,

danke für die Info und die schnelle Lösung. Morgen Abend sollte ich Zeit haben um die aktuelle Beta mal auf das Gerät zu laden. Ich werde berichten.

Gruß
booker
Nach oben
Benutzeravatar
MoinMoin
Moderator
Moderator
Beiträge: 1979
Registriert: 12 Nov 2004, 16:04

Re: M-Net, abgehende Gespräche schlagen fehl

Beitrag von MoinMoin »

Moin, moin!

Ist nicht mein Verdienst. Ich hab es nur weitergemeldet.

Ciao, Georg
Nach oben
booker
Beiträge: 100
Registriert: 01 Aug 2005, 16:05

Re: M-Net, abgehende Gespräche schlagen fehl

Beitrag von booker »

Hallo Georg,

habe gerade mit der LCOS10.00.0221 von heute Nacht getestet. Leider ohne nennenswerten Erfolg. Man sieht zwar nun den geänderten PrAck, aber der "403 FORBIDDEN" kommt dann doch noch. Den Trace, nun mit der Beta, packe ich hier nochmal mit rein.

Der Watchdog im VCM (http://www.lancom-forum.de/aktuelle-lan ... 16009.html) scheint hier aber auch irgendwie mit dran zu hängen. Nach meinen Versuchen vom Wochenende die alle ca. 18 Minuten mit einem Watchdog "unterbrochen" wurden hatte ich die M-Net-Leitung wieder deaktiviert (und auch die weitere Leitung die versuchsweise TCP statt UDP nutzte wieder auf UDP zurück gestellt) und die Watchdogs waren weg, bis heute. Gleich nach der Aktivierung für den Test mit der Beta fand ich den Watchdog wieder im Trace. Habe nun die M-Net-Leitung wieder deaktiviert und hoffe, dass jetzt wieder alles stabil läuft.

Wenn ich mit einem zusätzlichem, umfangreicheren usw. Trace bei der Problemsuche/-lösung behilflich sein kann, dann lasst es mich wissen, ich helfe gerne.

Gruß
booker

Code: Alles auswählen

[SIP-Packet] 2017/04/25 19:31:00,936  Devicetime: 2017/04/25 19:31:00,682 [Packet]: 
Sending datagram (1306 Bytes) from [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 to [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
INVITE sip:<Ziel-Rufnummer>@phone.mnet-voip.de SIP/2.0\r\n
Via: SIP/2.0/UDP [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701;branch=z9hG4bK-c5ea61e2-0916631e;rport\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 100 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: Yealink SIP-T26P 6.70.13.9\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE\r\n
Supported: 100rel\r\n
Contact: <sip:<M-Net-Rufnummer>@[2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701;transport=UDP>\r\n
Authorization: Digest username="<M-Net-Rufnummer>", realm="phone.mnet-voip.de", algorithm=MD5, uri="sip:<Ziel-Rufnummer>@phone.mnet-voip.de", nonce="b24cb32a68ff",qop=auth, cnonce="161fa4ce0b0fd267", nc=00000002, response="5a4c8294807be85c7b0d971c9ba862ee"\r\n
Content-Type: application/sdp\r\n
Content-Length: 413\r\n
\r\n
v=0\r\n
o=- 742345116 742345116 IN IP6 2001:a61:10f0:cc00:a0:57ff:fe24:898a\r\n
s=call\r\n
c=IN IP6 2001:a61:10f0:cc00:a0:57ff:fe24:898a\r\n
t=0 0\r\n
m=audio 61956 RTP/AVP 9 8 18 4 112 0 101\r\n
a=rtpmap:9 G722/8000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=rtpmap:4 G723/8000\r\n
a=rtpmap:112 G726-16/8000\r\n
a=rtpmap:0 PCMU/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=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2017/04/25 19:31:01,136  Devicetime: 2017/04/25 19:31:00,700 [Packet]: 
Receiving datagram (418 Bytes) at [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 from [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 100 INVITE\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+4+698f0000+b8cdedd8\r\n
Via: SIP/2.0/UDP [2001:A61:10F0:CC00:A0:57FF:FE24:898A]:58701;received=2001:A61:10F0:CC00:A0:57FF:FE24:898A;rport=58701;branch=z9hG4bK-c5ea61e2-0916631e\r\n
Server: SIP/2.0\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2017/04/25 19:31:03,296  Devicetime: 2017/04/25 19:31:03,040 [Packet]: 
Receiving datagram (849 Bytes) at [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 from [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
SIP/2.0 183 Session Progress\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 100 INVITE\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+4+698f0000+b8cdedd8\r\n
Via: SIP/2.0/UDP [2001:A61:10F0:CC00:A0:57FF:FE24:898A]:58701;received=2001:A61:10F0:CC00:A0:57FF:FE24:898A;rport=58701;branch=z9hG4bK-c5ea61e2-0916631e\r\n
Require: 100rel\r\n
RSeq: 1023070323\r\n
Content-Length: 266\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:7::10]:5060;user=phone>\r\n
Content-Type: application/sdp\r\n
Server: DC-SIP/2.0\r\n
\r\n
v=0\r\n
o=- 126534533299304 126534533299304 IN IP6 2001:A60:1:107::10\r\n
s=-\r\n
c=IN IP6 2001:A60:1:107::10\r\n
t=0 0\r\n
m=audio 31580 RTP/AVP 8 18 101\r\n
a=sendrecv\r\n
a=rtpmap:8 PCMA/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=ptime:20\r\n

[SIP-Packet] 2017/04/25 19:31:03,296  Devicetime: 2017/04/25 19:31:03,040 [Packet]: 
Sending datagram (844 Bytes) from [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 to [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
PRACK sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:7::10]:5060;user=phone SIP/2.0\r\n
Via: SIP/2.0/UDP [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701;branch=z9hG4bK-950b236f-1ef938d4;rport\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+4+698f0000+b8cdedd8\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 101 PRACK\r\n
Max-Forwards: 70\r\n
User-Agent: Yealink SIP-T26P 6.70.13.9\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE\r\n
Authorization: Digest username="<M-Net-Rufnummer>", realm="phone.mnet-voip.de", algorithm=MD5, uri="sip:<Ziel-Rufnummer>@phone.mnet-voip.de", nonce="b24cb32a68ff",qop=auth, cnonce="161fa4ce0b0fd267", nc=00000002, response="5a4c8294807be85c7b0d971c9ba862ee"\r\n
RAck: 1023070323 100 INVITE\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2017/04/25 19:31:03,378  Devicetime: 2017/04/25 19:31:03,060 [Packet]: 
Receiving datagram (656 Bytes) at [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 from [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
SIP/2.0 401 Unauthorized\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 101 PRACK\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+4+698f0000+b8cdedd8\r\n
Via: SIP/2.0/UDP [2001:A61:10F0:CC00:A0:57FF:FE24:898A]:58701;received=2001:A61:10F0:CC00:A0:57FF:FE24:898A;rport=58701;branch=z9hG4bK-950b236f-1ef938d4\r\n
Content-Length: 0\r\n
Supported: resource-priority, siprec, 100rel\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:7::10]:5060>\r\n
WWW-Authenticate: Digest realm="phone.mnet-voip.de",nonce="b24cbb847159",stale=false,algorithm=MD5,qop="auth"\r\n
Server: DC-SIP/2.0\r\n
\r\n

[SIP-Packet] 2017/04/25 19:31:03,378  Devicetime: 2017/04/25 19:31:03,061 [Packet]: 
Sending datagram (469 Bytes) from [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 to [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
ACK sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:7::10]:5060;user=phone SIP/2.0\r\n
Via: SIP/2.0/UDP [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701;branch=z9hG4bK-c5ea61e2-0916631e;rport\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+4+698f0000+b8cdedd8\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 100 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: Yealink SIP-T26P 6.70.13.9\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2017/04/25 19:31:03,378  Devicetime: 2017/04/25 19:31:03,062 [Packet]: 
Sending datagram (1369 Bytes) from [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 to [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
INVITE sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:7::10]:5060;user=phone SIP/2.0\r\n
Via: SIP/2.0/UDP [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701;branch=z9hG4bK-3aa80225-a2a463d2;rport\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 102 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: Yealink SIP-T26P 6.70.13.9\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE\r\n
Supported: 100rel\r\n
Authorization: Digest username="<M-Net-Rufnummer>", realm="phone.mnet-voip.de", algorithm=MD5, uri="sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:7::10]:5060", nonce="b24cbb847159",qop=auth, cnonce="50b58c1a285ac60d", nc=00000001, response="e72542c84e74d56782ac0fe8c80b5124"\r\n
Contact: <sip:<M-Net-Rufnummer>@[2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701;transport=UDP>\r\n
Content-Type: application/sdp\r\n
Content-Length: 413\r\n
\r\n
v=0\r\n
o=- 742345116 742345116 IN IP6 2001:a61:10f0:cc00:a0:57ff:fe24:898a\r\n
s=call\r\n
c=IN IP6 2001:a61:10f0:cc00:a0:57ff:fe24:898a\r\n
t=0 0\r\n
m=audio 61956 RTP/AVP 9 8 18 4 112 0 101\r\n
a=rtpmap:9 G722/8000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=rtpmap:4 G723/8000\r\n
a=rtpmap:112 G726-16/8000\r\n
a=rtpmap:0 PCMU/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=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2017/04/25 19:31:03,378  Devicetime: 2017/04/25 19:31:03,079 [Packet]: 
Receiving datagram (418 Bytes) at [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 from [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 102 INVITE\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+4+698f0000+3f301932\r\n
Via: SIP/2.0/UDP [2001:A61:10F0:CC00:A0:57FF:FE24:898A]:58701;received=2001:A61:10F0:CC00:A0:57FF:FE24:898A;rport=58701;branch=z9hG4bK-3aa80225-a2a463d2\r\n
Server: SIP/2.0\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2017/04/25 19:31:03,379  Devicetime: 2017/04/25 19:31:03,124 [Packet]: 
Receiving datagram (464 Bytes) at [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 from [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
SIP/2.0 403 Forbidden\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 102 INVITE\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+4+698f0000+3f301932\r\n
Via: SIP/2.0/UDP [2001:A61:10F0:CC00:A0:57FF:FE24:898A]:58701;received=2001:A61:10F0:CC00:A0:57FF:FE24:898A;rport=58701;branch=z9hG4bK-3aa80225-a2a463d2\r\n
Content-Length: 0\r\n
Contact: <sip:[2001:A60:1:7::10]:5060>\r\n
Server: DC-SIP/2.0\r\n
\r\n

[SIP-Packet] 2017/04/25 19:31:03,379  Devicetime: 2017/04/25 19:31:03,125 [Packet]: 
Sending datagram (469 Bytes) from [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 to [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
ACK sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:7::10]:5060;user=phone SIP/2.0\r\n
Via: SIP/2.0/UDP [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701;branch=z9hG4bK-3aa80225-a2a463d2;rport\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+4+698f0000+3f301932\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 102 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: Yealink SIP-T26P 6.70.13.9\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2017/04/25 19:31:03,993  Devicetime: 2017/04/25 19:31:03,540 [Packet]: 
Receiving datagram (849 Bytes) at [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 from [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
SIP/2.0 183 Session Progress\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 100 INVITE\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+4+698f0000+b8cdedd8\r\n
Via: SIP/2.0/UDP [2001:A61:10F0:CC00:A0:57FF:FE24:898A]:58701;received=2001:A61:10F0:CC00:A0:57FF:FE24:898A;rport=58701;branch=z9hG4bK-c5ea61e2-0916631e\r\n
Require: 100rel\r\n
RSeq: 1023070323\r\n
Content-Length: 266\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:7::10]:5060;user=phone>\r\n
Content-Type: application/sdp\r\n
Server: DC-SIP/2.0\r\n
\r\n
v=0\r\n
o=- 126534533299304 126534533299304 IN IP6 2001:A60:1:107::10\r\n
s=-\r\n
c=IN IP6 2001:A60:1:107::10\r\n
t=0 0\r\n
m=audio 31580 RTP/AVP 8 18 101\r\n
a=sendrecv\r\n
a=rtpmap:8 PCMA/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=ptime:20\r\n

[SIP-Packet] 2017/04/25 19:31:04,993  Devicetime: 2017/04/25 19:31:04,540 [Packet]: 
Receiving datagram (849 Bytes) at [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 from [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
SIP/2.0 183 Session Progress\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 100 INVITE\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+4+698f0000+b8cdedd8\r\n
Via: SIP/2.0/UDP [2001:A61:10F0:CC00:A0:57FF:FE24:898A]:58701;received=2001:A61:10F0:CC00:A0:57FF:FE24:898A;rport=58701;branch=z9hG4bK-c5ea61e2-0916631e\r\n
Require: 100rel\r\n
RSeq: 1023070323\r\n
Content-Length: 266\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:7::10]:5060;user=phone>\r\n
Content-Type: application/sdp\r\n
Server: DC-SIP/2.0\r\n
\r\n
v=0\r\n
o=- 126534533299304 126534533299304 IN IP6 2001:A60:1:107::10\r\n
s=-\r\n
c=IN IP6 2001:A60:1:107::10\r\n
t=0 0\r\n
m=audio 31580 RTP/AVP 8 18 101\r\n
a=sendrecv\r\n
a=rtpmap:8 PCMA/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=ptime:20\r\n

[SIP-Packet] 2017/04/25 19:31:06,993  Devicetime: 2017/04/25 19:31:06,540 [Packet]: 
Receiving datagram (849 Bytes) at [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 from [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
SIP/2.0 183 Session Progress\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 100 INVITE\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+4+698f0000+b8cdedd8\r\n
Via: SIP/2.0/UDP [2001:A61:10F0:CC00:A0:57FF:FE24:898A]:58701;received=2001:A61:10F0:CC00:A0:57FF:FE24:898A;rport=58701;branch=z9hG4bK-c5ea61e2-0916631e\r\n
Require: 100rel\r\n
RSeq: 1023070323\r\n
Content-Length: 266\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:7::10]:5060;user=phone>\r\n
Content-Type: application/sdp\r\n
Server: DC-SIP/2.0\r\n
\r\n
v=0\r\n
o=- 126534533299304 126534533299304 IN IP6 2001:A60:1:107::10\r\n
s=-\r\n
c=IN IP6 2001:A60:1:107::10\r\n
t=0 0\r\n
m=audio 31580 RTP/AVP 8 18 101\r\n
a=sendrecv\r\n
a=rtpmap:8 PCMA/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=ptime:20\r\n


[SIP-Packet] 2017/04/25 19:31:10,764  Devicetime: 2017/04/25 19:31:10,510 [Packet]: 
Receiving datagram (558 Bytes) at [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 from [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
SIP/2.0 486 Busy Here\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 100 INVITE\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+4+698f0000+b8cdedd8\r\n
Via: SIP/2.0/UDP [2001:A61:10F0:CC00:A0:57FF:FE24:898A]:58701;received=2001:A61:10F0:CC00:A0:57FF:FE24:898A;rport=58701;branch=z9hG4bK-c5ea61e2-0916631e\r\n
Content-Length: 0\r\n
Supported: from-change, resource-priority, histinfo, 100rel\r\n
Contact: <sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:7::10]:5060>\r\n
Server: DC-SIP/2.0\r\n
\r\n

[SIP-Packet] 2017/04/25 19:31:10,764  Devicetime: 2017/04/25 19:31:10,510 [Packet]: 
Sending datagram (490 Bytes) from [2001:a61:10f0:cc00:a0:57ff:fe24:898a]:58701 to [2001:a60:1:7::10]:5060 using UDP (RtgTag 0):
ACK sip:711c3c1cfd72a6a014dd8dd4b1550654@[2001:A60:1:7::10]:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP [2001:A61:10F0:CC00:A0:57FF:FE24:898A]:58701;received=2001:A61:10F0:CC00:A0:57FF:FE24:898A;rport=58701;branch=z9hG4bK-c5ea61e2-0916631e\r\n
From: <sip:<M-Net-Rufnummer>@phone.mnet-voip.de;user=phone>;tag=-1490530601-1203138810\r\n
To: <sip:<Ziel-Rufnummer>@phone.mnet-voip.de>;tag=sip+4+698f0000+b8cdedd8\r\n
Call-ID: 1484690232@00a05724898a\r\n
CSeq: 100 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: Lancom\r\n
Content-Length: 0\r\n
\r\n
Nach oben
Dr.Einstein
Beiträge: 2920
Registriert: 12 Jan 2010, 14:10

Re: M-Net, abgehende Gespräche schlagen fehl

Beitrag von Dr.Einstein »

Hi booker,

hatten das Problem auch, sollte jetzt mit der 9.24RU5 gefixt sein.

Gruß Dr.Einstein
Nach oben
Benutzeravatar
Jirka
Beiträge: 5225
Registriert: 03 Jan 2005, 13:39
Wohnort: Ex-OPAL-Gebiet
Kontaktdaten:
Kontaktdaten von Jirka

Re: M-Net, abgehende Gespräche schlagen fehl

Beitrag von Jirka »

Dr.Einstein hat geschrieben:hatten das Problem auch, sollte jetzt mit der 9.24RU5 gefixt sein.
Nachdem hier der nächste von der 9.24-RU5 geschrieben hat, war ich mir ziemlich sicher, ich habe Tomaten auf den Augen. Jedoch: Unter Releases findet man bei entsprechenden Geräten die 9.24-RU4 und im Archiv die 9.24-RU5? Verstehe das wer will - ich kapiere es nicht.

Viele Grüße,
Jirka
Nach oben
Antworten

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