JaeJay Posted October 31, 2008 Report Share Posted October 31, 2008 First off, my sincerest of apologies if I am posting something here that has been 1) already answered and I've ever so blindly missed 2) something that is painfully simple and I am just waaay overthinking it or 3) do anything in this post that could generate an onslaught of people to virtually tar and feather me forum style. Okay, now that is out of the way, on to the good stuff. I've been reading this forum for months now, as well as googled till I can google no more in search of the ellusive answer to (what seems to be?) getting Inbound T.38 faxing from my ITSP (Callcentric) to my Exchange UM Server, and on to the destined mailbox with my beloved PBXnSIP (loved more and more each day!) sitting right in the middle of ITSP and Exchange. I feel as if I am very close, either that or my fear will shortly be proven and I have very little idea what the heck is actually going on. However, When sending a fax from the PSTN (310) 305-1073, to a DID on my callcentric account (310) 496-7515, Callcentric delivers the call as expected, PBXnSIP (localhost) sees it, sends the INVITE to across my Exchange UM trunk to the Exchange UM Server (oim-lax-ums-002), where I have added as a secondary fax-enabled extension 7515 (and faxing is enabled on the Exchange dial plan as well), the voicemail box picks up, Exchange says hey you aren't talking, you're beeping in CNG, I need to change. At that point, I think it looks like everything switches over to T38, and then just like magic, boom, absolutely nothing happens. I can hear the voicemail greeting thru the PSTN fax on via the speaker. <Simulation of Voice> "Hello this is me, I'm a voicemail box, please oh please let the fax just work!" </the end> I can see the T38 switch happening (I think) from the logfile (see below) SIP/2.0 200 Ok Via: SIP/2.0/UDP 188.8.131.52:5080;branch=z9hG4bK-dcbcf5a31b41b4dedebcd0e68c48fd79 From: <sip:email@example.com>;tag=3434448420-488153 To: <sip:firstname.lastname@example.org>;tag=4dd28c48d5 Call-ID: email@example.com CSeq: 1 INVITE Contact: <sip:firstname.lastname@example.org: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/184.108.40.20637 Content-Type: application/sdp Content-Length: 196 v=0 o=- 23537 23537 IN IP4 192.168.12.129 s=- c=IN IP4 192.168.12.129 t=0 0 m=audio 56518 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv  2008/10/31 06:27:37: SIP Rx udp:220.127.116.11:5080: ACK sip:email@example.com:5060;transport=udp SIP/2.0 v: SIP/2.0/UDP 18.104.22.168:5080;branch=z9hG4bK-d07ae536da0612b3ab058fe9274dafa8 f: <sip:firstname.lastname@example.org>;tag=3434448420-488153 t: <sip:email@example.com>;tag=4dd28c48d5 i: firstname.lastname@example.org CSeq: 1 ACK Max-Forwards: 15 m: <sip:email@example.com:5080;transport=udp> l: 0  2008/10/31 06:27:38: SIP Rx tcp:192.168.12.114:5065: INVITE sip:firstname.lastname@example.org:57932;transport=tcp SIP/2.0 FROM: <sip:email@example.com;user=phone>;epid=D1809C5B9B;tag=513be24042 TO: <sip:firstname.lastname@example.org;user=phone>;tag=7619 CSEQ: 1 INVITE CALL-ID: 444a52d7@pbx MAX-FORWARDS: 70 VIA: SIP/2.0/TCP 192.168.12.114:5065;branch=z9hG4bKf31bc4d2 CONTACT: <sip:OIM-LAX-UMS-002.omegaidentitymedia.net:5065;transport=Tcp;maddr=192.168.12.114;ms-opaque=6b221c7eb4bdd3da>;automata CONTENT-LENGTH: 290 USER-AGENT: RTCC/22.214.171.124 CONTENT-TYPE: application/sdp v=0 o=- 0 1 IN IP4 192.168.12.114 s=session c=IN IP4 192.168.12.114 t=0 0 m=audio 0 RTP/AVP 0 8 101 13 a=rtpmap:0 PCMU/8000/1 a=rtpmap:8 PCMA/8000/1 a=rtpmap:101 telephone-event/8000 m=image 55320 udptl t38 a=T38FaxRateManagement:transferredTCF a=T38FaxUdpEC:t38UDPRedundancy I can read that Exchange got a call that it thought was a fax, by looking at the Event Log on the UM Server, curiously saying no pages were received (see event log item directly below): Log Name: Application Source: MSExchange Unified Messaging Date: 10/31/2008 6:28:26 AM Event ID: 1028 Task Category: UMCore Level: Information Keywords: Classic User: N/A Computer: OIM-LAX-UMS-002.omegaidentitymedia.net Description: The fax call from "7515" for "Jeremiah L. Maudlin" at number "7515" was received but no pages were received. The fax call was 48.7017504 seconds long. The fax call was received from UM IP gateway "192.168.12.126". <Provider Name="MSExchange Unified Messaging" /> <EventID Qualifiers="32772">1028</EventID> <Level>4</Level> <Task>2</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2008-10-31T13:28:26.000Z" /> <EventRecordID>18101</EventRecordID> <Channel>Application</Channel> <Computer>OIM-LAX-UMS-002.omegaidentitymedia.net</Computer> <Security /> </System> <EventData> <Data>7515</Data> <Data>Jeremiah L. Maudlin</Data> <Data>7515</Data> <Data>48.7017504</Data> <Data>192.168.12.126</Data> </EventData> </Event> Alas, no fax in my inbox, an agry PSTN fax machine that says "would you give it up already!" and starts beeping at me, and one confused IT guy sitting at his desk shaking his head and ever so hopeful that a forum post will lead to his rescue. A couple other quick items of note: Exchange 2007 SP1 UM, CA, MB, and HT roles all on 4 seperate servers PBXnSIP 3.0.3037 w/ Permanent License, 3 Trunks, a number of accounts, 1 Dial Plan Fully OCS Integrated w/o issue (horray! thanks to pbxnsip dev & Jan B. for excellent work!) Callcentric SIP Trunk w/ ~30 DIDs Exchange globalcfg.xml file changes: <EnableInbandFaxDetection>true</EnableInbandFaxDetection> <UseT38UDPRedundancyForFax>true</UseT38UDPRedundancyForFax> (As for two items above, I have tried various combinations of true/false, and this seems to get me closest to success) I've also attached the complete PBXnSIP log (Level 9) to this post for review from a failed Fax call just a few moments ago. Thanks in advance to all, it is most appreciated! SIPLogT38Failure.txt Quote Link to comment Share on other sites More sharing options...
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.