VOIP-Router 1724 - Probleme mit Verbindungsabbrüchen VOIP

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

Moderator: Lancom-Systems Moderatoren

Antworten
protec
Beiträge: 18
Registriert: 03 Sep 2009, 14:58

VOIP-Router 1724 - Probleme mit Verbindungsabbrüchen VOIP

Beitrag von protec »

Hi Forum,

wir haben einen 1724 im Einsatz, der an 2 NTBA's hängt und an 2 VOIP-Leitungen von 1&1, der Router dient als Gateway / Trunk für eine 3CX VOIP-Anlage.
Leider häufen sich in letzter Zeit die Verbindungsabbrüche bei Telefonaten, die defaultmäßig über die VOIP-Leitungen gehen. An der 3CX sieht das wie ein "normales" Auflegen aus.

Nach Recherche könnte es vielleicht etwas mit aktiviertem SIP-ALG zu tun haben. Leider lässt sich das weder über den LANCONFIG, Telnet oder HTTP im Menü des 1724 sehen. Wie kann ich prüfen ob das ein- oder ausgeschaltet ist ?

Hat irgendjemand im Forum ähnliche Probleme ?

Dankbar für alle Hinweise :shock:
Nach oben
ua
Beiträge: 762
Registriert: 29 Apr 2005, 12:29

Re: VOIP-Router 1724 - Probleme mit Verbindungsabbrüchen VOI

Beitrag von ua »

Hi,
schau mal im LOG der 3CX ob Verbindungsabfragen ggf. in einen Time-out laufen.
Bei mir ist ähnlich (nur das die Verbindungen nicht auf dem LC terminiert werden):
http://www.lancom-forum.de/aktuelle-lan ... 13267.html

Viele Grüße

Udo
... das Netz ist der Computer ...
n* LC und vieles mehr...
Nach oben
backslash
Moderator
Moderator
Beiträge: 7129
Registriert: 08 Nov 2004, 21:26
Wohnort: Aachen

Re: VOIP-Router 1724 - Probleme mit Verbindungsabbrüchen VOI

Beitrag von backslash »

Hi protec

der 1724 hat kein SIP-ALG, weil es ja den Callmanager hat...

Gruß
Backslash
Nach oben
protec
Beiträge: 18
Registriert: 03 Sep 2009, 14:58

Re: VOIP-Router 1724 - Probleme mit Verbindungsabbrüchen VOI

Beitrag von protec »

Hi Udo,

danke für den Hinweis - leider lässt sich im Log der 3CX nichts herausfinden - hier taucht ein normales "Call terminated normally" auf.

@backslash - ok - dann wundert mich nicht dass der Menüpunkt nicht auftaucht - gibt es sonst eine Möglichkeit hier herauszufinden was der Lancom mit den Gesprächen macht ?

bin so langsam ratlos :G)

Gruß,
Markus
Nach oben
cpuprofi
Beiträge: 1365
Registriert: 12 Jun 2009, 12:44
Wohnort: Bremen

Re: VOIP-Router 1724 - Probleme mit Verbindungsabbrüchen VOI

Beitrag von cpuprofi »

Hallo Markus,
protec hat geschrieben:...gibt es sonst eine Möglichkeit hier herauszufinden was der Lancom mit den Gesprächen macht...
mache mal einen SIP-Paket Trace, dann siehst Du was mit den Paketen passiert.

Grüße
Cpuprofi
Nach oben
protec
Beiträge: 18
Registriert: 03 Sep 2009, 14:58

Re: VOIP-Router 1724 - Probleme mit Verbindungsabbrüchen VOI

Beitrag von protec »

Hi cpuprofi,

bin diese Woche außer Haus - werde das nächste Woche mal machen.
SIP-Trace - über den Lanmonitor ? was muss ich dann genau anhaken ?

Gruß,
Markus
Nach oben
cpuprofi
Beiträge: 1365
Registriert: 12 Jun 2009, 12:44
Wohnort: Bremen

Re: VOIP-Router 1724 - Probleme mit Verbindungsabbrüchen VOI

Beitrag von cpuprofi »

Hallo Markus,

LANconfig und im Trace SIP-PAKET anklicken.

Grüße
Cpuprofi
Nach oben
protec
Beiträge: 18
Registriert: 03 Sep 2009, 14:58

Re: VOIP-Router 1724 - Probleme mit Verbindungsabbrüchen VOI

Beitrag von protec »

so - hier ist der Trace bei Verbindungsabbruch - wäre klasse wenn hier irgendjemand sieht was den Fehler verursacht

Legende:
UNSERENR
GEWÄHLTENR
VOIPPROVIDER
LANCOMROUTER
3CXSRV

Fehler : "temporary failure"

Trace:

[SIP-Packet] 2014/05/05 11:03:53,268 Devicetime: 2014/05/05 11:06:05,935 [PACKET] :
Receiving datagram with length 1009 from 3CXSRV:5060 to LANCOMROUTER:5060
INVITE sip:GEWÄHLTENR@LANCOMROUTER:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 3CXSRV:5060;branch=z9hG4bK-d8754z-7a10d5042179df36-1---d8754z-;rport\r\n
Max-Forwards: 70\r\n
Contact: <sip:20001@3CXSRV:5060>\r\n
To: <sip:GEWÄHLTENR@LANCOMROUTER:5060>\r\n
From: "Stefanie Hayer"<sip:20001@3CXSRV:5060>;tag=d308e470\r\n
Call-ID: ZGQ5ZWUxYTdlMGQ5NDYwZWIxNWMwMDZhZmFlZjQ5MzA.\r\n
CSeq: 1 INVITE\r\n
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE\r\n
Content-Type: application/sdp\r\n
Supported: replaces\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Content-Length: 406\r\n
\r\n
v=0\r\n
o=3cxPS 221207592960 446777262081 IN IP4 3CXSRV\r\n
s=3cxPS Audio call\r\n
c=IN IP4 3CXSRV\r\n
t=0 0\r\n
m=audio 7192 RTP/AVP 0 8 3 13 9 18 110 99 101\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:3 GSM/8000\r\n
a=rtpmap:13 CN/8000\r\n
a=rtpmap:9 G722/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=fmtp:18 annexb=no\r\n
a=rtpmap:110 iLBC/8000\r\n
a=rtpmap:99 SPEEX/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=sendrecv\r\n

