Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Translation Rule?

I've a cisco 1760 router with 6 FXO cards. One of the incoming POT line is connected to one of these card and is designated for 911 call. The problem is that when incoming call is hitting this voice port 1/1 (and 2/1) as it's part of the hunt group, the display on the user's 7940 phone is shown as "911" instead of the actual number of the caller. There's no translation rule anywhere in our router config, and yet it seems to do the translation anyway...

Has anyone encounter this before? I'd like to setup a translation rule to allow incoming to remain as is without being translated..

Current config:

voice-port 1/0

echo-cancel coverage 24

no comfort-noise

connection plar 3113

!

voice-port 1/1

echo-cancel coverage 24

no comfort-noise

connection plar 3113

!

voice-port 2/0

echo-cancel coverage 24

no comfort-noise

connection plar 3102

!

voice-port 2/1

echo-cancel coverage 24

no comfort-noise

connection plar 3102

!

voice-port 3/0

echo-cancel coverage 24

no comfort-noise

connection plar 3102

!

voice-port 3/1

echo-cancel coverage 24

no comfort-noise

connection plar 3102

mgcp profile default

!

dial-peer cor custom

!

!

!

dial-peer voice 1 voip

destination-pattern 3113

progress_ind setup enable 3

session target ipv4:192.168.30.2

dtmf-relay h245-alphanumeric

codec g711ulaw

ip qos dscp cs5 media

no vad

!

dial-peer voice 2 voip

preference 1

destination-pattern 3113

progress_ind setup enable 3

session target ipv4:192.168.25.4

dtmf-relay h245-alphanumeric

codec g711ulaw

ip qos dscp cs5 media

no vad

!

dial-peer voice 3 voip

destination-pattern 3102

progress_ind setup enable 3

session target ipv4:192.168.30.2

dtmf-relay h245-alphanumeric

codec g711ulaw

ip qos dscp cs5 media

no vad

!

dial-peer voice 4 voip

preference 1

destination-pattern 3102

progress_ind setup enable 3

session target ipv4:192.168.25.4

dtmf-relay h245-alphanumeric

codec g711ulaw

ip qos dscp cs5 media

no vad

!

dial-peer voice 5 pots

preference 1

destination-pattern .T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 2/0

!

dial-peer voice 6 pots

preference 1

destination-pattern .T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 2/1

!

dial-peer voice 7 pots

preference 1

destination-pattern 911

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 2/1

prefix 911

!

dial-peer voice 8 pots

preference 1

destination-pattern .T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 3/0

!

dial-peer voice 9 pots

preference 1

destination-pattern .T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 3/1

!

dial-peer voice 10 pots

preference 1

destination-pattern 911

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 1/1

prefix 911

!

dial-peer voice 11 pots

preference 1

destination-pattern .T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 1/0

!

dial-peer voice 12 pots

preference 1

destination-pattern .T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 1/1

Will this translation rule help?

Voice translation-rule-NoTransation

rule 1 /^$/ // NULL NULL

Any input is greatly appreciated.

Thanks!

Hieu

2 REPLIES

Re: Translation Rule?

Hieu,

This is a very common problem, possibly because of the way the router matches an incoming call leg. It looks at incoming-called number, answer-address or destination-pattern command to match an inbound leg. I would recommend you to put the following dial-peer (as your first pots dial-peer - This would mean you will have to remove all pots dial-peers and reconfigure the dial-peers with the following dial-peer first in the list. You can simply cut and paste from your existing configs)

dial-peer voice 20 pots

incoming called-number .

dial-peer voice 5 pots

preference 1

destination-pattern .T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 2/0

!

dial-peer voice 6 pots

preference 1

destination-pattern .T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 2/1

!

dial-peer voice 7 pots

preference 1

destination-pattern 911

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 2/1

prefix 911

!

dial-peer voice 8 pots

preference 1

destination-pattern .T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 3/0

!

dial-peer voice 9 pots

preference 1

destination-pattern .T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 3/1

!

dial-peer voice 10 pots

preference 1

destination-pattern 911

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 1/1

prefix 911

!

dial-peer voice 11 pots

preference 1

destination-pattern .T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 1/0

!

dial-peer voice 12 pots

preference 1

destination-pattern .T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 1/1

New Member

Re: Translation Rule?

Thanks Sankar for your response.

I missed to mention that voice ports 1/0 and 1/1 are in one hunt group, and voice ports 2/0,2/1,3/0,3/1 are in a different hunt group. So incoming calls are received from 2 different pubished number.

If I use the commands you suggested, will it affect both hunt groups such that incoming calls are still allowed for voice ports 1/1 and 2/1 but they'll not be translated to "911" on the display?

Greatly appreciated your input.

Hieu

127
Views
0
Helpful
2
Replies
CreatePlease to create content