Outbound Route Patterns seem to be crossing over after call started through another Outbound Route?

@wciit wrote:

We have two servers, one at each of our plants. We had direct inter-company route via IAX for the longest time. The IAX is not working currently due to some other routing issues, so we started just using the normal trunk and lines to communicate between plants. Our Dial plans are as follows

SITE A
ToSiteB -> IAX : pattern 1XX
ToTDS -> SIP : everything else normal outbound

SITE B
ToSiteA -> IAX : pattern 3XX
ToNextiva -> SIP : everything else normal outbound

When site A outbounds through ToTDS using site B's external number and dials an extension all is well. when site B outbounds through ToNextiva using site A's external number this is where things get wierd.

Say I am calling...
from B to A and I want extension 331 I will get 333
from B to A and I want extension 342 I will get 334

See the pattern? First two digits dialed are added to the 3XX pattern and last digit is ignored. This does not happen calling through external lines from A to B only from B to A. Deleting the Outbound route for B to A with the 3XX pattern in it solved the issue.

Thing is once I have already outbound through one route in these cases I hit site A's IVR dialing from site B how can in the middle of that call another route and pattern take over?

Posts: 3

Participants: 2

Read full topic