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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Etisalat ISDN IP Phone not disconnecting when remote end hangs up

Has anyone had experience with Etisalat ISDN E1 setup as H323?

Installed a H323 GW with CUCM 9.1 and all working fine apart from when the call is made through the ISDN the Cisco IP Phone doesn't hang the call if the other person has hung up first.  Just get busy tone for 20-30 seconds before the phone "hangs up"

Debug Q931 message as follows after the remote end hangs up.

May 12 17:15:37.321: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8  callref = 0x8099
        Progress Ind i = 0x8288 - In-band info or appropriate now available
May 12 17:15:37.321: ISDN Se0/0/0:15 **ERROR**: L3_ProcessEvent: UNEXPECTED event - 0x1 state 10
May 12 17:15:37.321: ISDN Se0/0/0:15 **ERROR**: Ux_BadMsg: Invalid Message for call state 10, call id 0x801A, call ref 0x99, event 0x1
May 12 17:15:37.321: ISDN Se0/0/0:15 Q931: TX -> STATUS pd = 8  callref = 0x0099
        Cause i = 0x80E201 - Message not compatible with call state or not implemented
        Call State i = 0x0A
May 12 17:15:37.433: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x8099
        Cause i = 0x82E500000000 - Message not compatible with call state
        Progress Ind i = 0x8288 - In-band info or appropriate now available
May 12 17:15:37.433: ISDN Se0/0/0:15 Q931: call_disc: PI received in disconnect; Postpone sending RELEASE for callid 0x801A
May 12 17:15:37.565: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8  callref = 0x0099
May 12 17:15:38.017: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x8099

 

The config of the gateway is as follows:

card type e1 0 0

 

network-clock-participate wic 0
network-clock-select 1 E1 0/0/0

 

isdn switch-type primary-net5
!
voice-card 0
 dspfarm
 dsp services dspfarm
!
!
voice call send-alert
voice call disc-pi-off
voice rtp send-recv
!
voice class codec 1
 codec preference 1 g711ulaw
 codec preference 2 g711alaw
!
voice class h323 1
  h225 timeout tcp establish 3
!

controller E1 0/0/0
 framing NO-CRC4
 pri-group timeslots 1-10,16
 description PSTN

 

interface Serial0/0/0:15
 no ip address
 encapsulation hdlc
 isdn switch-type primary-net5
 isdn incoming-voice voice
 no cdp enable

voice-port 0/0/0:15
disc_pi_off

dial-peer voice 99 pots
 destination-pattern 9T
 progress_ind setup enable 3
 progress_ind alert enable 8
 progress_ind progress enable 8
 direct-inward-dial
 port 0/0/0:15
!
dial-peer voice 100 voip
 description ** Call Manager Pub **
 preference 1
 destination-pattern 3029..
 progress_ind setup enable 3
 modem passthrough nse codec g711ulaw
 session target ipv4:10.188.36.12
 dtmf-relay h245-alphanumeric
 no vad

Thank you in advance

 

 

 

3 REPLIES
New Member

Hope your problem is resolved

Hope your problem is resolved, kindly advise what is the finding.

 

BR

New Member

this did the trick

this did the trick

voice service voip
allow-connections h323 to h323
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
h323
no h225 timeout keepalive
h225 timeout ntf 100
h225 display-ie ccm-compatible
call preserve limit-media-detection

New Member

It may did the trick, but it

It may did the trick, but it is not the solution. With the call preserve limit-media-detection you achieve that you don't here a busy signal, but the internal phone is not hanging up the call.

This is a provider issue. When the remote party hangs up, PSTN sends ALERTING again and this is not an expected message after call connect. As ALERTING is not expected message for a CONNECTED call is why the Cisco Router throw that error.

270
Views
0
Helpful
3
Replies
CreatePlease to create content