[SIP-Packet] 2014/05/05 11:03:53,268 Devicetime: 2014/05/05 11:06:05,938 [PACKET] :
Sending datagram with length 433 from LANCOMROUTER:5060 to 3CXSRV:5060
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 3CXSRV:5060;branch=z9hG4bK-d8754z-7a10d5042179df36-1---d8754z-;rport\r\n
From: "Stefanie Hayer"<sip:20001@3CXSRV>;tag=d308e470\r\n
To: <sip:GEWÄHLTENR@LANCOMROUTER>;tag=935451725-2068621776\r\n
Call-ID: ZGQ5ZWUxYTdlMGQ5NDYwZWIxNWMwMDZhZmFlZjQ5MzA.\r\n
CSeq: 1 INVITE\r\n
Max-Forwards: 70\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:03:53,331 Devicetime: 2014/05/05 11:06:05,964 [PACKET] :
Sending datagram with length 976 from 84.146.124.108:50452 to 212.227.67.202:5060
INVITE sip:GEWÄHLTENR@VOIPPROVIDER.de SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-52d367bd-f0a8af8b\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 1 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Contact: <sip:UNSERENR@84.146.124.108:50452>\r\n
P-Asserted-Identity: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>\r\n
Content-Type: application/sdp\r\n
Content-Length: 388\r\n
\r\n
v=0\r\n
o=- 4250812250 4250812250 IN IP4 84.146.124.108\r\n
s=call\r\n
c=IN IP4 84.146.124.108\r\n
t=0 0\r\n
m=audio 8798 RTP/AVP 9 8 0 110 18 3 13 99 101\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:110 iLBC/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=rtpmap:3 GSM/8000\r\n
a=rtpmap:13 CN/8000\r\n
a=rtpmap:99 speex/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:18 annexb=no\r\n
a=sendrecv\r\n


[SIP-Packet] 2014/05/05 11:03:53,362 Devicetime: 2014/05/05 11:06:06,004 [PACKET] :
Receiving datagram with length 441 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 407 Proxy Authentication Required\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-52d367bd-f0a8af8b\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=b27e1a1d33761e85846fc98f5f3a7e58.b169\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 1 INVITE\r\n
Proxy-Authenticate: Digest realm="VOIPPROVIDER.de", nonce="U2dVplNnVHrdq/0XYOxTh4zEHdU7Pybv"\r\n
Server: UI Kamailio\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:03:53,362 Devicetime: 2014/05/05 11:06:06,005 [PACKET] :
Sending datagram with length 480 from 84.146.124.108:50452 to 212.227.67.202:5060
ACK sip:GEWÄHLTENR@VOIPPROVIDER.de SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-52d367bd-f0a8af8b\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=b27e1a1d33761e85846fc98f5f3a7e58.b169\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 1 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:03:53,362 Devicetime: 2014/05/05 11:06:06,009 [PACKET] :
Sending datagram with length 1177 from 84.146.124.108:50452 to 212.227.67.202:5060
INVITE sip:GEWÄHLTENR@VOIPPROVIDER.de SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Proxy-Authorization: Digest username="UNSERENR",realm="VOIPPROVIDER.de",nonce="U2dVplNnVHrdq/0XYOxTh4zEHdU7Pybv",uri="sip:GEWÄHLTENR@VOIPPROVIDER.de",algorithm=MD5,response="40c693009b43b89332b6b5c4d00461db"\r\n
Contact: <sip:UNSERENR@84.146.124.108:50452>\r\n
P-Asserted-Identity: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>\r\n
Content-Type: application/sdp\r\n
Content-Length: 388\r\n
\r\n
v=0\r\n
o=- 2125406125 2125406125 IN IP4 84.146.124.108\r\n
s=call\r\n
c=IN IP4 84.146.124.108\r\n
t=0 0\r\n
m=audio 8798 RTP/AVP 9 8 0 110 18 3 13 99 101\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:110 iLBC/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=rtpmap:3 GSM/8000\r\n
a=rtpmap:13 CN/8000\r\n
a=rtpmap:99 speex/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:18 annexb=no\r\n
a=sendrecv\r\n

[SIP-Packet] 2014/05/05 11:03:53,362 Devicetime: 2014/05/05 11:06:06,056 [PACKET] :
Receiving datagram with length 321 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 100 trying -- your call is important to us\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Server: UI Kamailio\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:03:54,626 Devicetime: 2014/05/05 11:06:07,278 [PACKET] :
Receiving datagram with length 848 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 183 Session Progress\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on;did=16b.6d8ef183>\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Contact: <sip:GEWÄHLTENR@89.246.79.44:5060;user=phone;transport=udp>\r\n
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER\r\n
Content-Length: 207\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=HuaweiSoftX3000 32566680 32566680 IN IP4 89.246.79.44\r\n
s=Sip Call\r\n
c=IN IP4 89.246.79.44\r\n
t=0 0\r\n
m=audio 45974 RTP/AVP 8 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n

[SIP-Packet] 2014/05/05 11:03:54,626 Devicetime: 2014/05/05 11:06:07,286 [PACKET] :
Sending datagram with length 728 from LANCOMROUTER:5060 to 3CXSRV:5060
SIP/2.0 183 Session Progress\r\n
Via: SIP/2.0/UDP 3CXSRV:5060;branch=z9hG4bK-d8754z-7a10d5042179df36-1---d8754z-;rport\r\n
From: "Stefanie Hayer"<sip:20001@3CXSRV>;tag=d308e470\r\n
To: <sip:GEWÄHLTENR@LANCOMROUTER>;tag=935451725-2068621776\r\n
Call-ID: ZGQ5ZWUxYTdlMGQ5NDYwZWIxNWMwMDZhZmFlZjQ5MzA.\r\n
CSeq: 1 INVITE\r\n
Max-Forwards: 70\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Contact: <sip:GEWÄHLTENR@LANCOMROUTER:5060>\r\n
Content-Type: application/sdp\r\n
Content-Length: 205\r\n
\r\n
v=0\r\n
o=- 1769440891 1769440891 IN IP4 LANCOMROUTER\r\n
s=call\r\n
c=IN IP4 LANCOMROUTER\r\n
t=0 0\r\n
m=audio 10612 RTP/AVP 8 101\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

[SIP-Packet] 2014/05/05 11:03:55,374 Devicetime: 2014/05/05 11:06:07,775 [PACKET] :
Receiving datagram with length 599 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 180 Ringing\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on;did=16b.6d8ef183>\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER\r\n
Contact: <sip:GEWÄHLTENR@89.246.79.44:5060;user=phone;transport=udp>\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:03:55,374 Devicetime: 2014/05/05 11:06:07,786 [PACKET] :
Sending datagram with length 434 from LANCOMROUTER:5060 to 3CXSRV:5060
SIP/2.0 180 Ringing\r\n
Via: SIP/2.0/UDP 3CXSRV:5060;branch=z9hG4bK-d8754z-7a10d5042179df36-1---d8754z-;rport\r\n
From: "Stefanie Hayer"<sip:20001@3CXSRV>;tag=d308e470\r\n
To: <sip:GEWÄHLTENR@LANCOMROUTER>;tag=935451725-2068621776\r\n
Call-ID: ZGQ5ZWUxYTdlMGQ5NDYwZWIxNWMwMDZhZmFlZjQ5MzA.\r\n
CSeq: 1 INVITE\r\n
Max-Forwards: 70\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:09,743 Devicetime: 2014/05/05 11:06:22,416 [PACKET] :
Receiving datagram with length 738 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on;did=16b.6d8ef183>\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Contact: <sip:GEWÄHLTENR@89.246.79.44:5060;user=phone;transport=udp>\r\n
Content-Length: 207\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=HuaweiSoftX3000 32566680 32566681 IN IP4 89.246.79.44\r\n
s=Sip Call\r\n
c=IN IP4 89.246.79.44\r\n
t=0 0\r\n
m=audio 45974 RTP/AVP 8 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n

[SIP-Packet] 2014/05/05 11:04:09,743 Devicetime: 2014/05/05 11:06:22,430 [PACKET] :
Sending datagram with length 708 from LANCOMROUTER:5060 to 3CXSRV:5060
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 3CXSRV:5060;branch=z9hG4bK-d8754z-7a10d5042179df36-1---d8754z-;rport\r\n
From: "Stefanie Hayer"<sip:20001@3CXSRV>;tag=d308e470\r\n
To: <sip:GEWÄHLTENR@LANCOMROUTER>;tag=935451725-2068621776\r\n
Call-ID: ZGQ5ZWUxYTdlMGQ5NDYwZWIxNWMwMDZhZmFlZjQ5MzA.\r\n
CSeq: 1 INVITE\r\n
Max-Forwards: 70\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Contact: <sip:20000@LANCOMROUTER:26709>\r\n
Content-Type: application/sdp\r\n
Content-Length: 205\r\n
\r\n
v=0\r\n
o=- 1084002711 1084002711 IN IP4 LANCOMROUTER\r\n
s=call\r\n
c=IN IP4 LANCOMROUTER\r\n
t=0 0\r\n
m=audio 10612 RTP/AVP 8 101\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

[SIP-Packet] 2014/05/05 11:04:09,883 Devicetime: 2014/05/05 11:06:22,559 [PACKET] :
Receiving datagram with length 459 from 3CXSRV:5060 to LANCOMROUTER:26709
ACK sip:20000@LANCOMROUTER:26709 SIP/2.0\r\n
Via: SIP/2.0/UDP 3CXSRV:5060;branch=z9hG4bK-d8754z-880de627e6063463-1---d8754z-;rport\r\n
Max-Forwards: 70\r\n
Contact: <sip:20001@3CXSRV:5060>\r\n
To: <sip:GEWÄHLTENR@LANCOMROUTER>;tag=935451725-2068621776\r\n
From: "Stefanie Hayer"<sip:20001@3CXSRV>;tag=d308e470\r\n
Call-ID: ZGQ5ZWUxYTdlMGQ5NDYwZWIxNWMwMDZhZmFlZjQ5MzA.\r\n
CSeq: 1 ACK\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:09,883 Devicetime: 2014/05/05 11:06:22,563 [PACKET] :
Sending datagram with length 603 from 84.146.124.108:50452 to 212.227.67.202:5060
ACK sip:GEWÄHLTENR@89.246.79.44:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-4fa9ba64-93200c9a\r\n
Route: <SIP:212.227.67.198:5060;lr=on>\r\n
Route: <SIP:212.227.67.226:5060;lr=on;did=16b.6d8ef183>\r\n
Route: <SIP:212.227.67.202:5060;lr=on>\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:10,242 Devicetime: 2014/05/05 11:06:22,916 [PACKET] :
Receiving datagram with length 738 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on;did=16b.6d8ef183>\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Contact: <sip:GEWÄHLTENR@89.246.79.44:5060;user=phone;transport=udp>\r\n
Content-Length: 207\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=HuaweiSoftX3000 32566680 32566681 IN IP4 89.246.79.44\r\n
s=Sip Call\r\n
c=IN IP4 89.246.79.44\r\n
t=0 0\r\n
m=audio 45974 RTP/AVP 8 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n

