Mapping Phone Extension to FXO port -- CME Outbound Call

[apmorgan]

I have a 1751-V with CME and 2 port fxo with 2 pots.

On a 7960 with 2 extensions I would like to be able to map all outbound calls from extension 1 to fxo port #1 and ext2 to fxo#2.

As per: http://www.cisco.com/en/US/partner/tech/tk652/tk90/technologies_configuration_example09186a00801bc341.shtml

I tried this, but doesn't seem to work.

voice translation-rule 2

rule 1 /^/ /2/

!

voice translation-rule 3

rule 1 /^/ /3/

!

!

voice translation-profile Line2

translate called 3

!

voice translation-profile Line1

translate called 2

dial-peer voice 22 pots

destination-pattern 2T

port 2/1

forward-digits all

prefix 1

!

dial-peer voice 23 pots

destination-pattern 3T

port 2/0

forward-digits all

prefix 1

!

dial-peer voice 1 voip

translation-profile incoming Line3

answer-address 3003

!

dial-peer voice 2 voip

translation-profile incoming Line2

answer-address 2002

[anup.anand]

For CME phones, the translations need to be applied on the ephone-dn's corresponding to the phone lines using the translate called command

ephone-dn 1

translate called 10

Also, CME does not support voice translation-profile commands. You need to use the old "translation-rule" commands.

Regards,

Anup

[apmorgan]

Thanks for the reply.

I tried this:

voice translation-rule 2

rule 1 /^/ /2/

!

voice translation-rule 3

rule 1 /^/ /3/

dial-peer voice 22 pots

destination-pattern 2T

port 2/1

forward-digits all

prefix 1

!

dial-peer voice 23 pots

destination-pattern 3T

port 2/0

forward-digits all

prefix 1

ephone-dn 1

number 2002

translate called 2

!

!

ephone-dn 2

number 3003

translate called 3

but it still doesn't work.

Only calls started with a 2 or a 3 work.I hoped that my translation rule would prepend a 2 or 3 to any dial string and then match dial-peer destination pattern which in turn would forward to a FXO port.

[anup.anand]

Try these translation commands

translation-rule 2

Rule 1 ^% 2

translation-rule 3

Rule 1 ^% 3

[dmenkel]

It seems that the extension is not being mapped to the ports. The doc you referred to states:

Configuring the H323 Gateway Inbound dial-peers.

An incoming dial-peer in the gateway will accept an outgoing call from the Cisco IP Phone.

Thought it say's inbound it is still referring to an outbound call from the DN.

Unless I missed something you will need to add:

dial-peer voice 1 voip

translation-profile incoming Phone1

answer-address 8378

!--- A call from Cisco IP Phone 8378 will match this dial-peer.

!--- The answer-address matches the ANI of the calling party, which triggers the

!--- translation-profile Phone1. This profile then prefixes a "1" onto the destination

!--- pattern so that the call can be sent out a specific FXS port.

[apmorgan]

Almost working...

It seems like destination-pattern 2T is not stripping the 2, so 9175551212 is being dialed as 29175551212, at least according to debug voice dialpeer.

To test I changed forward-digits all to forward-digits 10 and calls work because it takes right most 10 digits.

digit-strip is enabled on dial-peer.

Any ideas on why "2" remains in dialout number?

Thanks for your help

Andrew

[patsbc]

This is kind of tricky, and I've wanted to do something similiar. I think your voice translation-rules are mangled (or they are not being posted correctly by the forum). You are substituting all digits for the number 2, or the number 3 in your translation rules, versus adding the required correct digits.

This should take all digits and append the prefix correctly. Try this instead:

voice translation-rule 2

rule 1 /^\(.*\)/ /2\1/

voice translation-rule 3

rule 1 /^\(.*\)/ /3\1/

Let me know if you get it working. Have a good one.

Pat

[rcfoltz]

You can also use Class Of Restriction CoR for this. For example:

dial-peer cor custom

name port100

name port101

dial-peer cor list use100

member port100

dial-peer cor list use101

member port101

dial-peer voice 100 pots

port 1/0/0

corlist outgoing use100

destination-pattern 9T

dial-peer voice 101 pots

port 1/0/1

corlist outgoing use101

destination-pattern 9T

dial-peer voice 10 voip

answer-address 3000

corlist incoming use100

dial-peer voice 20 voip

answer-address 3001

corlist incoming use101

!

Now extension 3000 will use only port 1/0/0 and Extension 3001 will use 1/0/1. I'm lazy and I dont like messing with translations so this is the way I would take care of this issue.

[apmorgan]

Thanks -- implementation with COR is getting the job done.