[cisco-voip] Anyone with Dialogic SR-140 / RightFax experience?

[JP Senior]

I have managed to do this with interesting dialing rules that apply per city, with applicable route patterns in CUCM.  I wanted to use CUCM to do this with a  single sip trunk, rather than relying on complicated sip trunk routing rules directly to gateways.

Rightfax is configured with a few SIP trunks on the SR-140 to call manager for redundancy, but we wanted to do least-cost routing.  It was difficult to differentiate which gateway a call should go out based on which username was logged in - identical scenario you are experiencing.  I managed to do this with applying routing groups within Rightfax with defined dialing rules.

Create new dialing rules under your dialing plan, matching a restriction that you administratively define: in our case, we group users based on their physical city they're a member of.  Secondly, make use of the number adjustments tab.  (Enterprise Fax Manager\Fax Servers\Servername\Dialing Plan\Dialing Rules)

Set up a match pattern of "+"

For City A, the dialing rules prepends "215", so the SIP trunk receives a dialed number of 215-999-555-1234.
For City B, the dialing rules prepends "216", so the SIP trunk receives a dialed number of 216-998-555-1234.

CUCM would then have route patterns configured:
215.@ -> Route list for City A, predot discard digits
216.@ -> Route list for City B, predot discard digits

You can leverage normal redundancy rules within your route list and route groups to kick a call out CityB if CityA is offline.


From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Scott Voll
Sent: 25 May 2012 4:22 PM
To: Jason Aarons (AM)
Cc: cisco-voip (cisco-voip at puck.nether.net)
Subject: Re: [cisco-voip] Anyone with Dialogic SR-140 / RightFax experience?

our Rightfax system has a PRI from it to our VGW.  Then we do everything with CM for Least cost routing.

if your doing H323 can't you do a H323 trunk with CM?

YMMV

Scott
On Fri, May 25, 2012 at 2:17 PM, Jason Aarons (AM) <jason.aarons at dimensiondata.com<mailto:jason.aarons at dimensiondata.com>> wrote:
Trying to figure out if I can point RightFax/SR-140 to multiple ip addresses based on destination address.

I'm pretty sure the RightFax 9.4 / SR-140 doing H323/T38  can only point to 1 ip address or RightFax can route to particular SR-140, then it's up to your peer PBX/H323 gateway to do the TEHO/Least Cost Routing etc.


Example customer request, they only have a couple SR-140s and locations in many more cities and want outbound to go out the end user's city.

We have some scope items that I want to make sure that we can meet for the outbound faxing project.

*             Outbound faxes will use the PRI/trunk of the site of the originating fax.  For example, if the fax is sent out of Tokyo it will use the local Tokyo PRI for the outbound call.
*             If the outbound trunk is down, the fax can route out of a secondary path.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip


The contents of this message may contain confidential and/or privileged
subject matter. If this message has been received in error, please contact
the sender and delete all copies. Like other forms of communication,
e-mail communications may be vulnerable to interception by unauthorized
parties. If you do not wish us to communicate with you by e-mail, please
notify us at your earliest convenience. In the absence of such
notification, your consent is assumed. Should you choose to allow us to
communicate by e-mail, we will not take any additional security measures
(such as encryption) unless specifically requested.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120525/7e63d919/attachment.html>