I want to attach h323 client(SJPhone) but problem to dial from SJPhone to IP Phone.
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
-CCM6.1.2 IP address=10.0.131.11
-h323 client ip address=10.0.20.21
-create the Phone via 'Device > Phone > Phone type=H.323 client'
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>
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 126.96.36.19990-X which is one of the last...
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.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...