Multi-Site dial plan conflict with area code

Answered Question

Hi,

I have a question regarding our setup.

We have 3 UC520 on different locations configured to connect to each other.

To dial to Site A from other sites you have to enter 81 XXX

To Site B, 82 XXX and

To Site C, 83 XXX


Problem is, the Site C area code is 819 and whenever someone enters 819 and the local number they want to reach, the UC tries to transfer the call to Site A... I'm guessing I'm not doing things properly with regex or dialplans... Here is some relevant part of the UC520 Site C config :


dial-peer voice 1 pots
destination-pattern 401
port 0/0/0
no sip-register
!
dial-peer voice 2 pots
destination-pattern 402
port 0/0/1
no sip-register
!
dial-peer voice 3 pots
destination-pattern 403
port 0/0/2
no sip-register
!
dial-peer voice 4 pots
destination-pattern 404
port 0/0/3
no sip-register
!
dial-peer voice 5 pots
description ** MOH Port **
destination-pattern ABC
port 0/4/0
no sip-register
!
dial-peer voice 50 pots
description ** incoming dial peer **
incoming called-number .%
port 0/1/0
!
dial-peer voice 51 pots
description ** incoming dial peer **
incoming called-number .%
port 0/1/1
!
dial-peer voice 52 pots
description ** incoming dial peer **
incoming called-number .%
port 0/1/2
!
dial-peer voice 53 pots
description ** incoming dial peer **
incoming called-number .%
port 0/1/3
!
dial-peer voice 54 pots
description ** FXO pots dial-peer **
destination-pattern A0
port 0/1/0
no sip-register
!
dial-peer voice 55 pots
description ** FXO pots dial-peer **
destination-pattern A1
port 0/1/1
no sip-register
!
dial-peer voice 56 pots
description ** FXO pots dial-peer **
destination-pattern A2
port 0/1/2
no sip-register
!
dial-peer voice 57 pots
description ** FXO pots dial-peer **
destination-pattern A3
port 0/1/3
no sip-register
!
dial-peer voice 2000 voip
description ** cue voicemail pilot number **
translation-profile outgoing XFER_TO_VM_PROFILE
destination-pattern 499
b2bua
voice-class sip outbound-proxy ipv4:10.1.10.1
session protocol sipv2
session target ipv4:10.1.10.1
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 2001 voip
description ** cue auto attendant number **
translation-profile outgoing PSTN_CallForwarding
destination-pattern 498
b2bua
voice-class sip outbound-proxy ipv4:10.1.10.1
session protocol sipv2
session target ipv4:10.1.10.1
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 2012 voip
description ** cue prompt manager number **
translation-profile outgoing PSTN_CallForwarding
destination-pattern 297
b2bua
voice-class sip outbound-proxy ipv4:10.1.10.1
session protocol sipv2
session target ipv4:10.1.10.1
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 58 pots
trunkgroup ALL_FXO
corlist outgoing call-emergency
description **CCA*North American*Emergency**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE
preference 5
destination-pattern 9911
forward-digits all
no sip-register
!
dial-peer voice 59 pots
trunkgroup ALL_FXO
corlist outgoing call-emergency
description **CCA*North American*Emergency**
translation-profile outgoing CALLER_ID_TRANSLATION_PROFILE
preference 5
destination-pattern 911
forward-digits all
no sip-register
!
dial-peer voice 60 pots
trunkgroup ALL_FXO
corlist outgoing call-local
description **CCA*North American*7-Digit Local**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE
preference 5
destination-pattern 9[2-9]......
forward-digits all
no sip-register
!
dial-peer voice 61 pots
trunkgroup ALL_FXO
corlist outgoing call-local
description **CCA*North American*10-Digit Local**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE
preference 5
destination-pattern 9[2-9]..[2-9]......
forward-digits all
no sip-register
!
dial-peer voice 62 pots
trunkgroup ALL_FXO
corlist outgoing call-local
description **CCA*North American*Service Numbers**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE
preference 5
destination-pattern 9[2-9]11
forward-digits all
no sip-register
!
dial-peer voice 63 pots
trunkgroup ALL_FXO
corlist outgoing call-national
description **CCA*North American*Long Distance**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE
preference 5
destination-pattern 91[2-9]..[2-9]......
forward-digits all
no sip-register
!
dial-peer voice 64 pots
trunkgroup ALL_FXO
corlist outgoing call-international
description **CCA*North American*International**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE
preference 5
destination-pattern 9011T
forward-digits all
no sip-register
!
dial-peer voice 65 pots
trunkgroup ALL_FXO
corlist outgoing call-toll-free
description **CCA*North American*Toll-Free**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE
preference 5
destination-pattern 91800.......
forward-digits all
no sip-register
!
dial-peer voice 66 pots
trunkgroup ALL_FXO
corlist outgoing call-toll-free
description **CCA*North American*Toll-Free**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE
preference 5
destination-pattern 91888.......
forward-digits all
no sip-register
!
dial-peer voice 67 pots
trunkgroup ALL_FXO
corlist outgoing call-toll-free
description **CCA*North American*Toll-Free**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE
preference 5
destination-pattern 91877.......
forward-digits all
no sip-register
!
dial-peer voice 68 pots
trunkgroup ALL_FXO
corlist outgoing call-toll-free
description **CCA*North American*Toll-Free**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE
preference 5
destination-pattern 91866.......
forward-digits all
no sip-register
!
dial-peer voice 83200 voip
description INCOMING CALLS
translation-profile incoming intersite
incoming called-number 83...
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 81200 voip
description OUTGOING CALLS TO SITE A

destination-pattern 81...
session target ipv4:192.168.254.254
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!

Correct Answer by Steven Smith about 7 years 7 months ago

Here is what I can say that is happening.  On the call that is not working, it isn't matching dialpeer 61, only dialpeer 60.  61 does the 10 digit dialing.  60 is 7 digit dialing.  It should match both until you enter the 8th digit.  On the failing call, it matches dialpeer 60, and will display 7 digits on the phone, and send the call to the PSTN.  You can enter the other 3 digits because the telco is waiting for more digits for the call to complete.


One thing you could try would be to delete the 7 digit dialing.  I was thinking that this might be a corlist problem, but it doesn't appear so.  If removing the 7 digit dialing doesn't work (and I really don't expect it to), I would recommend opening a tac case.  This appears to be a bug.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Steven DiStefano Mon, 11/23/2009 - 06:56
User Badges:
  • Blue, 1500 points or more

Wondering if you changed the site index to avoid ambiguity?  Use CCA Multisite manager?

MSM_index.GIF

Hello Steve,

I'm pretty sure changing the site index will solve the issue, but then again, why does it works that way?

I mean, if I dial 98195555555 why is it handled as if I entered 81955?

I'd prefer solving this by really fixing my configuration either than just patching it...


As for using CCA, since I have created the tunnels manually, CCA's not letting me view that section, unless I delete all VPN Settings which is not an option right now... :S


Thanks!

Steven Smith Mon, 11/23/2009 - 09:15
User Badges:
  • Gold, 750 points or more

Would you mind posting your full config?  Looking at the configuration that is currently posted, there is no reason for 98195551212 to go multisite. 

Steven Smith Mon, 11/23/2009 - 16:02
User Badges:
  • Gold, 750 points or more

Can you do a debug voip dialpeer on this?  I am still not sure why it would be doing this.

Ok, I've got some new info.

The SiteC has 2 7945 phones. One can make local calls and the other one can't.

I've attached three files with dialpeer debug data.


Here are three files :

First one is working call made from SiteC to SiteA using the tunnel.

Second one is a local call made from SiteC that didn't go through and tried to connect to SiteA using a 7945

Third one is a local call made from SiteC that did go through using another 7945 phone

Steven Smith Wed, 11/25/2009 - 10:20
User Badges:
  • Gold, 750 points or more

I have looked at the calls, and it appears that the not working call is not able to make a 10 digit call. 


In the config, I do not see the phones you mentioned.  Is this the newest config?  I only see one CIPC phone.  No 7945's.  The problem could be a corlist problem, but from the config I have, I don't see how that would matter.

Yeah might have trimmed the config file a little bit too much.

Here's the file with the phones in it.


If I may add, on the phone that works, if we dial 98195551212 the phone will trim the 9 and display 8195551212 when dialing.

On the non-working phone, if we dial 98195551212, the phone will trim the last three digit. We found out that when that happens, we can enter the last 3 digits while dialing and it works...

Attachment: 
Correct Answer
Steven Smith Wed, 11/25/2009 - 14:09
User Badges:
  • Gold, 750 points or more

Here is what I can say that is happening.  On the call that is not working, it isn't matching dialpeer 61, only dialpeer 60.  61 does the 10 digit dialing.  60 is 7 digit dialing.  It should match both until you enter the 8th digit.  On the failing call, it matches dialpeer 60, and will display 7 digits on the phone, and send the call to the PSTN.  You can enter the other 3 digits because the telco is waiting for more digits for the call to complete.


One thing you could try would be to delete the 7 digit dialing.  I was thinking that this might be a corlist problem, but it doesn't appear so.  If removing the 7 digit dialing doesn't work (and I really don't expect it to), I would recommend opening a tac case.  This appears to be a bug.





Shame on me for not deleting that 7-digits dialing rule. We have to dial the area code anyway in our province so the 7-digits never applies...

I'm not on site right now so I cannot test it out but I've delete the rule anyway.


Will post the results tomorrow.


Thank you so much, I really think this will solve our issue!




Matt

Actions

This Discussion

Related Content