[SIP-Packet] 2014/05/05 11:04:10,242 Devicetime: 2014/05/05 11:06:22,918 [PACKET] :
Sending datagram with length 603 from 84.146.124.108:50452 to 212.227.67.202:5060
ACK sip:GEWÄHLTENR@89.246.79.44:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-4fa9ba64-93200c9a\r\n
Route: <SIP:212.227.67.198:5060;lr=on>\r\n
Route: <SIP:212.227.67.226:5060;lr=on;did=16b.6d8ef183>\r\n
Route: <SIP:212.227.67.202:5060;lr=on>\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:11,240 Devicetime: 2014/05/05 11:06:23,917 [PACKET] :
Receiving datagram with length 738 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on;did=16b.6d8ef183>\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Contact: <sip:GEWÄHLTENR@89.246.79.44:5060;user=phone;transport=udp>\r\n
Content-Length: 207\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=HuaweiSoftX3000 32566680 32566681 IN IP4 89.246.79.44\r\n
s=Sip Call\r\n
c=IN IP4 89.246.79.44\r\n
t=0 0\r\n
m=audio 45974 RTP/AVP 8 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n

[SIP-Packet] 2014/05/05 11:04:11,240 Devicetime: 2014/05/05 11:06:23,919 [PACKET] :
Sending datagram with length 603 from 84.146.124.108:50452 to 212.227.67.202:5060
ACK sip:GEWÄHLTENR@89.246.79.44:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-4fa9ba64-93200c9a\r\n
Route: <SIP:212.227.67.198:5060;lr=on>\r\n
Route: <SIP:212.227.67.226:5060;lr=on;did=16b.6d8ef183>\r\n
Route: <SIP:212.227.67.202:5060;lr=on>\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:13,237 Devicetime: 2014/05/05 11:06:25,917 [PACKET] :
Receiving datagram with length 738 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on;did=16b.6d8ef183>\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Contact: <sip:GEWÄHLTENR@89.246.79.44:5060;user=phone;transport=udp>\r\n
Content-Length: 207\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=HuaweiSoftX3000 32566680 32566681 IN IP4 89.246.79.44\r\n
s=Sip Call\r\n
c=IN IP4 89.246.79.44\r\n
t=0 0\r\n
m=audio 45974 RTP/AVP 8 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n

[SIP-Packet] 2014/05/05 11:04:13,237 Devicetime: 2014/05/05 11:06:25,919 [PACKET] :
Sending datagram with length 603 from 84.146.124.108:50452 to 212.227.67.202:5060
ACK sip:GEWÄHLTENR@89.246.79.44:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-4fa9ba64-93200c9a\r\n
Route: <SIP:212.227.67.198:5060;lr=on>\r\n
Route: <SIP:212.227.67.226:5060;lr=on;did=16b.6d8ef183>\r\n
Route: <SIP:212.227.67.202:5060;lr=on>\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:13,378 Devicetime: 2014/05/05 11:06:25,949 [PACKET] :
Sending datagram with length 509 from LANCOMROUTER:28689 to 3CXSRV:5060
REGISTER sip:3CXSRV SIP/2.0\r\n
Via: SIP/2.0/UDP LANCOMROUTER:28689;branch=z9hG4bK-31668d81-44d17795\r\n
From: "20001"<sip:20001@3CXSRV>;tag=2061946040--202201304\r\n
To: "20001"<sip:20001@3CXSRV>\r\n
Call-ID: 20001-3CXSRV-9ff3de0e@00a05711fc12\r\n
CSeq: 37103 REGISTER\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Max-Forwards: 70\r\n
Contact: <sip:20001@LANCOMROUTER:28689>\r\n
Expires: 60\r\n
User-Agent: LANCOM 1724 VoIP (Annex B) / 8.84.0132 / 31.01.2014\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:13,378 Devicetime: 2014/05/05 11:06:26,055 [PACKET] :
Receiving datagram with length 501 from 3CXSRV:5060 to LANCOMROUTER:28689
SIP/2.0 407 Proxy Authentication Required\r\n
Via: SIP/2.0/UDP LANCOMROUTER:28689;branch=z9hG4bK-31668d81-44d17795\r\n
Proxy-Authenticate: Digest nonce="414d535c0977e50d90:030f11361ce8ffd46e31249564170fdc",algorithm=MD5,realm="3CXPhoneSystem"\r\n
To: "20001"<sip:20001@3CXSRV>;tag=353f1632\r\n
From: "20001"<sip:20001@3CXSRV>;tag=2061946040--202201304\r\n
Call-ID: 20001-3CXSRV-9ff3de0e@00a05711fc12\r\n
CSeq: 37103 REGISTER\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:13,378 Devicetime: 2014/05/05 11:06:26,057 [PACKET] :
Sending datagram with length 720 from LANCOMROUTER:28689 to 3CXSRV:5060
REGISTER sip:3CXSRV SIP/2.0\r\n
Via: SIP/2.0/UDP LANCOMROUTER:28689;branch=z9hG4bK-266a2b98-f9f789a9\r\n
From: "20001"<sip:20001@3CXSRV>;tag=2061946040--202201304\r\n
To: "20001"<sip:20001@3CXSRV>\r\n
Call-ID: 20001-3CXSRV-9ff3de0e@00a05711fc12\r\n
CSeq: 37104 REGISTER\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Max-Forwards: 70\r\n
Contact: <sip:20001@LANCOMROUTER:28689>\r\n
Expires: 60\r\n
User-Agent: LANCOM 1724 VoIP (Annex B) / 8.84.0132 / 31.01.2014\r\n
Proxy-Authorization: Digest username="20001",realm="3CXPhoneSystem",nonce="414d535c0977e50d90:030f11361ce8ffd46e31249564170fdc",uri="sip:3CXSRV",algorithm=MD5,response="33065779b207c8f7df220c62a23cc9a5"\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:13,580 Devicetime: 2014/05/05 11:06:26,167 [PACKET] :
Receiving datagram with length 401 from 3CXSRV:5060 to LANCOMROUTER:28689
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP LANCOMROUTER:28689;branch=z9hG4bK-266a2b98-f9f789a9\r\n
Contact: <sip:20001@LANCOMROUTER:28689>;expires=60\r\n
To: "20001"<sip:20001@3CXSRV>;tag=9e68355c\r\n
From: "20001"<sip:20001@3CXSRV>;tag=2061946040--202201304\r\n
Call-ID: 20001-3CXSRV-9ff3de0e@00a05711fc12\r\n
CSeq: 37104 REGISTER\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:13,908 Devicetime: 2014/05/05 11:06:26,488 [PACKET] :
Sending datagram with length 509 from LANCOMROUTER:26709 to 3CXSRV:5060
REGISTER sip:3CXSRV SIP/2.0\r\n
Via: SIP/2.0/UDP LANCOMROUTER:26709;branch=z9hG4bK-3a2cb4af-67c0f93c\r\n
From: "20000"<sip:20000@3CXSRV>;tag=793570703--1678348029\r\n
To: "20000"<sip:20000@3CXSRV>\r\n
Call-ID: 20000-3CXSRV-9dc93c0a@00a05711fc12\r\n
CSeq: 37097 REGISTER\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Max-Forwards: 70\r\n
Contact: <sip:20000@LANCOMROUTER:26709>\r\n
Expires: 60\r\n
User-Agent: LANCOM 1724 VoIP (Annex B) / 8.84.0132 / 31.01.2014\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:13,908 Devicetime: 2014/05/05 11:06:26,593 [PACKET] :
Receiving datagram with length 501 from 3CXSRV:5060 to LANCOMROUTER:26709
SIP/2.0 407 Proxy Authentication Required\r\n
Via: SIP/2.0/UDP LANCOMROUTER:26709;branch=z9hG4bK-3a2cb4af-67c0f93c\r\n
Proxy-Authenticate: Digest nonce="414d535c0977e50d64:3a226d5c7ede1c8d75c60cabb26b4b24",algorithm=MD5,realm="3CXPhoneSystem"\r\n
To: "20000"<sip:20000@3CXSRV>;tag=68742c4a\r\n
From: "20000"<sip:20000@3CXSRV>;tag=793570703--1678348029\r\n
Call-ID: 20000-3CXSRV-9dc93c0a@00a05711fc12\r\n
CSeq: 37097 REGISTER\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:13,908 Devicetime: 2014/05/05 11:06:26,595 [PACKET] :
Sending datagram with length 720 from LANCOMROUTER:26709 to 3CXSRV:5060
REGISTER sip:3CXSRV SIP/2.0\r\n
Via: SIP/2.0/UDP LANCOMROUTER:26709;branch=z9hG4bK-f193aeec-95342311\r\n
From: "20000"<sip:20000@3CXSRV>;tag=793570703--1678348029\r\n
To: "20000"<sip:20000@3CXSRV>\r\n
Call-ID: 20000-3CXSRV-9dc93c0a@00a05711fc12\r\n
CSeq: 37098 REGISTER\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Max-Forwards: 70\r\n
Contact: <sip:20000@LANCOMROUTER:26709>\r\n
Expires: 60\r\n
User-Agent: LANCOM 1724 VoIP (Annex B) / 8.84.0132 / 31.01.2014\r\n
Proxy-Authorization: Digest username="20000",realm="3CXPhoneSystem",nonce="414d535c0977e50d64:3a226d5c7ede1c8d75c60cabb26b4b24",uri="sip:3CXSRV",algorithm=MD5,response="bd508b90afecab2850c12bd0fa6686d2"\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:14,126 Devicetime: 2014/05/05 11:06:26,704 [PACKET] :
Receiving datagram with length 401 from 3CXSRV:5060 to LANCOMROUTER:26709
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP LANCOMROUTER:26709;branch=z9hG4bK-f193aeec-95342311\r\n
Contact: <sip:20000@LANCOMROUTER:26709>;expires=60\r\n
To: "20000"<sip:20000@3CXSRV>;tag=7f441871\r\n
From: "20000"<sip:20000@3CXSRV>;tag=793570703--1678348029\r\n
Call-ID: 20000-3CXSRV-9dc93c0a@00a05711fc12\r\n
CSeq: 37098 REGISTER\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:17,231 Devicetime: 2014/05/05 11:06:29,917 [PACKET] :
Receiving datagram with length 739 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:+UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on;did=16b.6d8ef183>\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Contact: <sip:GEWÄHLTENR@89.246.79.44:5060;user=phone;transport=udp>\r\n
Content-Length: 207\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=HuaweiSoftX3000 32566680 32566681 IN IP4 89.246.79.44\r\n
s=Sip Call\r\n
c=IN IP4 89.246.79.44\r\n
t=0 0\r\n
m=audio 45974 RTP/AVP 8 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n

[SIP-Packet] 2014/05/05 11:04:17,231 Devicetime: 2014/05/05 11:06:29,918 [PACKET] :
Sending datagram with length 603 from 84.146.124.108:50452 to 212.227.67.202:5060
ACK sip:GEWÄHLTENR@89.246.79.44:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-4fa9ba64-93200c9a\r\n
Route: <SIP:212.227.67.198:5060;lr=on>\r\n
Route: <SIP:212.227.67.226:5060;lr=on;did=16b.6d8ef183>\r\n
Route: <SIP:212.227.67.202:5060;lr=on>\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:21,240 Devicetime: 2014/05/05 11:06:33,916 [PACKET] :
Receiving datagram with length 739 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:+UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on;did=16b.6d8ef183>\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Contact: <sip:GEWÄHLTENR@89.246.79.44:5060;user=phone;transport=udp>\r\n
Content-Length: 207\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=HuaweiSoftX3000 32566680 32566681 IN IP4 89.246.79.44\r\n
s=Sip Call\r\n
c=IN IP4 89.246.79.44\r\n
t=0 0\r\n
m=audio 45974 RTP/AVP 8 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n

