I'm using an EX90(TC220.127.116.115090) registered at VCS -Cluster (X7.1)and using ServerPhonebook from TMS-Server (13.2).
I have several C20(TC18.104.22.1682001) registert also on VCS-Cluster.
For all endpoints I made entries on TMS Server-Phonebook.
Using EX90 some of the C20 can be dialed, they are shown with H323, some C20 can't be dialed, they are shonw with SIP-Numbers on the EX90.
Why is there a diffrent behaivor between these systems? All of them are configured the same way!
Can anyone help me here?
The fix is included in 13.2.1 specifically so you have to upgrade.
The reason why this is happening is that TMS is sending IP as a protocol. This has now been changed to H323 which is accepted by the touch panel.
You can refer this BUG# CSCtw52223. This is already fixed in TMS version 13.2.1
This is the details listed under the online help in TMS regarding the function. However it does not state exactly what factors TMS is looking at and I believe its several things including where its registered and if TMS thinks the unit can reach it using that address.
This setting applies to the phone books specified in Cisco System Phone Books (below).
- Yes (default): Cisco TMS will check routing for the system requesting phone book and filter the non-routable entries out of the phone book presented to the system.
- No: Cisco TMS will not check routing and deliver the phone book.
Why your TMS thinks it cannot route to that address might be rooted in the fact that all the C20's that you only saw IP for is registered on a different VCS than the Ex90. TMS checks these things and manipulates the phonebook asccordingly if the routed phonebook is set to Yes. The VCS plays a big part when TMS checks if the systems can actually dial eachother. Is both the VCS's in TMS? Does the VCS's have a neighbor relationship?
I saw this issue once before but the scenario was that the VCS had hit the 13.1 bug where the management and feedback address changed it protocol to HTTPS and if HTTPS wa not enabled on the TMS this communication would fail.
In this scenario the TMS server did not think that the EX90 could reach those H323 addresses and replaced them with an IP address (only some of the systems) which the EX90 could not dial. It seems like the same issue here but changing the route phonebook entries to no resolved this issue. Worth giving it a try.
Do you use the cisco touch only on the ex90 or also on the other endpoints?
What happens if you also add the sip address for this endpoint in the pb?
I would not only check on the vcs if it shows the endpoint as registered, also check on the
endpoint if its registered. Whats the default call protocol used on the endpoints?
If its sip, does the behavior change if you set it to h323?
Is there a special reason to use the form of h323 ids as you use it?
I would use the same then the sip registration.
Do you have a cucm/phone integration or why do you only use e164 numbers in the list?
If you do not need it for a phone integration I would use alphanumeric addresses like [email protected]
You might also have an issue with your searchrules, transforms, findme.
Possibly adding a transform adding a domain to everything that comes in without
and then a search rule hitting with and an other one stripping the domain might also help.
Its all dependent on what you would expect or not expect to work and then the setup.
As we dont know much about both its not easy to say.
I would recomend that you talk to a Cisco Partner who can help you to review your network
and find the best solution for you!
Is the manual list the only phonebook set on the EX90?
Are the c20's in the same ip zone in tms?
If you can see the ip entry in the phonebook and when you dial it you cannot.. Try to set the call setup mode to direct just to see if that works then change it back. If it works with direct call setup i would take a look at the event log on the vcs and see what is going on.
You have for a fact setup all your entries in the phonebook as H323 but yet they show up as SIP definition on the ex90. How does this look on the c20's when doing the same search?
I'm trying to imagine how you set this up but what you see compared to how you say you have configured it makes no sense
I wish i could see it at this point. Any screenshots you would like to share? Else i think a quick tac case should do the trick...
Sent from Cisco Technical Support iPhone App