All-IP/VoIP: Wie Geistereinträge in der Calls-Tabelle entst.

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

Moderator: Lancom-Systems Moderatoren

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

All-IP/VoIP: Wie Geistereinträge in der Calls-Tabelle entst.

Beitrag von Jirka »

Hallo zusammen,

in der Calls-Tabelle (Status/Voice-Call-Manager/Calls; LANmonitor: VoIP Call Manager -> Anrufe -> Vollständige Anruftabelle anzeigen...) gibt es mitunter leere Geister-Einträge, die z. B. so aussehen:

Syslog (nur Meldungsteil):
ACCOUNTING_INFO: [CDR] Src: "" "" "" "" Dest: "" "" Conn: "" "" "" "" Times: "2018-03-28 17:28:00 +2" "" "2018-03-28 17:28:00 +2" Codecs: "" "" Status: "normal_unspecified" Fax-Detected: "No"

Status/Voice-Call-Manager/Calls:
Index INFO: 2147483134
From_Line INFO:
From_DisplayName INFO:
From_Number/Name INFO:
From_Domain INFO:
To_Number/Name INFO:
To_Domain INFO:
Dest-Line INFO:
Dest-DisplayName INFO:
Dest-Number/Name INFO:
Dest-Domain INFO:
CF-Method INFO:
Start INFO: 03/28/2018 17:28:00
Connect INFO:
End INFO: 03/28/2018 17:28:00
From_Codec INFO:
To_Codec INFO:
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

LANmonitor:
dementsprechend

In diesem Thread will ich ab und an SIP-Packet-Traces angeben, die aufzeigen, wie es zu so einem leeren Calls-Eintrag kommen kann. Hier ist Nummer 1.

Code: Alles auswählen

[SIP-Packet] 2018/03/28 17:28:00,116 [PACKET] : 
Receiving datagram with length 841 from 10.10.22.1:14034 to 10.10.19.1:5060 using UDP
INVITE sip:*21@xyz SIP/2.0\r\n
Via: SIP/2.0/UDP 10.10.22.1:14034;branch=z9hG4bK-fbcba2e3-9fa005a2\r\n
From: "xyz"<sip:30@xyz>;tag=959384970-945536522\r\n
To: <sip:*21@xyz;user=phone>\r\n
Call-ID: 3305687502@00a0572283e5\r\n
CSeq: 100 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: C430A IP/42.243.00.000.000\r\n
Server: Router-NS-L\r\n
Supported: 100rel\r\n
Contact: <sip:30@10.10.22.1:14034;transport=UDP>\r\n
Content-Type: application/sdp\r\n
Content-Length: 398\r\n
\r\n
v=0\r\n
o=- 1652843751 1652843751 IN IP4 10.10.22.1\r\n
s=call\r\n
c=IN IP4 10.10.22.1\r\n
t=0 0\r\n
m=audio 10878 RTP/AVP 9 8 0 96 97 2 18 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:96 G726-32/8000\r\n
a=rtpmap:97 AAL2-G726-32/8000\r\n
a=rtpmap:2 G726-32/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:18 annexb=no\r\n
a=fmtp:101 0-15\r\n
a=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2018/03/28 17:28:00,119 [PACKET] : 
Sending datagram with length 325 from 10.10.19.1:5060 to 10.10.22.1:14034 using UDP
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 10.10.22.1:14034;branch=z9hG4bK-fbcba2e3-9fa005a2\r\n
From: "xyz"<sip:30@xyz>;tag=959384970-945536522\r\n
To: <sip:*21@xyz;user=phone>\r\n
Call-ID: 3305687502@00a0572283e5\r\n
CSeq: 100 INVITE\r\n
User-Agent: LANCOM 1781EF+ / 9.24.0376 / 22.02.2018\r\n
Server: xyz-Router\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/03/28 17:28:00,120 [PACKET] : 
Sending datagram with length 418 from 10.10.19.1:5060 to 10.10.22.1:14034 using UDP
SIP/2.0 407 Proxy Authentication Required\r\n
Via: SIP/2.0/UDP 10.10.22.1:14034;branch=z9hG4bK-fbcba2e3-9fa005a2\r\n
From: "xyz"<sip:30@xyz>;tag=959384970-945536522\r\n
To: <sip:*21@xyz>;tag=-2108216818-1360210506\r\n
Call-ID: 3305687502@00a0572283e5\r\n
CSeq: 100 INVITE\r\n
Server: xyz-Router\r\n
Proxy-Authenticate: Digest realm="xyz",nonce="b3443e45b41a9c025a0d4e01c0be2420",opaque="",algorithm=MD5\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/03/28 17:28:00,174 [PACKET] : 
Receiving datagram with length 362 from 10.10.22.1:14034 to 10.10.19.1:5060 using UDP
ACK sip:*21@xyz SIP/2.0\r\n
Via: SIP/2.0/UDP 10.10.22.1:14034;branch=z9hG4bK-fbcba2e3-9fa005a2\r\n
From: "xyz"<sip:30@xyz>;tag=959384970-945536522\r\n
To: <sip:*21@xyz;user=phone>;tag=-2108216818-1360210506\r\n
Call-ID: 3305687502@00a0572283e5\r\n
CSeq: 100 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: C430A IP/42.243.00.000.000\r\n
Server: Router-NS-L\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/03/28 17:28:00,180 [PACKET] : 
Receiving datagram with length 1035 from 10.10.22.1:14034 to 10.10.19.1:5060 using UDP
INVITE sip:*21@xyz SIP/2.0\r\n
Via: SIP/2.0/UDP 10.10.22.1:14034;branch=z9hG4bK-d0b1bb1e-5559908d\r\n
From: "xyz"<sip:30@xyz>;tag=959384970-945536522\r\n
To: <sip:*21@xyz;user=phone>\r\n
Call-ID: 3305687502@00a0572283e5\r\n
CSeq: 101 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: C430A IP/42.243.00.000.000\r\n
Server: Router-NS-L\r\n
Supported: 100rel\r\n
Proxy-Authorization: Digest username="xyz", realm="xyz", algorithm=MD5, uri="sip:*21@xyz", nonce="b3443e45b41a9c025a0d4e01c0be2420", opaque="", response="15798a7b5b0dc64a864c648d4c1721ba"\r\n
Contact: <sip:30@10.10.22.1:14034;transport=UDP>\r\n
Content-Type: application/sdp\r\n
Content-Length: 398\r\n
\r\n
v=0\r\n
o=- 1652843751 1652843751 IN IP4 10.10.22.1\r\n
s=call\r\n
c=IN IP4 10.10.22.1\r\n
t=0 0\r\n
m=audio 10878 RTP/AVP 9 8 0 96 97 2 18 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:96 G726-32/8000\r\n
a=rtpmap:97 AAL2-G726-32/8000\r\n
a=rtpmap:2 G726-32/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:18 annexb=no\r\n
a=fmtp:101 0-15\r\n
a=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2018/03/28 17:28:00,180 [PACKET] : 
Sending datagram with length 325 from 10.10.19.1:5060 to 10.10.22.1:14034 using UDP
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 10.10.22.1:14034;branch=z9hG4bK-d0b1bb1e-5559908d\r\n
From: "xyz"<sip:30@xyz>;tag=959384970-945536522\r\n
To: <sip:*21@xyz;user=phone>\r\n
Call-ID: 3305687502@00a0572283e5\r\n
CSeq: 101 INVITE\r\n
User-Agent: LANCOM 1781EF+ / 9.24.0376 / 22.02.2018\r\n
Server: xyz-Router\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/03/28 17:28:00,184 [PACKET] : 
Sending datagram with length 309 from 10.10.19.1:5060 to 10.10.22.1:14034 using UDP
SIP/2.0 500 Resource Reservation Failed\r\n
Via: SIP/2.0/UDP 10.10.22.1:14034;branch=z9hG4bK-d0b1bb1e-5559908d\r\n
From: "xyz"<sip:30@xyz>;tag=959384970-945536522\r\n
To: <sip:*21@xyz>;tag=-2108216818-1360210506\r\n
Call-ID: 3305687502@00a0572283e5\r\n
CSeq: 101 INVITE\r\n
Server: xyz-Router\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/03/28 17:28:00,236 [PACKET] : 
Receiving datagram with length 362 from 10.10.22.1:14034 to 10.10.19.1:5060 using UDP
ACK sip:*21@xyz SIP/2.0\r\n
Via: SIP/2.0/UDP 10.10.22.1:14034;branch=z9hG4bK-d0b1bb1e-5559908d\r\n
From: "xyz"<sip:30@xyz>;tag=959384970-945536522\r\n
To: <sip:*21@xyz;user=phone>;tag=-2108216818-1360210506\r\n
Call-ID: 3305687502@00a0572283e5\r\n
CSeq: 101 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: C430A IP/42.243.00.000.000\r\n
Server: Router-NS-L\r\n
Content-Length: 0\r\n
\r\n
Vielen Dank und viele Grüße,
Jirka
Benutzeravatar
Jirka
Beiträge: 5225
Registriert: 03 Jan 2005, 13:39
Wohnort: Ex-OPAL-Gebiet
Kontaktdaten:

Re: All-IP/VoIP: Wie Geistereinträge in der Calls-Tabelle en

Beitrag von Jirka »

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
Benutzeravatar
Jirka
Beiträge: 5225
Registriert: 03 Jan 2005, 13:39
Wohnort: Ex-OPAL-Gebiet
Kontaktdaten:

Re: All-IP/VoIP: Wie Geistereinträge in der Calls-Tabelle en

Beitrag von Jirka »

Hallo,

eigentlich wollte ich hier nur die Geistereinträge (leere Einträge, siehe erstes Posting) sammmeln, aber die kommen plötzlich nicht mehr, wenn man den Trace laufen hat. Dafür hier jetzt ein "hängender" Call. Davon gab es zwei heute, da diese sich aber bis auf die Zeitverschiebung exakt gleichen, präsentiere ich hier nur einen. Die Calls hingen mit "Klingeln" in der Calls-Tabelle.

Code: Alles auswählen

Index                INFO:    2147482269
From_Line            INFO:    SIP03088888880
From_DisplayName     INFO:
From_Number/Name     INFO:    SIP03088888880
From_Domain          INFO:    172.20.172.223
To_Number/Name       INFO:    +4930222222
To_Domain            INFO:    172.20.172.223
Dest-Line            INFO:    DTAGSIPTRUNK
Dest-DisplayName     INFO:
Dest-Number/Name     INFO:    +4930222222
Dest-Domain          INFO:    sip-trunk.telekom.de
CF-Method            INFO:
Start                INFO:    04/09/2018 09:26:00
Connect              INFO:
End                  INFO:
From_Codec           INFO:
To_Codec             INFO:
Status               INFO:    Ringing
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
Und hier der Trace (wie man sieht, hat der LANCOM sogar selber den Call beendet!):