[SIP-Packet] 2014/05/05 11:04:21,240 Devicetime: 2014/05/05 11:06:33,918 [PACKET] :
Sending datagram with length 603 from 84.146.124.108:50452 to 212.227.67.202:5060
ACK sip:GEWÄHLTENR@89.246.79.44:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-4fa9ba64-93200c9a\r\n
Route: <SIP:212.227.67.198:5060;lr=on>\r\n
Route: <SIP:212.227.67.226:5060;lr=on;did=16b.6d8ef183>\r\n
Route: <SIP:212.227.67.202:5060;lr=on>\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:25,234 Devicetime: 2014/05/05 11:06:37,916 [PACKET] :
Receiving datagram with length 739 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:+UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on;did=16b.6d8ef183>\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Contact: <sip:GEWÄHLTENR@89.246.79.44:5060;user=phone;transport=udp>\r\n
Content-Length: 207\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=HuaweiSoftX3000 32566680 32566681 IN IP4 89.246.79.44\r\n
s=Sip Call\r\n
c=IN IP4 89.246.79.44\r\n
t=0 0\r\n
m=audio 45974 RTP/AVP 8 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n

[SIP-Packet] 2014/05/05 11:04:25,234 Devicetime: 2014/05/05 11:06:37,918 [PACKET] :
Sending datagram with length 603 from 84.146.124.108:50452 to 212.227.67.202:5060
ACK sip:GEWÄHLTENR@89.246.79.44:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-4fa9ba64-93200c9a\r\n
Route: <SIP:212.227.67.198:5060;lr=on>\r\n
Route: <SIP:212.227.67.226:5060;lr=on;did=16b.6d8ef183>\r\n
Route: <SIP:212.227.67.202:5060;lr=on>\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:29,244 Devicetime: 2014/05/05 11:06:41,926 [PACKET] :
Receiving datagram with length 739 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:+UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on;did=16b.6d8ef183>\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Contact: <sip:GEWÄHLTENR@89.246.79.44:5060;user=phone;transport=udp>\r\n
Content-Length: 207\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=HuaweiSoftX3000 32566680 32566681 IN IP4 89.246.79.44\r\n
s=Sip Call\r\n
c=IN IP4 89.246.79.44\r\n
t=0 0\r\n
m=audio 45974 RTP/AVP 8 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n

[SIP-Packet] 2014/05/05 11:04:29,244 Devicetime: 2014/05/05 11:06:41,928 [PACKET] :
Sending datagram with length 603 from 84.146.124.108:50452 to 212.227.67.202:5060
ACK sip:GEWÄHLTENR@89.246.79.44:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-4fa9ba64-93200c9a\r\n
Route: <SIP:212.227.67.198:5060;lr=on>\r\n
Route: <SIP:212.227.67.226:5060;lr=on;did=16b.6d8ef183>\r\n
Route: <SIP:212.227.67.202:5060;lr=on>\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:33,237 Devicetime: 2014/05/05 11:06:45,917 [PACKET] :
Receiving datagram with length 739 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:+UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on;did=16b.6d8ef183>\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Contact: <sip:GEWÄHLTENR@89.246.79.44:5060;user=phone;transport=udp>\r\n
Content-Length: 207\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=HuaweiSoftX3000 32566680 32566681 IN IP4 89.246.79.44\r\n
s=Sip Call\r\n
c=IN IP4 89.246.79.44\r\n
t=0 0\r\n
m=audio 45974 RTP/AVP 8 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n

[SIP-Packet] 2014/05/05 11:04:33,237 Devicetime: 2014/05/05 11:06:45,919 [PACKET] :
Sending datagram with length 603 from 84.146.124.108:50452 to 212.227.67.202:5060
ACK sip:GEWÄHLTENR@89.246.79.44:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-4fa9ba64-93200c9a\r\n
Route: <SIP:212.227.67.198:5060;lr=on>\r\n
Route: <SIP:212.227.67.226:5060;lr=on;did=16b.6d8ef183>\r\n
Route: <SIP:212.227.67.202:5060;lr=on>\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:37,231 Devicetime: 2014/05/05 11:06:49,916 [PACKET] :
Receiving datagram with length 739 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:+UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on;did=16b.6d8ef183>\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Contact: <sip:GEWÄHLTENR@89.246.79.44:5060;user=phone;transport=udp>\r\n
Content-Length: 207\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=HuaweiSoftX3000 32566680 32566681 IN IP4 89.246.79.44\r\n
s=Sip Call\r\n
c=IN IP4 89.246.79.44\r\n
t=0 0\r\n
m=audio 45974 RTP/AVP 8 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n

[SIP-Packet] 2014/05/05 11:04:37,231 Devicetime: 2014/05/05 11:06:49,918 [PACKET] :
Sending datagram with length 603 from 84.146.124.108:50452 to 212.227.67.202:5060
ACK sip:GEWÄHLTENR@89.246.79.44:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-4fa9ba64-93200c9a\r\n
Route: <SIP:212.227.67.198:5060;lr=on>\r\n
Route: <SIP:212.227.67.226:5060;lr=on;did=16b.6d8ef183>\r\n
Route: <SIP:212.227.67.202:5060;lr=on>\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:41,240 Devicetime: 2014/05/05 11:06:53,919 [PACKET] :
Receiving datagram with length 739 from 212.227.67.202:5060 to 84.146.124.108:50452
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-c1855c41-993e42c3\r\n
From: <sip:+49UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 INVITE\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on;did=16b.6d8ef183>\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Contact: <sip:GEWÄHLTENR@89.246.79.44:5060;user=phone;transport=udp>\r\n
Content-Length: 207\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=HuaweiSoftX3000 32566680 32566681 IN IP4 89.246.79.44\r\n
s=Sip Call\r\n
c=IN IP4 89.246.79.44\r\n
t=0 0\r\n
m=audio 45974 RTP/AVP 8 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n

