ciscoguy

Can you post the debugs from the Cisco? Make sure you have the following debugging on:

isdn q931
isdn events
isdn error

I need to see specifically what IEs are sent to know what it may not like, though the invalid IE may not be the problem (sometime's it's just a minor error that doesn't actually cause a problem).

I only had q931 debug on and have switched back to NI2 for the moment. here is what I get on a call FROM the PBX

0:08:01: ISDN Se1/1:23 Q931: RX <- SETUP pd = 8 callref = 0x02
Bearer Capability i = 0x8090A2
Standard = CCITT
Transer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xE9808302
Exclusive, Interface 0, Channel 2
Calling Party Number i = 'A', 0x80, '5582802'
Plan:ISDN, Type:Subscriber(local)
Called Party Number i = 0xC1, '6263032'
Plan:ISDN, Type:Subscriber(local)
20:08:01: ISDN Se1/1:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x8002
Channel ID i = 0xA98382
Exclusive, Channel 2
20:08:01: ISDN Se1/1:23 Q931: RX <- RELEASE pd = 8 callref = 0x02
Cause i = 0x81E4 - Invalid information element contents
20:08:8589934591: ISDN Se1/1:23 **ERROR**: CCPRI_Go: call id 0x2B event 0x57 No ccb Source->HOST
20:08:01: ISDN Se1/1:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x8002

And to the PBX:

2600-cm#
19:08:01: %SYS-5-CONFIG_I: Configured from console by vty0 (192.168.177.10)
19:08:04: ISDN Se1/1:23 Q931: TX -> SETUP pd = 8 callref = 0x0002
Bearer Capability i = 0x8090A2
Standard = CCITT
Transer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98317
Exclusive, Channel 23
Display i = '2900,Cisco7960'
Calling Party Number i = 'A', 0x81, '2900'
Plan:ISDN, Type:Subscriber(local)
Called Party Number i = 0x80, '2802'
Plan:Unknown, Type:Unknown
19:08:04: ISDN Se1/1:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x82
Cause i = 0x81B6 - Incoming calls are barred

ciscoguy

Hmm... not sure on the "Incoming calls are barred" part, is the trunk configured for bidirectional traffic on the Nortel side (ICOG on the RDB - options are IAO=In and Out, ICT=Incoming Only, OGT=Outgoing Only)?

As far as the outgoing, in debug it appears that the Cisco's "Call Proceeding" message uses a channel ID different from the ID sent by the Meridian, and I suspect this may be the problem. What rev of IOS is on the router? Is this a straight IOS H.323 gateway, or is it a Callmanager-controlled MGCP gateway? If it's MGCP I believe the Callmanager controls the Channel ID.

ciscoguy

Hmm, I must've misread the debug, the channel ID does match (channel 2)... long day. :P

Could you post the Cisco IOS config, along with IOS version info and Callmanager version info? Meridian configs would be helpful as well, specifically RDB/DCH parts relevant to this PRI.

I don't often see the call rejected based on the CALL_PROC message, I would like to see both ends of the config to see if there's something that sticks out.

rhack

I'll see if I can get you an answer tommorrow. We encountered the same exact thing, and I believe something was changed on the router to correct it. I have my mini setup for S100, and the RDB as a two way DID route (IAO/DID). The router is set for DMS100.

Fletch

Post the BUG message as well please.............

(chomp chomp chomp) :P

__________________
Fletch

For more on Nortel E911 Solutions on the web:
http://nortel.com/e911

rhack

Talked with the Cisco SE today. He tells me with the 3600 routers, the router should be set to DMS100, and the M1 to S100. On the router, this command must be issued:

ISDN - Flip - Chan - Flag

This resolved the Incoming Call Barred and Invalid IE problem.

ciscoguy

Worth a try, I'm not sure that will work if it's an MGCP controlled gateway though - that may only work for straight H.323.

I know my Callmanager has a checkbox for MGCP gateways labelled "MCDN Channel Number Extension Bit Set to Zero" specific to DMS100 that I believe accomplishes the same thing, though I'm not sure.

rhack

The SE mentioned that there was a Check box with the Call manager. Also, remember to change the M1 from NI2 to S100.