cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
562
Views
5
Helpful
9
Replies

Configure Router to default to answering service.

carbonscoring
Level 1
Level 1

Hi All, I have a single site deployment with one 2821 gateway and one callmanager. We have an answering service that we use to take calls after hours. I've been given the task to see if I can set the router to default to the answeing service if our callmanager goes down. Is there a way I can configure this on the router? Thanks for the help

equipment info:

Cisco 2821

IOS version (C2800NM-SPSERVICESK9-M), Version 12.4(22)T

1 PRI threw timewarner

Callmanager system version 6.1.2.1002-1

9 Replies 9

If you're using H323:

translation-rule 1

rule 1 /.*/ /5551234/ <-- 5551234 is the number of your answering service

translation-profile 1

translate called 1

dial-peer voice 1 voip

destination-pattern 5... <-- for example we're saying your DNs are the 5XXX range.

preference 0 <--default

dial-peer voice 2 pots

destination-pattern 5...

translation-profile outgoing 1

preference 1

port 0/0/0:23

MGCP:

Well, it would look the same, except you wouldn't have dial-peer 1. You might if you're using fallback.

So it would be:

ccm fallback-mgcp

translation-rule 1

rule 1 /.*/ /5551234/ <-- 5551234 is the number of your answering service

translation-profile 1

translate called 1

dial-peer voice 2 pots

destination-pattern 5...

translation-profile outgoing 1

preference 1

port 0/0/0:23

Does this make sense?

hth,

nick

Hi Nick I already have to two dial-peers in my gateway:

dial-peer voice 9999999 pots

destination-pattern 9T

direct-inward-dial

port 0/0/0:23

!

dial-peer voice 9994900 voip

description H.323 routing to CM

destination-pattern 49..

session target ipv4:192.168.103.10

do I still need to add your dial-peers or just the translation pattern?

thanks for the help,

Mike

Hi Mike,

Yes you're using H323. So you would follow the example of the first one.

You would make a secondary pots dial peer with the destination-pattern of 49.. and a preference of 1 or higher, with the translation pattern.

hth,

nick

Hi Nick,

Here is what I inputed into the router:

voice translation-rule 1

rule 1 /.*/ /5551234/

!

!

voice translation-profile 1

translate called 1

dial-peer voice 2 pots

translation-profile outgoing 1

preference 1

destination-pattern 49..

port 0/0/0:23

!

dial-peer voice 3 pots

translation-profile outgoing 1

preference 1

destination-pattern 6040

port 0/0/0:23

The translation works great I first tested it to my extension and I had it call my cell phone and it worked. However, when I enabled for all extensions "49.." and did a "shut" on the switch port for our callmanager and called our office numbers It does not go threw. If I change the prefence to zero it works however, once I enable the switchport for callmanager it still forwards to translation number and does not revert to sending calls to our callmanager?

What am I missing?

thanks for your help,

Mike

Hi Mike,

I think your voip dial peer isn't going into the down state when CCM isn't reachable.

You can add this to your CCM voip dial peer so that it pings CCM to maintain that the dial peer is still valid:

nicmatth-sip(config-dial-peer)#monitor probe icmp-ping 1.1.1.1

Keep the preferences like I had mentioned, just add this to your voip dial peer.

'show dial-peer voice summary' should show the "Out Status" of the dial peer as up/down, depending on the reachability.

hth,

nick

Hi Nick, thanks for the help thus far. I did as you reccommended however, when I dial in I still get a fast busy. If I do a "sh vo call sum" I see the call comming into the router:

But then it looks like it gets dropped, here is part of my config starting with my voice port maybe you can see something that I'm missing:

voice-port 0/0/0:23

!

ccm-manager fallback-mgcp

ccm-manager mgcp

no ccm-manager fax protocol cisco

ccm-manager music-on-hold

ccm-manager config server 192.168.103.10

ccm-manager config

!

mgcp

mgcp call-agent 192.168.103.10 2427 service-type mgcp version 0.1