[SIP-Packet] 2014/05/05 11:04:41,240 Devicetime: 2014/05/05 11:06:53,920 [PACKET] :
Sending datagram with length 603 from 84.146.124.108:50452 to 212.227.67.202:5060
ACK sip:GEWÄHLTENR@89.246.79.44:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-4fa9ba64-93200c9a\r\n
Route: <SIP:212.227.67.198:5060;lr=on>\r\n
Route: <SIP:212.227.67.226:5060;lr=on;did=16b.6d8ef183>\r\n
Route: <SIP:212.227.67.202:5060;lr=on>\r\n
From: <sip:49UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:41,740 Devicetime: 2014/05/05 11:06:54,417 [PACKET] :
Receiving datagram with length 770 from 212.227.67.202:5060 to 84.146.124.108:50452
BYE sip:49UNSERENR@84.146.124.108:50452 SIP/2.0\r\n
Record-Route: <sip:212.227.67.202;lr=on>\r\n
Record-Route: <sip:212.227.67.226;lr=on>\r\n
Record-Route: <sip:212.227.67.198;lr=on>\r\n
Via: SIP/2.0/UDP 212.227.67.202;branch=z9hG4bK89bd.58eebe6d2bb9344c561e0ee6ea234f38.0\r\n
Via: SIP/2.0/UDP 212.227.67.226;branch=z9hG4bK89bd.42e69e0b8d8f586b21508752a7529cc7.0\r\n
Via: SIP/2.0/UDP 212.227.67.198;branch=z9hG4bK89bd.5fe8ae558c0be1f6c535994786a05c73.0\r\n
Via: SIP/2.0/UDP 89.246.79.44:5060;branch=z9hG4bK6e8mdn30c86gqks9f1d0.1\r\n
Call-ID: 567113973@00a05711fc12\r\n
From: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
To: <sip:49UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
CSeq: 1 BYE\r\n
Reason: Q.850;cause=41;text="temporary failure"\r\n
Max-Forwards: 66\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:41,740 Devicetime: 2014/05/05 11:06:54,418 [PACKET] :
Sending datagram with length 434 from 84.146.124.108:50452 to 212.227.67.202:5060
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-4fa9ba64-93200c9a\r\n
From: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
To: <sip:49UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 BYE\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:41,740 Devicetime: 2014/05/05 11:06:54,433 [PACKET] :
Sending datagram with length 428 from LANCOMROUTER:26709 to 3CXSRV::5060
BYE sip:20001@ 3CXSRV::5060 SIP/2.0\r\n
Via: SIP/2.0/UDP LANCOMROUTER:26709;branch=z9hG4bK-4e4ab483-d8028ce5\r\n
From: <sip:GEWÄHLTENR@LANCOMROUTER>;tag=935451725-2068621776\r\n
To: "Stefanie Hayer"<sip:20001@ 3CXSRV:>;tag=d308e470\r\n
Call-ID: ZGQ5ZWUxYTdlMGQ5NDYwZWIxNWMwMDZhZmFlZjQ5MzA.\r\n
CSeq: 2 BYE\r\n
Max-Forwards: 70\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:41,896 Devicetime: 2014/05/05 11:06:54,576 [PACKET] :
Receiving datagram with length 391 from 3CXSRV::5060 to LANCOMROUTER:26709
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP LANCOMROUTER:26709;branch=z9hG4bK-4e4ab483-d8028ce5\r\n
Contact: <sip:20001@ 3CXSRV::5060>\r\n
To: "Stefanie Hayer"<sip:20001@ 3CXSRV:>;tag=d308e470\r\n
From: <sip:GEWÄHLTENR@LANCOMROUTER>;tag=935451725-2068621776\r\n
Call-ID: ZGQ5ZWUxYTdlMGQ5NDYwZWIxNWMwMDZhZmFlZjQ5MzA.\r\n
CSeq: 2 BYE\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:41,896 Devicetime: 2014/05/05 11:06:54,580 [PACKET] :
Sending datagram with length 696 from 84.146.124.108:50452 to 212.227.67.202:5060
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 212.227.67.202;branch=z9hG4bK89bd.58eebe6d2bb9344c561e0ee6ea234f38.0\r\n
Via: SIP/2.0/UDP 212.227.67.226;branch=z9hG4bK89bd.42e69e0b8d8f586b21508752a7529cc7.0\r\n
Via: SIP/2.0/UDP 212.227.67.198;branch=z9hG4bK89bd.5fe8ae558c0be1f6c535994786a05c73.0\r\n
Via: SIP/2.0/UDP 89.246.79.44:5060;branch=z9hG4bK6e8mdn30c86gqks9f1d0.1\r\n
From: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
To: <sip:49UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 1 BYE\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2014/05/05 11:04:50,164 Devicetime: 2014/05/05 11:07:02,830 [PACKET] :
Receiving datagram with length 1008 from 3CXSRV::5060 to LANCOMROUTER:5060
INVITE sip:GEWÄHLTENR@LANCOMROUTER:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 3CXSRV::5060;branch=z9hG4bK-d8754z-c6215a62a358ed26-1---d8754z-;rport\r\n
Max-Forwards: 70\r\n
Contact: <sip:20001@ 3CXSRV::5060>\r\n
To: <sip:GEWÄHLTENR@LANCOMROUTER:5060>\r\n
From: "Stefanie Hayer"<sip:20001@ 3CXSRV::5060>;tag=1b21083b\r\n
Call-ID: NWJmZmI5MTUyMTA3NjVmMjk2OWM4Yzk3MWFmYTdjZDI.\r\n
CSeq: 1 INVITE\r\n
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE\r\n
Content-Type: application/sdp\r\n
Supported: replaces\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Content-Length: 405\r\n
\r\n
v=0\r\n
o=3cxPS 38705037312 109773324289 IN IP4 3CXSRV:\r\n
s=3cxPS Audio call\r\n
c=IN IP4 3CXSRV:\r\n
t=0 0\r\n
m=audio 7196 RTP/AVP 0 8 3 13 9 18 110 99 101\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:3 GSM/8000\r\n
a=rtpmap:13 CN/8000\r\n
a=rtpmap:9 G722/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=fmtp:18 annexb=no\r\n
a=rtpmap:110 iLBC/8000\r\n
a=rtpmap:99 SPEEX/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=sendrecv\r\n
Zuletzt geändert von protec am 05 Mai 2014, 13:41, insgesamt 1-mal geändert.
Nach oben
cpuprofi
Beiträge: 1365
Registriert: 12 Jun 2009, 12:44
Wohnort: Bremen

Re: VOIP-Router 1724 - Probleme mit Verbindungsabbrüchen VOI

Beitrag von cpuprofi »

Hallo Markus,

da fehlen am Anfang noch die ersten SIP-Pakete, kannst Du diese noch einfügen?

Die Beendigung des Gespräches geht im Trace vom 1&1 SIP-Server aus (BYE), warum beendet wird, kann Dir nur 1&1 sagen (die können ja, wenn die einen Trace machen, sehen warum beendet wird).

Ich denke es liegt vielleicht an dem SIP-Header Aufbau, denn der bei Dir von 1&1 verwendete SIP-Server HuaweiSoftX3000 ist in diesem Punkt problematisch, aber da kann Dir auch nur 1&1 weiterhelfen... :G)

Grüße
Cpuprofi
Nach oben
protec
Beiträge: 18
Registriert: 03 Sep 2009, 14:58

Re: VOIP-Router 1724 - Probleme mit Verbindungsabbrüchen VOI

Beitrag von protec »

Hi CpuProfi,

habe es ergänzt - alles VOR

[SIP-Packet] 2014/05/05 11:04:41,240 Devicetime: 2014/05/05 11:06:53,919 [PACKET] :

sollten die noch fehlenden Daten sein

Bin mal gespannt ob du noch was findest - wenn das an 1und1 liegt wird es lustig - die Pfeifen vom First Level Support fragen immer erst nach ihrem tollen AVM :?

Danke dir schon mal,
Markus
Nach oben
Benutzeravatar
Jirka
Beiträge: 5288
Registriert: 03 Jan 2005, 13:39
Wohnort: Ex-OPAL-Gebiet
Kontaktdaten:
Kontaktdaten von Jirka

Re: VOIP-Router 1724 - Probleme mit Verbindungsabbrüchen VOI

Beitrag von Jirka »

Hallo Markus,

da scheint wohl dieses Paket hier:

Code: Alles auswählen

[SIP-Packet] 2014/05/05 11:04:09,883 Devicetime: 2014/05/05 11:06:22,563 [PACKET] : 
Sending datagram with length 603 from 84.146.124.108:50452 to 212.227.67.202:5060
ACK sip:GEWÄHLTENR@89.246.79.44:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 84.146.124.108:50452;branch=z9hG4bK-4fa9ba64-93200c9a\r\n
Route: <SIP:212.227.67.198:5060;lr=on>\r\n
Route: <SIP:212.227.67.226:5060;lr=on;did=16b.6d8ef183>\r\n
Route: <SIP:212.227.67.202:5060;lr=on>\r\n
From: <sip:UNSERENR@VOIPPROVIDER.de;user=phone>;tag=-2017293603--201019226\r\n
To: <sip:GEWÄHLTENR@VOIPPROVIDER.de>;tag=onblvobu-CC-26\r\n
Call-ID: 567113973@00a05711fc12\r\n
CSeq: 2 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: 3CXPhoneSystem 11.0.28976.849 (28862)\r\n
Server: RPRO0001\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n
nicht angekommen zu sein oder 1&1 gefällt da irgendwas nicht dran (ich kann da aber nichts fehlerhaftes erkennen).
Aufgrund dieser Situation, dass 1&1 dieses ACK nicht erhält, sendet der Server immer wieder das OK. So kommen, wenn ich richtig gezählt habe, in einer halben Minute 10 weitere Versuche zusammen, die der LANCOM auch beantwortet, die anscheinend die Gegenseite aber nicht erreichen. Je nachdem wie der 1724 angebunden ist, könnte man noch einen weiteren Trace machen, um zu sehen, ob das Paket das LANCOM so wirklich verlässt (was ich eigentlich aber annehme). Ist denn in solchen Situationen ein hoher Upload zu verzeichnen? Hängt der 1724 mit seinem ADSL-Modem direkt am 1&1-Anschluss?

Viele Grüße,
Jirka
Nach oben
protec
Beiträge: 18
Registriert: 03 Sep 2009, 14:58

Re: VOIP-Router 1724 - Probleme mit Verbindungsabbrüchen VOI

Beitrag von protec »

Hi Jirka,

ja - der 1724 hängt direkt mit seinem ADSL-Modem am 1&1 Anschluss.
und - soweit ich nachvollziehen kann ändert sich nichts am "normalen" Upload.
Seltsamerweise passiert das auch nicht immer sondern nur bei bestimmten Gegenstellen sehr häufig, ist aber nicht so wirklich nachvollziehbar.

Gruß,
Markus

P.S. meinst du der 1&1 Service kann da überhaupt was damit anfangen ? Das letzte Mal als ich Kontakt mit denen hatte wollte der auf die nie angeschlossene Fritz!Box :wink: . Als ich denen gesagt habe wir hätten einen Lancom-Router hieß es Ups - damit kennen wir uns nicht aus und dann könne er mir nicht weiterhelfen :G)
Nach oben
Antworten

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