Code: Alles auswählen

[SIP-Packet] 2018/04/09 09:28:53,280  Devicetime: 2018/04/09 09:26:00,154 [Packet]: 
Receiving datagram (1110 Bytes) at 192.168.193.1:11891 from 172.20.172.223:5060 using UDP (RtgTag 193):
INVITE sip:SIP03088888880@192.168.193.1:11891;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 172.20.172.223:5060;branch=z9hG4bK-d8754z-2511ae50573c696d-1---d8754z-;rport\r\n
Max-Forwards: 70\r\n
Contact: <sip:SIP03088888880@172.20.172.223:5060;transport=udp>\r\n
To: <sip:+4930222222@172.20.172.223;user=phone>\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=f857f35a\r\n
Call-ID: OTc0Mjg4MWE0ODFkZWMzYTAzMmM1NTYxMzAzYTk0YTQ.\r\n
CSeq: 1 INVITE\r\n
Session-Expires: 90;refresher=uac\r\n
Min-SE: 90\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE\r\n
Content-Type: application/sdp\r\n
Supported: timer\r\n
User-Agent: T-Com IpPbxSrv/11.10.0.325\r\n
Privacy: id\r\n
P-Asserted-Identity: <sip:+493088888880@172.20.172.223;user=phone>\r\n
P-Asserted-Identity: <sip:+493088888880@172.20.172.223;user=phone;x-type=unknown;x-plan=unknown;x-pres=allowed;x-screen=network;x-sendingcomplete>\r\n
P-Preferred-Identity: <sip:+493088888880@172.20.172.223;user=phone>\r\n
Content-Length: 153\r\n
\r\n
v=0\r\n
o=- 4140335521 1 IN IP4 192.168.193.58\r\n
s=T-Com IpPbxSrv\r\n
c=IN IP4 192.168.193.58\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/09 09:28:53,280  Devicetime: 2018/04/09 09:26:00,157 [Packet]: 
Sending datagram (536 Bytes) from 192.168.193.1:11891 to 172.20.172.223:5060 using UDP (RtgTag 193):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 172.20.172.223:5060;branch=z9hG4bK-d8754z-2511ae50573c696d-1---d8754z-;received=172.20.172.223;rport=5060\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=f857f35a\r\n
To: <sip:+4930222222@172.20.172.223;user=phone>;tag=-579579449-2109245942\r\n
Call-ID: OTc0Mjg4MWE0ODFkZWMzYTAzMmM1NTYxMzAzYTk0YTQ.\r\n
CSeq: 1 INVITE\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, SUBSCRIBE, UPDATE, PRACK\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 09:28:54,032  Devicetime: 2018/04/09 09:26:00,912 [Packet]: 
Sending datagram (1167 Bytes) from 87.139.100.100:14694 to 217.0.26.35:5060 using TCP (RtgTag 0):
INVITE sip:+4930222222@sip-trunk.telekom.de SIP/2.0\r\n
Via: SIP/2.0/TCP 87.139.100.100:14694;branch=z9hG4bK-a15e52e2-ad1b6823;rport\r\n
From: "Anonymous"<sip:anonymous@anonymous.invalid>;tag=271559671-1077764673\r\n
To: <sip:+4930222222@sip-trunk.telekom.de>\r\n
Call-ID: 2703721011@00a0572e9685\r\n
CSeq: 100 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, SUBSCRIBE, UPDATE, PRACK\r\n
Supported: 100rel\r\n
Contact: <sip:+493088888880@87.139.100.100:14694;transport=TCP>\r\n
P-Asserted-Identity: <sip:+493088888880@sip-trunk.telekom.de;user=phone>\r\n
Privacy: id\r\n
Authorization: Digest username="551122334455", realm="sip-trunk.telekom.de", algorithm=MD5, uri="sip:+4930222222@sip-trunk.telekom.de", nonce="ea460bfa8553c0a0ea460bfa5aaacdfa19d1b4fbb0eabb0dcd1c47f84f40b042", response="2c04589e17343d490081ca9161206c31"\r\n
Content-Type: application/sdp\r\n
Content-Length: 219\r\n
\r\n
v=0\r\n
o=- 3173728825 3173728825 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 11384 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/09 09:28:54,033  Devicetime: 2018/04/09 09:26:00,945 [Packet]: 
Receiving datagram (290 Bytes) at 87.139.100.100:14694 from 217.0.26.35:5060 using TCP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/TCP 87.139.100.100:14694;rport;branch=z9hG4bK-a15e52e2-ad1b6823\r\n
To: <sip:+4930222222@sip-trunk.telekom.de>\r\n
From: Anonymous <sip:anonymous@anonymous.invalid>;tag=271559671-1077764673\r\n
Call-ID: 2703721011@00a0572e9685\r\n
CSeq: 100 INVITE\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 09:28:54,388  Devicetime: 2018/04/09 09:26:01,265 [Packet]: 
Receiving datagram (629 Bytes) at 87.139.100.100:14694 from 217.0.26.35:5060 using TCP (RtgTag 0):
SIP/2.0 180 Ringing\r\n
Via: SIP/2.0/TCP 87.139.100.100:14694;rport=14694;branch=z9hG4bK-a15e52e2-ad1b6823\r\n
Record-Route: <sip:reg.sip-trunk.telekom.de;transport=tcp;lr>\r\n
To: <sip:+4930222222@sip-trunk.telekom.de>;tag=ab5995d1\r\n
From: Anonymous <sip:anonymous@anonymous.invalid>;tag=271559671-1077764673\r\n
Call-ID: 2703721011@00a0572e9685\r\n
Contact: <sip:qGQfxaBMFsYsCuwkE9+k2C19mdiho96dw0PXq7uY29psOpVPozVgRFmwhTaZWP9Z@th1>\r\n
CSeq: 100 INVITE\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK, REFER, REGISTER, UPDATE\r\n
Reason: TSSI;cause=0\r\n
Call-Info: <sip:+4930222222@tel.t-online.de>;purpose=call-completion;m=NR\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 09:28:54,389  Devicetime: 2018/04/09 09:26:01,266 [Packet]: 
Sending datagram (537 Bytes) from 192.168.193.1:11891 to 172.20.172.223:5060 using UDP (RtgTag 193):
SIP/2.0 180 Ringing\r\n
Via: SIP/2.0/UDP 172.20.172.223:5060;branch=z9hG4bK-d8754z-2511ae50573c696d-1---d8754z-;received=172.20.172.223;rport=5060\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=f857f35a\r\n
To: <sip:+4930222222@172.20.172.223;user=phone>;tag=-579579449-2109245942\r\n
Call-ID: OTc0Mjg4MWE0ODFkZWMzYTAzMmM1NTYxMzAzYTk0YTQ.\r\n
CSeq: 1 INVITE\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, SUBSCRIBE, UPDATE, PRACK\r\n
Content-Length: 0\r\n
\r\n


[SIP-Packet] 2018/04/09 09:30:54,362  Devicetime: 2018/04/09 09:28:01,266 [Packet]: 
Sending datagram (545 Bytes) from 192.168.193.1:11891 to 172.20.172.223:5060 using UDP (RtgTag 193):
SIP/2.0 408 Request Timeout\r\n
Via: SIP/2.0/UDP 172.20.172.223:5060;branch=z9hG4bK-d8754z-2511ae50573c696d-1---d8754z-;received=172.20.172.223;rport=5060\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=f857f35a\r\n
To: <sip:+4930222222@172.20.172.223;user=phone>;tag=-579579449-2109245942\r\n
Call-ID: OTc0Mjg4MWE0ODFkZWMzYTAzMmM1NTYxMzAzYTk0YTQ.\r\n
CSeq: 1 INVITE\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Server: Lancom\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, SUBSCRIBE, UPDATE, PRACK\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 09:30:54,362  Devicetime: 2018/04/09 09:28:01,268 [Packet]: 
Sending datagram (546 Bytes) from 87.139.100.100:14694 to 217.0.26.35:5060 using TCP (RtgTag 0):
CANCEL sip:+4930222222@sip-trunk.telekom.de SIP/2.0\r\n
Via: SIP/2.0/TCP 87.139.100.100:14694;branch=z9hG4bK-a15e52e2-ad1b6823;rport\r\n
Route: <sip:reg.sip-trunk.telekom.de;transport=tcp;lr>\r\n
From: "Anonymous"<sip:anonymous@anonymous.invalid>;tag=271559671-1077764673\r\n
To: <sip:+4930222222@sip-trunk.telekom.de>\r\n
Call-ID: 2703721011@00a0572e9685\r\n
CSeq: 100 CANCEL\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, SUBSCRIBE, UPDATE, PRACK\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 09:30:54,363  Devicetime: 2018/04/09 09:28:01,283 [Packet]: 
Receiving datagram (389 Bytes) at 192.168.193.1:11891 from 172.20.172.223:5060 using UDP (RtgTag 193):
ACK sip:SIP03088888880@192.168.193.1:11891;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 172.20.172.223:5060;branch=z9hG4bK-d8754z-2511ae50573c696d-1---d8754z-;rport\r\n
Max-Forwards: 70\r\n
To: <sip:+4930222222@172.20.172.223;user=phone>;tag=-579579449-2109245942\r\n
From: <sip:SIP03088888880@172.20.172.223>;tag=f857f35a\r\n
Call-ID: OTc0Mjg4MWE0ODFkZWMzYTAzMmM1NTYxMzAzYTk0YTQ.\r\n
CSeq: 1 ACK\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 09:30:54,375  Devicetime: 2018/04/09 09:28:01,300 [Packet]: 
Receiving datagram (299 Bytes) at 87.139.100.100:14694 from 217.0.26.35:5060 using TCP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/TCP 87.139.100.100:14694;rport;branch=z9hG4bK-a15e52e2-ad1b6823\r\n
To: <sip:+4930222222@sip-trunk.telekom.de>;tag=101db24d\r\n
From: Anonymous <sip:anonymous@anonymous.invalid>;tag=271559671-1077764673\r\n
Call-ID: 2703721011@00a0572e9685\r\n
CSeq: 100 CANCEL\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 09:30:54,376  Devicetime: 2018/04/09 09:28:01,309 [Packet]: 
Receiving datagram (512 Bytes) at 87.139.100.100:14694 from 217.0.26.35:5060 using TCP (RtgTag 0):
SIP/2.0 487 Request Terminated\r\n
Via: SIP/2.0/TCP 87.139.100.100:14694;rport=14694;branch=z9hG4bK-a15e52e2-ad1b6823\r\n
To: <sip:+4930222222@sip-trunk.telekom.de>;tag=ab5995d1\r\n
From: Anonymous <sip:anonymous@anonymous.invalid>;tag=271559671-1077764673\r\n
Call-ID: 2703721011@00a0572e9685\r\n
Contact: <sip:qGQfxaBMFsYsCuwkE9+k2C19mdiho96dw0PXq7uY29psOpVPozVgRFmwhTaZWP9Z@th1>\r\n
CSeq: 100 INVITE\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK, REGISTER, SUBSCRIBE, UPDATE\r\n
Reason: TSSI;cause=4870003\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/09 09:30:54,376  Devicetime: 2018/04/09 09:28:01,309 [Packet]: 
Sending datagram (461 Bytes) from 87.139.100.100:14694 to 217.0.26.35:5060 using TCP (RtgTag 0):
ACK sip:qGQfxaBMFsYsCuwkE9+k2C19mdiho96dw0PXq7uY29psOpVPozVgRFmwhTaZWP9Z@th1:5060 SIP/2.0\r\n
Via: SIP/2.0/TCP 87.139.100.100:14694;rport=14694;branch=z9hG4bK-a15e52e2-ad1b6823\r\n
From: "Anonymous"<sip:anonymous@anonymous.invalid>;tag=271559671-1077764673\r\n
To: <sip:+4930222222@sip-trunk.telekom.de>;tag=ab5995d1\r\n
Call-ID: 2703721011@00a0572e9685\r\n
CSeq: 100 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0292 / 06.03.2018\r\n
Content-Length: 0\r\n
\r\n
Vielen Dank und viele Grüße,
Jirka
Benutzeravatar
Jirka
Beiträge: 5225
Registriert: 03 Jan 2005, 13:39
Wohnort: Ex-OPAL-Gebiet
Kontaktdaten:

