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

Mobile Connect, CUBE & Mutliple CCM.

Hi,

I have kind of a difficult problem ....

I have

PSTN

!

(E1)

!

GW--(H323)--CCM1--(SCCP)--Phone1

!

(H323)

!

CCM2

!

(SCCP)

!

Phone2

Phone2 can Call Phone1

Phone 1 can Call Phone 2

PSTN can call Phone 1 a Phone 2

Transfer works in all way (pstn to/from CCM1, CCM1 to/from CCM2, PSTN to/from CCM2)

But, I have a problem with mobile connect.

Phone 1 has mobile connect enable with remote destination to phone 2.

If a phone on CCM1 call phone1, everything is ok. Phone1&2 ring, I can answer on phone2 (or phone1) without any problem.

But if a call comes from pstn to phone1, phone2 rings but if it pickup the call, Pstn caller still hear the ringing tone. It seems that it doesn't detect anything ...

Any idea on what could be the problem ?

Thanx,

Bastien.

11 REPLIES
New Member

Re: Mobile Connect, CUBE & Mutliple CCM.

Hi ,

By any chance you solved the issue. I am having Similar issue with my implementation.

I have a CUBE element as H323 to H323  in between my CUCM network and the Mobile Connect remote destination.

I found out h245 signnaling problem but am unable to figure out the exact issue. It is probably related to h245 Capability exchange , But i still need to verify it to be sure.

Will be glad to hear someones input on it.

Regards

Mazin

Cisco Employee

Re: Mobile Connect, CUBE & Mutliple CCM.

If a phone is still ringing, I wouldn't expect an h245 issue, since the call shouldn't be in a connected state yet.

You want to look at h225 and see if the calling phone is getting the connect all the way back to itself.  Describe the complete logical topology, and run signaling debugs at every hop during an issue.  Look for where a connect doesn't occur.

If you want to post your CUBE config and h225 & h245 debugs during a call, I can see if there is an h245 issue at CUBE for you, though.

New Member

Re: Mobile Connect, CUBE & Mutliple CCM.

Steven,

I have a CUCM 7.0(1) connectivity with H323 Gateway which is acting as a CUBE. The CUBE is pointing to a PSTN which is a H323 Gateway

CUCM --> H323-CUBE Gateway --> PSTN Gateway

The IP Phone Remote Destination is : 2141ABCD

The Gateway @ CUCM is Configured with Standard Setting with proper Device Pool along with CSS.
With one Exception "Wait for Far End H.245 Terminal Capability Set" Unticked.

CUBE is configured with :

voice service voip
allow-connections h323 to h323
fax protocol cisco
h323

Dial-peer matches :
Incoming Dial-peer=210
Outgoing Dial-peer=210

dial-peer voice 210 voip
voice-class codec 20
voice-class h323 1
session target ipv4:PSTN IP ADDRESS
incoming called-number 2141....
dtmf-relay h245-alphanumeric

I am including the Debug When the Remote Destination Picks Up the Call
Debug cch323 h225 :

