We have several carriers. One of which does not support T.38. My question is... is there a way to specify the outbound route when using the Send Fax from the portal ? We want to use the non-T.38 supported carrier for normal calls because we get the best rates from them, verses the other carriers that do support T.38. We only want to go out over the more expensive carrier on faxes only.
Patrick
Yes....but...
Is it possible (if so how)... would I prepend a pattern (lets say '444') to a number entered from the Send Fax form in the user portal, so I can match it to a '_444' pattern in the dialplan rules to force it out over a specific carrier regardless of the destination number.
_444XXX. that would make it 7
_444XXX.
that would make it 7 or more digits (including the 444) and you asign the trunk for that pattern as your faxing trunk
I understand...
Let me try this again.. sure the user could enter from the send fax form on the portal 4440018585551212 which would match against the dial plan, and go out via the fax trunk. What I want to do is automatically prepend the 444 (or whatever dial pattern I want) AFTER they hit submit on the send fax form. Can this be done?
not right now. The web form
not right now. The web form creates a callfile that gets dropped into /var/spool/asterisk/outgoing/ (you can do a test and cat the file to see what it looks like). This is statically defined in the .cgi file. In order to change this you would need to get a copy of the .cgi in a format you can modify. Alternatively the .cgi could be re-designed to use a template for the callfile that is stored in plain-text. This would allow you to put a 444 in front of the variable for the extension. You would have to make a request for alex to turn the send fax callfile into a template that can be customized.
outbound calls are based on dialplan rules. In order to use a different carrier you would have to use a different patter that is defined for that carrier.