Re: All-IP/VoIP: Wie Geistereinträge in der Calls-Tabelle en

Beitrag von Jirka »

Hallo,

ich bin ja heute Nacht auf die 10.12.0355 umgestiegen, in der Hoffnung, dass da Fax geht. Ergebnis ist Fax geht nicht, dafür habe ich aber einen hängenden Call:

Code: Alles auswählen

Index                INFO:    2147483131
From_Line            INFO:    USER.SIP
From_DisplayName     INFO:    Fax Xyz
From_Number/Name     INFO:    56
From_Domain          INFO:    Xyz
To_Number/Name       INFO:    040888888888
To_Domain            INFO:    Xyz
Dest-Line            INFO:    1UND1-2222222
Dest-DisplayName     INFO:
Dest-Number/Name     INFO:    040888888888
Dest-Domain          INFO:    1und1.de
CF-Method            INFO:
Start                INFO:    04/18/2018 02:08:35
Connect              INFO:    04/18/2018 02:08:38
End                  INFO:
From_Codec           INFO:    PCMA
To_Codec             INFO:    PCMA
Status               INFO:    Connected
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-Remote-Proposal
Und das kam so:
Ich habe im LANCOM T.38 ausgeschaltet und im Sagem IP PhoneFax auch. Weil T.38 nicht geht, möchte ich das Fax per G.711 übertragen.
Ich wähle die Faxnummer am Faxgerät und drücke auf Senden:

Code: Alles auswählen

[SIP-Packet] 2018/04/18 02:08:35,919 [Packet]: 
Receiving datagram (592 Bytes) at 10.10.10.1:5060 from 10.10.10.17:5060 using UDP (RtgTag 1):
INVITE sip:040888888888@Xyz SIP/2.0\r\n
Via: SIP/2.0/UDP 10.10.10.17:5060;branch=z9hG4bK1094;rport\r\n
To: <sip:040888888888@Xyz>\r\n
From: Fax Xyz <sip:56@Xyz>;tag=sagem-sip4148\r\n
Call-ID: 30428@10.10.10.17\r\n
CSeq: 102 INVITE\r\n
Contact: <sip:56@10.10.10.17:5060>\r\n
Max-Forwards: 70\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, INFO, PRACK\r\n
Supported: replaces,100rel\r\n
Content-Type: application/sdp\r\n
Content-Length: 168\r\n
\r\n
v=0\r\n
o=56 30428 30428 IN IP4 10.10.10.17\r\n
s=Phone Call\r\n
c=IN IP4 10.10.10.17\r\n
t=0 0\r\n
m=audio 17358 RTP/AVP 8 0\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=sendrecv\r\n

[SIP-Packet] 2018/04/18 02:08:35,921 [Packet]: 
Sending datagram (391 Bytes) from 10.10.10.1:5060 to 10.10.10.17:5060 using UDP (RtgTag 1):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 10.10.10.17:5060;branch=z9hG4bK1094;received=10.10.10.17;rport=5060\r\n
From: "Fax Xyz"<sip:56@Xyz>;tag=sagem-sip4148\r\n
To: <sip:040888888888@Xyz>\r\n
Call-ID: 30428@10.10.10.17\r\n
CSeq: 102 INVITE\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Server: Lancom\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, PRACK, REGISTER\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/18 02:08:35,921 [Packet]: 
Sending datagram (546 Bytes) from 10.10.10.1:5060 to 10.10.10.17:5060 using UDP (RtgTag 1):
SIP/2.0 407 Proxy Authentication Required\r\n
Via: SIP/2.0/UDP 10.10.10.17:5060;branch=z9hG4bK1094;received=10.10.10.17;rport=5060\r\n
From: "Fax Xyz"<sip:56@Xyz>;tag=sagem-sip4148\r\n
To: <sip:040888888888@Xyz>;tag=-188001577-708805966\r\n
Call-ID: 30428@10.10.10.17\r\n
CSeq: 102 INVITE\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Server: Lancom\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, PRACK, REGISTER\r\n
Proxy-Authenticate: Digest realm="Xyz",nonce="446ca782223653c1fca3aac07e51d560",opaque="",algorithm=MD5\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/18 02:08:35,948 [Packet]: 
Receiving datagram (320 Bytes) at 10.10.10.1:5060 from 10.10.10.17:5060 using UDP (RtgTag 1):
ACK sip:040888888888@Xyz SIP/2.0\r\n
Via: SIP/2.0/UDP 10.10.10.17:5060;branch=z9hG4bK1094;rport\r\n
To: <sip:040888888888@Xyz>;tag=-188001577-708805966\r\n
From: Fax Xyz <sip:56@Xyz>;tag=sagem-sip4148\r\n
Call-ID: 30428@10.10.10.17\r\n
CSeq: 102 ACK\r\n
Contact: <sip:56@10.10.10.17:5060>\r\n
Max-Forwards: 70\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/18 02:08:35,955 [Packet]: 
Receiving datagram (789 Bytes) at 10.10.10.1:5060 from 10.10.10.17:5060 using UDP (RtgTag 1):
INVITE sip:040888888888@Xyz SIP/2.0\r\n
Via: SIP/2.0/UDP 10.10.10.17:5060;branch=z9hG4bK29763;rport\r\n
To: <sip:040888888888@Xyz>\r\n
From: Fax Xyz <sip:56@Xyz>;tag=sagem-sip4148\r\n
Call-ID: 30428@10.10.10.17\r\n
CSeq: 103 INVITE\r\n
Contact: <sip:56@10.10.10.17:5060>\r\n
Max-Forwards: 70\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, INFO, PRACK\r\n
Supported: replaces,100rel\r\n
Proxy-Authorization: Digest username="Fax",realm="Xyz",uri="sip:040888888888@Xyz",response="4c14a6cbe589cf82094f6ef2c4966f18",nonce="446ca782223653c1fca3aac07e51d560",opaque="",algorithm=MD5\r\n
Content-Type: application/sdp\r\n
Content-Length: 168\r\n
\r\n
v=0\r\n
o=56 30428 30428 IN IP4 10.10.10.17\r\n
s=Phone Call\r\n
c=IN IP4 10.10.10.17\r\n
t=0 0\r\n
m=audio 17358 RTP/AVP 8 0\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=sendrecv\r\n

[SIP-Packet] 2018/04/18 02:08:35,956 [Packet]: 
Sending datagram (392 Bytes) from 10.10.10.1:5060 to 10.10.10.17:5060 using UDP (RtgTag 1):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 10.10.10.17:5060;branch=z9hG4bK29763;received=10.10.10.17;rport=5060\r\n
From: "Fax Xyz"<sip:56@Xyz>;tag=sagem-sip4148\r\n
To: <sip:040888888888@Xyz>\r\n
Call-ID: 30428@10.10.10.17\r\n
CSeq: 103 INVITE\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Server: Lancom\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, PRACK, REGISTER\r\n
Content-Length: 0\r\n
\r\n
Soweit ist im LANCOM nun alles angekommen und ok. Der LANCOM schickt es nun zum Provider (1&1), die Ziel-Faxnummer ist übrigens bei Dus.net Premium-Fax-Dienst:

Code: Alles auswählen

