Faxing & unable to pass a *99+phone number as the final dial string

General Help
1

any help with diagnosis or solution would be greatly apprec :pray: :pray:

I want to send a fax, and line provider want me to dial *99 before dialing the phone numbe. The fax fails, suspect the cause is *99 is triggering something internal to freepbx/asterik and and not letting it through. any way get the *99+ph# to pass thru to from pbx to dialing? both the freepbx and the ooma trunk has * feature codes. any ideas on how to accomplish getting the final outbound call to be *99+ph#.

what i tried so far:

  • voice call to 19292070142 (faxbeep.com) - success. I hear fax tones, confirming the service.
  • voice call to *99+ph#, i get an operator msg “the number you have dialed not in service, try again…”. *99+ph# dialed appears not to reaching the desired 19292070142 endpoint.
  • Faxing w/ WinPrint Hylafax ph# (without *99) ; this leads to a fail, see log below. appears to make contact with fax machine VoxFax but not successful. Guess this is why ooma want to pre-identify faxes with a *99 tag to optimize.
  • make sure *99 isnt on the pbx feature code list (no changes, *99 is not a feature code, * is listed as a direct dial prefix – not sure what that means),
  • WinPrint *99+Ph#; lead to the fax keeps re-queuing, and finally fail after X attempts.
  • tried creating a dial pattern of *991NXXNXXXXXX ; dial *99+ph#; output incorrect dialing, “no carrier” from the hylafax logs

hardware setup: (ooma pstn) to (grandstream ata) to ( RasPBX with hylafax )
(Ooma needs to know that you are making a fax call so the connection can be optimized for fax transmissions. Dial the prefix *99 before dialing the number you wish to reach.)

hylafax error report: ( this is standard dialing w.o. the *99 recommendation)
Your job to 19292070142 failed because:

---- Transcript of session follows ----

Jul 23 11:35:52.34: [ 9064]: SESSION BEGIN 000000017 19292070142
Jul 23 11:35:52.34: [ 9064]: HylaFAX ™ Version 6.0.6
Jul 23 11:35:52.34: [ 9064]: SEND FAX: JOB 4 DEST 19292070142 COMMID 000000017 DEVICE ‘/dev/ttyI150’ FROM ‘root <[___@gmail.com)>’ USER root
Jul 23 11:35:52.34: [ 9064]: ← [14:AT+FCLASS=1.0\r]
Jul 23 11:35:52.34: [ 9064]: → [2:OK]
Jul 23 11:35:52.35: [ 9064]: DIAL 19292070142
Jul 23 11:35:52.35: [ 9064]: ← [16:ATDT19292070142\r]
Jul 23 11:36:05.67: [ 9064]: → [7:CONNECT]
Jul 23 11:36:06.93: [ 9064]: → [5:ERROR]
Jul 23 11:36:06.93: [ 9064]: MODEM Command error
Jul 23 11:36:06.93: [ 9064]: FCS error
Jul 23 11:36:06.93: [ 9064]: ← [10:AT+FRS=21\r]
Jul 23 11:36:07.65: [ 9064]: → [2:OK]
Jul 23 11:36:07.65: [ 9064]: ← [9:AT+FTH=3\r]
Jul 23 11:36:07.67: [ 9064]: → [7:CONNECT]
Jul 23 11:36:07.67: [ 9064]: ← data [3]
Jul 23 11:36:07.67: [ 9064]: ← data [2]
Jul 23 11:36:08.75: [ 9064]: → [2:OK]
Jul 23 11:36:08.75: [ 9064]: SEND send CRP (command repeat)
Jul 23 11:36:08.75: [ 9064]: ← [9:AT+FRH=3\r]
Jul 23 11:36:09.67: [ 9064]: → [7:CONNECT]
Jul 23 11:36:11.39: [ 9064]: → [5:ERROR]
Jul 23 11:36:11.39: [ 9064]: MODEM Command error
Jul 23 11:36:11.39: [ 9064]: FCS error
Jul 23 11:36:11.43: [ 9064]: ← [10:AT+FRS=21\r]
Jul 23 11:36:12.12: [ 9064]: → [2:OK]
Jul 23 11:36:12.12: [ 9064]: ← [9:AT+FTH=3\r]
Jul 23 11:36:12.13: [ 9064]: → [7:CONNECT]
Jul 23 11:36:12.13: [ 9064]: ← data [3]
Jul 23 11:36:12.13: [ 9064]: ← data [2]
Jul 23 11:36:13.21: [ 9064]: → [2:OK]
Jul 23 11:36:13.21: [ 9064]: SEND send CRP (command repeat)
Jul 23 11:36:13.21: [ 9064]: ← [9:AT+FRH=3\r]
Jul 23 11:36:14.15: [ 9064]: → [7:CONNECT]
Jul 23 11:36:15.09: [ 9064]: → [5:ERROR]
Jul 23 11:36:15.09: [ 9064]: MODEM Command error
Jul 23 11:36:15.09: [ 9064]: FCS error
Jul 23 11:36:15.09: [ 9064]: ← [10:AT+FRS=21\r]
Jul 23 11:36:16.61: [ 9064]: → [2:OK]
Jul 23 11:36:16.61: [ 9064]: ← [9:AT+FTH=3\r]
Jul 23 11:36:16.63: [ 9064]: → [7:CONNECT]
Jul 23 11:36:16.63: [ 9064]: ← data [3]
Jul 23 11:36:16.63: [ 9064]: ← data [2]
Jul 23 11:36:17.71: [ 9064]: → [2:OK]
Jul 23 11:36:17.71: [ 9064]: SEND send CRP (command repeat)
Jul 23 11:36:17.71: [ 9064]: ← [9:AT+FRH=3\r]
Jul 23 11:36:18.91: [ 9064]: → [7:CONNECT]
Jul 23 11:36:20.63: [ 9064]: → [5:ERROR]
Jul 23 11:36:20.63: [ 9064]: MODEM Command error
Jul 23 11:36:20.63: [ 9064]: FCS error
Jul 23 11:36:20.63: [ 9064]: ← [9:AT+FRS=7\r]
Jul 23 11:36:21.23: [ 9064]: → [2:OK]
Jul 23 11:36:21.23: [ 9064]: ← [9:AT+FRH=3\r]
Jul 23 11:36:26.57: [ 9064]: → [7:CONNECT]
Jul 23 11:36:28.25: [ 9064]: → [2:OK]
Jul 23 11:36:28.25: [ 9064]: REMOTE CSI “VoxFax”
Jul 23 11:36:28.25: [ 9064]: ← [9:AT+FRH=3\r]
Jul 23 11:36:28.75: [ 9064]: → [7:CONNECT]
Jul 23 11:36:28.81: [ 9064]: → [2:OK]
Jul 23 11:36:28.81: [ 9064]: REMOTE best rate 9600 bit/s
Jul 23 11:36:28.81: [ 9064]: REMOTE max A4 page width (215 mm)
Jul 23 11:36:28.81: [ 9064]: REMOTE max unlimited page length
Jul 23 11:36:28.81: [ 9064]: REMOTE best vres 15.4 line/mm
Jul 23 11:36:28.81: [ 9064]: REMOTE format support: MH, MR
Jul 23 11:36:28.81: [ 9064]: REMOTE best 0 ms/scanline
Jul 23 11:36:28.81: [ 9064]: USE 9600 bit/s
Jul 23 11:36:28.81: [ 9064]: ← [9:AT+FRS=7\r]
Jul 23 11:36:28.89: [ 9064]: → [2:OK]
Jul 23 11:36:28.89: [ 9064]: ← [9:AT+FTH=3\r]
Jul 23 11:36:28.91: [ 9064]: → [7:CONNECT]
Jul 23 11:36:28.91: [ 9064]: ← data [3]
Jul 23 11:36:28.91: [ 9064]: ← data [2]
Jul 23 11:36:29.99: [ 9064]: → [2:OK]
Jul 23 11:36:30.99: [ 9064]: ← [5:ATH0\r]
Jul 23 11:36:31.12: [ 9064]: → [2:OK]
Jul 23 11:36:31.12: [ 9064]: SESSION END

