Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Fast busy sending call to H.323 GW

CM 4.2(3) connected to 3825 with MultiFLex T1 card connected to Avaya PBX. Originally, the router was an H.323 GW and the T1 was a DS0/CAS circuit. I was able to offnet calls fine. Then to set up for E911, we changed the T1 to a PRI. Avaya operator changed his end, I changed the router config. Sh voice port summary and sh controller indicates all is good. I went to the CM and the GW. Now, calls going to the GW get fast busy.

Config below as well as show commands. I trimmed the show run:

!

isdn switch-type primary-ni

voice-card 0

dspfarm

dsp services dspfarm

!

!

!

!

controller T1 0/0/0

framing esf

linecode b8zs

pri-group timeslots 1-24

!

controller T1 0/0/1

framing esf

linecode b8zs

!

!

!

!

interface GigabitEthernet0/0

description Link to 008

duplex auto

speed auto

media-type rj45

negotiation auto

h323-gateway voip interface

h323-gateway voip h323-id 3825-1

h323-gateway voip tech-prefix 1#

h323-gateway voip bind srcaddr xxx.xxx.xxx.xxx

!

interface GigabitEthernet0/1

no ip address

shutdown

duplex auto

speed auto

media-type rj45

negotiation auto

interface Serial0/0/0:23

no ip address

isdn switch-type primary-ni

isdn incoming-voice voice

no cdp enable

!

control-plane

!

!

!

voice-port 0/0/0:23

echo-cancel enable type hardware

!

!dial-peer voice 1 pots

description Dial Peer for Outbound 4 digit on post dialing

destination-pattern ....

forward-digits all

!

On the CM, the GW window shows the GW, known by its IP address, device protocol H.225, and registration unknown

4 REPLIES
Cisco Employee

Re: Fast busy sending call to H.323 GW

On the router, do a SH ISDN status. If it has correct layer 1 operation, it should be in Multi Frame Established.

Next, enable 'debug isdn q921' and do a shut/no shut on the T1 controller. Capture these logs, then turn off these debugs.

Finally, enable 'debug isdn q931' and make a test call through the gateway and capture these logs. Post them here so we can go through them.

Community Member

Re: Fast busy sending call to H.323 GW

OK, looks like I have a Layer 2 issue. Sho ISDN status indicates that the state is alternating between TEI_Assigned/Awaiting_Establishment

Show ISDN Status below:

3825-1#sh isdn status

Global ISDN Switchtype = primary-ni

ISDN Serial0/0/0:23 interface

dsl 0, interface ISDN Switchtype = primary-ni

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 0 CCBs = 0

The Free Channel Mask: 0x807FFFFF

Number of L2 Discards = 0, L2 Session ID = 176

Total Allocated ISDN CCBs = 0

Hall of Fame Super Gold

Re: Fast busy sending call to H.323 GW

Hi,

router needs to be ISDN network-side:

int Serial0/0/0:23

isdn protocol-emulate network

Hope this helps, please rate post if it does!

Community Member

Re: Fast busy sending call to H.323 GW

OK, last post from p.bevilacqua fixed my L1/L2 problem - I now have MultiFrame Established. I have run the debugs as requested by a previous poster. Debug isdn q921 is below. Debug q931 and then placing a call produced not debug output

3825-1#debug isdn q921

debug isdn q921 is ON.

*Jan 23 16:40:09.987: ISDN Se0/0/0:23 Q921: Net RX <- RRp sapi=0 tei=0 nr=48

*Jan 23 16:40:09.991: ISDN Se0/0/0:23 Q921: Net TX -> RRf sapi=0 tei=0 nr=48conc t ft t

*Jan 23 16:40:20.055: ISDN Se0/0/0:23 Q921: Net RX <- RRp sapi=0 tei=0 nr=48

*Jan 23 16:40:20.055: ISDN Se0/0/0:23 Q921: Net TX -> RRf sapi=0 tei=0 nr=48f t

*Jan 23 16:40:30.119: ISDN Se0/0/0:23 Q921: Net RX <- RRp sapi=0 tei=0 nr=48

*Jan 23 16:40:30.119: ISDN Se0/0/0:23 Q921: Net TX -> RRf sapi=0 tei=0 nr=48

3825-1(config-controller)#shut

3825-1(config-controller)#

*Jan 23 16:40:38.243: %CONTROLLER-5-UPDOWN: Controller T1 0/0/0, changed state to administratively down

*Jan 23 16:40:38.247: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:23, TEI 0 changed to down

*Jan 23 16:40:40.243: %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)#exit

3825-1(config)#exit

3825-1#

*Jan 23 16:41:06.719: %SYS-5-CONFIG_I: Configured from console by girardj on console

*Jan 23 16:41:09.955: %CONTROLLER-5-UPDOWN: Controller T1 0/0/0, changed state to up

*Jan 23 16:41:09.955: ISDN Se0/0/0:23 Q921: L2_EstablishDataLink: sending SABME

*Jan 23 16:41:09.955: ISDN Se0/0/0:23 Q921: Net TX -> SABMEp sapi=0 tei=0

*Jan 23 16:41:10.955: ISDN Se0/0/0:23 Q921: Net TX -> SABMEp sapi=0 tei=0

*Jan 23 16:41:10.959: ISDN Se0/0/0:23 Q921: Net RX <- UAf sapi=0 tei=0

*Jan 23 16:41:10.959: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/0/0:23, TEI 0 changed to up

*Jan 23 16:41:11.955: %LINK-3-UPDOWN: Interface Serial0/0/0:23, changed state to up

*Jan 23 16:41:21.067: ISDN Se0/0/0:23 Q921: Net RX <- RRp sapi=0 tei=0 nr=0

*Jan 23 16:41:21.067: ISDN Se0/0/0:23 Q921: Net TX -> RRf sapi=0 tei=0 nr=0

*Jan 23 16:41:31.131: ISDN Se0/0/0:23 Q921: Net RX <- RRp sapi=0 tei=0 nr=0

*Jan 23 16:41:31.131: ISDN Se0/0/0:23 Q921: Net TX -> RRf sapi=0 tei=0 nr=0

3825-1#no debug all

Port Statistics for unclassified packets is not turned on.

236
Views
3
Helpful
4
Replies
CreatePlease to create content