[SIP-Packet] 2018/04/18 02:08:36,710 [Packet]: 
Sending datagram (994 Bytes) from 91.66.100.100:9491 to 212.227.124.130:5060 using UDP (RtgTag 0):
INVITE sip:040888888888@1und1.de SIP/2.0\r\n
Via: SIP/2.0/UDP 91.66.100.100:9491;branch=z9hG4bK-78ce0920-6215b841;rport\r\n
From: "Fax Xyz"<sip:4930222222222@1und1.de;user=phone>;tag=1894358470-563355305\r\n
To: <sip:040888888888@1und1.de>\r\n
Call-ID: 529823064@00a05711aa2d\r\n
CSeq: 100 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, PRACK\r\n
Supported: 100rel\r\n
Contact: <sip:4930222222222@91.66.100.100:9491;transport=UDP>\r\n
Proxy-Authorization: Digest username="4930222222222", realm="1und1.de", algorithm=MD5, uri="sip:040888888888@1und1.de", nonce="WtaJWFrWiCzE1MeOX9K9wLKvv5/5/COU", response="b23c88ff08794df5bc9b56576e6d61e6"\r\n
Content-Type: application/sdp\r\n
Content-Length: 239\r\n
\r\n
v=0\r\n
o=- 264911532 264911532 IN IP4 91.66.100.100\r\n
s=call\r\n
c=IN IP4 91.66.100.100\r\n
t=0 0\r\n
m=audio 12986 RTP/AVP 8 0 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n
a=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2018/04/18 02:08:36,742 [Packet]: 
Receiving datagram (484 Bytes) at 91.66.100.100:9491 from 212.227.124.130:5060 using UDP (RtgTag 0):
SIP/2.0 407 Proxy Authentication Required\r\n
Via: SIP/2.0/UDP 91.66.100.100:9491;received=91.66.100.100;branch=z9hG4bK-78ce0920-6215b841;rport=9491\r\n
From: "Fax Xyz"<sip:4930222222222@1und1.de;user=phone>;tag=1894358470-563355305\r\n
To: <sip:040888888888@1und1.de>;tag=b27e1a1d33761e85846fc98f5f3a7e58.c4d9\r\n
Call-ID: 529823064@00a05711aa2d\r\n
CSeq: 100 INVITE\r\n
Proxy-Authenticate: Digest realm="1und1.de", nonce="WtaNsFrWjISABdL2nak0xxdxWA7OuBYj"\r\n
Server: UI Kamailio\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/18 02:08:36,742 [Packet]: 
Sending datagram (470 Bytes) from 91.66.100.100:9491 to 212.227.124.130:5060 using UDP (RtgTag 0):
ACK sip:040888888888@1und1.de SIP/2.0\r\n
Via: SIP/2.0/UDP 91.66.100.100:9491;branch=z9hG4bK-78ce0920-6215b841;rport\r\n
From: "Fax Xyz"<sip:4930222222222@1und1.de;user=phone>;tag=1894358470-563355305\r\n
To: <sip:040888888888@1und1.de>;tag=b27e1a1d33761e85846fc98f5f3a7e58.c4d9\r\n
Call-ID: 529823064@00a05711aa2d\r\n
CSeq: 100 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, PRACK\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/18 02:08:36,743 [Packet]: 
Sending datagram (994 Bytes) from 91.66.100.100:9491 to 212.227.124.130:5060 using UDP (RtgTag 0):
INVITE sip:040888888888@1und1.de SIP/2.0\r\n
Via: SIP/2.0/UDP 91.66.100.100:9491;branch=z9hG4bK-e699f1e3-b26b9cbb;rport\r\n
From: "Fax Xyz"<sip:4930222222222@1und1.de;user=phone>;tag=1894358470-563355305\r\n
To: <sip:040888888888@1und1.de>\r\n
Call-ID: 529823064@00a05711aa2d\r\n
CSeq: 101 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, PRACK\r\n
Supported: 100rel\r\n
Proxy-Authorization: Digest username="4930222222222", realm="1und1.de", algorithm=MD5, uri="sip:040888888888@1und1.de", nonce="WtaNsFrWjISABdL2nak0xxdxWA7OuBYj", response="3121be07cb10fd80f02552232784a846"\r\n
Contact: <sip:4930222222222@91.66.100.100:9491;transport=UDP>\r\n
Content-Type: application/sdp\r\n
Content-Length: 239\r\n
\r\n
v=0\r\n
o=- 264911532 264911532 IN IP4 91.66.100.100\r\n
s=call\r\n
c=IN IP4 91.66.100.100\r\n
t=0 0\r\n
m=audio 12986 RTP/AVP 8 0 101\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-15\r\n
a=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2018/04/18 02:08:36,787 [Packet]: 
Receiving datagram (364 Bytes) at 91.66.100.100:9491 from 212.227.124.130:5060 using UDP (RtgTag 0):
SIP/2.0 100 trying -- your call is important to us\r\n
Via: SIP/2.0/UDP 91.66.100.100:9491;received=91.66.100.100;branch=z9hG4bK-e699f1e3-b26b9cbb;rport=9491\r\n
From: "Fax Xyz"<sip:4930222222222@1und1.de;user=phone>;tag=1894358470-563355305\r\n
To: <sip:040888888888@1und1.de>\r\n
Call-ID: 529823064@00a05711aa2d\r\n
CSeq: 101 INVITE\r\n
Server: UI Kamailio\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/18 02:08:38,515 [Packet]: 
Receiving datagram (1207 Bytes) at 91.66.100.100:9491 from 212.227.124.130:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 91.66.100.100:9491;received=91.66.100.100;branch=z9hG4bK-e699f1e3-b26b9cbb;rport=9491\r\n
From: "Fax Xyz"<sip:4930222222222@1und1.de;user=phone>;tag=1894358470-563355305\r\n
To: <sip:040888888888@1und1.de>;tag=008ea3.Ab2b7179.Pb2b629.B2b29.Tb2b1-1\r\n
Call-ID: 529823064@00a05711aa2d\r\n
CSeq: 101 INVITE\r\n
Record-Route: <sip:212.227.124.146;lr=on>\r\n
Record-Route: <sip:212.227.18.163;lr=on;ftag=1894358470-563355305>\r\n
Record-Route: <sip:212.227.124.130;lr=on>\r\n
Contact: <sip:040888888888@195.71.188.6:5060;transport=udp>\r\n
Accept: application/sdp,application/isup,multipart/mixed,application/vnd.siemens.key-event,application/vnd.siemens.surpass,application/dtmf-relay\r\n
Allow: PUBLISH,MESSAGE,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL\r\n
x-hmr: iis12!ois14!\r\n
Content-Length: 338\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=tsbc-frnk-de56 1541083696 1 IN IP4 212.227.124.67\r\n
s=sip call\r\n
c=IN IP4 212.227.124.67\r\n
t=0 0\r\n
m=audio 44428 RTP/AVP 8 0 101\r\n
a=sqn: 0\r\n
a=cdsc: 1 image udptl t38\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:8 vad=no\r\n
a=fmtp:0 vad=no\r\n
a=fmtp:101 0-15\r\n
a=sendrecv\r\n
a=rtcp:44429\r\n
a=ptime:20\r\n

[SIP-Packet] 2018/04/18 02:08:38,518 [Packet]: 
Sending datagram (729 Bytes) from 10.10.10.1:5060 to 10.10.10.17:5060 using UDP (RtgTag 1):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 10.10.10.17:5060;branch=z9hG4bK29763;received=10.10.10.17;rport=5060\r\n
From: "Fax Xyz"<sip:56@Xyz>;tag=sagem-sip4148\r\n
To: <sip:040888888888@Xyz>;tag=-188001577-708805966\r\n
Call-ID: 30428@10.10.10.17\r\n
CSeq: 103 INVITE\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Server: Lancom\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, PRACK, REGISTER\r\n
Contact: <sip:56@10.10.10.1:5060;transport=UDP>\r\n
Content-Type: application/sdp\r\n
Content-Length: 234\r\n
\r\n
v=0\r\n
o=- 0 0 IN IP4 10.10.10.1\r\n
s=call\r\n
c=IN IP4 10.10.10.1\r\n
t=0 0\r\n
m=audio 13556 RTP/AVP 8 0\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=fmtp:8 vad=no\r\n
a=fmtp:0 vad=no\r\n
a=sendrecv\r\n
a=ptime:20\r\n
a=sqn: 0\r\n
a=cdsc: 1 image udptl t38\r\n

[SIP-Packet] 2018/04/18 02:08:38,537 [Packet]: 
Receiving datagram (316 Bytes) at 10.10.10.1:5060 from 10.10.10.17:5060 using UDP (RtgTag 1):
ACK sip:56@10.10.10.1 SIP/2.0\r\n
Via: SIP/2.0/UDP 10.10.10.17:5060;branch=z9hG4bK16750;rport\r\n
To: <sip:040888888888@Xyz>;tag=-188001577-708805966\r\n
From: Fax Xyz <sip:56@Xyz>;tag=sagem-sip4148\r\n
Call-ID: 30428@10.10.10.17\r\n
CSeq: 103 ACK\r\n
Contact: <sip:56@10.10.10.17:5060>\r\n
Max-Forwards: 70\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/18 02:08:38,538 [Packet]: 
Sending datagram (833 Bytes) from 91.66.100.100:9491 to 212.227.124.130:5060 using UDP (RtgTag 0):
ACK sip:040888888888@195.71.188.6:5060;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 91.66.100.100:9491;branch=z9hG4bK-c714db60-3342bf57;rport\r\n
Route: <sip:212.227.124.130;lr=on>\r\n
Route: <sip:212.227.18.163;lr=on;ftag=1894358470-563355305>\r\n
Route: <sip:212.227.124.146;lr=on>\r\n
From: "Fax Xyz"<sip:4930222222222@1und1.de;user=phone>;tag=1894358470-563355305\r\n
To: <sip:040888888888@1und1.de>;tag=008ea3.Ab2b7179.Pb2b629.B2b29.Tb2b1-1\r\n
Call-ID: 529823064@00a05711aa2d\r\n
CSeq: 101 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, PRACK\r\n
Proxy-Authorization: Digest username="4930222222222", realm="1und1.de", algorithm=MD5, uri="sip:040888888888@1und1.de", nonce="WtaNsFrWjISABdL2nak0xxdxWA7OuBYj", response="3121be07cb10fd80f02552232784a846"\r\n
Content-Length: 0\r\n
\r\n
So, Anruf steht. Nun kommt vom Provider ein T.38-ReINVITE, was der LANCOM-Router passieren lässt und was das Fax-Gerät ordnungsgemäß ablehnt.

Code: Alles auswählen

[SIP-Packet] 2018/04/18 02:08:41,802 [Packet]: 
Receiving datagram (1824 Bytes) at 91.66.100.100:9491 from 212.227.124.130:5060 using UDP (RtgTag 0):
INVITE sip:4930222222222@91.66.100.100:9491;transport=UDP SIP/2.0\r\n
Record-Route: <sip:212.227.124.130;lr=on>\r\n
Record-Route: <sip:212.227.18.163;lr=on;ftag=008ea3.Ab2b7179.Pb2b629.B2b29.Tb2b1-1>\r\n
Record-Route: <sip:212.227.124.146;lr=on>\r\n
Via: SIP/2.0/UDP 212.227.124.130;branch=z9hG4bK3389.93b948e6a835678245f7158ffbeb804f.0\r\n
Via: SIP/2.0/UDP 212.227.18.163;branch=z9hG4bK3389.aeeea1cd3b93ee07323bed3cc2e0ce3c.0\r\n
Via: SIP/2.0/UDP 212.227.124.146;branch=z9hG4bK3389.2ef3569e14900e4c4f22241e41c82a0e.0\r\n
Via: SIP/2.0/UDP 195.71.188.6:5060;branch=z9hG4bKdnu43q306gd1s2np7250sb0000g00.1\r\n
Call-ID: 529823064@00a05711aa2d\r\n
From: <sip:040888888888@telefonica.de>;tag=008ea3.Ab2b7179.Pb2b629.B2b29.Tb2b1-1\r\n
To: <sip:+4930222222222@telefonica.carrier.sip.1und1.de;user=phone>;tag=1894358470-563355305\r\n
CSeq: 1 INVITE\r\n
Contact: <sip:040888888888@195.71.188.6:5060;transport=udp>\r\n
Max-Forwards: 62\r\n
Accept: application/sdp,application/isup,multipart/mixed,application/vnd.siemens.key-event,application/vnd.siemens.surpass,application/dtmf-relay\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, REGISTER, INFO, UPDATE, PRACK, MESSAGE, REFER, PUBLISH, NOTIFY\r\n
Min-SE: 600\r\n
Session-Expires: 3600;refresher=uas\r\n
Supported: timer\r\n
x-hmr: iis12!ois14!\r\n
Content-Length: 542\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=tsbc-frnk-de56 1541083696 2 IN IP4 62.52.146.44\r\n
s=sip call\r\n
c=IN IP4 62.52.146.44\r\n
t=0 0\r\n
m=image 34442 udptl t38\r\n
a=T38FaxVersion:0\r\n
a=T38MaxBitRate:14400\r\n
a=T38FaxRateManagement:transferredTCF\r\n
a=T38FaxMaxDatagram:849\r\n
a=ptime:20\r\n
a=T38FaxUdpEC:t38UDPRedundancy\r\n
v=0\r\n
o=tsbc-frnk-de56 1541083696 2 IN IP4 212.227.124.67\r\n
s=sip call\r\n
c=IN IP4 212.227.124.67\r\n
t=0 0\r\n
m=image 44428 udptl t38\r\n
a=T38FaxVersion:0\r\n
a=T38MaxBitRate:14400\r\n
a=T38FaxRateManagement:transferredTCF\r\n
a=T38FaxMaxDatagram:849\r\n
a=ptime:20\r\n
a=sendrecv\r\n
a=ptime:20\r\n
Ach an dieser Stelle gleich noch ein anderes Problem. Man achte auf die Angaben im SDP vom Provider und was der LANCOM daraus macht (siehe übernächstes Paket).

Code: Alles auswählen

[SIP-Packet] 2018/04/18 02:08:41,804 [Packet]: 
Sending datagram (903 Bytes) from 91.66.100.100:9491 to 212.227.124.130:5060 using UDP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 212.227.124.130;branch=z9hG4bK3389.93b948e6a835678245f7158ffbeb804f.0;received=212.227.124.130\r\n
Via: SIP/2.0/UDP 212.227.18.163;branch=z9hG4bK3389.aeeea1cd3b93ee07323bed3cc2e0ce3c.0\r\n
Via: SIP/2.0/UDP 212.227.124.146;branch=z9hG4bK3389.2ef3569e14900e4c4f22241e41c82a0e.0\r\n
Via: SIP/2.0/UDP 195.71.188.6:5060;branch=z9hG4bKdnu43q306gd1s2np7250sb0000g00.1\r\n
Record-Route: <sip:212.227.124.130;lr=on>,<sip:212.227.18.163;lr=on;ftag=008ea3.Ab2b7179.Pb2b629.B2b29.Tb2b1-1>,<sip:212.227.124.146;lr=on>\r\n
From: <sip:+4930222222222@telefonica.carrier.sip.1und1.de;user=phone>;tag=008ea3.Ab2b7179.Pb2b629.B2b29.Tb2b1-1\r\n
To: <sip:040888888888@telefonica.de>;tag=1894358470-563355305\r\n
Call-ID: 529823064@00a05711aa2d\r\n
CSeq: 1 INVITE\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Server: Lancom\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, PRACK\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/18 02:08:41,807 [Packet]: 
Sending datagram (944 Bytes) from 10.10.10.1:5060 to 10.10.10.17:5060 using UDP (RtgTag 1):
INVITE sip:56@10.10.10.17:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 10.10.10.1:5060;branch=z9hG4bK-fa10b7a2-7420db50;rport\r\n
From: <sip:040888888888@Xyz>;tag=-188001577-708805966\r\n
To: "Fax Xyz"<sip:56@Xyz>;tag=sagem-sip4148\r\n
Call-ID: 30428@10.10.10.17\r\n
CSeq: 1 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, PRACK, REGISTER\r\n
Supported: 100rel\r\n
Contact: <sip:040888888888@10.10.10.1:5060;transport=UDP>\r\n
Content-Type: application/sdp\r\n
Content-Length: 410\r\n
\r\n
v=0\r\n
o=- 0 1 IN IP4 10.10.10.1\r\n
s=call\r\n
c=IN IP4 10.10.10.1\r\n
t=0 0\r\n
m=image 13556 udptl t38\r\n
a=sendrecv\r\n
a=ptime:20\r\n
a=T38FaxVersion:0\r\n
a=T38MaxBitRate:14400\r\n
a=T38FaxRateManagement:transferredTCF\r\n
a=T38FaxMaxDatagram:849\r\n
a=T38FaxUdpEC:t38UDPRedundancy\r\n
m=image 44428 udptl t38\r\n
a=sendrecv\r\n
a=ptime:20\r\n
a=T38FaxVersion:0\r\n
a=T38MaxBitRate:14400\r\n
a=T38FaxRateManagement:transferredTCF\r\n
a=T38FaxMaxDatagram:849\r\n
Hier sieht man, was ich meine. Der Port 44428 ist falsch. Die anderen Angaben zumindest "doppelt".

Das Fax sagt jetzt, dass es kein T.38 möchte:

Code: Alles auswählen

[SIP-Packet] 2018/04/18 02:08:41,824 [Packet]: 
Receiving datagram (362 Bytes) at 10.10.10.1:5060 from 10.10.10.17:5060 using UDP (RtgTag 1):
SIP/2.0 415 Unsupported Media Type\r\n
Via: SIP/2.0/UDP 10.10.10.1:5060;branch=z9hG4bK-fa10b7a2-7420db50;rport=5060\r\n
To: "Fax Xyz" <sip:56@Xyz>;tag=sagem-sip4148\r\n
From: <sip:040888888888@Xyz>;tag=-188001577-708805966\r\n
Call-ID: 30428@10.10.10.17\r\n
CSeq: 1 INVITE\r\n
Accept: application/sdp,application/dtmf-relay\r\n
Accept-Encoding: identity\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/18 02:08:41,824 [Packet]: 
Sending datagram (417 Bytes) from 10.10.10.1:5060 to 10.10.10.17:5060 using UDP (RtgTag 1):
ACK sip:56@10.10.10.17:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 10.10.10.1:5060;branch=z9hG4bK-fa10b7a2-7420db50;rport\r\n
From: <sip:040888888888@Xyz>;tag=-188001577-708805966\r\n
To: "Fax Xyz"<sip:56@Xyz>;tag=sagem-sip4148\r\n
Call-ID: 30428@10.10.10.17\r\n
CSeq: 1 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, PRACK, REGISTER\r\n
Content-Length: 0\r\n
\r\n
Der LANCOM gibt das an den Provider weiter:

Code: Alles auswählen

[SIP-Packet] 2018/04/18 02:08:41,825 [Packet]: 
Sending datagram (919 Bytes) from 91.66.100.100:9491 to 212.227.124.130:5060 using UDP (RtgTag 0):
SIP/2.0 415 Unsupported Media Type\r\n
Via: SIP/2.0/UDP 212.227.124.130;branch=z9hG4bK3389.93b948e6a835678245f7158ffbeb804f.0;received=212.227.124.130\r\n
Via: SIP/2.0/UDP 212.227.18.163;branch=z9hG4bK3389.aeeea1cd3b93ee07323bed3cc2e0ce3c.0\r\n
Via: SIP/2.0/UDP 212.227.124.146;branch=z9hG4bK3389.2ef3569e14900e4c4f22241e41c82a0e.0\r\n
Via: SIP/2.0/UDP 195.71.188.6:5060;branch=z9hG4bKdnu43q306gd1s2np7250sb0000g00.1\r\n
Record-Route: <sip:212.227.124.130;lr=on>,<sip:212.227.18.163;lr=on;ftag=008ea3.Ab2b7179.Pb2b629.B2b29.Tb2b1-1>,<sip:212.227.124.146;lr=on>\r\n
From: <sip:+4930222222222@telefonica.carrier.sip.1und1.de;user=phone>;tag=008ea3.Ab2b7179.Pb2b629.B2b29.Tb2b1-1\r\n
To: <sip:040888888888@telefonica.de>;tag=1894358470-563355305\r\n
Call-ID: 529823064@00a05711aa2d\r\n
CSeq: 1 INVITE\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Server: Lancom\r\n
Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, PRACK\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/18 02:08:41,855 [Packet]: 
Receiving datagram (511 Bytes) at 91.66.100.100:9491 from 212.227.124.130:5060 using UDP (RtgTag 0):
ACK sip:4930222222222@91.66.100.100:9491;transport=UDP SIP/2.0\r\n
Record-Route: <sip:212.227.124.130;lr=on>\r\n
Via: SIP/2.0/UDP 212.227.124.130;branch=z9hG4bK3389.93b948e6a835678245f7158ffbeb804f.0\r\n
Via: SIP/2.0/UDP 212.227.18.163;branch=z9hG4bK3389.aeeea1cd3b93ee07323bed3cc2e0ce3c.0\r\n
Call-ID: 529823064@00a05711aa2d\r\n
From: <sip:040888888888@telefonica.de>;tag=008ea3.Ab2b7179.Pb2b629.B2b29.Tb2b1-1\r\n
To: <sip:040888888888@telefonica.de>;tag=1894358470-563355305\r\n
CSeq: 1 ACK\r\n
Max-Forwards: 62\r\n
Content-Length: 0\r\n
\r\n
Leider schickt der Provider nun ein BYE. Ohne T.38 also leider Fehlanzeige. Fehlverhalten vom Provider meiner Ansicht nach. Bescheiden, aber ein BYE ist ein BYE und dürfte ja noch nicht zu einem hängenden Call führen, um den es hier in erster Linie geht:

Code: Alles auswählen

[SIP-Packet] 2018/04/18 02:08:41,921 [Packet]: 
Receiving datagram (1006 Bytes) at 91.66.100.100:9491 from 212.227.124.130:5060 using UDP (RtgTag 0):
BYE sip:4930222222222@91.66.100.100:9491;transport=UDP SIP/2.0\r\n
Record-Route: <sip:212.227.124.130;lr=on>\r\n
Record-Route: <sip:212.227.18.163;lr=on;ftag=008ea3.Ab2b7179.Pb2b629.B2b29.Tb2b1-1>\r\n
Record-Route: <sip:212.227.124.146;lr=on>\r\n
Via: SIP/2.0/UDP 212.227.124.130;branch=z9hG4bK0389.d9131a7e4b436b43c954e715820ecab4.0\r\n
Via: SIP/2.0/UDP 212.227.18.163;branch=z9hG4bK0389.01ab0d152571ae9306f588e1d8bfc7db.0\r\n
Via: SIP/2.0/UDP 212.227.124.146;branch=z9hG4bK0389.841ccc75e3e0db07940a018fbacd2d09.0\r\n
Via: SIP/2.0/UDP 195.71.188.6:5060;branch=z9hG4bKdnu43q306gd1s2np7250sd0000010.1\r\n
Call-ID: 529823064@00a05711aa2d\r\n
From: <sip:040888888888@1und1.de>;tag=008ea3.Ab2b7179.Pb2b629.B2b29.Tb2b1-1\r\n
To: <sip:+4930222222222@1und1.de;user=phone>;tag=1894358470-563355305\r\n
CSeq: 2 BYE\r\n
Max-Forwards: 62\r\n
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, REGISTER, INFO, UPDATE, MESSAGE, REFER, PUBLISH, NOTIFY\r\n
Reason: SIP;cause=415,  Q.850;cause=127;text="Interworking, unspecified"\r\n
x-hmr: iis12!ois14!\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/04/18 02:08:41,922 [Packet]: 
Sending datagram (793 Bytes) from 91.66.100.100:9491 to 212.227.124.130:5060 using UDP (RtgTag 0):
SIP/2.0 481 Call/Transaction Does Not Exist\r\n
Via: SIP/2.0/UDP 212.227.124.130;branch=z9hG4bK0389.d9131a7e4b436b43c954e715820ecab4.0;received=212.227.124.130\r\n
Via: SIP/2.0/UDP 212.227.18.163;branch=z9hG4bK0389.01ab0d152571ae9306f588e1d8bfc7db.0\r\n
Via: SIP/2.0/UDP 212.227.124.146;branch=z9hG4bK0389.841ccc75e3e0db07940a018fbacd2d09.0\r\n
Via: SIP/2.0/UDP 195.71.188.6:5060;branch=z9hG4bKdnu43q306gd1s2np7250sd0000010.1\r\n
From: <sip:040888888888@1und1.de>;tag=008ea3.Ab2b7179.Pb2b629.B2b29.Tb2b1-1\r\n
To: <sip:+4930222222222@1und1.de;user=phone>;tag=1894358470-563355305\r\n
Call-ID: 529823064@00a05711aa2d\r\n
CSeq: 2 BYE\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Server: Lancom\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE\r\n
Content-Length: 0\r\n
\r\n
Der LANCOM sagt, der Call existiert nicht? Im LANCOM aber schon noch, der hängt hier ja noch. Auch das Faxgerät gibt nach einer Weile auf und schickt ein BYE, die zweite Chance, dass der LANCOM-Router den Call auch beendet:

Code: Alles auswählen

[SIP-Packet] 2018/04/18 02:09:17,483 [Packet]: 
Receiving datagram (373 Bytes) at 10.10.10.1:5060 from 10.10.10.17:5060 using UDP (RtgTag 1):
BYE sip:56@10.10.10.1 SIP/2.0\r\n
Via: SIP/2.0/UDP 10.10.10.17:5060;branch=z9hG4bK18745;rport\r\n
To: <sip:040888888888@Xyz>;tag=-188001577-708805966\r\n
From: Fax Xyz <sip:56@Xyz>;tag=sagem-sip4148\r\n
Call-ID: 30428@10.10.10.17\r\n
CSeq: 104 BYE\r\n
Max-Forwards: 70\r\n
Content-Length: 92\r\n
\r\n
v=0\r\n
o=56 30428 30428 IN IP4 10.10.10.17\r\n
s=Phone Call\r\n
c=IN IP4 10.10.10.17\r\n
t=0 0\r\n
m= 0 \r\n

[SIP-Packet] 2018/04/18 02:09:17,483 [Packet]: 
Sending datagram (466 Bytes) from 10.10.10.1:5060 to 10.10.10.17:5060 using UDP (RtgTag 1):
SIP/2.0 481 Call/Transaction Does Not Exist\r\n
Via: SIP/2.0/UDP 10.10.10.17:5060;branch=z9hG4bK18745;received=10.10.10.17;rport=5060\r\n
From: "Fax Xyz"<sip:56@Xyz>;tag=sagem-sip4148\r\n
To: <sip:040888888888@Xyz>;tag=-188001577-708805966\r\n
Call-ID: 30428@10.10.10.17\r\n
CSeq: 104 BYE\r\n
User-Agent: LANCOM 1781EF+ / 10.12.0355 / 13.04.2018\r\n
Server: Lancom\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE\r\n
Content-Length: 0\r\n
\r\n
Aber auch da sagt er, dass der Call nicht existiert, obwohl er noch da ist. Und so hängt er jetzt immer noch.

Vielen Dank und viele Grüße,
Jirka
Benutzeravatar
Jirka
Beiträge: 5225
Registriert: 03 Jan 2005, 13:39
Wohnort: Ex-OPAL-Gebiet
Kontaktdaten:

Re: All-IP/VoIP: Wie Geistereinträge in der Calls-Tabelle en

Beitrag von Jirka »

Hallo,

hängender Call:

Code: Alles auswählen

Status/Voice-Call-Manager/Calls:
Index                INFO:    2147483023
From_Line            INFO:    TELEKOM-88888888
From_DisplayName     INFO:
From_Number/Name     INFO:    +491737777777
From_Domain          INFO:    arcor.de
To_Number/Name       INFO:    +493088888888
To_Domain            INFO:    telekom.de
Dest-Line            INFO:    SWYXGW-WRM
Dest-DisplayName     INFO:
Dest-Number/Name     INFO:    +493088888888
Dest-Domain          INFO:    172.20.172.223
CF-Method            INFO:
Start                INFO:    05/22/2018 15:22:23
Connect              INFO:    05/22/2018 15:22:26
End                  INFO:
From_Codec           INFO:    PCMA
To_Codec             INFO:    PCMA
Status               INFO:    Connected
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
Trace:
Am Anfang verläuft alles nach Plan:

Code: Alles auswählen