2

This message means that you don’t have an Outbound Route matching the *99 number.
In the (non-emergency) Outbound Route that uses the Grandstream trunk, add an entry with
prepend: (leave blank)
prefix: (leave blank)
match pattern: *99X. (or as you had it)
CallerID: (leave blank)

Test with a voice call first. If you hear “all circuits are busy now”, the dial plan in the Grandstream is probably not matching the *99 number. Also, make sure that *99 isn’t set up as an internally recognized code.

Once you hear fax tones on a voice call, test with Hylafax.

1 Like
3

may have to live without this feature since faxing is not operationally critical. unfortunately the grandstream and the ooma do not provide log level access to see what is passing or not. too many middleware in this stream

correction dial plan didnt work until i wiped it and started over. however, *99phone# still doesnt work.

4

Assuming that you have an HT503 or HT 813, it has a good syslog feature that will tell you why it is rejecting a call.

Also, pjsip logger shows communication between Asterisk and the ATA.

What do you hear now when you dial the *99 number as a voice call?

1 Like
5

wow thanks for the syslog tip. can confirm pbx is sending *99phone# string to the grandstream HT813. seen- TO: <sip:*9919292070142@ip grandstream:5062>

Dialed:

  • number as a voice call = fax tones ( expected )
  • *99 + number as a voice call= “this this number is were sorry the number you dial is no longer in service or has been disconnected.” – not the desired fax tones as above. the ooma call log says its call (991) 929-2070 ( dropping the * & missing last two 3 digits ).
  • plugging a phone directly into the ooma ( bypass pbx, bypass the ATA) calling *99+number as a voice call=fax tones ( expected, also noted that the dialtone pauses briefly as it confirms *99 feature code was detected ).

I think the number passed as *9919292070142 is triggering an error on the dial side. I’ve read this might be called a “live dialing” issue (human take time to press keys vs a machine dialing really fast). this may no longer a PBX general help issue since the full string is now passing fully on to the ATA.
unless someone can offer how to insert a pause in the pbx dial plan, I will be not be making much progress. I tried adjusting the dial plan in the ATA; correct number dialed, however still not able to fax successfully. thanks everyone.

solution for now is to use faxzero :frowning:

6

Perhaps choose dtmfmode=inband in the trunk, maybe add a ; or , after the *99 also

7

@dicko, negative; didnt achieve a better outcome.
thanks for the try

8

According to

the FXO page default Dial Plan is
{x+}
which would disallow the initial *.
Please try changing it to
{x+ | *x+}
and retest dialling *9919292070142 as a voice call.

1 Like
9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.