10-15-2006 04:52 AM - edited 03-13-2019 03:24 PM
Hi,
my service provider added me additional phone numbers to my E1 line (DID).
but they begin with different digits.
My fiest number plan is: 2232195.., SP added me 10 phone nmbers beginig with 2234674.., ho wshould I configure CME to handle it?
Like you can see, some internal numbers starts with 5.. and some with 4.., when calling internaly it is not a problem.
When I have added:
dialplan-pattern 2 2234674.. extension-length 3 extension-pattern 4..
CME stopped to work with my first dialplan-pattern which is:
dialplan-pattern 1 2232195.. extension-length 3 extension-pattern 5..
any suggestions?
regards
Slawek
10-15-2006 12:20 PM
Can you please post your configuration?
Chris
10-16-2006 07:40 AM
Hi,
my config looks like:
voip-incoming translation-rule called 1
translation-rule 1
Rule 1 ^2232195 5
Rule 2 ^2234674 4
translation-rule 11
Rule 1 ^0 00
dial-peer voice 10 pots
incoming called-number 223319...
direct-inward-dial
dial-peer voice 100 pots
destination-pattern 0T
translate-outgoing called 11
port 0/0/0:15
telephony-service
load 7912 P00307020200
max-ephones 48
max-dn 96
ip source-address 10.48.4.1 port 2000
system message CISCO powered by InfoLAN
url services http://10.48.4.2/voiceview/common/login.do
url authentication http://10.48.4.2/voiceview/authentication/authenticate.do
time-format 24
date-format dd-mm-yy
create cnf-files version-stamp 7960 Oct 14 2006 16:45:08
dialplan-pattern 1 2232195.. extension-length 3 extension-pattern 5..
voicemail 2369
max-conferences 8 gain -6
dn-webedit
time-webedit
what to do to make work both dial-plans?
regards
Slawek
10-16-2006 08:03 AM
Well, you have only one inbound pots dial-peer defined (dial-peer 10), which will only match 223319... numbers, in order to match the 2234674.. numbers as well you have couple of options:
1. change dial-peer 10 to the following
dial-peer voice 10 pots
incoming called-number .
direct-inward-dial
port 0/0/0:15
2. Add another dial-peer
dial-peer voice 10 pots
incoming called-number 2234674..
direct-inward-dial
port 0/0/0:15
And add the 2 dialplan pattern under telephony-service.
Also, I'm not sure what the translation rule 1 is for, but it's not applied to anything.
HTH,
Chris
10-18-2006 09:34 AM
Hi,
I have added another dial-peer
dial-peer voice 11 pots
incoming called-number 2234674..
direct-inward-dial
port 0/0/0:15
in dial-peer voice 10 I have added line:
port 0/0/0:15
then in telephony-service:
dialplan-pattern 2 2234674.. extension-length 3 extension-pattern 4..
After that, my 2nd dialplan is working, 1st is not working :-(
Why?
regards
Slawek
10-18-2006 12:02 PM
What does your "debug isdn q931" show?
What happens if you change the "incoming called number ."
Chris
10-19-2006 01:21 AM
but when I change to "incoming called-number ." should I also add dialplan-pattern?
Slawek
10-19-2006 03:47 AM
I have just change (only this) "incoming called-number 2232195.." to "incoming called-number .", now I can dial this numbers (form public), but cannot dial 2234674.. numbers :-(
Do I have to reload CME or sth?
Slawek
10-19-2006 04:18 AM
Can you post your entire config, and "debug isdn q931" for both calls?
10-19-2006 05:06 AM
10-19-2006 06:47 AM
Slawek,
I looked at your configuration and there are couple of things:
1. The voip-incoming translation-rule 1, is a global translation-rule that will apply to all incoming voip dial-peers, not sure why you need it?
2. I noticed that you have only one ephone-dn, When you perform your testing do you change it back and forth, same with your FXS ports?
Besides the isdn q931 debugs another one to try is "debug voice dialpeer" and "debug voice translation"
Chris
10-19-2006 04:21 AM
Slawek,
I do not see any voip dialpeers in your config. I have the similar with one of my sites and here is an extract of my config:
dial-peer voice 101 pots
incoming called-number
direct-inward-dial
!
dial-peer voice 102 pots
incoming called-number
direct-inward-dial
!
dial-peer voice 1001 voip
destination-pattern
session protocol sipv2
session target ipv4:
incoming called-number
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 1002 voip
destination-pattern
session protocol sipv2
session target ipv4:
incoming called-number
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
telephony-service
dialplan-pattern 1
dialplan-pattern 2
I also had the second DID range come in on another PRI, which is why I also had to add custom cor lists but in your case this is not needed.
Hope it helps,
Leo
10-19-2006 04:51 AM
You do not need any voip dialpeers if the CME is on the same router as the PRIs.
Chris
10-19-2006 06:13 AM
Chris,
If combined with CUE like Slavek and I do there is a need to create the Voip dialpeers for voice mail to work. You will see this in his config as well:
dial-peer voice 1 voip
translation-profile outgoing 1
destination-pattern 2...
session protocol sipv2
session target ipv4:10.48.4.2
dtmf-relay sip-notify
codec g711ulaw
no vad
All Slawek needs to do IMHO is adding the following:
dial-peer voice 2 voip
translation-profile outgoing 1
destination-pattern 4...
session protocol sipv2
session target ipv4:10.48.4.2
dtmf-relay sip-notify
codec g711ulaw
no vad
Leo
10-19-2006 06:36 AM
Leo,
I appologize for not reading your entire post.
I was only concentrating on his issue which is that calls do not get delivered to the phones.
You are correct that you require the dial-peers to re-direct to CUE.
Chris
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide