different DID's pool on the same interface

Unanswered Question
Aug 18th, 2010

We have gateway with 2 E1 ISDN PRI cards. On both cards we have two groups of DID numbers which work fine. Now we ordered addtional DID numbers on one of ISDN PRI but we got different numbers than existing from telecom. Additional telecom forward  these DID to us on different way and we have also different numbers in local net. My question is: Is it possible configuring these situation on VG200? VG200 is configured at CUCM as H.323 gateway.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
philip.e.denton Wed, 08/18/2010 - 07:12

So as I understand it, you initially have two E1s that are bonded together and originally provided two DID ranges, but you ordered more telephone numbers from your carrier and the numbers they provided are not within your DID range(s)?  Additionally, you have non-DIDs in use locally?

If that is the case you're curious how to configure the new DID range as part of your dial plan?

mljevakovic Wed, 08/18/2010 - 07:26

No we have 2 independent PRI ISDN 1/0 and 1/1. And these two PRI have two different DID pool 264500 and 241000.

dial-peer voice 264500 pots
incoming called-number 0312645..
direct-inward-dial
port 1/0:15
forward-digits all

dial-peer voice 241000 pots
incoming called-number 0312410..
direct-inward-dial
port 1/1:15
forward-digits all

on the first port we got another DID pool 24800 with 50 numbers but here telecom forward us only last two numbers.

philip.e.denton Wed, 08/18/2010 - 08:07

So the first DID pool on the first port is really 0312645..?  So you own 031264500 through 031264599?  If the new pool is (some part of) 03124800 there is no way sending only two digits will work.  The carrier must send at least three digits.

philip.e.denton Thu, 08/19/2010 - 05:33

It would appear to the that the carrier is sending nine digits in all cases.  Have you verified that your translation patterns in CUCM are matching the correct patterns?  Can you put screenshots of the TPs that seem to be broken?  Or maybe you're missing some?

philip.e.denton Fri, 08/20/2010 - 05:42

It looks like you're missing the outbound (to CUCM) dial-peer for the new DN range.  Insert the following into your config and retest:

!        

dial-peer voice 249001 voip

destination-pattern 0512490..

voice-class codec 2

session target ipv4:10.51.80.1

fax-relay ecm disable

fax rate disable

no vad  

!

mljevakovic Fri, 08/20/2010 - 06:58

Example on CUCM I have number 3111. My public number is 249011. When I call this number from outside Telecom just forward last two numbers :

Aug 20 15:51:15.411 utc: ISDN Se1/0:15 Q931: RX <- SETUP pd = 8  callref = 0x00F8
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transer Capability = Speech 
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA1839F
                Preferred, Channel 31
        Calling Party Number i = '!', 0x81, '66465628'
                Plan:ISDN, Type:National
       Called Party Number i = 0x81, '11'
                Plan:ISDN, Type:Unknown
        High Layer Compat i = 0x9181
Aug 20 15:51:15.451 utc: ISDN Se1/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x80F8
        Channel ID i = 0xA9839F
                Exclusive, Channel 31
Aug 20 15:51:15.451 utc: ISDN Se1/0:15 Q931: TX -> CONNECT pd = 8  callref = 0x80F8
Aug 20 15:51:15.475 utc: ISDN Se1/0:15 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x00F8
Aug 20 15:51:26.192 utc: ISDN Se1/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x00F8
        Cause i = 0x829F - Normal, unspecified
Aug 20 15:51:26.200 utc: ISDN Se1/0:15 Q931: TX -> RELEASE pd = 8  callref = 0x80F8
Aug 20 15:51:26.224 utc: ISDN Se1/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x00F8

after this I got dial ton. When I put next

dial-peer voice 249001 voip
destination-pattern 3111
voice-class codec 2
session target ipv4:10.51.80.1
fax-relay ecm disable
fax rate disable
no vad

after dial ton I must dial 3111 to reach local numbers 3111.

Why I got dial ton? Do I have to do translation and where?

philip.e.denton Fri, 08/20/2010 - 07:08

Can you try unchecking the "Provide Outside Dial Tone" checkbox on the translation pattern that corresponds to the dial-peer I pasted previously?

Or add "direct-inward-dial" to the dial-peer, since you already have two DID ranges that seem to work ok with that checkbox checked?

mljevakovic Fri, 08/20/2010 - 07:19

It dosn't work.Look when I call some number in the first DID 241503 what I see n debug q931 message:

Aug 20 16:14:37.374 utc: ISDN Se1/0:15 Q931: RX <- SETUP pd = 8  callref = 0x00FB
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transer Capability = Speech 
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA1839C
                Preferred, Channel 28
        Calling Party Number i = 0x0181, '066465628'
                Plan:ISDN, Type:Unknown
       Called Party Number i = 0x81, '051241503'
                Plan:ISDN, Type:Unknown
        High Layer Compat i = 0x9181
Aug 20 16:14:37.426 utc: ISDN Se1/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x80FB
        Channel ID i = 0xA9839C
                Exclusive, Channel 28
Aug 20 16:14:37.466 utc: ISDN Se1/0:15 Q931: TX -> ALERTING pd = 8  callref = 0x80FB

Aug 20 16:14:38.822 utc: ISDN Se1/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x00FB
        Cause i = 0x829F - Normal, unspecified
Aug 20 16:14:38.834 utc: ISDN Se1/0:15 Q931: TX -> RELEASE pd = 8  callref = 0x80FB
Aug 20 16:14:38.854 utc: ISDN Se1/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x00FB

which directly connect to 5103 on CUCM.

but with DID 24900 the isdn q931 message is different (I called 249011)

Aug 20 15:51:15.411 utc: ISDN Se1/0:15 Q931: RX <- SETUP pd = 8  callref = 0x00F8
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transer Capability = Speech 
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA1839F
                Preferred, Channel 31
        Calling Party Number i = '!', 0x81, '66465628'
                Plan:ISDN, Type:National
        Called Party Number i = 0x81, '11'
                Plan:ISDN, Type:Unknown
        High Layer Compat i = 0x9181
Aug 20 15:51:15.451 utc: ISDN Se1/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x80F8
        Channel ID i = 0xA9839F
                Exclusive, Channel 31
Aug 20 15:51:15.451 utc: ISDN Se1/0:15 Q931: TX -> CONNECT pd = 8  callref = 0x80F8
Aug 20 15:51:15.475 utc: ISDN Se1/0:15 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x00F8
Aug 20 15:51:26.192 utc: ISDN Se1/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x00F8
        Cause i = 0x829F - Normal, unspecified
Aug 20 15:51:26.200 utc: ISDN Se1/0:15 Q931: TX -> RELEASE pd = 8  callref = 0x80F8
Aug 20 15:51:26.224 utc: ISDN Se1/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x00F8

telecom removed 2490.

philip.e.denton Fri, 08/20/2010 - 07:25

I'm sorry, I keep forgetting the telco is sending you a different number of digits for that dial-peer.  What if you change your digit strings to match the carrier, like this:

!        

dial-peer voice 249000 pots

call-block translation-profile incoming reject_m

incoming called-number ..

port 1/0:15

forward-digits all

!

!       

dial-peer voice 249001 voip

destination-pattern ..

voice-class codec 2

forward-digits all

session target ipv4:10.51.80.1

fax-relay ecm disable

fax rate disable

no vad 

!

Don't forget to change your translation pattern in CM to match.  Just for the record, I think it's silly that the telco is sending 2 digits sometimes and 9 others.  I think they should be all 9 digits.

mljevakovic Tue, 08/24/2010 - 06:13

Hi,I've done it. I've got from telco six numbers and I had to put direct-inward-dial and translation-profile incoming which translate incoming numbers 2490xx to 31xx. I didn't do anything more on CM. Thanks for your support.

Actions

This Discussion