Three Rules - Two Worked

[DrainBamaged]

This began as an issue report, but I found the cause as I was writing, so I thought I'd post it in case some one else ran into the same issue.

We have a Toronto based office and I wanted to route any calls from our head office to any local Toronto area code through our 3CX Bridge. This makes it a local call from the TO office instead of an international long distance call from head office.

Here's my setup, I had three outbound rules in place.

1. Any 10 digit number dialed, with prefix 416,437,647,905, go to route1 (Canada bridge), or route2 (normal long distance, if bridge is down)
2. Any 11 digit number dialed, with prefix 1416,1437,1647,1905, go to route1 (Canada bridge), or route2 (normal long distance, if bridge is down)
3. Any 12 digit number dialed, with prefix +1416,+1437,+1647,+1905, go to route1 (Canada bridge), or route2 (normal long distance, if bridge is down)

The first two rules route calls properly to the Canada bridge. Calls to +1416,+1437,+1647,+1905 (Toronto area codes) skipped rule 3 and went to the International Long Distance rule further down. I see this in the activity log for each rule:

1. [Flow] Call(C:5042): has built target endpoint: Out#:>>Rule{Long Distance - Canada No 1 (Inside TO)}>>416869XXXX for call from L:5042.1[Extn:XXX]
2. [Flow] Call(C:5048): has built target endpoint: Out#:>>Rule{Long Distance - Canada 1 (Inside TO)}>>1416869XXXX for call from L:5048.1[Extn:XXX]
3. [Flow] Call(C:5038): has built target endpoint: Out#:>>Rule{Overseas Long Distance 011}>>0111416869XXXX for call from L:5038.1[Extn:XXX]

The + was being translated to 011 by the system so the +1416,+1437,+1647,+1905 prefixes on rule 3 were not being seen by the system.

I amended rule 3 to use prefixes, 0111416,0111437,0111647,0111905 plus 14 digits and it now routes correctly on rule 3.

[Flow] Call(C:5604): has built target endpoint: Out#:>>Rule{Long Distance - Canada +1 (Inside TO)}>>0111416869XXXX for call from L:5604.1[Extn:XXX]

Thanks.

 

[leejor]

If you set up e164 (sounds like you have), it will "translate" (convert), the + into the required international prefix, which the rules then use to route. This allows callers dialling the full number (not using a + prefix), to route correctly.

 

[DrainBamaged]

@leejor Good call, we do use e164 at that site. I have three rules to cover all of the possibilities that a user can dial out as the numbers need to be massaged to be presented to our SIP provider properly.

I took it that outbound rules used the number dialed as the basis for the decision logic. Once I referenced the Activity Log and saw the system morphed "+" into "011" it made sense why it was failing.