T303 times out on calls to Avaya PBX

jeffrey.girard · ‎01-29-2008

Interface between 3825 with T1 Multiflex card and Avaya Definity PBX. Link worked fine as a DSO group. Changed to PRI, now cannot complete calls. About 4 seconds of dead air and then reorder tone. Q921 shows Multiframe established. Q931 debug is below

debug isdn q931

debug isdn q931 is ON.

3825-1#

3825-1#debug isdn q931

debug isdn q931 is ON.

3825-1#

*Jan 24 16:34:29.185: ISDN Se0/0/0:23 Q931: Applying typeplan for sw-type 0xD is 0x0 0x0, Calling num 1123

*Jan 24 16:34:29.185: ISDN Se0/0/0:23 Q931: Applying typeplan for sw-type 0xD is 0x0 0x0, Called num 4345

*Jan 24 16:34:29.185: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0083

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Calling Party Number i = 0x0081, '1123'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '4345'

Plan:Unknown, Type:Unknown

*Jan 24 16:34:33.185: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0083

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Calling Party Number i = 0x0081, '1123'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '4345'

Plan:Unknown, Type:Unknown

*Jan 24 16:34:37.185: ISDN Se0/0/0:23 **ERROR**: CCPCC_CallOrigination: SETUP timed-out (2nd T303) to NETWORK. The SETUP failed.

3825-1#no debug all

Port Statistics for unclassified packets is not turned on.

All possible debugging has been turned off

3825-1#

pcameron · ‎01-29-2008

There is no response from the PBX. Run 'debug isdn q921' and do a shut/no shut under the T1 controller to confirm correct layer 2 link establishment.

If you see a message 'bad frame' , add (or remove) the command 'isdn protocol-emulate network' from the D channel.

You might need your PBX techs to check the operation of the PBX as well.

jeffrey.girard · ‎01-29-2008

Yes, I have already been down the Q921 road with the TAC. Output is below. TAC basically told me the same thing - check with your PBX engineer. What I am hoping for is something more specific to tell my PBX engineer (who is not overly excited about this VoIP connection to begin with).

3825-1(config)# debug isdn q921

debug isdn q921 is ON.

3825-1#conf t

Enter configuration commands, one per line. End with CNTL/Z.

3825-1(config)#int

*Jan 24 15:41:20.821: ISDN Se0/0/0:23 Q921: Net RX <- RRp sapi=0 tei=0 nr=31

*Jan 24 15:41:20.821: ISDN Se0/0/0:23 Q921: Net TX -> RRf sapi=0 tei=0 nr=31 controller t1

*Jan 24 15:41:30.885: ISDN Se0/0/0:23 Q921: Net RX <- RRp sapi=0 tei=0 nr=31

*Jan 24 15:41:30.885: ISDN Se0/0/0:23 Q921: Net TX -> RRf sapi=0 tei=0 nr=310/0/0

3825-1(config-controller)#shut

3825-1(config-controller)#

*Jan 24 15:41:37.313: %CONTROLLER-5-UPDOWN: Controller T1 0/0/0, changed state to administratively down

*Jan 24 15:41:37.317: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:23, TEI 0 changed to down

3825-1(config-controller)#

*Jan 24 15:41:39.313: %LINK-3-UPDOWN: Interface Serial0/0/0:23, changed state to down

3825-1(config-controller)#

3825-1(config-controller)#no shut

3825-1(config-controller)#

*Jan 24 15:42:03.201: %CONTROLLER-5-UPDOWN: Controller T1 0/0/0, changed state to up

*Jan 24 15:42:03.201: ISDN Se0/0/0:23 Q921: L2_EstablishDataLink: sending SABME

*Jan 24 15:42:03.201: ISDN Se0/0/0:23 Q921: Net TX -> SABMEp sapi=0 tei=0

*Jan 24 15:42:04.201: ISDN Se0/0/0:23 Q921: Net TX -> SABMEp sapi=0 tei=0

*Jan 24 15:42:04.205: ISDN Se0/0/0:23 Q921: Net RX <- UAf sapi=0 tei=0

*Jan 24 15:42:04.205: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/0/0:23, TEI 0 changed to up

*Jan 24 15:42:05.201: %LINK-3-UPDOWN: Interface Serial0/0/0:23, changed state to up

*Jan 24 15:42:14.285: ISDN Se0/0/0:23 Q921: Net RX <- RRp sapi=0 tei=0 nr=0

*Jan 24 15:42:14.285: ISDN Se0/0/0:23 Q921: Net TX -> RRf sapi=0 tei=0 nr=0

3825-1(config-controller)#

*Jan 24 15:42:24.349: ISDN Se0/0/0:23 Q921: Net RX <- RRp sapi=0 tei=0 nr=0

*Jan 24 15:42:24.353: ISDN Se0/0/0:23 Q921: Net TX -> RRf sapi=0 tei=0 nr=0

*Jan 24 15:42:34.417: ISDN Se0/0/0:23 Q921: Net RX <- RRp sapi=0 tei=0 nr=0

*Jan 24 15:42:34.417: ISDN Se0/0/0:23 Q921: Net TX -> RRf sapi=0 tei=0 nr=0

*Jan 24 15:42:44.481: ISDN Se0/0/0:23 Q921: Net RX <- RRp sapi=0 tei=0 nr=0

*Jan 24 15:42:44.481: ISDN Se0/0/0:23 Q921: Net TX -> RRf sapi=0 tei=0 nr=0

*Jan 24 15:42:54.545: ISDN Se0/0/0:23 Q921: Net RX <- RRp sapi=0 tei=0 nr=0

*Jan 24 15:42:54.545: ISDN Se0/0/0:23 Q921: Net TX -> RRf sapi=0 tei=0 nr=0

pcameron · ‎01-29-2008

It looks like layer 2 is fine, so the issue is almost certainly on the PBX - it should respond to the SETUP message with either a setup-ack, call proceeding, progress or alerting message within milliseconds.

It could be due to an ISDN switch type mismatch or some other PBX setting. There is a lot of material relating to integration of Avaya Definity PBX's with Cisco gear on Cisco.Com - just put in 'avaya definity' in the search box.

I found this note that has screen shots of the PBX config - it may be what your PBX tech needs.

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_troubleshooting_guide09186a00808b6259.html

This VOIP stuff isn't going away ... your crusty old PBX tech is going to have to get across it or get out of the way :-)