Looking for a bit of assistance with some configuration. Am i missing or mis-configured something here? If any other debugging is needed pls let me know. I ahve attached a ccapi inout debug of a fax transmission
The issue is that the fax keeps coming back with busy message. It can however receive faxes with no issues and the number is not busy as we provide the DDI.
When the user sends the fax I can see the call being set up and billed for meaning the connection has been established but the fax transmission itself fails.
The router hosting the fax is using h323 and the fax is termination on a SIP trunk.
voice service voip fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none fax-relay ans-disable h323 no call service stop sip call service stop
The fax is directly connected to the Fax via FXS. Their is an MTP translating between the H323 GW and the SIP connection to our provider so there are no end to end SIP messages.
I have noticed whilst checked the sho voice call sum that when the port is in "digit_collect" or "alerting" the codec used is G711uLAW then it goes to G729br8 when the FXS port in "Connect" then changes to S_Fax. SO i am wondering if the 729 codec is causing some distortion in the tones which would be contributing to the failures.
I will try configuring a dial peer with a incoming number configured and set the codec as G711uLAW.
Do you have any other ideas failing that?
PORT CODEC VAD VTSP STATE VPM STATE ============== ========= === ==================== ====================== 0/2/0 g711ulaw n S_DIGIT_COLLECT FXSLS_OFFHOOK 0/2/1 - - - FXSLS_ONHOOK 0/2/2 - - - FXSLS_ONHOOK 0/2/3 - - - FXSLS_ONHOOK
PORT CODEC VAD VTSP STATE VPM STATE ============== ========= === ==================== ====================== 0/2/0 g729br8 n S_CONNECT FXSLS_CONNECT 0/2/1 - - - FXSLS_ONHOOK 0/2/2 - - - FXSLS_ONHOOK 0/2/3 - - - FXSLS_ONHOOK
PORT CODEC VAD VTSP STATE VPM STATE ============== ========= === ==================== ====================== 0/2/0 t38 n S_FAX FXSLS_CONNECT 0/2/1 - - - FXSLS_ONHOOK 0/2/2 - - - FXSLS_ONHOOK 0/2/3 - - - FXSLS_ONHOOK
G.729 can work, as long as the end result is to do t.38. I actually have all my fax machines start the call with G.729 and then negotiate T.38.
Looking at your debug it shows disconnect cause = 38, means your network is out of order, usually a configuration problem with the h323 voip gateway, but also it looks like your caller-id is going out as 2226 and not a full DID, if the carrier is not accepting your outgoing calls this might explain why you can receive but not send:
I have the voice team revert back to the PSTN away from SIP and I created new Dial peer to ensure G711 is used. I also added a station ID to ensure the ANI confirmed to e.164 Standard. Fax is now working to a possible issue with the SIP provider negotiation.
I will revert back to SIP, adjust Dialpeer back to T38 and see if it works.
In the meantime, you can create a "Test dial peer" with a fax number and point it to the SIP trunk, that way you won't affect all of the other calls. If you don't want to modify your station id you could also create a translation rule to transform 2226 into XXX XXX 2226. Let me know if you need help with any of that, or testing, you can use my fax #.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...