Please verify my POTS dial-peers

[voip7372]

This should be simple, but I just want to be sure I have it correct before doing this.  In this example (for the USA), CUCM will not send the leading 9 to the router/gateway.  9-1-858-555-1212 dialed by the user would result in 1-858-555-1212 being sent to the router.  I will strip off the 9 and only send the number the phone company wants to see to the router and the router should then forward those digits on to the phone company via the ISDN PRI circuit.

This is for 10 digit local calls and I want to send the 10 digits to the phone company:

dial-peer voice 13 pots

 trunkgroup LOCAL-ISDN-PRI

 description LOCAL 10 DIGIT CALLS

 destination-pattern [2-9]..[2-9]......

forward-digits 10

This is for 11 digit long distance calls and I want to send the 11 digits to the phone company:

dial-peer voice 14 pots

 trunkgroup LOCAL-ISDN-PRI

 description LD CALLS

 destination-pattern 1[2-9]..[2-9]......

 forward-digits 11

This is for international calls and I want to send 011 plus the rest of the digits the user dialed to the phone company:

dial-peer voice 15 pots

 trunkgroup LOCAL-ISDN-PRI

 description INTL CALLS

 destination-pattern 011T

 prefix 011

This is for 911 emergency calls and I want to send the 3 digits to the phone company:

dial-peer voice 16 pots

 trunkgroup LOCAL-ISDN-PRI

 description 911 CALLS

 destination-pattern 911

 forward-digits 3

[Chris Deren]

My preference is not to strip the leading 9 on CUCM, and instead let the GW strip it. Keep in mind that POTS dial-peers strip all leading explicitly matched digits, so there is no need for translation, for example 1[2-9]..[2-9]..... would automatically strip 1, and one way around it is the forward-digits command. I would adjust the dial peers as following:

This is for 10 digit local calls and I want to send the 10 digits to the phone company:

dial-peer voice 13 pots

 destination-pattern 9[2-9]..[2-9]......

forward-digits 10

This is for 11 digit long distance calls and I want to send the 11 digits to the phone company:

dial-peer voice 14 pots

 destination-pattern 91[2-9]..[2-9]......

 forward-digits 11

This is for international calls and I want to send 011 plus the rest of the digits the user dialed to the phone company:

dial-peer voice 15 pots

 destination-pattern 9011T

 prefix 011

This is for 911 emergency calls and I want to send the 3 digits to the phone company:

dial-peer voice 16 pots

 destination-pattern 911

 forward-digits 3

Your way will work too, but may create conflicts with inbound calls that need to be directed to CUCM.

[voip7372]

We currently have it setup to send the 9 to the router and my existing POTS dial-peers are shown below.  Now that you mention it, I'm starting to remember...maybe the tech that helped me with the first install suggested we let the 9 go to the router from CUCM because that makes the SRST setup easier...I.E. use the same dial-peers for CUCM calls coming to the router or from phones locally registered to the router during a SRST situation, does that sound right?

I was thinking about changing it to not send the 9 to the router/gateway because we don't send the outside dialing prefix to the gateways on another CUCM setup we have in another country and I was thinking about emulating that.  BUT...if you agree that sending the 9 to the router is a very logical and proper way to do it for various reasons (please briefly list the reasons if you have a moment :-))....then I'll leave it as is (sending 9 to the router) and make some notes for future reference to explain why it's configured that way.

My existing dial-peers below:

dial-peer voice 13 pots

 trunkgroup LOCAL-ISDN-PRI

 description LOCAL 10 DIGIT CALLS

 destination-pattern 9[2-9]..[2-9]......

!

dial-peer voice 14 pots

 trunkgroup LOCAL-ISDN-PRI

 description LD CALLS

 destination-pattern 91[2-9]..[2-9]......

 forward-digits 11

!

dial-peer voice 15 pots

 trunkgroup LOCAL-ISDN-PRI

 description INTL CALLS

 destination-pattern 9011T

 prefix 011

!

dial-peer voice 16 pots

 trunkgroup LOCAL-ISDN-PRI

 description 911 CALLS

 destination-pattern 911

 forward-digits 3

!

dial-peer voice 17 pots

 trunkgroup LOCAL-ISDN-PRI

 description 911 CALLS WITH EXTRA 9

 destination-pattern 9911

 forward-digits 3

[Chris Deren · Accepted solution]

" because that makes the SRST setup easier...I.E. use the same dial-peers for CUCM calls coming to the router or from phones locally registered to the router during a SRST situation, does that sound right?"

Yes, this is another reason to keep the 9, otherwise SRST users would need to dial it without 9.

I was thinking about changing it to not send the 9 to the router/gateway because we don't send the outside dialing prefix to the gateways on another CUCM setup we have in another country and I was thinking about emulating that.  BUT...if you agree that sending the 9 to the router is a very logical and proper way to do it for various reasons (please briefly list the reasons if you have a moment :-))....then I'll leave it as is (sending 9 to the router) and make some notes for future reference to explain why it's configured that way.

Yes, I definitely recommend keeping the 9. You may want to review other locations if those are also SRST GWs as you will have confused users when dialing in SRST.

HTH, please rate all useful posts!

Chris

[voip7372]

Ok, thanks.  I'll leave it as is then.  

The other sites I mentioned are on a totally separate cluster in other countries.  My plan going forward is to have all US sites (as well as all sites in the Americas that will be registered to the cluster in the US) setup similar to what we're talking about here...where the outside access code (9 or whatever it happens to be) is sent to the router from CUCM during normal operation and during SRST, the users would continue with the same dialing habits as if nothing had changed (CUCM controlling the phones or SRST/router controlling the phones - same dialing habits apply).

[Deepak Rawat]

same dialing habits: That says every thing, user experience should be the same whether the phones are connected to CM or not.

Regards

Deepak

[Deepak Rawat]

I completely agree with Chris on this and would let the stripping task with GW itself rather than doing it on CM that makes it slightly easier from an admin perspective (choice is yours). Adding to what Chris already had said, your way of doing it will also work

I personally prefer forward-digits all or no digit-strip command to send all the numbers out rather than defining 10, 11

For 9011T pattern, you will definitely need to use prefix command as others will not serve the purpose.

Different ways to do it, outcome is same so just go ahead with what you feel comfortable and used to doing and it will work.

Regards

Deepak

[voip7372]

Thanks.   Please see my reply to Chris and feel free to provide your feedback as well :-)