Hallo zusammen,
der Anruf gehört hier eigentlich nicht ganz rein, aber einen eigenen Thread möchte ich dafür auch nicht aufmachen. Letztlich beendet der LANCOM zweimal den Call, die Gegenseite antwortet auf das zweite BYE mit "404 Not Found" und der LANCOM nimmt das für den Status in der Calls-Tabelle - also unallocated_number (nicht-vergebene Nummer). Falsch ist also das zweimalige verschicken des BYE (mit geänderter CSeq), der falsche Status des Anrufs ist dann die Folge.
Code: Alles auswählen
Nr. 1
Index INFO: 2147482795
From_Line INFO: DTAGSIPTRUNK
From_DisplayName INFO:
From_Number/Name INFO: +493022222222
From_Domain INFO: sip-trunk.telekom.de
To_Number/Name INFO: +4930888888813
To_Domain INFO: arcor.de
Dest-Line INFO: SIP03088888880
Dest-DisplayName INFO:
Dest-Number/Name INFO: +4930888888813
Dest-Domain INFO: 172.20.172.223
CF-Method INFO:
Start INFO: 04/04/2018 07:32:27
Connect INFO: 04/04/2018 07:32:30
End INFO: 04/04/2018 07:32:40
From_Codec INFO: PCMA
To_Codec INFO: PCMA
Status INFO: normal_unspecified
Fax-Detected INFO: No
Jitter-Underrun INFO: 0
Jitter-Overrun INFO: 0
Missing-Packets INFO: 0
Wrong-Order-Packets INFO: 0
From-SRTP INFO: No-Remote-Proposal
Dest-SRTP INFO: No-Local-Proposal
Nr. 2 (nach REFER)
Index INFO: 2147482794
From_Line INFO: DTAGSIPTRUNK
From_DisplayName INFO:
From_Number/Name INFO: +493022222222
From_Domain INFO: sip-trunk.telekom.de
To_Number/Name INFO: +4930888888813
To_Domain INFO: arcor.de
Dest-Line INFO: SIP03088888880
Dest-DisplayName INFO:
Dest-Number/Name INFO: Anonymous
Dest-Domain INFO: 172.20.172.223
CF-Method INFO:
Start INFO: 04/04/2018 07:32:40
Connect INFO: 04/04/2018 07:32:40
End INFO: 04/04/2018 07:33:12
From_Codec INFO:
To_Codec INFO: PCMA
Status INFO: unallocated_number
Fax-Detected INFO: No
Jitter-Underrun INFO: 0
Jitter-Overrun INFO: 0
Missing-Packets INFO: 0
Wrong-Order-Packets INFO: 0
From-SRTP INFO: No-Local-Proposal
Dest-SRTP INFO: No-Local-Proposal
Teil 1:
Code: Alles auswählen
[SIP-Packet] 2018/04/04 07:32:27,098 [Packet]:
Receiving datagram (1111 Bytes) at 87.139.100.100:10509 from 217.0.26.69:5060 using TCP (RtgTag 0):
INVITE sip:+493088888880@87.139.100.100:10509;transport=TCP SIP/2.0\r\n
Via: SIP/2.0/TCP 217.0.26.69:5060;branch=z9hG4bK8a5c90e9e9e3433781186b5a505e2575.25e64d40\r\n
Record-Route: <sip:reg.sip-trunk.telekom.de;transport=tcp;lr>\r\n
Max-Forwards: 62\r\n
To: <sip:+4930888888813@arcor.de;user=phone>\r\n
From: <sip:+493022222222@sip-trunk.telekom.de;user=phone>;tag=595ab58c\r\n
Call-ID: b61418030f1814a0@62.156.102.199\r\n
Contact: <sip:6yHKpADYG0l0QpKCOJlt72z5Po453KQK9kraaP6JGkbls+N8EiVP2RDveEHetqBKMm2G@th1>\r\n
Supported: 100rel,histinfo,resource-priority\r\n
CSeq: 20026873 INVITE\r\n
Allow: ACK, BYE, CANCEL, INFO, INVITE, OPTIONS, PRACK, REGISTER, UPDATE\r\n
P-Asserted-Identity: <sip:+493022222222@sip-trunk.telekom.de;user=phone>\r\n
P-Called-Party-ID: <sip:+4930888888813@sip-trunk.telekom.de;user=phone>\r\n
Content-Type: application/sdp\r\n
Content-Disposition: session\r\n
Content-Length: 249\r\n
\r\n
v=0\r\n
o=- 20772 20773 IN IP4 217.0.26.69\r\n
s=on transit\r\n
c=IN IP4 217.0.132.56\r\n
t=0 0\r\n
m=audio 18492 RTP/AVP 8 0 18 111 9 101\r\n
a=fmtp:18 annexb=no\r\n
a=rtpmap:111 G726-32/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-16\r\n
a=ptime:20\r\n
a=sendrecv\r\n
[SIP-Packet] 2018/04/04 07:32:27,100 [Packet]:
Sending datagram (576 Bytes) from 87.139.100.100:10509 to 217.0.26.69:5060 using TCP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/TCP 217.0.26.69:5060;branch=z9hG4bK8a5c90e9e9e3433781186b5a505e2575.25e64d40;received=217.0.26.69\r\n
Record-Route: <sip:reg.sip-trunk.telekom.de;transport=tcp;lr>\r\n
From: <sip:+493022222222@sip-trunk.telekom.de;user=phone>;tag=595ab58c\r\n
To: <sip:+4930888888813@arcor.de;user=phone>;tag=-2045733692--1181052403\r\n
Call-ID: b61418030f1814a0@62.156.102.199\r\n
CSeq: 20026873 INVITE\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK, REGISTER, UPDATE\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:32:27,857 [Packet]:
Sending datagram (1157 Bytes) from 172.20.172.3:14775 to 172.20.172.223:5060 using UDP (RtgTag 172):
INVITE sip:+4930888888813@172.20.172.223 SIP/2.0\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-3f36d583-a1d19b0c;rport\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-574456591--1775606263\r\n
To: <sip:+4930888888813@arcor.de;user=phone>\r\n
Call-ID: 377581304@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK, UPDATE\r\n
Supported: 100rel\r\n
Contact: <sip:SIP03088888880@172.20.172.3:14775;transport=UDP>\r\n
P-Preferred-Identity: <sip:+493022222222@sip-trunk.telekom.de;user=phone>\r\n
Authorization: Digest username="SIP03088888880", realm="172.20.172.223", algorithm=MD5, uri="sip:+4930888888813@172.20.172.223", nonce="282283106:9ed75704a5e74a963c4a1e54f53d1a28", response="27a69505f79de269a8b1c74ed66b90bb"\r\n
Content-Type: application/sdp\r\n
Content-Length: 285\r\n
\r\n
v=0\r\n
o=- 188790652 188790652 IN IP4 172.20.172.3\r\n
s=call\r\n
c=IN IP4 172.20.172.3\r\n
t=0 0\r\n
m=audio 14044 RTP/AVP 8 0 18 111 9\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:111 G726-32/8000\r\n
a=rtpmap:9 G722/8000\r\n
a=fmtp:18 annexb=no\r\n
a=sendrecv\r\n
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:32:27,864 [Packet]:
Receiving datagram (422 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-3f36d583-a1d19b0c;rport=14775\r\n
To: <sip:+4930888888813@arcor.de;user=phone>\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-574456591--1775606263\r\n
Call-ID: 377581304@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:32:28,063 [Packet]:
Receiving datagram (610 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 180 Ringing\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-3f36d583-a1d19b0c;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: "XYZ-ANML-813"<sip:+4930888888813@arcor.de;user=phone>;tag=42736532\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-574456591--1775606263\r\n
Call-ID: 377581304@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
X-IPPBXServerCallContext: a3vm9actbtez\r\n
X-IPPBXCalledNumber: +4930888888813\r\n
X-IPPBXCalledName: XYZ-ANML-813\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:32:28,065 [Packet]:
Sending datagram (577 Bytes) from 87.139.100.100:10509 to 217.0.26.69:5060 using TCP (RtgTag 0):
SIP/2.0 180 Ringing\r\n
Via: SIP/2.0/TCP 217.0.26.69:5060;branch=z9hG4bK8a5c90e9e9e3433781186b5a505e2575.25e64d40;received=217.0.26.69\r\n
Record-Route: <sip:reg.sip-trunk.telekom.de;transport=tcp;lr>\r\n
From: <sip:+493022222222@sip-trunk.telekom.de;user=phone>;tag=595ab58c\r\n
To: <sip:+4930888888813@arcor.de;user=phone>;tag=-2045733692--1181052403\r\n
Call-ID: b61418030f1814a0@62.156.102.199\r\n
CSeq: 20026873 INVITE\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK, REGISTER, UPDATE\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:32:30,068 [Packet]:
Receiving datagram (682 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-3f36d583-a1d19b0c;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: "XYZ-ANML-813"<sip:+4930888888813@arcor.de;user=phone>;tag=42736532\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-574456591--1775606263\r\n
Call-ID: 377581304@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Content-Type: application/sdp\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 154\r\n
\r\n
v=0\r\n
o=- 1187092195 1 IN IP4 172.20.172.223\r\n
s=T-Com IpPbxSrv\r\n
c=IN IP4 172.20.172.223\r\n
t=0 0\r\n
m=audio 51342 RTP/AVP 8\r\n
a=rtpmap:8 PCMA/8000\r\n
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:32:30,071 [Packet]:
Sending datagram (870 Bytes) from 87.139.100.100:10509 to 217.0.26.69:5060 using TCP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/TCP 217.0.26.69:5060;branch=z9hG4bK8a5c90e9e9e3433781186b5a505e2575.25e64d40;received=217.0.26.69\r\n
Record-Route: <sip:reg.sip-trunk.telekom.de;transport=tcp;lr>\r\n
From: <sip:+493022222222@sip-trunk.telekom.de;user=phone>;tag=595ab58c\r\n
To: <sip:+4930888888813@arcor.de;user=phone>;tag=-2045733692--1181052403\r\n
Call-ID: b61418030f1814a0@62.156.102.199\r\n
CSeq: 20026873 INVITE\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK, REGISTER, UPDATE\r\n
Contact: <sip:+493088888880@87.139.100.100:10509;transport=TCP>\r\n
Content-Type: application/sdp\r\n
Content-Length: 201\r\n
\r\n
v=0\r\n
o=- 0 0 IN IP4 87.139.100.100\r\n
s=call\r\n
c=IN IP4 87.139.100.100\r\n
t=0 0\r\n
m=audio 10850 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
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:32:30,219 [Packet]:
Receiving datagram (623 Bytes) at 87.139.100.100:10509 from 217.0.26.69:5060 using TCP (RtgTag 0):
ACK sip:+493088888880@87.139.100.100:10509;transport=TCP SIP/2.0\r\n
Via: SIP/2.0/TCP 217.0.26.69;branch=z9hG4bK8a5c90e9e9e3433781186b5a505e2575.1b8f9670\r\n
Record-Route: <sip:reg.sip-trunk.telekom.de;transport=tcp;lr>\r\n
Max-Forwards: 63\r\n
To: <sip:+4930888888813@arcor.de;user=phone>;tag=-2045733692--1181052403\r\n
From: <sip:+493022222222@sip-trunk.telekom.de;user=phone>;tag=595ab58c\r\n
Call-ID: b61418030f1814a0@62.156.102.199\r\n
Contact: <sip:6yHKpADYG0l0QpKCOJlt72z5Po453KQK9kraaP6JGkbls+N8EiVP2RDveEHetqBKMm2G@th1>\r\n
CSeq: 20026873 ACK\r\n
Allow: ACK, BYE, CANCEL, INFO, INVITE, OPTIONS, PRACK, REGISTER, UPDATE\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:32:30,222 [Packet]:
Sending datagram (692 Bytes) from 172.20.172.3:14775 to 172.20.172.223:5060 using UDP (RtgTag 172):
ACK sip:172.20.172.223:5060;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-fa7a2e93-5c6000ff;rport\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-574456591--1775606263\r\n
To: <sip:+4930888888813@arcor.de;user=phone>;tag=42736532\r\n
Call-ID: 377581304@00a0572e318a\r\n
CSeq: 100 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK, UPDATE\r\n
Authorization: Digest username="SIP03088888880", realm="172.20.172.223", algorithm=MD5, uri="sip:+4930888888813@172.20.172.223", nonce="282283106:9ed75704a5e74a963c4a1e54f53d1a28", response="27a69505f79de269a8b1c74ed66b90bb"\r\n
Content-Length: 0\r\n
\r\n
So, bis hierhin ist noch alles gut.
Teil 2:
Code: Alles auswählen
[SIP-Packet] 2018/04/04 07:32:40,106 [Packet]:
Receiving datagram (750 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
REFER sip:SIP03088888880@172.20.172.3:14775;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 172.20.172.223:5060;branch=z9hG4bK-d8754z-d264b645c9787745-1---d8754z-;rport\r\n
Max-Forwards: 70\r\n
Contact: <sip:+4930888888813@172.20.172.223:5060;transport=udp>\r\n
To: <sip:SIP03088888880@172.20.172.223>;tag=-574456591--1775606263\r\n
From: <sip:+4930888888813@arcor.de;user=phone>;tag=42736532\r\n
Call-ID: 377581304@00a0572e318a\r\n
CSeq: 1 REFER\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Supported: timer\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Refer-To: <sip:Anonymous@172.20.172.223?Replaces=x-ippbx-transferid%3Bto-tag%3D352%3Bfrom-tag%3D352>\r\n
Referred-By: <sip:+4930888888813@arcor.de;user=phone>\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:32:40,106 [Packet]:
Sending datagram (546 Bytes) from 172.20.172.3:14775 to 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 202 Accepted\r\n
Via: SIP/2.0/UDP 172.20.172.223:5060;branch=z9hG4bK-d8754z-d264b645c9787745-1---d8754z-;received=172.20.172.223;rport=5060\r\n
From: <sip:+4930888888813@arcor.de;user=phone>;tag=42736532\r\n
To: <sip:SIP03088888880@172.20.172.223>;tag=-574456591--1775606263\r\n
Call-ID: 377581304@00a0572e318a\r\n
CSeq: 1 REFER\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK, UPDATE\r\n
Contact: <sip:+493022222222@172.20.172.3:14775;transport=UDP>\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:32:40,113 [Packet]:
Sending datagram (1190 Bytes) from 172.20.172.3:14775 to 172.20.172.223:5060 using UDP (RtgTag 172):
INVITE sip:Anonymous@172.20.172.223 SIP/2.0\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-9761d009-7c2dd3ee;rport\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Supported: 100rel\r\n
Contact: <sip:SIP03088888880@172.20.172.3:14775;transport=UDP>\r\n
Replaces: x-ippbx-transferid;from-tag=352;to-tag=352\r\n
Referred-By: <sip:+4930888888813@arcor.de>\r\n
P-Asserted-Identity: <sip:+493022222222@sip-trunk.telekom.de;user=phone>\r\n
Authorization: Digest username="SIP03088888880", realm="172.20.172.223", algorithm=MD5, uri="sip:Anonymous@172.20.172.223", nonce="282283106:9ed75704a5e74a963c4a1e54f53d1a28", response="f1df3bf689fa403b88cdefc46e524ed3"\r\n
Content-Type: application/sdp\r\n
Content-Length: 287\r\n
\r\n
v=0\r\n
o=- 3010526016 3010526016 IN IP4 172.20.172.3\r\n
s=call\r\n
c=IN IP4 172.20.172.3\r\n
t=0 0\r\n
m=audio 15066 RTP/AVP 8 0 18 111 9\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:111 G726-32/8000\r\n
a=rtpmap:9 G722/8000\r\n
a=fmtp:18 annexb=no\r\n
a=sendrecv\r\n
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:32:40,113 [Packet]:
Sending datagram (654 Bytes) from 172.20.172.3:14775 to 172.20.172.223:5060 using UDP (RtgTag 172):
NOTIFY sip:172.20.172.223:5060;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-80c549e5-f135c02f;rport\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-574456591--1775606263\r\n
To: <sip:+4930888888813@arcor.de;user=phone>;tag=42736532\r\n
Call-ID: 377581304@00a0572e318a\r\n
CSeq: 101 NOTIFY\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK, UPDATE\r\n
Contact: <sip:SIP03088888880@172.20.172.3:14775;transport=UDP>\r\n
Event: refer\r\n
Subscription-State: active;expires=600\r\n
Content-Type: message/sipfrag;version=2.0\r\n
Content-Length: 20\r\n
\r\n
SIP/2.0 100 Trying\r\n
[SIP-Packet] 2018/04/04 07:32:40,121 [Packet]:
Receiving datagram (423 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-9761d009-7c2dd3ee;rport=14775\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:32:40,123 [Packet]:
Receiving datagram (481 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-80c549e5-f135c02f;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:+4930888888813@arcor.de;user=phone>;tag=42736532\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-574456591--1775606263\r\n
Call-ID: 377581304@00a0572e318a\r\n
CSeq: 101 NOTIFY\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:32:40,183 [Packet]:
Receiving datagram (668 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-9761d009-7c2dd3ee;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Content-Type: application/sdp\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 153\r\n
\r\n
v=0\r\n
o=- 2956961508 1 IN IP4 192.168.193.41\r\n
s=T-Com IpPbxSrv\r\n
c=IN IP4 192.168.193.41\r\n
t=0 0\r\n
m=audio 5004 RTP/AVP 8\r\n
a=rtpmap:8 PCMA/8000\r\n
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:32:40,186 [Packet]:
Sending datagram (660 Bytes) from 172.20.172.3:14775 to 172.20.172.223:5060 using UDP (RtgTag 172):
NOTIFY sip:172.20.172.223:5060;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-bf336407-5af17477;rport\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-574456591--1775606263\r\n
To: <sip:+4930888888813@arcor.de;user=phone>;tag=42736532\r\n
Call-ID: 377581304@00a0572e318a\r\n
CSeq: 102 NOTIFY\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK, UPDATE\r\n
Contact: <sip:SIP03088888880@172.20.172.3:14775;transport=UDP>\r\n
Event: refer\r\n
Subscription-State: terminated;reason=noresource\r\n
Content-Type: message/sipfrag;version=2.0\r\n
Content-Length: 16\r\n
\r\n
SIP/2.0 200 OK\r\n
[SIP-Packet] 2018/04/04 07:32:40,187 [Packet]:
Sending datagram (1134 Bytes) from 87.139.100.100:10509 to 217.0.26.69:5060 using TCP (RtgTag 0):
INVITE sip:6yHKpADYG0l0QpKCOJlt72z5Po453KQK9kraaP6JGkbls+N8EiVP2RDveEHetqBKMm2G@th1 SIP/2.0\r\n
Via: SIP/2.0/TCP 87.139.100.100:10509;branch=z9hG4bK-927ca438-7a70130a;rport\r\n
Route: <sip:reg.sip-trunk.telekom.de;transport=tcp;lr>\r\n
From: <sip:+4930888888813@arcor.de;user=phone>;tag=-2045733692--1181052403\r\n
To: <sip:+493022222222@sip-trunk.telekom.de;user=phone>;tag=595ab58c\r\n
Call-ID: b61418030f1814a0@62.156.102.199\r\n
CSeq: 1 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Supported: 100rel\r\n
Contact: <sip:+493088888880@87.139.100.100:10509;transport=TCP>\r\n
Authorization: Digest username="551122334455", realm="sip-trunk.telekom.de", algorithm=MD5, uri="sip:6yHKpADYG0l0QpKCOJlt72z5Po453KQK9kraaP6JGkbls+N8EiVP2RDveEH", nonce="5cb9e03c3fe624665cb9e03c5403ba3ce0cadafd9038f32df86d288c9f422a70", response="8c18bddfbd0b89d94ad2cafef3efae99"\r\n
Content-Type: application/sdp\r\n
Content-Length: 201\r\n
\r\n
v=0\r\n
o=- 0 1 IN IP4 87.139.100.100\r\n
s=call\r\n
c=IN IP4 87.139.100.100\r\n
t=0 0\r\n
m=audio 10850 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
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:32:40,192 [Packet]:
Receiving datagram (481 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-bf336407-5af17477;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:+4930888888813@arcor.de;user=phone>;tag=42736532\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-574456591--1775606263\r\n
Call-ID: 377581304@00a0572e318a\r\n
CSeq: 102 NOTIFY\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:32:40,192 [Packet]:
Receiving datagram (589 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
BYE sip:SIP03088888880@172.20.172.3:14775;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 172.20.172.223:5060;branch=z9hG4bK-d8754z-ae5c0e3f1f15b56e-1---d8754z-;rport\r\n
Max-Forwards: 70\r\n
Contact: <sip:+4930888888813@172.20.172.223:5060;transport=udp>\r\n
To: <sip:SIP03088888880@172.20.172.223>;tag=-574456591--1775606263\r\n
From: <sip:+4930888888813@arcor.de;user=phone>;tag=42736532\r\n
Call-ID: 377581304@00a0572e318a\r\n
CSeq: 2 BYE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Supported: timer\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:32:40,196 [Packet]:
Sending datagram (475 Bytes) from 172.20.172.3:14775 to 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.223:5060;branch=z9hG4bK-d8754z-ae5c0e3f1f15b56e-1---d8754z-;received=172.20.172.223;rport=5060\r\n
From: <sip:+4930888888813@arcor.de;user=phone>;tag=42736532\r\n
To: <sip:SIP03088888880@172.20.172.223>;tag=-574456591--1775606263\r\n
Call-ID: 377581304@00a0572e318a\r\n
CSeq: 2 BYE\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK, UPDATE\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:32:40,225 [Packet]:
Receiving datagram (322 Bytes) at 87.139.100.100:10509 from 217.0.26.69:5060 using TCP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/TCP 87.139.100.100:10509;rport;branch=z9hG4bK-927ca438-7a70130a\r\n
To: <sip:+493022222222@sip-trunk.telekom.de;user=phone>;tag=595ab58c\r\n
From: <sip:+4930888888813@arcor.de;user=phone>;tag=-2045733692--1181052403\r\n
Call-ID: b61418030f1814a0@62.156.102.199\r\n
CSeq: 1 INVITE\r\n
Content-Length: 0\r\n
\r\n
Bis hierhin ist auch noch alles gut. Leider antwortet der Provider nun nach dem Trying nicht mit OK. Könnte man also auch die Schuld auf den Provider schieben. In der Folge antwortet die Telefonanlage immer wieder mit OK, weil das ja seitens des LANCOMs nicht bestätigt werden konnte, weil der Provider das Re-INVITE nicht mit OK bestätigte.
Code: Alles auswählen
[SIP-Packet] 2018/04/04 07:32:40,678 [Packet]:
Receiving datagram (668 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-9761d009-7c2dd3ee;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Content-Type: application/sdp\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 153\r\n
\r\n
v=0\r\n
o=- 2956961508 1 IN IP4 192.168.193.41\r\n
s=T-Com IpPbxSrv\r\n
c=IN IP4 192.168.193.41\r\n
t=0 0\r\n
m=audio 5004 RTP/AVP 8\r\n
a=rtpmap:8 PCMA/8000\r\n
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:32:41,679 [Packet]:
Receiving datagram (668 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-9761d009-7c2dd3ee;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Content-Type: application/sdp\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 153\r\n
\r\n
v=0\r\n
o=- 2956961508 1 IN IP4 192.168.193.41\r\n
s=T-Com IpPbxSrv\r\n
c=IN IP4 192.168.193.41\r\n
t=0 0\r\n
m=audio 5004 RTP/AVP 8\r\n
a=rtpmap:8 PCMA/8000\r\n
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:32:43,679 [Packet]:
Receiving datagram (668 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-9761d009-7c2dd3ee;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Content-Type: application/sdp\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 153\r\n
\r\n
v=0\r\n
o=- 2956961508 1 IN IP4 192.168.193.41\r\n
s=T-Com IpPbxSrv\r\n
c=IN IP4 192.168.193.41\r\n
t=0 0\r\n
m=audio 5004 RTP/AVP 8\r\n
a=rtpmap:8 PCMA/8000\r\n
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:32:47,684 [Packet]:
Receiving datagram (668 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-9761d009-7c2dd3ee;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Content-Type: application/sdp\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 153\r\n
\r\n
v=0\r\n
o=- 2956961508 1 IN IP4 192.168.193.41\r\n
s=T-Com IpPbxSrv\r\n
c=IN IP4 192.168.193.41\r\n
t=0 0\r\n
m=audio 5004 RTP/AVP 8\r\n
a=rtpmap:8 PCMA/8000\r\n
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:32:51,680 [Packet]:
Receiving datagram (668 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-9761d009-7c2dd3ee;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Content-Type: application/sdp\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 153\r\n
\r\n
v=0\r\n
o=- 2956961508 1 IN IP4 192.168.193.41\r\n
s=T-Com IpPbxSrv\r\n
c=IN IP4 192.168.193.41\r\n
t=0 0\r\n
m=audio 5004 RTP/AVP 8\r\n
a=rtpmap:8 PCMA/8000\r\n
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:32:55,679 [Packet]:
Receiving datagram (668 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-9761d009-7c2dd3ee;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Content-Type: application/sdp\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 153\r\n
\r\n
v=0\r\n
o=- 2956961508 1 IN IP4 192.168.193.41\r\n
s=T-Com IpPbxSrv\r\n
c=IN IP4 192.168.193.41\r\n
t=0 0\r\n
m=audio 5004 RTP/AVP 8\r\n
a=rtpmap:8 PCMA/8000\r\n
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:32:59,680 [Packet]:
Receiving datagram (668 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-9761d009-7c2dd3ee;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Content-Type: application/sdp\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 153\r\n
\r\n
v=0\r\n
o=- 2956961508 1 IN IP4 192.168.193.41\r\n
s=T-Com IpPbxSrv\r\n
c=IN IP4 192.168.193.41\r\n
t=0 0\r\n
m=audio 5004 RTP/AVP 8\r\n
a=rtpmap:8 PCMA/8000\r\n
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:33:03,681 [Packet]:
Receiving datagram (668 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-9761d009-7c2dd3ee;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Content-Type: application/sdp\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 153\r\n
\r\n
v=0\r\n
o=- 2956961508 1 IN IP4 192.168.193.41\r\n
s=T-Com IpPbxSrv\r\n
c=IN IP4 192.168.193.41\r\n
t=0 0\r\n
m=audio 5004 RTP/AVP 8\r\n
a=rtpmap:8 PCMA/8000\r\n
a=ptime:20\r\n
[SIP-Packet] 2018/04/04 07:33:07,679 [Packet]:
Receiving datagram (668 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-9761d009-7c2dd3ee;rport=14775\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 100 INVITE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Content-Type: application/sdp\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 153\r\n
\r\n
v=0\r\n
o=- 2956961508 1 IN IP4 192.168.193.41\r\n
s=T-Com IpPbxSrv\r\n
c=IN IP4 192.168.193.41\r\n
t=0 0\r\n
m=audio 5004 RTP/AVP 8\r\n
a=rtpmap:8 PCMA/8000\r\n
a=ptime:20\r\n
Jetzt kommt ein Request Timeout vom Provider. Der LANCOM schickt daraufhin ein BYE zur Telefonanlage, merkt sich das nicht, und als dann vom Provider auch noch ein BYE kommt, schickt der LANCOM noch ein BYE zur Telefonanlage. Die antwortet, weil sie mit dem ersten BYE den Call schon abgeschlossen hat, mit "404 Not Found"...
Code: Alles auswählen
[SIP-Packet] 2018/04/04 07:33:12,262 [Packet]:
Receiving datagram (458 Bytes) at 87.139.100.100:10509 from 217.0.26.69:5060 using TCP (RtgTag 0):
SIP/2.0 408 Request Timeout\r\n
Via: SIP/2.0/TCP 87.139.100.100:10509;rport=10509;branch=z9hG4bK-927ca438-7a70130a\r\n
To: <sip:+493022222222@sip-trunk.telekom.de;user=phone>;tag=595ab58c\r\n
From: <sip:+4930888888813@arcor.de;user=phone>;tag=-2045733692--1181052403\r\n
Call-ID: b61418030f1814a0@62.156.102.199\r\n
Contact: <sip:2QHKpADYG0l0QpKCOJlt75u9wLg+Kicyd1lFte+L7S+3emhd@th1>\r\n
CSeq: 1 INVITE\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, REGISTER\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:33:12,262 [Packet]:
Sending datagram (529 Bytes) from 87.139.100.100:10509 to 217.0.26.69:5060 using TCP (RtgTag 0):
ACK sip:6yHKpADYG0l0QpKCOJlt72z5Po453KQK9kraaP6JGkbls+N8EiVP2RDveEHetqBKMm2G@th1 SIP/2.0\r\n
Via: SIP/2.0/TCP 87.139.100.100:10509;branch=z9hG4bK-927ca438-7a70130a;rport\r\n
Route: <sip:reg.sip-trunk.telekom.de;transport=tcp;lr>\r\n
From: <sip:+4930888888813@arcor.de;user=phone>;tag=-2045733692--1181052403\r\n
To: <sip:+493022222222@sip-trunk.telekom.de;user=phone>;tag=595ab58c\r\n
Call-ID: b61418030f1814a0@62.156.102.199\r\n
CSeq: 1 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:33:12,266 [Packet]:
Sending datagram (410 Bytes) from 172.20.172.3:14775 to 172.20.172.223:5060 using UDP (RtgTag 172):
BYE sip:172.20.172.223:5060;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-f1a1571d-b88b0abc;rport\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 101 BYE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:33:12,267 [Packet]:
Receiving datagram (628 Bytes) at 87.139.100.100:10509 from 217.0.26.69:5060 using TCP (RtgTag 0):
BYE sip:+493088888880@87.139.100.100:10509;transport=TCP SIP/2.0\r\n
Via: SIP/2.0/TCP 217.0.26.69:5060;branch=z9hG4bK20c4ca8c27586fa81d6343add7548b63.144f0990\r\n
Record-Route: <sip:reg.sip-trunk.telekom.de;transport=tcp;lr>\r\n
Max-Forwards: 68\r\n
To: <sip:+4930888888813@arcor.de;user=phone>;tag=-2045733692--1181052403\r\n
From: <sip:+493022222222@sip-trunk.telekom.de;user=phone>;tag=595ab58c\r\n
Call-ID: b61418030f1814a0@62.156.102.199\r\n
Contact: <sip:6yHKpADYG0l0QpKCOJlt72z5Po453KQK9kraaP6JGkbls+N8EiVP2RDveEHetqBKMm2G@th1>\r\n
CSeq: 20026874 BYE\r\n
Allow: ACK, BYE, CANCEL, INFO, INVITE, OPTIONS, PRACK, REGISTER, UPDATE\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:33:12,270 [Packet]:
Sending datagram (410 Bytes) from 172.20.172.3:14775 to 172.20.172.223:5060 using UDP (RtgTag 172):
BYE sip:172.20.172.223:5060;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-7927aa29-cf830d7f;rport\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 102 BYE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:33:12,273 [Packet]:
Receiving datagram (436 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 404 Not Found\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-7927aa29-cf830d7f;rport=14775\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 102 BYE\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:33:12,274 [Packet]:
Sending datagram (371 Bytes) from 172.20.172.3:14775 to 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-7927aa29-cf830d7f;rport\r\n
From: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
To: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 0 BYE\r\n
User-Agent: LANCOM 1783VAW (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Content-Length: 0\r\n
\r\n
[SIP-Packet] 2018/04/04 07:33:15,770 [Packet]:
Receiving datagram (301 Bytes) at 172.20.172.3:14775 from 172.20.172.223:5060 using UDP (RtgTag 172):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 172.20.172.3:14775;branch=z9hG4bK-f1a1571d-b88b0abc;rport=14775\r\n
To: <sip:Anonymous@172.20.172.223;user=phone>;tag=ed314c34\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=-646167531--686214809\r\n
Call-ID: 3180392641@00a0572e318a\r\n
CSeq: 101 BYE\r\n
Content-Length: 0\r\n
\r\n
Vielen Dank und viele Grüße,
Jirka