Daniel Floeckinger Posted May 31, 2007 Report Share Posted May 31, 2007 Hi! We have managed to set up T38 on both our, our gateway to the outside world and our ATA. If the ATA registers on the Gateway, T38 works fine. However, if i use the ATA as a PBXnSIP extension, and the gateway sends a re-invite, i receive the sip message "NOT SUPPORTED" from the PBX. Now, is the PBX T38 compatible or not???? And if yes, why does it react this way? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 31, 2007 Report Share Posted May 31, 2007 Do you have the SIP packets from the log? Would be interesting to see what is wrong. Quote Link to comment Share on other sites More sharing options...
Daniel Floeckinger Posted June 1, 2007 Author Report Share Posted June 1, 2007 Here u go... Both negotiate T38. But after that i can only see "malformed" packets in ethereal. The fax is 192.168.16.124, the Gateway 192.168.16.12, the pbx 192.168.16.110 [7] 2007/06/01 18:20:16: SIP Rx udp:192.168.16.124:5060: INVITE sip:0664771607997@192.168.16.110 SIP/2.0 Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK2113019710;rport Route: <sip:192.168.16.110:5060;lr> From: "Fax" <sip:15@192.168.16.110>;tag=1026814437 To: <sip:0664771607997@192.168.16.110> Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 60 INVITE Contact: <sip:15@192.168.16.124:5060> Max-Forwards: 70 Supported: replaces, path User-Agent: Grandstream HT-502 1.0.0.39 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Content-Type: application/sdp Content-Length: 363 v=0 o=15 8000 8000 IN IP4 192.168.16.124 s=SIP Call c=IN IP4 192.168.16.124 t=0 0 m=audio 5004 RTP/AVP 0 8 4 18 2 97 103 102 a=sendrecv a=rtpmap:0 PCMU/8000 a=ptime:20 a=rtpmap:8 PCMA/8000 a=rtpmap:4 G723/8000 a=rtpmap:18 G729/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=20 a=rtpmap:103 G726-40/8000 a=rtpmap:102 G729E/8000 [0] 2007/06/01 18:20:16: UDP: Illegal port number [7] 2007/06/01 18:20:16: UDP: Opening socket on port 49966 [7] 2007/06/01 18:20:16: UDP: Opening socket on port 49967 [5] 2007/06/01 18:20:16: Identify trunk 5 [8] 2007/06/01 18:20:16: Resolve destination 43538: a udp 192.168.16.124 5060 [8] 2007/06/01 18:20:16: Resolve destination 43538: udp 192.168.16.124 5060 [8] 2007/06/01 18:20:16: Send Packet 100 [7] 2007/06/01 18:20:16: SIP Tx udp:192.168.16.124:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK2113019710;rport=5060 From: "Fax" <sip:15@192.168.16.110>;tag=1026814437 To: <sip:0664771607997@192.168.16.110>;tag=ae3503080a Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 60 INVITE Content-Length: 0 [8] 2007/06/01 18:20:16: Resolve destination 43539: a udp 192.168.16.124 5060 [8] 2007/06/01 18:20:16: Resolve destination 43539: udp 192.168.16.124 5060 [8] 2007/06/01 18:20:16: Send Packet 401 [7] 2007/06/01 18:20:16: SIP Tx udp:192.168.16.124:5060: SIP/2.0 401 Authentication Required Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK2113019710;rport=5060 From: "Fax" <sip:15@192.168.16.110>;tag=1026814437 To: <sip:0664771607997@192.168.16.110>;tag=ae3503080a Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 60 INVITE User-Agent: FL-Connect IP-PBX/2.0.3.1715 WWW-Authenticate: Digest realm="192.168.16.110",nonce="69d3ec2d6c963ae7c3c5b49b6007f033",domain="sip:0664771607997@192.168.16.110",algorithm=MD5 Content-Length: 0 [7] 2007/06/01 18:20:16: SIP Rx udp:192.168.16.124:5060: ACK sip:0664771607997@192.168.16.110 SIP/2.0 Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK2113019710;rport Route: <sip:192.168.16.110:5060;lr> From: "Fax" <sip:15@192.168.16.110>;tag=1026814437 To: <sip:0664771607997@192.168.16.110>;tag=ae3503080a Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 60 ACK Content-Length: 0 [7] 2007/06/01 18:20:16: SIP Rx udp:192.168.16.124:5060: INVITE sip:0664771607997@192.168.16.110 SIP/2.0 Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK421753744;rport Route: <sip:192.168.16.110:5060;lr> From: "Fax" <sip:15@192.168.16.110>;tag=1026814437 To: <sip:0664771607997@192.168.16.110> Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 61 INVITE Contact: <sip:15@192.168.16.124:5060> Authorization: Digest username="15", realm="192.168.16.110", nonce="69d3ec2d6c963ae7c3c5b49b6007f033", uri="sip:0664771607997@192.168.16.110", response="ab9e1b2b4254ece8e78e910ebde5fdcc", algorithm=MD5 Max-Forwards: 70 Supported: replaces, path User-Agent: Grandstream HT-502 1.0.0.39 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Content-Type: application/sdp Content-Length: 363 v=0 o=15 8000 8000 IN IP4 192.168.16.124 s=SIP Call c=IN IP4 192.168.16.124 t=0 0 m=audio 5004 RTP/AVP 0 8 4 18 2 97 103 102 a=sendrecv a=rtpmap:0 PCMU/8000 a=ptime:20 a=rtpmap:8 PCMA/8000 a=rtpmap:4 G723/8000 a=rtpmap:18 G729/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=20 a=rtpmap:103 G726-40/8000 a=rtpmap:102 G729E/8000 [8] 2007/06/01 18:20:16: Tagging request with existing tag [8] 2007/06/01 18:20:16: Resolve destination 43541: a udp 192.168.16.124 5060 [8] 2007/06/01 18:20:16: Resolve destination 43541: udp 192.168.16.124 5060 [8] 2007/06/01 18:20:16: Send Packet 100 [7] 2007/06/01 18:20:16: SIP Tx udp:192.168.16.124:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK421753744;rport=5060 From: "Fax" <sip:15@192.168.16.110>;tag=1026814437 To: <sip:0664771607997@192.168.16.110>;tag=ae3503080a Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 61 INVITE Content-Length: 0 [7] 2007/06/01 18:20:16: UDP: Opening socket on port 51042 [7] 2007/06/01 18:20:16: UDP: Opening socket on port 51043 [8] 2007/06/01 18:20:16: Resolve destination 43544: url sip:192.168.16.12 [8] 2007/06/01 18:20:16: Resolve destination 43544: udp 192.168.16.12 5060 [8] 2007/06/01 18:20:16: Send Packet INVITE [7] 2007/06/01 18:20:16: SIP Tx udp:192.168.16.12:5060: INVITE sip:0664771607997@192.168.16.12;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-2b23244bd8acf79a6618c117976b228a;rport From: "Fax " <sip:+43724235108815@192.168.16.12>;tag=23234 To: <sip:0664771607997@192.168.16.12;user=phone> Call-ID: 841706e2@pbx CSeq: 17112 INVITE Max-Forwards: 70 Contact: <sip:sippbx@192.168.16.110:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PRACK, INFO, PUBLISH, NOTIFY, SUBSCRIBE, MESSAGE Accept: application/sdp User-Agent: FL-Connect IP-PBX/2.0.3.1715 Remote-Party-ID: "sippbx" <sip:sippbx@192.168.16.12>;party=calling;screen=yes Content-Type: application/sdp Content-Length: 296 v=0 o=- 11568 11568 IN IP4 192.168.16.110 s=- c=IN IP4 192.168.16.110 t=0 0 m=audio 51042 RTP/AVP 0 8 18 2 3 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:18 g729/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11 a=sendrecv [8] 2007/06/01 18:20:16: Resolve destination 43545: a udp 192.168.16.124 5060 [8] 2007/06/01 18:20:16: Resolve destination 43545: udp 192.168.16.124 5060 [8] 2007/06/01 18:20:16: Send Packet 183 [7] 2007/06/01 18:20:16: SIP Tx udp:192.168.16.124:5060: SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK421753744;rport=5060 From: "Fax" <sip:15@192.168.16.110>;tag=1026814437 To: <sip:0664771607997@192.168.16.110>;tag=ae3503080a Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 61 INVITE Contact: <sip:15@192.168.16.110:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PRACK, INFO, PUBLISH, NOTIFY, SUBSCRIBE, MESSAGE Accept: application/sdp User-Agent: FL-Connect IP-PBX/2.0.3.1715 Content-Type: application/sdp Content-Length: 152 v=0 o=- 29725 29725 IN IP4 192.168.16.110 s=- c=IN IP4 192.168.16.110 t=0 0 m=audio 49966 RTP/AVP 0 a=rtpmap:0 pcmu/8000 a=ptime:20 a=sendrecv [7] 2007/06/01 18:20:16: SIP Rx udp:192.168.16.12:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-2b23244bd8acf79a6618c117976b228a;rport From: "Fax " <sip:+43724235108815@192.168.16.12>;tag=23234 To: <sip:0664771607997@192.168.16.12;user=phone> Call-ID: 841706e2@pbx CSeq: 17112 INVITE Allow: INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFER User-Agent: TELES.VoIPBOX 13.0b 885 Content-Length: 0 7] 2007/06/01 18:20:17: SIP Tr udp:192.168.16.124:5060: SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK421753744;rport=5060 From: "Fax" <sip:15@192.168.16.110>;tag=1026814437 To: <sip:0664771607997@192.168.16.110>;tag=ae3503080a Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 61 INVITE Contact: <sip:15@192.168.16.110:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PRACK, INFO, PUBLISH, NOTIFY, SUBSCRIBE, MESSAGE Accept: application/sdp User-Agent: FL-Connect IP-PBX/2.0.3.1715 Content-Type: application/sdp Content-Length: 152 v=0 o=- 29725 29725 IN IP4 192.168.16.110 s=- c=IN IP4 192.168.16.110 t=0 0 m=audio 49966 RTP/AVP 0 a=rtpmap:0 pcmu/8000 a=ptime:20 a=sendrecv [8] 2007/06/01 18:20:18: Send Packet 183 [7] 2007/06/01 18:20:18: SIP Tr udp:192.168.16.124:5060: SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK421753744;rport=5060 From: "Fax" <sip:15@192.168.16.110>;tag=1026814437 To: <sip:0664771607997@192.168.16.110>;tag=ae3503080a Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 61 INVITE Contact: <sip:15@192.168.16.110:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PRACK, INFO, PUBLISH, NOTIFY, SUBSCRIBE, MESSAGE Accept: application/sdp User-Agent: FL-Connect IP-PBX/2.0.3.1715 Content-Type: application/sdp Content-Length: 152 v=0 o=- 29725 29725 IN IP4 192.168.16.110 s=- c=IN IP4 192.168.16.110 t=0 0 m=audio 49966 RTP/AVP 0 a=rtpmap:0 pcmu/8000 a=ptime:20 a=sendrecv [8] 2007/06/01 18:20:20: Send Packet 183 [7] 2007/06/01 18:20:20: SIP Tr udp:192.168.16.124:5060: SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK421753744;rport=5060 From: "Fax" <sip:15@192.168.16.110>;tag=1026814437 To: <sip:0664771607997@192.168.16.110>;tag=ae3503080a Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 61 INVITE Contact: <sip:15@192.168.16.110:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PRACK, INFO, PUBLISH, NOTIFY, SUBSCRIBE, MESSAGE Accept: application/sdp User-Agent: FL-Connect IP-PBX/2.0.3.1715 Content-Type: application/sdp Content-Length: 152 v=0 o=- 29725 29725 IN IP4 192.168.16.110 s=- c=IN IP4 192.168.16.110 t=0 0 m=audio 49966 RTP/AVP 0 a=rtpmap:0 pcmu/8000 a=ptime:20 a=sendrecv [7] 2007/06/01 18:20:22: SIP Rx udp:192.168.16.12:5060: SIP/2.0 183 Session progress Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-2b23244bd8acf79a6618c117976b228a;rport From: "Fax " <sip:+43724235108815@192.168.16.12>;tag=23234 To: <sip:0664771607997@192.168.16.12;user=phone>;tag=637880302461171716578104820567 Call-ID: 841706e2@pbx CSeq: 17112 INVITE Allow: INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFER Contact: <sip:0664771607997@192.168.16.12> User-Agent: TELES.VoIPBOX 13.0b 885 Content-Type: application/sdp Content-Length: 188 v=0 o=- 277 1 IN IP4 192.168.16.12 s=- c=IN IP4 192.168.16.12 t=0 0 m=audio 29000 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=ptime:40 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 [8] 2007/06/01 18:20:22: Resolve destination 43547: url sip:35@192.168.16.123:2054;line=4ym9kfvn [8] 2007/06/01 18:20:22: Resolve destination 43547: udp 192.168.16.123 2054 [8] 2007/06/01 18:20:22: Send Packet NOTIFY [7] 2007/06/01 18:20:22: SIP Tx udp:192.168.16.123:2054: NOTIFY sip:35@192.168.16.123:2054;line=4ym9kfvn SIP/2.0 Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-c5aa0cd3873a1e0a271234f3bed12af3;rport From: <sip:15@localhost;user=phone>;tag=003530fce3 To: <sip:35@localhost>;tag=qdifvavd0l Call-ID: 3c26700e3b25-np70hd4mtm3d CSeq: 1372 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.16.110:5060;transport=udp> Event: dialog Subscription-State: active;expires=66 Content-Type: application/dialog-info+xml Content-Length: 455 [8] 2007/06/01 18:20:24: Send Packet 183 [7] 2007/06/01 18:20:24: SIP Tr udp:192.168.16.124:5060: SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK421753744;rport=5060 From: "Fax" <sip:15@192.168.16.110>;tag=1026814437 To: <sip:0664771607997@192.168.16.110>;tag=ae3503080a Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 61 INVITE Contact: <sip:15@192.168.16.110:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PRACK, INFO, PUBLISH, NOTIFY, SUBSCRIBE, MESSAGE Accept: application/sdp User-Agent: FL-Connect IP-PBX/2.0.3.1715 Content-Type: application/sdp Content-Length: 152 v=0 o=- 29725 29725 IN IP4 192.168.16.110 s=- c=IN IP4 192.168.16.110 t=0 0 m=audio 49966 RTP/AVP 0 a=rtpmap:0 pcmu/8000 a=ptime:20 a=sendrecv [7] 2007/06/01 18:20:24: SIP Rx udp:192.168.16.12:5060: SIP/2.0 180 Ringing Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-2b23244bd8acf79a6618c117976b228a;rport From: "Fax " <sip:+43724235108815@192.168.16.12>;tag=23234 To: <sip:0664771607997@192.168.16.12;user=phone>;tag=637880302461171716578104820567 Call-ID: 841706e2@pbx CSeq: 17112 INVITE Allow: INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFER Contact: <sip:0664771607997@192.168.16.12> User-Agent: TELES.VoIPBOX 13.0b 885 Content-Type: application/sdp Content-Length: 188 v=0 o=- 277 1 IN IP4 192.168.16.12 s=- c=IN IP4 192.168.16.12 t=0 0 m=audio 29000 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=ptime:40 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 [7] 2007/06/01 18:20:24: SIP Rx udp:192.168.16.12:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-2b23244bd8acf79a6618c117976b228a;rport From: "Fax " <sip:+43724235108815@192.168.16.12>;tag=23234 To: <sip:0664771607997@192.168.16.12;user=phone>;tag=637880302461171716578104820567 Call-ID: 841706e2@pbx CSeq: 17112 INVITE Allow: INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFER Contact: <sip:0664771607997@192.168.16.12> User-Agent: TELES.VoIPBOX 13.0b 885 Content-Type: application/sdp Content-Length: 188 v=0 o=- 277 1 IN IP4 192.168.16.12 s=- c=IN IP4 192.168.16.12 t=0 0 m=audio 29000 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=ptime:40 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 [8] 2007/06/01 18:20:24: Resolve destination 43549: url sip:0664771607997@192.168.16.12 [8] 2007/06/01 18:20:24: Resolve destination 43549: udp 192.168.16.12 5060 [8] 2007/06/01 18:20:24: Send Packet ACK [7] 2007/06/01 18:20:24: SIP Tx udp:192.168.16.12:5060: ACK sip:0664771607997@192.168.16.12 SIP/2.0 Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-39707571dca058a987d135230482d4e8;rport From: "Fax " <sip:+43724235108815@192.168.16.12>;tag=23234 To: <sip:0664771607997@192.168.16.12;user=phone>;tag=637880302461171716578104820567 Call-ID: 841706e2@pbx CSeq: 17112 ACK Max-Forwards: 70 Contact: <sip:sippbx@192.168.16.110:5060;transport=udp> Remote-Party-ID: "sippbx" <sip:sippbx@192.168.16.12>;party=calling;screen=yes Content-Length: 0 [8] 2007/06/01 18:20:24: Resolve destination 43550: a udp 192.168.16.124 5060 [8] 2007/06/01 18:20:24: Resolve destination 43550: udp 192.168.16.124 5060 [8] 2007/06/01 18:20:24: Send Packet 200 [7] 2007/06/01 18:20:24: SIP Tx udp:192.168.16.124:5060: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK421753744;rport=5060 From: "Fax" <sip:15@192.168.16.110>;tag=1026814437 To: <sip:0664771607997@192.168.16.110>;tag=ae3503080a Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 61 INVITE Contact: <sip:15@192.168.16.110:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PRACK, INFO, PUBLISH, NOTIFY, SUBSCRIBE, MESSAGE Accept: application/sdp User-Agent: FL-Connect IP-PBX/2.0.3.1715 Content-Type: application/sdp Content-Length: 152 v=0 o=- 29725 29725 IN IP4 192.168.16.110 s=- c=IN IP4 192.168.16.110 t=0 0 m=audio 49966 RTP/AVP 0 a=rtpmap:0 pcmu/8000 a=ptime:20 a=sendrecv [7] 2007/06/01 18:20:24: SIP Rx udp:192.168.16.124:5060: ACK sip:15@192.168.16.110:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK662941648;rport From: "Fax" <sip:15@192.168.16.110>;tag=1026814437 To: <sip:0664771607997@192.168.16.110>;tag=ae3503080a Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 61 ACK Contact: <sip:15@192.168.16.124:5060> Max-Forwards: 70 Supported: replaces, path User-Agent: Grandstream HT-502 1.0.0.39 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Content-Length: 0 [7] 2007/06/01 18:20:24: SIP Rx udp:192.168.16.124:5060: REGISTER sip:192.168.16.110 SIP/2.0 Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK529997551;rport Route: <sip:192.168.16.110:5060;lr> From: <sip:15@192.168.16.110>;tag=780704202 To: <sip:15@192.168.16.110> Call-ID: 1506464803-5060-1@192.168.16.124 CSeq: 2020 REGISTER Contact: <sip:15@192.168.16.124:5060> Authorization: Digest username="15", realm="192.168.16.110", nonce="2fa227c4316caf5070e594d543c13f78", uri="sip:192.168.16.110", response="98e3da31d23059ab4a7152113633198d", algorithm=MD5 Expires: 3600 Max-Forwards: 70 User-Agent: Grandstream HT-502 1.0.0.39 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Content-Length: 0 [8] 2007/06/01 18:20:24: Resolve destination 43551: a udp 192.168.16.124 5060 [8] 2007/06/01 18:20:24: Resolve destination 43551: udp 192.168.16.124 5060 [8] 2007/06/01 18:20:24: Send Packet 200 [7] 2007/06/01 18:20:24: SIP Tx udp:192.168.16.124:5060: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK529997551;rport=5060 From: <sip:15@192.168.16.110>;tag=780704202 To: <sip:15@192.168.16.110>;tag=790fb62a3d Call-ID: 1506464803-5060-1@192.168.16.124 CSeq: 2020 REGISTER Contact: <sip:15@192.168.16.124:5060>;expires=60 Content-Length: 0 [7] 2007/06/01 18:20:31: SIP Rx udp:192.168.16.12:5060: INVITE sip:sippbx@192.168.16.110:5060;transport=udp SIP/2.0 Max-Forwards: 50 Via: SIP/2.0/UDP 192.168.16.12:5060;rport;branch=z9hG4bK04351950256772412077751 From: <sip:0664771607997@192.168.16.12;user=phone>;tag=637880302461171716578104820567 To: "Fax " <sip:+43724235108815@192.168.16.12>;tag=23234 Contact: <sip:0664771607997@192.168.16.12> User-Agent: TELES.VoIPBOX 13.0b 885 Call-ID: 841706e2@pbx CSeq: 17113 INVITE Allow: INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFER Content-Type: application/sdp Content-Length: 290 v=0 o=- 277 1 IN IP4 192.168.16.12 s=- c=IN IP4 192.168.16.12 t=0 0 m=image 29000 udptl t38 a=T38FaxVersion:0 a=T38MaxBitRate:14400 a=T38FaxUdpEC:t38UDPRedundancy a=T38FaxRateManagement:transferredTCF a=T38FaxFillBitRemoval:0 a=T38FaxTranscodingMMR:0 a=T38FaxTranscodingJBIG:0 [8] 2007/06/01 18:20:31: Resolve destination 43555: a udp 192.168.16.12 5060 [8] 2007/06/01 18:20:31: Resolve destination 43555: udp 192.168.16.12 5060 [8] 2007/06/01 18:20:31: Send Packet 100 [7] 2007/06/01 18:20:31: SIP Tx udp:192.168.16.12:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.16.12:5060;rport=5060;branch=z9hG4bK04351950256772412077751 From: <sip:0664771607997@192.168.16.12;user=phone>;tag=637880302461171716578104820567 To: "Fax " <sip:+43724235108815@192.168.16.12>;tag=23234 Call-ID: 841706e2@pbx CSeq: 17113 INVITE Content-Length: 0 [7] 2007/06/01 18:20:31: UDP: Opening socket on port 52350 [7] 2007/06/01 18:20:31: UDP: Opening socket on port 52351 [7] 2007/06/01 18:20:31: UDP: Opening socket on port 52670 [7] 2007/06/01 18:20:31: UDP: Opening socket on port 52671 [8] 2007/06/01 18:20:31: Resolve destination 43556: url sip:15@192.168.16.124:5060 [8] 2007/06/01 18:20:31: Resolve destination 43556: udp 192.168.16.124 5060 [8] 2007/06/01 18:20:31: Send Packet INVITE [7] 2007/06/01 18:20:31: SIP Tx udp:192.168.16.124:5060: INVITE sip:15@192.168.16.124:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-a65ceff6d69e0acae419decacfc1a337;rport From: <sip:0664771607997@192.168.16.110>;tag=ae3503080a To: "Fax" <sip:15@192.168.16.110>;tag=1026814437 Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 27896 INVITE Max-Forwards: 70 Contact: <sip:15@192.168.16.110:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PRACK, INFO, PUBLISH, NOTIFY, SUBSCRIBE, MESSAGE Accept: application/sdp User-Agent: FL-Connect IP-PBX/2.0.3.1715 Content-Type: application/sdp Content-Length: 298 v=0 o=- 29725 29727 IN IP4 192.168.16.110 s=- c=IN IP4 192.168.16.110 t=0 0 m=image 52670 udptl t38 a=T38FaxVersion:0 a=T38MaxBitRate:14400 a=T38FaxUdpEC:t38UDPRedundancy a=T38FaxRateManagement:transferredTCF a=T38FaxFillBitRemoval:0 a=T38FaxTranscodingMMR:0 a=T38FaxTranscodingJBIG:0 [5] 2007/06/01 18:20:31: UDP: recvfrom returns WSAEWOULDBLOCK [7] 2007/06/01 18:20:31: SIP Rx udp:192.168.16.124:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-a65ceff6d69e0acae419decacfc1a337;rport=5060 From: <sip:0664771607997@192.168.16.110>;tag=ae3503080a To: "Fax" <sip:15@192.168.16.110>;tag=1026814437 Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 27896 INVITE Contact: <sip:15@192.168.16.124:5060> Supported: replaces, path User-Agent: Grandstream HT-502 1.0.0.39 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Content-Length: 0 [7] 2007/06/01 18:20:31: SIP Rx udp:192.168.16.124:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-a65ceff6d69e0acae419decacfc1a337;rport=5060 From: <sip:0664771607997@192.168.16.110>;tag=ae3503080a To: "Fax" <sip:15@192.168.16.110>;tag=1026814437 Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 27896 INVITE Contact: <sip:15@192.168.16.124:5060> Supported: replaces, path User-Agent: Grandstream HT-502 1.0.0.39 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Content-Type: application/sdp Content-Length: 351 v=0 o=15 8000 8001 IN IP4 192.168.16.124 s=SIP Call c=IN IP4 192.168.16.124 t=0 0 m=image 5004 udptl t38 a=T38FaxVersion:0 a=T38MaxBitRate:14400 a=T38FaxFillBitRemoval:0 a=T38FaxTranscodingMMR:0 a=T38FaxTranscodingJBIG:0 a=T38FaxRateManagement:transferredTCF a=T38FaxMaxBuffer:400 a=T38FaxMaxDatagram:280 a=T38FaxUdpEC:t38UDPRedundancy [8] 2007/06/01 18:20:31: Resolve destination 43557: url sip:15@192.168.16.124:5060 [8] 2007/06/01 18:20:31: Resolve destination 43557: udp 192.168.16.124 5060 [8] 2007/06/01 18:20:31: Send Packet ACK [7] 2007/06/01 18:20:31: SIP Tx udp:192.168.16.124:5060: ACK sip:15@192.168.16.124:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-8c2bf4c60797fca57c45945d91d80936;rport From: <sip:0664771607997@192.168.16.110>;tag=ae3503080a To: "Fax" <sip:15@192.168.16.110>;tag=1026814437 Call-ID: 167922533-5060-7@192.168.16.124 CSeq: 27896 ACK Max-Forwards: 70 Contact: <sip:15@192.168.16.110:5060> Content-Length: 0 [8] 2007/06/01 18:20:31: Resolve destination 43558: a udp 192.168.16.12 5060 [8] 2007/06/01 18:20:31: Resolve destination 43558: udp 192.168.16.12 5060 [8] 2007/06/01 18:20:31: Send Packet 200 [7] 2007/06/01 18:20:31: SIP Tx udp:192.168.16.12:5060: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.16.12:5060;rport=5060;branch=z9hG4bK04351950256772412077751 From: <sip:0664771607997@192.168.16.12;user=phone>;tag=637880302461171716578104820567 To: "Fax " <sip:+43724235108815@192.168.16.12>;tag=23234 Call-ID: 841706e2@pbx CSeq: 17113 INVITE Contact: <sip:sippbx@192.168.16.110:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PRACK, INFO, PUBLISH, NOTIFY, SUBSCRIBE, MESSAGE Accept: application/sdp User-Agent: FL-Connect IP-PBX/2.0.3.1715 Content-Type: application/sdp Content-Length: 353 v=0 o=- 11568 11570 IN IP4 192.168.16.110 s=SIP Call c=IN IP4 192.168.16.110 t=0 0 m=image 52350 udptl t38 a=T38FaxVersion:0 a=T38MaxBitRate:14400 a=T38FaxFillBitRemoval:0 a=T38FaxTranscodingMMR:0 a=T38FaxTranscodingJBIG:0 a=T38FaxRateManagement:transferredTCF a=T38FaxMaxBuffer:400 a=T38FaxMaxDatagram:280 a=T38FaxUdpEC:t38UDPRedundancy [7] 2007/06/01 18:20:31: SIP Rx udp:192.168.16.12:5060: ACK sip:sippbx@192.168.16.110:5060;transport=udp SIP/2.0 Max-Forwards: 50 Via: SIP/2.0/UDP 192.168.16.12:5060;rport;branch=z9hG4bK16087354823085853174033 From: <sip:0664771607997@192.168.16.12;user=phone>;tag=637880302461171716578104820567 To: "Fax " <sip:+43724235108815@192.168.16.12>;tag=23234 Contact: <sip:0664771607997@192.168.16.12> User-Agent: TELES.VoIPBOX 13.0b 885 Call-ID: 841706e2@pbx CSeq: 17113 ACK Allow: INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFER Content-Length: 0 ... and now the malformed packets sending beginns and the fax does not hear anything anymore.... [7] 2007/06/01 18:21:04: SIP Rx udp:192.168.16.124:5060: REGISTER sip:192.168.16.110 SIP/2.0 Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK1124454462;rport Route: <sip:192.168.16.110:5060;lr> From: <sip:15@192.168.16.110>;tag=780704202 To: <sip:15@192.168.16.110> Call-ID: 1506464803-5060-1@192.168.16.124 CSeq: 2021 REGISTER Contact: <sip:15@192.168.16.124:5060> Authorization: Digest username="15", realm="192.168.16.110", nonce="2fa227c4316caf5070e594d543c13f78", uri="sip:192.168.16.110", response="98e3da31d23059ab4a7152113633198d", algorithm=MD5 Expires: 3600 Max-Forwards: 70 User-Agent: Grandstream HT-502 1.0.0.39 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Content-Length: 0 [8] 2007/06/01 18:21:04: Resolve destination 43575: a udp 192.168.16.124 5060 [8] 2007/06/01 18:21:04: Resolve destination 43575: udp 192.168.16.124 5060 [8] 2007/06/01 18:21:04: Send Packet 200 [7] 2007/06/01 18:21:04: SIP Tx udp:192.168.16.124:5060: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.16.124:5060;branch=z9hG4bK1124454462;rport=5060 From: <sip:15@192.168.16.110>;tag=780704202 To: <sip:15@192.168.16.110>;tag=790fb62a3d Call-ID: 1506464803-5060-1@192.168.16.124 CSeq: 2021 REGISTER Contact: <sip:15@192.168.16.124:5060>;expires=60 Content-Length: 0 [7] 2007/06/01 18:21:07: Other Ports: 1 [7] 2007/06/01 18:21:07: Call Port: 841706e2@pbx#23234 [8] 2007/06/01 18:21:07: Resolve destination 43579: url sip:0664771607997@192.168.16.12 [8] 2007/06/01 18:21:07: Resolve destination 43579: udp 192.168.16.12 5060 [8] 2007/06/01 18:21:07: Send Packet BYE [7] 2007/06/01 18:21:07: SIP Tx udp:192.168.16.12:5060: BYE sip:0664771607997@192.168.16.12 SIP/2.0 Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-3648224c7aac549c0b09cfdd2d85cbf5;rport From: "Fax " <sip:+43724235108815@192.168.16.12>;tag=23234 To: <sip:0664771607997@192.168.16.12;user=phone>;tag=637880302461171716578104820567 Call-ID: 841706e2@pbx CSeq: 17113 BYE Max-Forwards: 70 Contact: <sip:sippbx@192.168.16.110:5060;transport=udp> RTP-RxStat: Dur=51,Pkt=1270,Oct=421640,Underun=494 RTP-TxStat: Dur=43,Pkt=93,Oct=29604 Remote-Party-ID: "sippbx" <sip:sippbx@192.168.16.12>;party=calling;screen=yes Content-Length: 0 [8] 2007/06/01 18:21:07: Resolve destination 43580: url sip:35@192.168.16.123:2054;line=4ym9kfvn [8] 2007/06/01 18:21:07: Resolve destination 43580: udp 192.168.16.123 2054 [8] 2007/06/01 18:21:07: Send Packet NOTIFY [7] 2007/06/01 18:21:07: SIP Tx udp:192.168.16.123:2054: NOTIFY sip:35@192.168.16.123:2054;line=4ym9kfvn SIP/2.0 Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-888c61cd7c75989ae6ad5634a91b8444;rport From: <sip:15@localhost;user=phone>;tag=003530fce3 To: <sip:35@localhost>;tag=qdifvavd0l Call-ID: 3c26700e3b25-np70hd4mtm3d CSeq: 1373 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.16.110:5060;transport=udp> Event: dialog Subscription-State: active;expires=52 Content-Type: application/dialog-info+xml Content-Length: 147 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="51" state="full" entity="sip:15@localhost"></dialog-info> [8] 2007/06/01 18:21:07: Resolve destination 43581: url sip:25@192.168.16.121:1030;line=ymmilo56 [8] 2007/06/01 18:21:07: Resolve destination 43581: udp 192.168.16.121 1030 [8] 2007/06/01 18:21:07: Send Packet NOTIFY [7] 2007/06/01 18:21:07: SIP Tx udp:192.168.16.121:1030: NOTIFY sip:25@192.168.16.121:1030;line=ymmilo56 SIP/2.0 Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-30132f7a1d1f797d683a25286b1f21ac;rport From: <sip:15@localhost>;tag=6029d08633 To: <sip:25@localhost>;tag=gjc1casrya Call-ID: 3c26701bc9ca-8rwmzrkyi31t CSeq: 24243 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.16.110:5060;transport=udp> Event: dialog Subscription-State: active;expires=69 Content-Type: application/dialog-info+xml Content-Length: 147 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="51" state="full" entity="sip:15@localhost"></dialog-info> [7] 2007/06/01 18:21:07: SIP Rx udp:192.168.16.12:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-3648224c7aac549c0b09cfdd2d85cbf5;rport From: "Fax " <sip:+43724235108815@192.168.16.12>;tag=23234 To: <sip:0664771607997@192.168.16.12;user=phone>;tag=637880302461171716578104820567 Call-ID: 841706e2@pbx CSeq: 17113 BYE Allow: INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFER Contact: <sip:0664771607997@192.168.16.12> User-Agent: TELES.VoIPBOX 13.0b 885 Content-Length: 0 [5] 2007/06/01 18:21:07: BYE Response: Terminate 841706e2@pbx [7] 2007/06/01 18:21:07: SIP Rx udp:192.168.16.121:1030: SIP/2.0 200 Ok v: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-30132f7a1d1f797d683a25286b1f21ac;rport=5060 f: <sip:15@localhost>;tag=6029d08633 t: <sip:25@localhost>;tag=gjc1casrya i: 3c26701bc9ca-8rwmzrkyi31t CSeq: 24243 NOTIFY l: 0 [7] 2007/06/01 18:21:07: SIP Rx udp:192.168.16.123:2054: SIP/2.0 200 Ok v: SIP/2.0/UDP 192.168.16.110:5060;branch=z9hG4bK-888c61cd7c75989ae6ad5634a91b8444;rport=5060 f: <sip:15@localhost;user=phone>;tag=003530fce3 t: <sip:35@localhost>;tag=qdifvavd0l i: 3c26700e3b25-np70hd4mtm3d CSeq: 1373 NOTIFY l: 0 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 1, 2007 Report Share Posted June 1, 2007 The SIP part looks beautiful. You may try http://www.pbxnsip.com/download/pbxctrl-2.0.4.1759.exe to if it makes a difference. I remember there was a bug fix in 2.0.4 in the media relay part, maybe it makes a difference. P.S. You can also attach PCAP files for message posts (use the UPLOAD button). Quote Link to comment Share on other sites More sharing options...
Daniel Floeckinger Posted June 2, 2007 Author Report Share Posted June 2, 2007 Does not work :-( Have made a trace... dont have a upload button, so, where shall i send it? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 3, 2007 Report Share Posted June 3, 2007 Have made a trace... dont have a upload button, so, where shall i send it? When I reply, I get a "Attachments" section with a UPLOAD button. You should also see that option. Quote Link to comment Share on other sites More sharing options...
Daniel Floeckinger Posted June 3, 2007 Author Report Share Posted June 3, 2007 Maybe because you are Administrator. I dont have this section, i am afraid. Quote Link to comment Share on other sites More sharing options...
Daniel Floeckinger Posted June 5, 2007 Author Report Share Posted June 5, 2007 The problem is still unsolved. Could you please respond, where to send the trace to? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 5, 2007 Report Share Posted June 5, 2007 I guess you should open a trouble ticket on OTRS. Please ask km@pbxnsip.com for an account. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.