[SIP-Packet] 2018/05/22 15:22:19,855  Devicetime: 2018/05/22 15:22:23,676 [Packet]: 
Receiving datagram (1400 Bytes) at 217.92.10.10:13021 from 217.0.29.32:5060 using UDP (RtgTag 0):
INVITE sip:+493088888888@217.92.10.10:13021;transport=udp SIP/2.0\r\n
Max-Forwards: 19\r\n
Via: SIP/2.0/UDP 217.0.29.32:5060;branch=z9hG4bKg3Zqkv7igncq1g83ccmvf66hmufd6kyuh\r\n
To: <sip:+493088888888@telekom.de;user=phone>\r\n
From: <sip:+491737777777@arcor.de;user=phone>;tag=h7g4Esbg_p65550t1526995342m318445c903503255s1_1324612594-781683134\r\n
Call-ID: p65550t1526995342m318445c903503255s2\r\n
CSeq: 1 INVITE\r\n
Contact: <sip:sgc_c@217.0.29.32;transport=udp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"\r\n
Record-Route: <sip:217.0.29.32;transport=udp;lr>\r\n
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"\r\n
Min-Se: 900\r\n
P-Asserted-Identity: <sip:+491737777777@vodafone.de;user=phone>\r\n
Session-Expires: 1800\r\n
Supported: timer\r\n
Supported: resource-priority\r\n
Supported: 100rel\r\n
Content-Type: application/sdp\r\n
Content-Length: 207\r\n
Session-ID: 298418da9c8d2d137a0856c89c6fb69a\r\n
Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, PRACK, UPDATE, INFO, INVITE, ACK, OPTIONS, CANCEL, BYE\r\n
Accept: application/isup\r\n
Accept: application/xml\r\n
Accept: application/media_control+xml\r\n
Accept: application/vnd.etsi.cug+xml\r\n
Accept: application/vnd.etsi.sci+xml\r\n
Accept: application/sdp\r\n
\r\n
v=0\r\n
o=- 931497258 1324612372 IN IP4 217.0.29.32\r\n
s=IMSS\r\n
c=IN IP4 217.0.7.52\r\n
t=0 0\r\n
m=audio 6664 RTP/AVP 8 101 18 106\r\n
a=rtpmap:101 G726-32/8000\r\n
a=rtpmap:106 telephone-event/8000\r\n
a=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2018/05/22 15:22:19,859  Devicetime: 2018/05/22 15:22:23,680 [Packet]: 
Sending datagram (624 Bytes) from 217.92.10.10:13021 to 217.0.29.32:5060 using UDP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 217.0.29.32:5060;branch=z9hG4bKg3Zqkv7igncq1g83ccmvf66hmufd6kyuh;received=217.0.29.32\r\n
Record-Route: <sip:217.0.29.32;transport=udp;lr>\r\n
From: <sip:+491737777777@arcor.de;user=phone>;tag=h7g4Esbg_p65550t1526995342m318445c903503255s1_1324612594-781683134\r\n
To: <sip:+493088888888@telekom.de;user=phone>;tag=-394362422--1714954615\r\n
Call-ID: p65550t1526995342m318445c903503255s2\r\n
CSeq: 1 INVITE\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0375 / 18.05.2018\r\n
Server: Lancom\r\n
Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/05/22 15:22:20,610  Devicetime: 2018/05/22 15:22:24,436 [Packet]: 
Sending datagram (1166 Bytes) from 192.168.180.3:11037 to 172.20.172.223:5060 using UDP (RtgTag 0):
INVITE sip:+493088888888@172.20.172.223 SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-3e440eae-dbff008a;rport\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-1889106377-1302990114\r\n
To: <sip:+493088888888@telekom.de;user=phone>\r\n
Call-ID: 1831191444@00a0572e2d44\r\n
CSeq: 100 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0375 / 18.05.2018\r\n
Allow: REFER, NOTIFY, SUBSCRIBE, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE\r\n
Supported: 100rel\r\n
Contact: <sip:LANCOM102@192.168.180.3:11037;transport=UDP>\r\n
P-Preferred-Identity: <sip:+491737777777@arcor.de;user=phone>\r\n
Authorization: Digest username="LANCOM102", realm="172.20.172.223", algorithm=MD5, uri="sip:+493088888888@172.20.172.223", nonce="286268071:99e98e600f44287e64404929c61befec", response="0b7bf4c35b0ac9bfb2f0632b71adee3b"\r\n
Content-Type: application/sdp\r\n
Content-Length: 294\r\n
\r\n
v=0\r\n
o=- 915595722 915595722 IN IP4 192.168.180.3\r\n
s=call\r\n
c=IN IP4 192.168.180.3\r\n
t=0 0\r\n
m=audio 9452 RTP/AVP 8 101 18 106\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:101 G726-32/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=rtpmap:106 telephone-event/8000\r\n
a=fmtp:18 annexb=no\r\n
a=fmtp:106 0-15\r\n
a=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2018/05/22 15:22:20,689  Devicetime: 2018/05/22 15:22:24,485 [Packet]: 
Receiving datagram (420 Bytes) at 192.168.180.3:11037 from 172.20.172.223:5060 using UDP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-3e440eae-dbff008a;rport=11037\r\n
To: <sip:+493088888888@telekom.de;user=phone>\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-1889106377-1302990114\r\n
Call-ID: 1831191444@00a0572e2d44\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/05/22 15:22:20,832  Devicetime: 2018/05/22 15:22:24,658 [Packet]: 
Receiving datagram (594 Bytes) at 192.168.180.3:11037 from 172.20.172.223:5060 using UDP (RtgTag 0):
SIP/2.0 180 Ringing\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-3e440eae-dbff008a;rport=11037\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: "WM-MR-410"<sip:+493088888888@telekom.de;user=phone>;tag=712d1128\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-1889106377-1302990114\r\n
Call-ID: 1831191444@00a0572e2d44\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: h1kjawo4zwc1\r\n
X-IPPBXCalledNumber: 88888888\r\n
X-IPPBXCalledName: WM-MR-410\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/05/22 15:22:20,833  Devicetime: 2018/05/22 15:22:24,660 [Packet]: 
Sending datagram (625 Bytes) from 217.92.10.10:13021 to 217.0.29.32:5060 using UDP (RtgTag 0):
SIP/2.0 180 Ringing\r\n
Via: SIP/2.0/UDP 217.0.29.32:5060;branch=z9hG4bKg3Zqkv7igncq1g83ccmvf66hmufd6kyuh;received=217.0.29.32\r\n
Record-Route: <sip:217.0.29.32;transport=udp;lr>\r\n
From: <sip:+491737777777@arcor.de;user=phone>;tag=h7g4Esbg_p65550t1526995342m318445c903503255s1_1324612594-781683134\r\n
To: <sip:+493088888888@telekom.de;user=phone>;tag=-394362422--1714954615\r\n
Call-ID: p65550t1526995342m318445c903503255s2\r\n
CSeq: 1 INVITE\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0375 / 18.05.2018\r\n
Server: Lancom\r\n
Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/05/22 15:22:22,870  Devicetime: 2018/05/22 15:22:26,690 [Packet]: 
Receiving datagram (733 Bytes) at 192.168.180.3:11037 from 172.20.172.223:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-3e440eae-dbff008a;rport=11037\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: "WM-MR-410"<sip:+493088888888@telekom.de;user=phone>;tag=712d1128\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-1889106377-1302990114\r\n
Call-ID: 1831191444@00a0572e2d44\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: 210\r\n
\r\n
v=0\r\n
o=- 2253455223 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 51210 RTP/AVP 8 106\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:106 telephone-event/8000\r\n
a=fmtp:106 0-15\r\n
a=ptime:20\r\n

[SIP-Packet] 2018/05/22 15:22:22,871  Devicetime: 2018/05/22 15:22:26,693 [Packet]: 
Sending datagram (915 Bytes) from 217.92.10.10:13021 to 217.0.29.32:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 217.0.29.32:5060;branch=z9hG4bKg3Zqkv7igncq1g83ccmvf66hmufd6kyuh;received=217.0.29.32\r\n
Record-Route: <sip:217.0.29.32;transport=udp;lr>\r\n
From: <sip:+491737777777@arcor.de;user=phone>;tag=h7g4Esbg_p65550t1526995342m318445c903503255s1_1324612594-781683134\r\n
To: <sip:+493088888888@telekom.de;user=phone>;tag=-394362422--1714954615\r\n
Call-ID: p65550t1526995342m318445c903503255s2\r\n
CSeq: 1 INVITE\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0375 / 18.05.2018\r\n
Server: Lancom\r\n
Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE\r\n
Contact: <sip:+493088888888@217.92.10.10:13021;transport=UDP>\r\n
Content-Type: application/sdp\r\n
Content-Length: 199\r\n
\r\n
v=0\r\n
o=- 0 0 IN IP4 217.92.10.10\r\n
s=call\r\n
c=IN IP4 217.92.10.10\r\n
t=0 0\r\n
m=audio 11762 RTP/AVP 8 106\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:106 telephone-event/8000\r\n
a=fmtp:106 0-15\r\n
a=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2018/05/22 15:22:23,031  Devicetime: 2018/05/22 15:22:26,807 [Packet]: 
Receiving datagram (547 Bytes) at 217.92.10.10:13021 from 217.0.29.32:5060 using UDP (RtgTag 0):
ACK sip:+493088888888@217.92.10.10:13021;transport=udp SIP/2.0\r\n
Max-Forwards: 21\r\n
Via: SIP/2.0/UDP 217.0.29.32:5060;branch=z9hG4bKg3Zqkv7iujd3zgr63mdb8pkslr5dr9hme\r\n
To: <sip:+493088888888@telekom.de;user=phone>;tag=-394362422--1714954615\r\n
From: <sip:+491737777777@arcor.de;user=phone>;tag=h7g4Esbg_p65550t1526995342m318445c903503255s1_1324612594-781683134\r\n
Call-ID: p65550t1526995342m318445c903503255s2\r\n
CSeq: 1 ACK\r\n
Contact: <sip:sgc_c@217.0.29.32;transport=udp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/05/22 15:22:23,032  Devicetime: 2018/05/22 15:22:26,809 [Packet]: 
Sending datagram (709 Bytes) from 192.168.180.3:11037 to 172.20.172.223:5060 using UDP (RtgTag 0):
ACK sip:172.20.172.223:5060;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-3e76d4f0-4e109711;rport\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-1889106377-1302990114\r\n
To: <sip:+493088888888@telekom.de;user=phone>;tag=712d1128\r\n
Call-ID: 1831191444@00a0572e2d44\r\n
CSeq: 100 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0375 / 18.05.2018\r\n
Allow: REFER, NOTIFY, SUBSCRIBE, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE\r\n
Authorization: Digest username="LANCOM102", realm="172.20.172.223", algorithm=MD5, uri="sip:+493088888888@172.20.172.223", nonce="286268071:99e98e600f44287e64404929c61befec", response="0b7bf4c35b0ac9bfb2f0632b71adee3b"\r\n
Content-Length: 0\r\n
\r\n
Telefongespräch besteht, REFER:

Code: Alles auswählen

[SIP-Packet] 2018/05/22 15:22:33,209  Devicetime: 2018/05/22 15:22:37,022 [Packet]: 
Receiving datagram (771 Bytes) at 192.168.180.3:11037 from 172.20.172.223:5060 using UDP (RtgTag 0):
REFER sip:LANCOM102@192.168.180.3:11037;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 172.20.172.223:5060;branch=z9hG4bK-d8754z-d127813eb71fa906-1---d8754z-;rport\r\n
Max-Forwards: 70\r\n
Contact: <sip:+493088888888@172.20.172.223:5060;transport=udp>\r\n
To: <sip:LANCOM102@172.20.172.223>;tag=-1889106377-1302990114\r\n
From: <sip:+493088888888@telekom.de;user=phone>;tag=712d1128\r\n
Call-ID: 1831191444@00a0572e2d44\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: "HGW-TELR-167"<sip:03834555567@172.20.172.223;user=phone?Replaces=x-ippbx-transferid%3Bto-tag%3D315%3Bfrom-tag%3D315>\r\n
Referred-By: <sip:+493088888888@telekom.de;user=phone>\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/05/22 15:22:33,209  Devicetime: 2018/05/22 15:22:37,023 [Packet]: 
Sending datagram (569 Bytes) from 192.168.180.3:11037 to 172.20.172.223:5060 using UDP (RtgTag 0):
SIP/2.0 202 Accepted\r\n
Via: SIP/2.0/UDP 172.20.172.223:5060;branch=z9hG4bK-d8754z-d127813eb71fa906-1---d8754z-;received=172.20.172.223;rport=5060\r\n
From: <sip:+493088888888@telekom.de;user=phone>;tag=712d1128\r\n
To: <sip:LANCOM102@172.20.172.223>;tag=-1889106377-1302990114\r\n
Call-ID: 1831191444@00a0572e2d44\r\n
CSeq: 1 REFER\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0375 / 18.05.2018\r\n
Server: Lancom\r\n
Allow: REFER, NOTIFY, SUBSCRIBE, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE\r\n
Contact: <sip:+491737777777@192.168.180.3:11037;transport=UDP>\r\n
Content-Length: 0\r\n
\r\n
Weiter mit dem INVITE (aufgrund des REFERs), soweit ok:

Code: Alles auswählen

