Plar or Translation Pattern for all incoming Calls?

[dmeersman]

                  I am setting up a remote location that is in a different area code than the main site.  I need to have all incoming calls on PRI get forwarded to an internal DN on CUCM.  Should I just use a translation pattern on CUCM or setup a connection PLAR on the router and then a H323 dial peer forwarding to that destination? 

Thanks,

[Jason Lee]

You may have to ellaborate a little more if I get the setup wrong...

I'm assuming you have a voice gateway at the remote location and it will be connected via H.323 to the CUCM as an H.323 gateway.  In this case you can just set up a dial-peer on the H.323 gateway directing the calls in by destination to the CUCM.  You may want to, one with a lower pref to a secondary CUCM for redundancy. 

You can identify the destination numbers being provided by the PSTN provider by making calls in with the "debug isdn q931" debug running.  That will provide information on the call in including the internal destination.  Most likely, they are already stripping digits off the destination to some degree.  Match your dialpeer on whatever is being provided. 

When you add the H.323 gateway in CUCM there is a significant digits field.  Set that to the number of digits you have on your internal DNs.  For example if you have an 4 digit internal dialplan, set that field to 4.  It strips off everything from the dialed number except for the last 4 digits on the right. 

That's the easiest way to chop it down.

If you want, you could use MGCP as well.  That will prevent you from having to configure dialpeers.  In that case the CUCM will terminate the call directly and strip. 

HTH,

Jason

[Andrey Chertolyas]

You can do something like this:

dial-peer voice 1 pots

! incoming calls

translation-profile incoming INCOMING ! translate incoming calls to cucm dialplan

incoming called-number .

direct-inward-dial

port 0/1/0:15

!

dial-peer voice 100 voip

destination-pattern 1...$ ! cucm dialplan

session target ipv4:10.10.10.10 ! CUCM address

Kind regards,
Andrew C.

[jfernandorosa]

Hi Andrew,

Please, post the your translation rule incoming.

Do you can use the num-exp for this, and not necessary create the translations and dial-peer matching.

Ex:

num-exp 2...$ 1...

Is a global translation to outbound calls and first match, after this translate, call match in your dial-peer 100 to CUCM.

Regards,

J Rosa.

Please rate helpful answers!

[Andrey Chertolyas]

Hi J,

voice translation-rule 1

rule 1 /^46\(3...$\)/ /\1/

!

voice translation-profile INCOMING

translate called 1

I'd recommend to use voice translation-rules instead of num-exp command. Translation rules have the flexibility that num-exp doesn't.

Kind regards,
Andrew C.

[islam.kamal]

Hi

Can you please follow the below:-

1- create POTS dial-pear which will match any incoming number

dial-peer voice 10 pots

incoming called-number .

direct-inward-dial

2-create translation rule which match any number and only match last 4 digits which will be your internal ext

voice translation-rule 1

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

voice translation-profile DID

translate called 1

3-Then apply this to match any incoming call

voice-port 0/0/0:23    (as you use T1)

translation-profile incoming DID

4-You have to create VOIP dial-patterns which will direct the calls to the registered DNs on your CUCM.

dial-peer voice 10 voip

destination-pattern 4...

session target ipv4:X.X.X.X    where x.x.x.x is your Pub IP or sub

voice-class codec 1

voice-class h323 1

dtmf-relay h245-alphnumeric

no vad

Note:As Mr/Jason advised please capture incoming call by debug Isdn q931.

Thank you

please rate all useful information