We have had the Cisco telepresence solution in place for about 1 year. We have a VCS/VCSe/MCU/TMS13.1.2(yes old, but we are upgrading as we just had our smartnet upgraded. We were without it for a bit).
We are having a weird problem with units not being to place calls after a certain situation (we don't know what causes it).
Basically we get an error message saying that we can't route to host, but on the units themselves, we are able to ping and traceroute as well as on the VCS.
A reboot seems to resolve the issue, but I don't think that's practical. This October I will finally be taking a class to get a better understanding, but looking for some help as TAC can't figure it out or the assigned tech can't.
9/3/2013 9:55:45 AM Connection Error Source Number: , Destination Number: h323:172.xxx.xxx.xxx, Cause Code: No route to destination
The devices can ping each other and a traceroute works from endpoints and vcs/vcse/tms
IN THE LOGS I HAVE SEEN CALL REECTED WITH A RESPONSDE CODE UNKNOWN REASON
Also what causes a call to be rejected with an unknown reason
Now I got it. =)
Well, If you register them to TMS as room, you leave all the H323 option in blank, so that only SIP information will be imported to the phonebook. Also, you can completly disable H323 scheduling for those system, so only SIP will be used.
This is an example that should work fine:
Don't configure any H323 field, then you will be able to have phonebooks in TMS for those system with only the SIP information. Then, when the users dial from touch device using phonebook, only the SIP URI will be used, so you won't have IP H323 dialling and you wont have the call being routed to VCS Expressway.
I hope this help.
If it solves your issue, please, mark your topic as answered. =)
Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".