11-18-2004 02:25 PM - edited 03-13-2019 07:04 AM
I have a site that is in a 7-digit dial area, but *apparently* the LEC want us to send them 10 digits. I know how do this in CallManager, but how do I set this up for SRST? My current dial-peer is configured this way:
dial-peer voice 1 pots
description SRST Primary Dial Peer
preference 1
application default
destination-pattern 9T
incoming called-number .
direct-inward-dial
port 4/0:23
I'm running 12.3T and was thinking of using the prefix command, but I'm concerned that it'll apply to inbound calls as well, and the docs I've read don't really say...
TIA,
Jeff
11-18-2004 03:43 PM
You can use the prefix command on the pots dial-peer and this will affect only outbound calls. Inbound calls will not be affected by the prefix command.
11-19-2004 07:47 AM
Thanks. Another potential problem occured to me last night... can I exclude 911 from the prefix?
Jeff
11-19-2004 08:27 AM
Hi,
Create a separate dial-peer for 911 and 411 calls.
For example:
Dial-peer voice 3 pots
destination-pattern 9[4,9]11
no digit-strip
direct-inward-dial
port 1/0:23
forward-digits 3
11-23-2004 10:49 AM
Thanks for the replies... I ran into yet another snag when trying this: LD (I didn't want the local area code prefixed on those calls). Finally gave up the whole concept and was going to tell the users to just dial the full 10 digits when in SRST, but it works with 7 in SRST with my original dial-peer. It doesn't when it's registered with CCM, but it does as a stand-alone. Any ideas what's going on?
Jeff
11-23-2004 11:32 AM
Try to add a RP in your call manager with a filter for 7 digit dial.
11-23-2004 08:13 PM
You should probably setup different dialpeers for each unique pattern. This also gets around the inter-digit timeout issues. Following would be a good starting point:
dial-peer voice 1000 pots
application mgcpapp
incoming called-number .
direct-inward-dial
port 1/0:23
dial-peer voice 9000 pots
corlist outgoing 911-R
destination-pattern 911
port 1/0:23
forward-digits 3
dial-peer voice 9001 pots
corlist outgoing 911-R
destination-pattern 9911
port 1/0:23
forward-digits 3
dial-peer voice 9002 pots
corlist outgoing Local-R
destination-pattern 9[2-9]......
port 1/0:23
forward-digits 7
dial-peer voice 9003 pots
corlist outgoing LD-R
destination-pattern 91[2-9]..[2-9]......
port 1/0:23
forward-digits 10
dial-peer voice 9004 pots
corlist outgoing Intl-R
destination-pattern 9011T
port 1/0:23
prefix 011
***********
To address the issue of adding the area code, you could probably do it a couple ways. You might be able to just do a 'prefix
voice translation-rule 1
rule 1 /^92/ /5552/
rule 2 /^93/ /5553/
rule 3 /^94/ /5554/
rule 4 /^95/ /5555/
rule 5 /^96/ /5556/
rule 6 /^97/ /5557/
rule 7 /^98/ /5558/
rule 8 /^99/ /5559/
voice translation-profile Prefix555_SRST
translate called 1
dial-peer voice 9002 pots
destination-pattern 9[2-9]......
port 1/0:23
translation-profile out Prefix555_SRST
Good luck,
Vance
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