01-27-2014 09:36 AM - edited 03-16-2019 09:27 PM
So we ran out of DID's in our current range. We ordered some new ones and we will get the via our telco tomorrow. It seems they add them to the PRI on there side. My question is how do I get them into our cisico voip setup to work for our users? we are going from a 55xx range to adding a 89XX and 44XX range.
We are running cucm 8.6 and have a Cisco R2901 switch.
01-27-2014 10:07 AM
If using H323/SIP, add the dial peers to match those DIDs and send calls to CUCM
Also make sure the inbound CSS is correct in CUCM
For MGCP, just adjust the inbound CSS
Then you can start using those DIDs within CUCM
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk
01-27-2014 10:13 AM
Thanks for the quick response. Is there a guide for me to do each of these parts? We are using H323 as far as I know.
01-27-2014 10:17 AM
No, no guides. There are config guides for each bit, but they assume you know how to tie them together.
You can look at your current config for the DPs and just copy them, adjust the destination pattern as required
You might have one DP with 55.., add one with 89.. and another one with 44..
Those are just examples, adjust as necessary, if you happen to have one with ...., then it would work with all the other DID ranges.
For the inbound CSS from CUCM, you need to know whether it requires adjustment, or not. Based on your dial plan.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk
01-27-2014 10:22 AM
By DP you mean device pool? Is that under system -> device pool? Or do you mean Device Profile Configuration? That is specific tot he user though isint it? There is no range to add the new DID's into.
01-27-2014 10:24 AM
Dial-peer, in the GW. You should ask your voice network admin to do this.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk
01-27-2014 10:26 AM
unfortunatly that will be me on this project. We are a small company. So all the work will be done on the voice gateway it seems?
01-27-2014 10:29 AM
Assuming your inbound CSS in CUCM is correct, yes.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk
01-27-2014 10:31 AM
dial-peer voice 10 voip
destination-pattern 5..$
session target ipv4:10.0.1.100
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 11 voip
destination-pattern 7149105[57]..$
session target ipv4:10.0.1.100
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 12 voip
destination-pattern 71491057..$
session target ipv4:10.0.1.100
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
So basically I can use the references above and just create a dial-peer voice 13 and 14? and change the pattern?
01-27-2014 11:10 AM
Yes, no idea why you have all those DPs, I assume 10.0.1.100 is your CUCM.
You usually just match the number of digits telco will send at all times, and not have a 10 digit DP and 3 digit DP at the same time.
Also, 11 does almost the same thing as 12, it matches 5 or 7, when you already have one to match 7???
I have no idea why you have this, and how it works in your system without looking at all your config.
Call telco, ask them how many digits they will be sending for those DIDs.
Then adjust the destination pattern from this one as necessary.
dial-peer voice 10 voip
destination-pattern 5..$
session target ipv4:10.0.1.100
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
Change the DP number to something that does not exists already.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk
01-27-2014 11:20 AM
I cannot speak for why they are setup that way. I didnt create them. So you think I should use dial plan 10 as the example to file? I know our carrier is sending 10 digits.
So would it look something like
dial-peer voice 13 voip
destination-pattern 4..$
session target ipv4:10.0.1.100
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 14 voip
destination-pattern 8..$
session target ipv4:10.0.1.100
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
Or would I be better off using the others?
dial-peer voice 13 voip
destination-pattern 71485089..$
session target ipv4:10.0.1.100
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 14 voip
destination-pattern 71485044..$
session target ipv4:10.0.1.100
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
01-27-2014 11:23 AM
If you expect 10 digits, then you need to use the latter ones, that will match 10 digits.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk
01-27-2014 11:24 AM
Gotcha. Thanks for the help. Is there anything I should check in CUCM to make sure is matching? or will the GW changes be all that i need to do?
01-29-2014 08:27 AM
Jaime. Are you good with the voice gateway? below is the last 4 digits to the ranges I am adding. the first 3 digits are the same on all the ranges of 754. Currently the rules are as above. Is there a blanket config I can do for either all the ranges below. or do I need to create 3?
4300 to 4499
8960 to 8979
For example will
destination-pattern 714457....$
work for the whole range of 457? Or am i better off breaking up the DID's in chunks of 100?
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