cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
697
Views
0
Helpful
7
Replies

DID routing

mwatson
Level 1
Level 1

We have an office with a new set of did's the provider is handing off the last 3 digits and I can see them come in when doing a debug but I still get a fast busy.  I have the following in as a voice translation-rule: rule 2 /\(^8...$\)/ /949428\1/

Their firat set of DID's is 0XXX and that translation rule is rule 1 /\(^0...$\)/ /949428\1/

So is my rule correct?  Also I get the following error when I try to call from the outside:

Cause i = 0x8295 - Call rejected

I can call the 8XXX number internally via 4 digit dial from other offices.

Thanks

1 Accepted Solution

Accepted Solutions

The reason why you get fast busy for the last 4 digits ending in 8xxx is because you need to correct your voip dial peers. Right now, they are configured to accept calls to pattern 0xxx only. Let's say you have the following last for digits: 0123 and 8389. Your statement would look like:

dial-peer voice 12 voip

destination-pattern [0,8][1-3]..

[0,8] - it means that the first digits can be 0 or 8

[1-3] - the second digit can be 1, 2 or 3

. (dot) - the last two digits can be any number from 0 thru 9

The following link explains in more detail everything related to Call Routing/Dial Plans

http://www.cisco.com/en/US/docs/ios/12_2/voice/configuration/guide/vvfpeers.html#wp1261213

Give a try and let us know.

View solution in original post

7 Replies 7

Andrew Skelly
Level 7
Level 7

Have you tried using a translation pattern in UCM to convert the incoming 3 digits into a 4 digit extension?

Please rate helpful posts by clicking the thumbs up!

Limitless1801
Level 1
Level 1

mwatson...

It would be good if you let us know what type of voice gateway you are using. From what you had stated, it seems like you are dealing with an H323 GW. You said that the provider is handing you off the last 3 digits of the DID and later you said that the first digit starts with zero (0); therefore, it looks to me like the provider is really sending you four digits (e.g. 0XXX). Can you please clarify?

I'll say you have two different issues here: first: resolve your incoming call problem and second: work on outbound calls.

Here is the link that refers to the Cause error you are getting:

  http://www.cisco.com/en/US/tech/tk801/tk133/technologies_tech_note09186a008009469f.shtml#table9

  Please note that the issue you are experiencing with the outbound calls could by also related to the fact that your ISDN Type and Plan don't match the carrier's.

Hope it helps. RG

Sorry my bad the PRI's are coming into a 2921 router we are using UCM 8.0.  So this office has 2 DID ranges both have the same area code and prefix but the last 4 are 0XXX and 8XXX the provide is giving us the last 3 so what I am trying to do is get the second did group to ring through 8301 is my test number.  I have the translation rule in but I get a fast busy when I call from outside the company.  I have the UCM translation pattern set to \+19494288xxx.  Do I need to add a new destination-pattern in the dial-peer?

Thanks

Can you please post your gateway's config so we have a little bit more information to work with?

Thanks.

Is this enough for you.

voice-card 0

dspfarm

dsp services dspfarm

!

!

!

voice service voip

fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback none

h323

  h225 display-ie ccm-compatible

  call preserve

!

voice class codec 10

codec preference 1 g711ulaw

codec preference 2 g729r8

!

voice class h323 10

  h225 timeout tcp establish 3

!

!

!

voice translation-rule 10

rule 1 /\(^949.......$\)/ /9\1/

rule 2 /\(^..........$\)/ /91\1/

!

voice translation-rule 11

rule 1 /^9/ //

!

voice translation-rule 7959

rule 1 /\(^...$\)/ /0\1/

!

voice translation-rule 949428

rule 1 /\(^0...$\)/ /949428\1/

rule 2 /\(^8...$\)/ /9494288\1/

rule 3 /\(^....$\)/ /9494280288/

voice-port 0/0/0:23

!

voice-port 0/1/0

!

voice-port 0/1/1

!

voice-port 0/1/2

!

voice-port 0/1/3

!

!

!

!

dial-peer voice 22 voip

destination-pattern 0...$

session target ipv4:172.16.17.22

incoming called-number .

voice-class codec 10

voice-class h323 10

dtmf-relay h245-alphanumeric

no vad

!

dial-peer voice 12 voip

preference 1

destination-pattern 0...$

session target ipv4:172.16.17.12

voice-class codec 10

voice-class h323 10

dtmf-relay h245-alphanumeric

no vad

voice-card 0
dspfarm
dsp services dspfarm
!
!
!
voice service voip
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback none
h323
  h225 display-ie ccm-compatible
  call preserve
!
voice class codec 10
codec preference 1 g711ulaw
codec preference 2 g729r8
!
voice class h323 10
  h225 timeout tcp establish 3
!
!
!
voice translation-rule 10
rule 1 /\(^949.......$\)/ /9\1/
rule 2 /\(^..........$\)/ /91\1/
!
voice translation-rule 11
rule 1 /^9/ //
!
voice translation-rule 7959
rule 1 /\(^...$\)/ /0\1/
!
voice translation-rule 949428
rule 1 /\(^0...$\)/ /949428\1/
rule 2 /\(^8...$\)/ /9494288\1/
rule 3 /\(^....$\)/ /9494280288/

!

voice-port 0/0/0:23
!
voice-port 0/1/0
!
voice-port 0/1/1
!
voice-port 0/1/2
!
voice-port 0/1/3
!
!
!
!
dial-peer voice 22 voip
destination-pattern 0...$
session target ipv4:172.16.17.22
incoming called-number .
voice-class codec 10
voice-class h323 10
dtmf-relay h245-alphanumeric
no vad
!
dial-peer voice 12 voip
preference 1
destination-pattern 0...$
session target ipv4:172.16.17.12
voice-class codec 10
voice-class h323 10
dtmf-relay h245-alphanumeric
no vad

The reason why you get fast busy for the last 4 digits ending in 8xxx is because you need to correct your voip dial peers. Right now, they are configured to accept calls to pattern 0xxx only. Let's say you have the following last for digits: 0123 and 8389. Your statement would look like:

dial-peer voice 12 voip

destination-pattern [0,8][1-3]..

[0,8] - it means that the first digits can be 0 or 8

[1-3] - the second digit can be 1, 2 or 3

. (dot) - the last two digits can be any number from 0 thru 9

The following link explains in more detail everything related to Call Routing/Dial Plans

http://www.cisco.com/en/US/docs/ios/12_2/voice/configuration/guide/vvfpeers.html#wp1261213

Give a try and let us know.

Your information was very helpful I ended up contacting TAC and they finished off the issue there was a dial-peer hard coding in a 0 infront of the 3 digits.  All is working now.

Thanks