Kristan Posted November 21, 2008 Report Share Posted November 21, 2008 Hi guys, Just wondering if anyone has a standard setup for running this with PBXnSIP? I've got it registered to a PBX extension, but it doesn't seem to try to negotiate T.38 as part of the invite, it just sends it as ulaw, and the fax fails (it dials answers/correctly etc.). Also the invite seems to have the domain name appended rather a lot. Any ideas before I get onto their support guys? : INVITE sip:xxxx@pbxnsip.wm.local@pbxnsip.wm.local@pbxnsip.wm.local SIP/2.0 Via: SIP/2.0/UDP 10.50.4.41:5060;branch=z9hG4bK1106 From: IPFax <sip:xxxx@pbxnsip.wm.local@10.50.4.41>;tag=IPF_PORT_0001_1105 To: <sip:xxxxxx@pbxnsip.wm.local@pbxnsip.wm.local@pbxnsip.wm.local> Call-ID: f0627200-e41a-44eb-9328-b7152a8149ff@10.50.4.41 CSeq: 2 INVITE Max-Forwards: 70 Contact: <sip:6192@pbxnsip.wm.local@10.50.4.41:5060> User-Agent: Net Satisfaxtion/IP_FAX-8.5.4225.929 Authorization: Digest username="xxxx",realm="pbxnsip.wm.local@10.50.4.41",nonce="2101959bb16d637f6f099251b5ddc659",opaque="",uri="sip:xxxxxx@pbxnsip.wm.local@pbxnsip.wm.local@pbxnsip.wm.local",response="8ddf7a06f7ca94c7d46d228767c2873c" Allow: INVITE, ACK, BYE, CANCEL, REFER, NOTIFY Content-Type: application/sdp Content-Length: 216 v=0 o=IPFax 0 0 IN IP4 10.50.4.41 s=SIP Fax Call i=IPFax c=IN IP4 10.50.4.41 t=0 0 m=audio 49154 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 Quote Link to comment Share on other sites More sharing options...
Kristan Posted November 21, 2008 Author Report Share Posted November 21, 2008 Should also say I've had this working in the same config with a sipura 3102, so I know T.38 and faxes work, just need to figure out what I've done wrong with this one Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 21, 2008 Report Share Posted November 21, 2008 INVITE sip:xxxx@pbxnsip.wm.local@pbxnsip.wm.local@pbxnsip.wm.local SIP/2.0 That looks strange. Too many @ symbols... And it is not a valid SIP URI. Quote Link to comment Share on other sites More sharing options...
Kristan Posted November 21, 2008 Author Report Share Posted November 21, 2008 That looks strange. Too many @ symbols... And it is not a valid SIP URI. Agreed - it still dialled ok though! I think the @ symbols was my fault, I had it setup to add @pbxnsip.wm.local when it dialled, and it was doing it each time I tried to resend. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 21, 2008 Report Share Posted November 21, 2008 Agreed - it still dialled ok though! I think the @ symbols was my fault, I had it setup to add @pbxnsip.wm.local when it dialled, and it was doing it each time I tried to resend. And what does it say now? Quote Link to comment Share on other sites More sharing options...
Kristan Posted November 21, 2008 Author Report Share Posted November 21, 2008 And what does it say now? Still the same, but the invite is just xxx@pbxnsip.wm.local If no-one has a general "how-to" guide for configuring this with PBXnSIP don't worry too much, I'll keep playing and see if I can get it working. Quote Link to comment Share on other sites More sharing options...
hosted Posted December 31, 2008 Report Share Posted December 31, 2008 how did this work out? I am interested in trying this. I dont know if I will ever deploy it, to expensive for what it does. Quote Link to comment Share on other sites More sharing options...
cwernstedt Posted February 3, 2009 Report Share Posted February 3, 2009 how did this work out? I am interested in trying this. I dont know if I will ever deploy it, to expensive for what it does. I'm doing it with Vegastream ISDN devices. It works well, however I needed to bypass pbxnsip for incoming fax calls. I route those straight to NET SatisFAXtion through dial plans in Vegastream. The system is very scalable, reliable, and you can send and receive faxes as email attachments. I've got T38 transmissions to work over rather flaky Internet connections too with Net SatisFAXtion as an endpoint. (Though here, reliability is not 100% especially if the calls come from ISDN - a clocking issue, I believe.) /CW Quote Link to comment Share on other sites More sharing options...
hosted Posted February 22, 2009 Report Share Posted February 22, 2009 I just installed it for fun and it seems to pass T.38 quite well. 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.