mgcp dtmf-relay voip codec all mode out-of-band

mgcp rtp unreachable timeout 1000 action notify

mgcp modem passthrough voip mode nse

mgcp package-capability rtp-package

no mgcp package-capability res-package

mgcp package-capability sst-package

no mgcp package-capability fxr-package

mgcp package-capability pre-package

no mgcp timer receive-rtcp

mgcp sdp simple

mgcp fax t38 inhibit

mgcp rtp payload-type g726r16 static

!

mgcp profile default

!

!

dial-peer cor custom

!

!

!

dial-peer voice 9999999 pots

destination-pattern 9T

direct-inward-dial

port 0/0/0:23

!

dial-peer voice 9994900 voip

description H.323 routing to CM

destination-pattern 49..

monitor probe icmp-ping 192.168.103.10

session target ipv4:192.168.103.10

!

dial-peer voice 9994988 voip

description SIP Fax for 4988

answer-address 5205551234

destination-pattern 4988

session protocol sipv2

session target ipv4:192.168.100.16

session transport udp

dtmf-relay h245-signal

codec g711ulaw

fax rate 14400

fax protocol t38 ls-redundancy 5 hs-redundancy 2 fallback pass-through g711ulaw

clid network-number 5205551234

no vad

!

dial-peer voice 9990911 pots

destination-pattern 911

port 0/0/0:23

forward-digits all

!

dial-peer voice 9999911 pots

destination-pattern 9911

port 0/0/0:23

forward-digits 3

!

dial-peer voice 9996040 voip

destination-pattern 6040

session target ipv4:192.168.103.10

!

dial-peer voice 9994984 voip

description SIP Fax for 4984

answer-address 5205554321

destination-pattern 4984

session protocol sipv2

session target ipv4:192.168.100.17

session transport udp

dtmf-relay h245-signal

codec g711ulaw

fax rate 14400

fax protocol t38 ls-redundancy 5 hs-redundancy 2 fallback pass-through g711ulaw

clid network-number 5205554321

no vad

!

dial-peer voice 2 pots

translation-profile outgoing 1

preference 1

destination-pattern 49..

port 0/0/0:23

!

dial-peer voice 3 pots

translation-profile outgoing 1

preference 1

destination-pattern 6040

port 0/0/0:23

!

!

!

call-manager-fallback

max-conferences 8 gain -6

transfer-system full-consult

ip source-address 192.168.103.1 port 2000

max-ephones 52

max-dn 192

system message primary Phone System in local mode

default-destination 4985

thanks for you help,

Mike

Hi Mike,

What we're really interested in is whether the 'show dial-peer voice summary' shows that dial-peer 9994900 has a 'down' 'Out Status' when you shut the port. It may take a while for the monitor to take effect.

Other than that, dial peers seem to be in order.

-nick

Hi Nick, thanks for helping me out thus far. I did some more testing tonight and after I shut down the switchport for out callmanager and issue the show dial peer voice summary this is the output it shows me:

Core-2821#sh dial-peer vo sum

dial-peer hunt 0

AD PRE PASS OUT

TAG TYPE MIN OPER PREFIX DEST-PATTERN FER THRU SESS-TARGET STAT PORT

99999- pots up up 9T 0 up 0/0/0:23

99

99949- voip up up 49.. 0 syst ipv4:192.168.103.10

00

99949- voip up up 4988 0 syst ipv4:192.168.100.16

88

99909- pots up up 911 0 up 0/0/0:23

11

99999- pots up up 9911 0 up 0/0/0:23

11

99960- voip up up 6040 0 syst ipv4:192.168.103.10

40

99949- voip up up 4984 0 syst ipv4:192.168.100.17

84

20001 pots up up 4988$ 0 50/0/1

20002 pots up down 0 50/0/2

I kept the switchport down for about 12-15 minutes and I could never get the router to forward the call to my cell phone.

Any other suggestions?

thanks,

Mike

Hi, Im attaching a text file with the output command thats a little more readable.

thanks,

Mike

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: