Only one DiD number works and secondary ephone-dn are valid

tloran · ‎10-02-2007

I have a strange problem that is driving me nuts. I have a new test CME system Version 4.1(0) with a VIC2-2BRI-NT/TE ISDN card with two active spids. sh isdn status shows no ISDN trouble I am trying to set up DiD and have the following dial peer

dial-peer voice 20 pots

incoming called-number .

direct-inward-dial

port 0/0/0

interface BRI0/0/0

no ip address

isdn switch-type basic-ni

isdn point-to-point-setup

isdn spid1 97048484671111

isdn spid2 97048486741111

isdn incoming-voice voice

isdn supp-service name calling

end

and I have the following ephone-dn configured

ephone-dn 1 dual-line

number 2201 secondary 4848467

ephone-dn 2 dual-line

number 2202 secondary 4848674

Calls back and forth from all numbers inside the network work well. Calls from the PSTN to 9704848467 OR 4848467 route to ephone-dn without problem

Calls from the PSTN to either 9704848674 or 4848674 connect just fine (IAW debug isdn q931) however, I get the network message ?the line is busy?

Anyone have any ideas as to why ISDN connects, but I get the busy message for anything but the first SPID. BTW I have tried this with and without the area code and get the same result. I also have some non spid numbers that also ring through on the debug messages and get the same result. (They are tied to another ephone-dn) I have checked and triple checked to make sure I do not have a typo, incoming messages are tied to a ephone-dn.

Is their a voice debug command I should try?.

debug isdn q931

Oct 2 19:15:17.174 MDT: ISDN BR0/0/0 Q931: RX <- SETUP pd = 8 callref = 0x32

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x88

Exclusive, No B-channel

Signal i = 0x40 - Alerting on - pattern 0

ENDPOINT IDent i = 0x818B

Calling Party Number i = 0x2183, '9706919064'

Plan:ISDN, Type:National

Locking Shift to Codeset 5

Codeset 5 IE 0x2A i = 0x809403, ' a=', 0x9E05, 'From ', 0x8B0C, '970 691-9064', 0x8001019E03, 'to ', 0x830C, '970 484-8674', 0x8001048001, '('

Locking Shift to Codeset 6

Codeset 6 IE 0x7B i = 0x81

CME-2801#

Oct 2 19:15:17.186 MDT: ISDN BR0/0/0 Q931: TX -> CALL_PROC pd = 8 callref = 0xB2

Channel ID i = 0x89

Exclusive, B1

Oct 2 19:15:17.206 MDT: ISDN BR0/0/0 Q931: TX -> DISCONNECT pd = 8 callref = 0xB2

Cause i = 0x8090 - Normal call clearing

Oct 2 19:15:17.254 MDT: ISDN BR0/0/0 Q931: RX <- RELEASE pd = 8 callref = 0x32

Signal i = 0x4F - Alerting off

Locking Shift to Codeset 5

Codeset 5 IE 0x2A i = 0x808001, 'P'

Oct 2 19:15:17.258 MDT: ISDN BR0/0/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0xB2

tloran · ‎10-02-2007

debug voip ccapi seems to show that the destination number is include in the successful trace but not included in the unsuccessful trace yes the debug isdn q931 messages show a "to" number.

Is this a feature that my carrier needs to turn on for the other numbers?

! Successful

----- ccCallInfo IE subfields -----

cisco-ani=9706919064

cisco-anitype=2

cisco-aniplan=1

cisco-anipi=0

cisco-anisi=3

dest=4848467

cisco-desttype=4

cisco-destplan=1

cisco-rdie=FFFFFFFF

cisco-rdn=

cisco-rdntype=-1

cisco-rdnplan=-1

cisco-rdnpi=-1

cisco-rdnsi=-1

cisco-redirectreason=-1 fwd_final_type =0

final_redirectNumber =

hunt_group_timeout =0

-------------------------------------------------

! Unsuccessful