CUCM6.1, how to setup h323 client(SJPhone)?

cjrchoi11 · ‎09-26-2008

Hi,

I want to attach h323 client(SJPhone) but problem to dial from SJPhone to IP Phone.

Please advise!!

symptom) when I dial from SJPhone to IP Phone, ringing once in IP Phone but disconnec immediately (the reverse case that dail from IP Phone to SJPhone is works okay). the packet trace is captured while SJPhone dial to IP Phone

env)

-CCM6.1.2 IP address=10.0.131.11

-h323 client ip address=10.0.20.21

CCM device)

-create the Phone via 'Device > Phone > Phone type=H.323 client'

-device name=10.0.20.21

-device type=h.323 phone

-device protocol=h.225

-signalling port=1720

-extension=3003

-all other parameters are default

h323 Phone)

-product name=SJPhone (freeware)

-configure h323 gateway=10.0.131.11

packet trace)

No. Time Source Destination Protocol Info

1 2008-09-26 14:44:30.767454 10.0.20.21 10.0.131.11 TCP dproxy > h323hostcall [SYN] Seq=0 Win=64240 Len=0 MSS=1460

2 2008-09-26 14:44:30.767948 10.0.131.11 10.0.20.21 TCP h323hostcall > dproxy [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460

3 2008-09-26 14:44:30.768832 10.0.20.21 10.0.131.11 TCP dproxy > h323hostcall [ACK] Seq=1 Ack=1 Win=64240 Len=0

4 2008-09-26 14:44:31.233621 10.0.20.21 10.0.131.11 H.225.0/H.245 CS: setup OpenLogicalChannel terminalCapabilitySet masterSlaveDetermination

5 2008-09-26 14:44:31.234104 10.0.131.11 10.0.20.21 TCP h323hostcall > dproxy [ACK] Seq=1 Ack=561 Win=6720 Len=0

6 2008-09-26 14:44:31.241375 10.0.131.11 10.0.20.21 H.225.0 CS: callProceeding

7 2008-09-26 14:44:31.246636 10.0.131.11 10.0.20.21 H.225.0 CS: alerting

8 2008-09-26 14:44:31.246683 10.0.20.21 10.0.131.11 TCP dproxy > h323hostcall [ACK] Seq=561 Ack=186 Win=64055 Len=0

9 2008-09-26 14:44:31.246943 10.0.131.11 10.0.20.21 H.225.0 CS: notify

10 2008-09-26 14:44:31.287452 10.0.20.21 10.0.131.11 H.225.0 CS: releaseComplete

11 2008-09-26 14:44:31.290479 10.0.20.21 10.0.131.11 TCP dproxy > h323hostcall [FIN, ACK] Seq=615 Ack=242 Win=63999 Len=0

12 2008-09-26 14:44:31.290830 10.0.131.11 10.0.20.21 TCP h323hostcall > dproxy [FIN, ACK] Seq=242 Ack=616 Win=6720 Len=0

13 2008-09-26 14:44:31.291469 10.0.20.21 10.0.131.11 TCP dproxy > h323hostcall [ACK] Seq=616 Ack=243 Win=63999 Len=0

gogasca · ‎09-28-2008

Will try in my lab tomorrow and let you know

I remember I had some problems in old versions for SJ to work with CUCM, but keep in touch

I normally for 6.x I use SJ as SIP :d

cjrchoi11 · ‎09-30-2008

Hi Gonzalo,

Any luck from your LAB?

btw, I have below error from CUCM trace. SJPhone requesting with tcp/1720 but CUCM rejecting. CUCM h323 deivce signaling port=1720 (default). Any idea?

09/25/2008 00:03:11.253 CCM|H225Handler::SdlConnectionInd, rejecting the TCP connection from IP=10.0.20.21. Incoming H225 call on Port=1720, can't find this port in the registered H323 endpoints port list. |<:STANDALONECLUSTER><:10.0.131.11><:0><:><:><:ERROR><:0100>

sfurqanli · ‎10-07-2008

Any success on the above problem. I am facing the same issue with MS NetMeeting client on windows XP.

When I Call from NM to IP Phone, it rings on IP Phone but when i pick the phone there is nothing and after sometimes the message comes at NM "The other party did not accept your call"

But when i call from IP PHone to NM the call successfully get connected and everything works fine.

Please note that NM is configured as H.323 client on CUCM 6.0.1.

Any help !!!!!

Yorick Petey · ‎12-23-2009

Hi,

Did you find the fix of your problem?

I get the same traces from CCM service of my publisher:

12/23/2009 16:20:03.320 CCM|H225Handler::SdlConnectionInd, rejecting the TCP connection from IP=10.168.194.62. Incoming H225 call on Port=1720, can't find this port in the registered H323 endpoints port list. |<:STANDALONECLUSTER><:10.168.194.10><:0><:><:><:ERROR><:0100>

My situation is a little bit different, the remote H323 party is not configured as a Device, but as a H323 Gateway (it is a fax server).

From the trace, I understand that the CCM service does not accept this IP address as a trusted peer, even if I delete it and recreate it, or reset it. But when I try to reach another CUCM node from the FaxServer (tried to 3 other CUCM subscribers in the cluster), I don't get the error message, meaning that the configuration is accepted by SUB nodes.

So apparently, the issue is just located on the publisher CCM which does not commit my new gateway config in its trust table...

I cannot restart the CCM service of the pub because I am in production but this is the first thing I would test.

I run CUCM 6.1.3.3190-X which is one of the last...

Is someone aware of a possible known bug?

Thank you.

Yorick

metuzuner · ‎02-09-2010

Hello,

The "rejecting the TCP connection from IP=10.168.194.62. Incoming H225 call on Port=1720, can't find this port in the registered H323 endpoints port list."

issue occurs due to the fact that only the nodes in the Call Manager Group that the Device Pool of the H.323 Gateway is associated with accepts calls from the Gateway. We had experienced this issue and was able to fix it by sending calls from the H.323 gateway to subscribers that are defined in the gateway's device pool callmanager group.

Yorick, I bet your publisher is not a member of the Call Manager Group of H.323 Gateway's device pool.

Please advise if this answers your question.

Regards,

metuzuner

Yorick Petey · ‎02-10-2010

Hi metuzuner,

You are totally right! Since we have 4 nodes, the publisher is no more part of the default Device Pool I applied for gateways.

I changed the GW destination to point only to the nodes defined in the device pool (callmanager group) and now all incoming H.323 connection are accepted.

I don't think this limitation is documented and if this is the case, it should be... It's tricky!

Thank you for your great help.

Best regards,

Yorick

Naoufal KERBOUTE · ‎10-22-2008

Hi,

I'm facing the same probleme with H323, can you please show how to setup SJPhone on an HP IPAQ with CUCM 5.1.3??

Best regards