We have implemented the GFI fax maker solution using brooktrout SR140-L driver which should send and receive faxes through a Cisco voice gateway 2901 router using T38 fax protocol, my environment has a SIP Trunk connection with the provider for carrying external calls (actually it can be considered a VoIP connection using SIP protocol with the provider), the connection between the Cisco VGW and the fax server is also through SIP dial peer.
We can send faxes successfully from the fax server to the Cisco VGW to the PSTN but the problem is that we cannot receive faxes on the SIP line as the line open and the call is answered then the fax parameters handshaking is failed and the call is terminated.
We have contacted the fax server vendor and we have gone through a lot of troubleshooting with them which ends up with the following reply from their side:
”The reason this is not working is because SR140 finds no common codec. The Cisco is answering the T.38 switch request with a bad SDP:
Media Description, name and address (m): image 17232 udptl t38
Connection Information (c): IN IP4 172.16.61.250
Media Attribute (a): inactive
Media Attribute (a): rtpmap:8 PCMA/8000
Media Attribute (a): ptime:20
Media Attribute (a): T38FaxVersion:0
The three bolded lines should not be there. Technically, you cannot have media attributes from another codec creep into another codec's media description. Here it looks like the attributes for G.711A are inserted in the middle of the attributes for the T.38 stream. In effect, we want G.711 to be silenced (a=inactive), but those attributes are simply in the wrong place.
Please submit this to Cisco to get some input on what to rectify in the configuration”
I have attached some related logs including the following:
1. The network setup with IP Addresses.
2. Cisco router fax related configurations.
3. Cisco VGW Router Sh tech.
4. Debug output from the VGW for the “debug voice ccapi inout” and “debug ccsip messages” commands during a failed coming fax call knowing that the calling number is 138471627 and the called number is 8459410 which translated later to 9410 then sent to the fax server.
5. Wireshark Captured data from fax server for the same failed incoming fax call which shows the communication nature between the fax server and the VGW and the exchanged messages.
So based on all these inputs I need to know how the VGW T38 faxing configurations should be tuned to be able to communicate properly with the fax server.
New update of Cisco Meeting Server book with Streamer and Scheduler components, the book will cover the following:certificates requirements, clustering, dial plan with call flow, WebRTC, WebBridge3, CallBridge, recorder, streamer, scheduler, NAT Traversal...
The Scheduler component was introduced as a beta feature in version 3.3. It was added as anew component that enabled Web app users to schedule meetings, modify the scheduledmeetings, and notify participants via email. From version 3.4, Scheduler is fully ...
A collection of the most important notes from different resources for Cisco CMS and vbrick integration. Live Streaming (Webcast) integration with VBrick DME allow users to watch any live streamed CMS conference anywhere inside the network from differ...
The 2021 IT Blog Awards, hosted by Cisco, is now open for submissions. Submit your blog, vlog or podcast by Friday, December 3.
To learn what's new in this year's competition or to gain insights into the judging considerations, check out t...