*Oct  8 15:09:40.426: //-1/xxxxxxxxxxxx/H323/cch323_h225_receiver: Received msg of type SETUPCFM_CHOSEN
*Oct  8 15:09:40.426: //94/0095AB3B0200/H323/setup_cfm_ind: ====== PI = 0
*Oct  8 15:09:40.426: //94/0095AB3B0200/H323/setup_cfm_ind: Set new event H225_EV_SETUP_CFM_IND
*Oct  8 15:09:40.426: //94/0095AB3B0200/H323/setup_cfm_ind: Rcvd CONNECT Display Info IE =
*Oct  8 15:09:40.426: //94/0095AB3B0200/H323/cch323_h225_receiver: SETUPCFM_CHOSEN: src address = CUBE IP Address; dest addres
s = PSTN IP ADDRESS
*Oct  8 15:09:40.426: //94/0095AB3B0200/H323/run_h225_sm: Received event H225_EV_SETUP_CFM_IND while at state H225_ALERT
*Oct  8 15:09:40.426: //94/0095AB3B0200/H323/setup_cfm_notify: status = 8000009
*Oct  8 15:09:40.426: //94/0095AB3B0200/H323/cch323_h225_set_new_state: Changing from H225_ALERT state to H225_WAIT_FOR_H245 state
*Oct  8 15:09:40.426: //-1/xxxxxxxxxxxx/H323/cch323_h225_receiver: Received msg of type NOTIFYIND_CHOSEN
*Oct  8 15:09:40.426: //94/0095AB3B0200/H323/notify_ind: Rcvd NOTIFY Display Info IE =
*Oct  8 15:09:40.430: //94/0095AB3B0200/H323/notify_ind: Rcvd NOTIFY Notification Indicator IE = 113
*Oct  8 15:09:40.430: //94/0095AB3B0200/H323/notify_ind: Rcvd NOTIFY Connected Number as IE
*Oct  8 15:09:40.430: //94/0095AB3B0200/H323/notify_ind: [cnum]/[oct]/[oct3a]= [REMOTE DESTINATION PHONE NUMBER]/[0x00]/[0x00]
*Oct  8 15:09:40.430: //94/0095AB3B0200/H323/notify_ind: Notify data embedded, mask=0x00000007
*Oct  8 15:09:40.430: //94/0095AB3B0200/H323/cch323_h225_receiver: NOTIFYIND_CHOSEN: src address = CUBE IP ADDRESS; dest address = PSTN IP ADDRESS
*Oct  8 15:09:40.430: //94/0095AB3B0200/H323/run_h225_sm: Received event H225_EV_NOTIFY_IND while at state H225_WAIT_FOR_H245
*Oct  8 15:09:40.430: //94/0095AB3B0200/H323/notify_msg_notify: Notify data found, mask=0x00000007
*Oct  8 15:09:40.430: //-1/xxxxxxxxxxxx/H323/cch323_post_call_service_msg: callID=93, notify data mask=0x00000007
*Oct  8 15:09:40.430: //93/0095AB3B0200/H323/run_h225_sm: Received event H225_EV_PROGRESS while at state H225_ALERT
*Oct  8 15:09:40.430: //93/0095AB3B0200/H323/delay_h245_transport_address: CCM-ITS compatibility delay transport address for callid[5D]
*Oct  8 15:09:40.430: //93/0095AB3B0200/H323/send_generic_progress: ====== PI = 8, cause = 0
*Oct  8 15:09:40.430: //93/0095AB3B0200/H323/run_h225_sm: Received event H225_EV_PROGRESS while at state H225_ALERT
*Oct  8 15:09:40.434: //93/0095AB3B0200/H323/delay_h245_transport_address: CCM-ITS compatibility delay transport address for callid[5D]
*Oct  8 15:09:40.434: //93/0095AB3B0200/H323/send_generic_progress: ====== PI = 3, cause = 0
*Oct  8 15:09:40.434: //93/0095AB3B0200/H323/run_h225_sm: Received event H225_EV_NOTIFY while at state H225_ALERT
*Oct  8 15:09:40.434: //93/0095AB3B0200/H323/send_notify_msg: Notify data found, mask=0x00000007
*Oct  8 15:09:40.434: //93/0095AB3B0200/H323/send_notify_msg: Sending NOTIFY Display Info IE =
*Oct  8 15:09:40.434: //93/0095AB3B0200/H323/send_notify_msg: Sending NOTIFY Notification Indicator IE = 113
*Oct  8 15:09:40.434: //93/0095AB3B0200/H323/send_notify_msg: Sending NOTIFY Connected Number as IE
*Oct  8 15:09:40.434: //93/0095AB3B0200/H323/send_notify_msg: [cnum]/[oct]/[oct3a] = [REMOTE DESTINATION PHONE NUMBER]/[0x00]/[0x00]

*Oct  8 15:35:43.030: //-1/xxxxxxxxxxxx/H323/cch323_h225_receiver: Received msg of type RELEASEIND_CHOSEN
*Oct  8 15:35:43.030: //95/806623D80300/H323/cch323_h225_receiver: RELEASEIND_CHOSEN: src address = 177.1.254.3; dest address = 192.168.2.132
*Oct  8 15:35:43.030: //95/806623D80300/H323/run_h225_sm: Received event H225_EV_RELEASE_IND while at state H225_ALERT
*Oct  8 15:35:43.034: //95/806623D80300/H323/run_h225_sm: Received event H225_EV_CONN_LOST while at state H225_ALERT
*Oct  8 15:35:43.034: //96/806623D80300/H323/run_h225_sm: Received event H225_EV_RELEASE while at state H225_WAIT_FOR_H245
*Oct  8 15:35:43.034: //96/806623D80300/H323/cch323_h225_send_release: Cause = 127; Location = 0
*Oct  8 15:35:43.034: //96/806623D80300/H323/cch323_h225_send_release: h225TerminateRequest: src address = -1325269501; dest address = PSTN IP ADDRESS
*Oct  8 15:35:43.038: //96/806623D80300/H323/cch323_h225_set_new_state: Changing from H225_WAIT_FOR_H245 state to H225_IDLE state
*Oct  8 15:35:43.038: //95/806623D80300/H323/run_h225_sm: Received event H225_EV_RELEASE while at state H225_ALERT
*Oct  8 15:35:43.038: //95/806623D80300/H323/cch323_h225_set_new_state: Changing from H225_ALERT state to H225_IDLE state
*Oct  8 15:35:43.042: //-1/xxxxxxxxxxxx/H323/validate_crv: No CCB for crv: 0x31

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