[SIP-Packet] 2018/05/22 15:22:33,209  Devicetime: 2018/05/22 15:22:37,030 [Packet]: 
Sending datagram (1206 Bytes) from 192.168.180.3:11037 to 172.20.172.223:5060 using UDP (RtgTag 0):
INVITE sip:03834555567@172.20.172.223 SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-c866f833-06f33256;rport\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-883738807-1840969063\r\n
To: <sip:03834555567@172.20.172.223;user=phone>\r\n
Call-ID: 1793050362@00a0572e2d44\r\n
CSeq: 100 INVITE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0375 / 18.05.2018\r\n
Supported: 100rel\r\n
Contact: <sip:LANCOM102@192.168.180.3:11037;transport=UDP>\r\n
Replaces: x-ippbx-transferid;from-tag=315;to-tag=315\r\n
Referred-By: <sip:+493088888888@telekom.de>\r\n
P-Asserted-Identity: <sip:+491737777777@arcor.de;user=phone>\r\n
Authorization: Digest username="LANCOM102", realm="172.20.172.223", algorithm=MD5, uri="sip:03834555567@172.20.172.223", nonce="286268071:99e98e600f44287e64404929c61befec", response="110e5e965ec4f2119119948feb678277"\r\n
Content-Type: application/sdp\r\n
Content-Length: 319\r\n
\r\n
v=0\r\n
o=- 896525181 896525181 IN IP4 192.168.180.3\r\n
s=call\r\n
c=IN IP4 192.168.180.3\r\n
t=0 0\r\n
m=audio 13198 RTP/AVP 8 0 101 18 106\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:101 G726-32/8000\r\n
a=rtpmap:18 G729/8000\r\n
a=rtpmap:106 telephone-event/8000\r\n
a=fmtp:18 annexb=no\r\n
a=fmtp:106 0-15\r\n
a=sendrecv\r\n
a=ptime:20\r\n

[SIP-Packet] 2018/05/22 15:22:33,210  Devicetime: 2018/05/22 15:22:37,030 [Packet]: 
Sending datagram (673 Bytes) from 192.168.180.3:11037 to 172.20.172.223:5060 using UDP (RtgTag 0):
NOTIFY sip:172.20.172.223:5060;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-ef9d56d5-496365fb;rport\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-1889106377-1302990114\r\n
To: <sip:+493088888888@telekom.de;user=phone>;tag=712d1128\r\n
Call-ID: 1831191444@00a0572e2d44\r\n
CSeq: 101 NOTIFY\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0375 / 18.05.2018\r\n
Allow: REFER, NOTIFY, SUBSCRIBE, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE\r\n
Contact: <sip:LANCOM102@192.168.180.3:11037;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
Eigenartig ist die letzte Zeile hier oben ("SIP/2.0 100 Trying\r\n"). Wie kommt die dahin? Was soll die da?

Jetzt wird es interessant. Providerseitig wird das Telefongespräch beendet. Der LANCOM bestätigt das providerseitig mit OK:

Code: Alles auswählen

[SIP-Packet] 2018/05/22 15:22:33,210  Devicetime: 2018/05/22 15:22:37,042 [Packet]: 
Receiving datagram (571 Bytes) at 217.92.10.10:13021 from 217.0.29.32:5060 using UDP (RtgTag 0):
BYE sip:+493088888888@217.92.10.10:13021;transport=udp SIP/2.0\r\n
Max-Forwards: 64\r\n
Via: SIP/2.0/UDP 217.0.29.32:5060;branch=z9hG4bKg3Zqkv7iyoreb2uw49kncwhsq19qotnlf\r\n
To: <sip:+493088888888@telekom.de;user=phone>;tag=-394362422--1714954615\r\n
From: <sip:+491737777777@arcor.de;user=phone>;tag=h7g4Esbg_p65550t1526995342m318445c903503255s1_1324612594-781683134\r\n
Call-ID: p65550t1526995342m318445c903503255s2\r\n
CSeq: 2 BYE\r\n
Reason: Q.850;cause=16;text="10"\r\n
Content-Length: 0\r\n
Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, PRACK, UPDATE, INFO, INVITE, ACK, OPTIONS, CANCEL, BYE\r\n
\r\n

[SIP-Packet] 2018/05/22 15:22:33,210  Devicetime: 2018/05/22 15:22:37,045 [Packet]: 
Sending datagram (567 Bytes) from 217.92.10.10:13021 to 217.0.29.32:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 217.0.29.32:5060;branch=z9hG4bKg3Zqkv7iyoreb2uw49kncwhsq19qotnlf;received=217.0.29.32\r\n
From: <sip:+491737777777@arcor.de;user=phone>;tag=h7g4Esbg_p65550t1526995342m318445c903503255s1_1324612594-781683134\r\n
To: <sip:+493088888888@telekom.de;user=phone>;tag=-394362422--1714954615\r\n
Call-ID: p65550t1526995342m318445c903503255s2\r\n
CSeq: 2 BYE\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0375 / 18.05.2018\r\n
Server: Lancom\r\n
Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE\r\n
Content-Length: 0\r\n
\r\n
Jetzt schickt der LANCOM ein "Decline" an die Telefonanlage. Jedoch leider mit falscher Call-Sequence (CSeq):

Code: Alles auswählen

[SIP-Packet] 2018/05/22 15:22:33,211  Devicetime: 2018/05/22 15:22:37,047 [Packet]: 
Sending datagram (364 Bytes) from 192.168.180.3:11037 to 172.20.172.223:5060 using UDP (RtgTag 0):
SIP/2.0 603 Decline\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-c866f833-06f33256;rport\r\n
From: <sip:03834555567@172.20.172.223;user=phone>\r\n
To: <sip:LANCOM102@172.20.172.223>;tag=-883738807-1840969063\r\n
Call-ID: 1793050362@00a0572e2d44\r\n
CSeq: 0 INVITE\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0375 / 18.05.2018\r\n
Server: Lancom\r\n
Content-Length: 0\r\n
\r\n
Damit nimmt das Unheil seinen Lauf, die Telefonanlage kann das Paket nicht zuordnen und macht weiter:

Code: Alles auswählen

[SIP-Packet] 2018/05/22 15:22:33,239  Devicetime: 2018/05/22 15:22:37,075 [Packet]: 
Receiving datagram (422 Bytes) at 192.168.180.3:11037 from 172.20.172.223:5060 using UDP (RtgTag 0):
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-c866f833-06f33256;rport=11037\r\n
To: <sip:03834555567@172.20.172.223;user=phone>\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-883738807-1840969063\r\n
Call-ID: 1793050362@00a0572e2d44\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/05/22 15:22:33,239  Devicetime: 2018/05/22 15:22:37,076 [Packet]: 
Receiving datagram (479 Bytes) at 192.168.180.3:11037 from 172.20.172.223:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-ef9d56d5-496365fb;rport=11037\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:+493088888888@telekom.de;user=phone>;tag=712d1128\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-1889106377-1302990114\r\n
Call-ID: 1831191444@00a0572e2d44\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/05/22 15:22:33,286  Devicetime: 2018/05/22 15:22:37,104 [Packet]: 
Receiving datagram (681 Bytes) at 192.168.180.3:11037 from 172.20.172.223:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-c866f833-06f33256;rport=11037\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: "HGW-TELR-167"<sip:03834555567@172.20.172.223;user=phone>;tag=5103845d\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-883738807-1840969063\r\n
Call-ID: 1793050362@00a0572e2d44\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=- 2685701933 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 schickt der LANCOM ein BYE mit korrekter Call-Sequence:

Code: Alles auswählen

[SIP-Packet] 2018/05/22 15:22:33,286  Devicetime: 2018/05/22 15:22:37,104 [Packet]: 
Sending datagram (408 Bytes) from 192.168.180.3:11037 to 172.20.172.223:5060 using UDP (RtgTag 0):
BYE sip:172.20.172.223:5060;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-b78071ae-3492af17;rport\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-883738807-1840969063\r\n
To: <sip:03834555567@172.20.172.223;user=phone>;tag=5103845d\r\n
Call-ID: 1793050362@00a0572e2d44\r\n
CSeq: 101 BYE\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0375 / 18.05.2018\r\n
Content-Length: 0\r\n
\r\n
Es geht entsprechend weiter:

Code: Alles auswählen

[SIP-Packet] 2018/05/22 15:22:33,379  Devicetime: 2018/05/22 15:22:37,148 [Packet]: 
Receiving datagram (447 Bytes) at 192.168.180.3:11037 from 172.20.172.223:5060 using UDP (RtgTag 0):
SIP/2.0 487 Request Terminated\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-c866f833-06f33256;rport=11037\r\n
To: <sip:03834555567@172.20.172.223;user=phone>;tag=5103845d\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-883738807-1840969063\r\n
Call-ID: 1793050362@00a0572e2d44\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/05/22 15:22:33,379  Devicetime: 2018/05/22 15:22:37,149 [Packet]: 
Sending datagram (627 Bytes) from 192.168.180.3:11037 to 172.20.172.223:5060 using UDP (RtgTag 0):
ACK sip:172.20.172.223:5060;transport=udp SIP/2.0\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-b78071ae-3492af17;rport\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-883738807-1840969063\r\n
To: <sip:03834555567@172.20.172.223;user=phone>;tag=5103845d\r\n
Call-ID: 1793050362@00a0572e2d44\r\n
CSeq: 100 ACK\r\n
Max-Forwards: 70\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0375 / 18.05.2018\r\n
Authorization: Digest username="LANCOM102", realm="172.20.172.223", algorithm=MD5, uri="sip:03834555567@172.20.172.223", nonce="286268071:99e98e600f44287e64404929c61befec", response="110e5e965ec4f2119119948feb678277"\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/05/22 15:22:33,379  Devicetime: 2018/05/22 15:22:37,153 [Packet]: 
Sending datagram (369 Bytes) from 192.168.180.3:11037 to 172.20.172.223:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-b78071ae-3492af17;rport\r\n
From: <sip:03834555567@172.20.172.223;user=phone>;tag=5103845d\r\n
To: <sip:LANCOM102@172.20.172.223>;tag=-883738807-1840969063\r\n
Call-ID: 1793050362@00a0572e2d44\r\n
CSeq: 0 BYE\r\n
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0375 / 18.05.2018\r\n
Server: Lancom\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2018/05/22 15:22:33,380  Devicetime: 2018/05/22 15:22:37,155 [Packet]: 
Receiving datagram (478 Bytes) at 192.168.180.3:11037 from 172.20.172.223:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 192.168.180.3:11037;branch=z9hG4bK-b78071ae-3492af17;rport=11037\r\n
Contact: <sip:172.20.172.223:5060;transport=udp>\r\n
To: <sip:03834555567@172.20.172.223;user=phone>;tag=5103845d\r\n
From: <sip:LANCOM102@172.20.172.223>;tag=-883738807-1840969063\r\n
Call-ID: 1793050362@00a0572e2d44\r\n
CSeq: 101 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
Telefonat wurde also nun das "zweite Mal" beendet und hängt trotzdem noch...

Vielen Dank und viele Grüße,
Jirka
Antworten