ShadowAnt Posted February 4, 2010 Report Share Posted February 4, 2010 Hello! I install faxback and I have a trouble with recieving faxes. I try to send fax from analog fax-sip provider (with T.38) - pbxnsip - NET SatisFAXtion here is a log: 1.1.1.3 - faxback 1.1.1.5 - pbxnsip 1.1.1.101 - sip provider [7] 2010/02/05 08:28:11: Last message repeated 2 times [6] 2010/02/05 08:28:11: Received DTMF F [7] 2010/02/05 08:28:11: Attendant: Calling extension 777 [7] 2010/02/05 08:28:11: SIP Tx udp:1.1.1.3:5060: INVITE sip:777@1.1.1.3:5060 SIP/2.0 Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-77d89e821eab1998222b24bcb014ca34;rport From: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943 To: <sip:777@pbx.case.ru> Call-ID: 6ec1ef94@pbx CSeq: 21702 INVITE Max-Forwards: 70 Contact: <sip:777@1.1.1.5:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.4.0.3201 Alert-Info: <http://127.0.0.1/Bellcore-dr3> Content-Type: application/sdp Content-Length: 327 v=0 o=- 13668 13668 IN IP4 1.1.1.5 s=- c=IN IP4 1.1.1.5 t=0 0 m=audio 63512 RTP/AVP 0 8 9 18 2 3 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [7] 2010/02/05 08:28:11: SIP Rx udp:1.1.1.3:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-77d89e821eab1998222b24bcb014ca34;rport From: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943 To: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010 Call-ID: 6ec1ef94@pbx CSeq: 21702 INVITE Contact: <sip:IPFax@1.1.1.3:5060> User-Agent: Net Satisfaxtion/IP_FAX-8.5.4225.929 Content-Length: 0 [7] 2010/02/05 08:28:11: SIP Rx udp:1.1.1.3:5060: SIP/2.0 180 Ringing Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-77d89e821eab1998222b24bcb014ca34;rport From: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943 To: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010 Call-ID: 6ec1ef94@pbx CSeq: 21702 INVITE Contact: <sip:IPFax@1.1.1.3:5060> User-Agent: Net Satisfaxtion/IP_FAX-8.5.4225.929 Content-Length: 0 [7] 2010/02/05 08:28:11: SIP Rx udp:1.1.1.3:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-77d89e821eab1998222b24bcb014ca34;rport From: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943 To: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010 Call-ID: 6ec1ef94@pbx CSeq: 21702 INVITE Contact: <sip:IPFax@1.1.1.3:5060> User-Agent: Net Satisfaxtion/IP_FAX-8.5.4225.929 Allow: INVITE, ACK, BYE, CANCEL, REFER, NOTIFY Content-Type: application/sdp Content-Length: 210 v=0 o=IPFax 0 0 IN IP4 1.1.1.3 s=SIP Fax Call i=IPFax c=IN IP4 1.1.1.3 t=0 0 m=audio 49248 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv [7] 2010/02/05 08:28:11: Call 6ec1ef94@pbx#5943: Clear last INVITE [7] 2010/02/05 08:28:11: Set packet length to 20 [6] 2010/02/05 08:28:11: Send codec=pcmu/8000 afrer answer [6] 2010/02/05 08:28:11: Sending RTP for 6ec1ef94@pbx#5943 to 1.1.1.3:49248 [7] 2010/02/05 08:28:11: SIP Tx udp:1.1.1.3:5060: ACK sip:IPFax@1.1.1.3:5060 SIP/2.0 Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-37ac123baf4fee949d4eaf868c72d713;rport From: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943 To: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010 Call-ID: 6ec1ef94@pbx CSeq: 21702 ACK Max-Forwards: 70 Contact: <sip:777@1.1.1.5:5060;transport=udp> Content-Length: 0 [7] 2010/02/05 08:28:11: Determine pass-through mode after receiving response [7] 2010/02/05 08:28:11: 6ec1ef94@pbx#5943: RTP pass-through mode [7] 2010/02/05 08:28:11: 7007803330339123745-1265347685@172.30.77.25#f72475646e: RTP pass-through mode [7] 2010/02/05 08:28:11: 7007803330339123745-1265347685@172.30.77.25#f72475646e: Media-aware pass-through mode [7] 2010/02/05 08:28:15: SIP Rx udp:1.1.1.3:5060: INVITE sip:8632370680@pbx.case.ru:5060 SIP/2.0 Via: SIP/2.0/UDP 1.1.1.3:5060;branch=z9hG4bK1011 From: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010 To: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943 Call-ID: 6ec1ef94@pbx CSeq: 21703 INVITE Max-Forwards: 70 Contact: <sip:777@1.1.1.3:5060> User-Agent: Net Satisfaxtion/IP_FAX-8.5.4225.929 Session-Expires: 3600;refresher=uas Supported: timer,replaces,billing,presence,* Allow: INVITE, ACK, BYE, CANCEL, REFER, NOTIFY Content-Type: application/sdp Content-Length: 347 v=0 o=IPFax 0 1 IN IP4 1.1.1.3 s=SIP Fax Call i=IPFax c=IN IP4 1.1.1.3 t=0 0 m=image 49200 udptl t38 a=T38FaxVersion:0 a=T38MaxBitRate:14400 a=T38FaxRateManagement:transferredTCF a=T38FaxMaxBuffer:200 a=T38FaxMaxDatagram:72 a=T38FaxFillBitRemoval:0 a=T38FaxTranscodingMMR:0 a=T38FaxTranscodingJBIG:0 a=T38FaxUdpEC:t38UDPRedundancy [0] 2010/02/05 08:28:15: UDP: bind() to port 54900 failed [7] 2010/02/05 08:28:15: UDP: Opening socket on :57948 [7] 2010/02/05 08:28:15: UDP: Opening socket on :57140 [7] 2010/02/05 08:28:15: SIP Tx udp:1.1.1.101:5060: INVITE sip:8632370680@1.1.1.101:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-290b90ac185fe1cdcaf1380f07c14040;rport From: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e To: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237 Call-ID: 7007803330339123745-1265347685@172.30.77.25 CSeq: 27403 INVITE Max-Forwards: 70 Contact: <sip:2688634@1.1.1.5:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.4.0.3201 Content-Type: application/sdp Content-Length: 331 v=0 o=- 54151 54152 IN IP4 1.1.1.5 s=- c=IN IP4 1.1.1.5 t=0 0 m=image 57140 udptl t38 a=T38FaxVersion:0 a=T38MaxBitRate:14400 a=T38FaxRateManagement:transferredTCF a=T38FaxMaxBuffer:200 a=T38FaxMaxDatagram:72 a=T38FaxFillBitRemoval:0 a=T38FaxTranscodingMMR:0 a=T38FaxTranscodingJBIG:0 a=T38FaxUdpEC:t38UDPRedundancy [7] 2010/02/05 08:28:15: SIP Tx udp:1.1.1.3:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 1.1.1.3:5060;branch=z9hG4bK1011 From: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010 To: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943 Call-ID: 6ec1ef94@pbx CSeq: 21703 INVITE Content-Length: 0 [7] 2010/02/05 08:28:15: SIP Rx udp:1.1.1.101:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 1.1.1.5:5060;received=1.1.1.5;branch=z9hG4bK-290b90ac185fe1cdcaf1380f07c14040;rport=5060 From: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e To: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237 Call-ID: 7007803330339123745-1265347685@172.30.77.25 CSeq: 27403 INVITE [5] 2010/02/05 08:28:15: Passthrough: Changing destination [7] 2010/02/05 08:28:15: SIP Rx udp:1.1.1.101:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 1.1.1.5:5060;received=1.1.1.5;branch=z9hG4bK-290b90ac185fe1cdcaf1380f07c14040;rport=5060 From: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e To: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237 Call-ID: 7007803330339123745-1265347685@172.30.77.25 CSeq: 27403 INVITE Content-Type: application/sdp Contact: <sip:8632370680@1.1.1.101:5060;transport=udp>;user=phone Supported: timer,100rel Content-Length: 103 v=0 o=MG4000|2.0 3420 6706 IN IP4 1.1.1.101 s=- c=IN IP4 1.1.1.101 t=0 0 m=image 52860 udptl t38 [7] 2010/02/05 08:28:15: Call 7007803330339123745-1265347685@172.30.77.25#f72475646e: Clear last INVITE [7] 2010/02/05 08:28:15: SIP Tx udp:1.1.1.3:5060: SIP/2.0 200 Ok Via: SIP/2.0/UDP 1.1.1.3:5060;branch=z9hG4bK1011 From: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010 To: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943 Call-ID: 6ec1ef94@pbx CSeq: 21703 INVITE Contact: <sip:777@1.1.1.5:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.4.0.3201 Content-Type: application/sdp Content-Length: 92 v=0 o=- 13668 13669 IN IP4 1.1.1.5 s=- c=IN IP4 1.1.1.5 t=0 0 m=image 57948 udptl t38 [7] 2010/02/05 08:28:15: SIP Tx udp:1.1.1.101:5060: ACK sip:8632370680@1.1.1.101:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-91155c8a0f5db5c3c077e16dd28ac96c;rport From: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e To: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237 Call-ID: 7007803330339123745-1265347685@172.30.77.25 CSeq: 27403 ACK Max-Forwards: 70 Contact: <sip:2688634@1.1.1.5:5060;transport=udp> Content-Length: 0 [7] 2010/02/05 08:28:15: Determine pass-through mode after receiving response [7] 2010/02/05 08:28:15: SIP Rx udp:1.1.1.3:5060: ACK sip:777@1.1.1.5:5060 SIP/2.0 Via: SIP/2.0/UDP 1.1.1.3:5060;branch=z9hG4bK1011 From: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010 To: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943 Call-ID: 6ec1ef94@pbx CSeq: 21703 ACK Max-Forwards: 70 User-Agent: Net Satisfaxtion/IP_FAX-8.5.4225.929 Content-Length: 0 [5] 2010/02/05 08:28:26: SIP port accept from 1.1.7.8:63891 [7] 2010/02/05 08:28:26: SIP Rx tcp:1.1.7.8:63891: OPTIONS sip:1.1.1.5:5060 SIP/2.0 FROM: <sip:s-caseexch.case.ru:5060;transport=Tcp;ms-opaque=2cb7e09927aa4652>;epid=FC0ADCD96D;tag=b9a0d84671 TO: <sip:1.1.1.5:5060> CSEQ: 18599 OPTIONS CALL-ID: b819daf2a97c490ebf7d55910cc06236 MAX-FORWARDS: 70 VIA: SIP/2.0/TCP 1.1.7.8:63891;branch=z9hG4bK27c8619a ACCEPT: application/sdp CONTENT-LENGTH: 0 USER-AGENT: RTCC/3.1.0.0 [7] 2010/02/05 08:28:26: SIP Tx tcp:1.1.7.8:63891: SIP/2.0 200 Ok Via: SIP/2.0/TCP 1.1.7.8:63891;branch=z9hG4bK27c8619a From: <sip:s-caseexch.case.ru:5060;transport=Tcp;ms-opaque=2cb7e09927aa4652>;tag=b9a0d84671;epid=FC0ADCD96D To: <sip:1.1.1.5:5060>;tag=f7ce52c8fc Call-ID: b819daf2a97c490ebf7d55910cc06236 CSeq: 18599 OPTIONS Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Content-Length: 0 [7] 2010/02/05 08:28:30: SIP Rx udp:1.1.1.101:5060: INVITE sip:2688634@1.1.1.5:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 1.1.1.101:5060;branch=z9hG4bK5jh8d610700gvec8h7g0.1 Call-ID: 7007803330339123745-1265347685@172.30.77.25 From: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237 To: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e Content-Type: application/sdp CSeq: 2 INVITE Contact: <sip:8632370680@1.1.1.101:5060;transport=udp>;user=phone Allow: INVITE,CANCEL,BYE,ACK,REFER,UPDATE,INFO Supported: timer,100rel Max-Forwards: 69 Content-Length: 222 v=0 o=MG4000|2.0 3420 6707 IN IP4 1.1.1.101 s=- c=IN IP4 1.1.1.101 t=0 0 m=audio 52860 RTP/AVP 0 101 13 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=silenceSupp:off - - - - a=ptime:20 a=rtpmap:13 CN/8000 [7] 2010/02/05 08:28:30: Set packet length to 20 [7] 2010/02/05 08:28:30: SIP Tx udp:1.1.1.101:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 1.1.1.101:5060;branch=z9hG4bK5jh8d610700gvec8h7g0.1 From: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237 To: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e Call-ID: 7007803330339123745-1265347685@172.30.77.25 CSeq: 2 INVITE Content-Length: 0 [6] 2010/02/05 08:28:41: SIP TCP/TLS timeout on 1.1.1.4:41773, closing connection [7] 2010/02/05 08:28:57: SIP Rx udp:1.1.1.3:5060: BYE sip:777@1.1.1.5:5060 SIP/2.0 Via: SIP/2.0/UDP 1.1.1.3:5060;branch=z9hG4bK1012 From: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010 To: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943 Call-ID: 6ec1ef94@pbx CSeq: 21704 BYE Max-Forwards: 70 User-Agent: Net Satisfaxtion/IP_FAX-8.5.4225.929 Content-Length: 0 [7] 2010/02/05 08:28:57: SIP Tx udp:1.1.1.3:5060: SIP/2.0 200 Ok Via: SIP/2.0/UDP 1.1.1.3:5060;branch=z9hG4bK1012 From: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010 To: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943 Call-ID: 6ec1ef94@pbx CSeq: 21704 BYE Contact: <sip:777@1.1.1.5:5060;transport=udp> User-Agent: pbxnsip-PBX/3.4.0.3201 RTP-RxStat: Dur=46,Pkt=734,Oct=43912,Underun=0 RTP-TxStat: Dur=46,Pkt=910,Oct=155327 Content-Length: 0 [7] 2010/02/05 08:28:57: Other Ports: 1 [7] 2010/02/05 08:28:57: Call Port: 7007803330339123745-1265347685@172.30.77.25#f72475646e [7] 2010/02/05 08:28:57: SIP Tx udp:1.1.1.101:5060: BYE sip:8632370680@1.1.1.101:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-8c7f32049f3c81d47cc43e0eea58e3a2;rport From: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e To: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237 Call-ID: 7007803330339123745-1265347685@172.30.77.25 CSeq: 27404 BYE Max-Forwards: 70 Contact: <sip:2688634@1.1.1.5:5060;transport=udp> RTP-RxStat: Dur=52,Pkt=1210,Oct=206927,Underun=0 RTP-TxStat: Dur=42,Pkt=3162,Oct=461528 Content-Length: 0 [7] 2010/02/05 08:28:57: SIP Rx udp:1.1.1.101:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 1.1.1.5:5060;received=1.1.1.5;branch=z9hG4bK-8c7f32049f3c81d47cc43e0eea58e3a2;rport=5060 From: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e To: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237 Call-ID: 7007803330339123745-1265347685@172.30.77.25 CSeq: 27404 BYE Contact: <sip:8632370680@1.1.1.101:5060;transport=udp>;user=phone Supported: timer,100rel Content-Length: 0 [7] 2010/02/05 08:28:57: Call 7007803330339123745-1265347685@172.30.77.25#f72475646e: Clear last request [5] 2010/02/05 08:28:57: BYE Response: Terminate 7007803330339123745-1265347685@172.30.77.25 [7] 2010/02/05 08:29:02: SIP Rx udp:1.1.1.101:5060: CANCEL sip:2688634@1.1.1.5:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 1.1.1.101:5060;branch=z9hG4bK5jh8d610700gvec8h7g0.1 CSeq: 2 CANCEL Call-ID: 7007803330339123745-1265347685@172.30.77.25 From: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237 To: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e Max-Forwards: 69 Content-Length: 0 [7] 2010/02/05 08:29:02: SIP Tx udp:1.1.1.101:5060: SIP/2.0 481 Call/Transaction Does Not Exist Via: SIP/2.0/UDP 1.1.1.101:5060;branch=z9hG4bK5jh8d610700gvec8h7g0.1 From: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237 To: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e Call-ID: 7007803330339123745-1265347685@172.30.77.25 CSeq: 2 CANCEL Content-Length: 0 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 7, 2010 Report Share Posted February 7, 2010 [7] 2010/02/05 08:28:15: UDP: Opening socket on :57948[7] 2010/02/05 08:28:15: UDP: Opening socket on :57140 That worries me. It should say something like "Opening socket on 0.0.0.0:57948". What is the content of "port_bind4" in the pbx.xml directory? Maybe there is some garbage that tells the PBX to bind the ports to something which is impossible. Quote Link to comment Share on other sites More sharing options...
ShadowAnt Posted February 8, 2010 Author Report Share Posted February 8, 2010 <port_bind4/><port_bind6/> I didn't see any parameters in this string... Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 10, 2010 Report Share Posted February 10, 2010 Anyway, ":57948" means that the PBX did not bind it to any ports. That is very strange. I cant imagine a situation where this can happen. The only thing I can think of would be that the host does not have a IP address at all (maybe temporarily because the link got lost or the DHCP server did not renew the lease). Quote Link to comment Share on other sites More sharing options...
ShadowAnt Posted February 11, 2010 Author Report Share Posted February 11, 2010 The host have a static IP. maybe it is because windows 2008 x64...? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 11, 2010 Report Share Posted February 11, 2010 Well, Win64 is something unusual, still these days. IMHO it should not make a difference, but maybe there is really something different. If you can give it a try on a 32-bit system and it behaves different, I would say that would be worth a try. Quote Link to comment Share on other sites More sharing options...
ShadowAnt Posted February 12, 2010 Author Report Share Posted February 12, 2010 Well, Win64 is something unusual, still these days. IMHO it should not make a difference, but maybe there is really something different. If you can give it a try on a 32-bit system and it behaves different, I would say that would be worth a try. I try it on 32-bit edition of windows server 2003, windows XP, but still have the same problem... Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 14, 2010 Report Share Posted February 14, 2010 At 08:28:30 (15 seconds after switching to T.38) the "MG4000|2.0" wants to get back to regular voice. At least it sends a Re-INVITE without T.38. I guess that is the problem here. Maybe it does not like the T.38. Is there anything in the log of this device? That should should contain the hint why this call fails. From the PBX perspective it is hard to say. Until the Re-INVITE the call looks normal. 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.