The H245 Debugs when The Remote Destination Pick Up the Call

*Oct  8 15:39:12.306: //97/0053DD5B0400/H323/cch323_send_event_to_h245_connection_sm: Changing to new event H245_LISTEN_REQ_EVENT
*Oct  8 15:39:12.306: //97/0053DD5B0400/H323/cch323_h245_connection_sm: H245_LISTEN: Received event H245_LISTEN_REQ_EVENT while at H245_NONE state
*Oct  8 15:39:12.306: //97/0053DD5B0400/H323/cch323_h245_set_new_state: Changing from H245_NONE state to H245_WAITING state

*Oct  8 15:39:24.470: //98/0053DD5B0400/H323/run_h245_iwf_sm: received IWF_EV_H245_DISCONN while at state IWF_IDLE
*Oct  8 15:39:24.470: //98/0053DD5B0400/H323/defaultHdlr: DEFAULT: Received IWF_EV_H245_DISCONN in state IWF_IDLE
*Oct  8 15:39:24.470: //97/0053DD5B0400/H323/run_h245_iwf_sm: received IWF_EV_H245_DISCONN while at state IWF_IDLE
*Oct  8 15:39:24.470: //97/0053DD5B0400/H323/defaultHdlr: DEFAULT: Received IWF_EV_H245_DISCONN in state IWF_IDLE

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

Thanks

Mazin

New Member

Re: Mobile Connect, CUBE & Mutliple CCM.

Make sure you have the emptycapability parameter set under voice service voip.

voice service voip
h323
   emptycapability

I've seen many transfer issues between CUCM and CUBE using h323 if this parameter is not enabled.

John

New Member

Re: Mobile Connect, CUBE & Mutliple CCM.

I did tried the emptycapability before didnt worked.

I think it is used when my RTP media have to be redirected to someother device during a call?

Thanks Though.

Cisco Employee

Re: Mobile Connect, CUBE & Mutliple CCM.

ECS is used any time media needs to be brought down and reneogitated mid call with H323.  It is a blank TCS.

Also make sure h450.2 and h450.3 are disabled on CUBE since CM doens't support those.

Cisco Employee

Re: Mobile Connect, CUBE & Mutliple CCM.

You need to run more debugs to diagnose the issue though; cch323 isn't enough:

debug cch323 all

debug h225 asn1

debug h245 asn1

debug voip ccapi inout

debug ip tcp trans

New Member

Re: Mobile Connect, CUBE & Mutliple CCM.

Just to recap what exactly is the call scenario:

1. When Someone calls a CUCM IP Phone configured with Mobile Connect having a PSTN Remote Destination .

2. The IP Phone rings , along with the PSTN Remote Destination Number as configured.

3. When the PSTN Remote Destination Picks up, nothing is heard on the PSTN Remote Destination.The call gets dropped afterwards.

4. The Called CUCM IP Phone keeps ringing.

CUCM --> H323/CUBE --> PSTN H323 GW

I have attached the debugs requested.

There are no CCH323 H245 debug outputs.

What I have noticed in the H225 debug is that the H225 State remains in H225_WAIT_FOR_H245 and then after recieving no information goes to IDLE State.

Thanks

Cisco Employee

Re: Mobile Connect, CUBE & Mutliple CCM.

Please run the test again with all the debugs running at the same time.  It doesn't let you see how the stacks interoperate with each other when you run them separately.

It sounds like the H245 TCP socket isn't getting built, but when you re-collect the debugs in a single file I'll take a look at them and confirm.

Cisco Employee

Re: Mobile Connect, CUBE & Mutliple CCM.

And you have 'wait for far end h.245 capability' unchecked in CM, right?

New Member

Re: Mobile Connect, CUBE & Mutliple CCM.

Yes, the  'wait for far end h.245 capability' is unchecked in CM

My Normal Calls are working fine from the CUCM to the PSTN. Only the Mobile Connect Call is having this problem.

571
Views
0
Helpful
11
Replies