I have a customer that complains about his phonebook in Jabber. Whenever he types the name of his boardroom, he gets back 3 different ways of making his call which are:
- IP address
His phonebook is using his ALL SYSTEM source. All his systems are registered in both SIP and H.323 to his VCS.
Is there a way to use the ALL SYSTEM phonebook source and select to show just one of the dialing strings or do you have to manually create your phonebook inorder for it to show just one of the 3 ways of making calls.
Administrative Tools> Configuration> General Settings> Route Phone Book Entries
Is it set to no, can you try change it to yes?
If that is not going to help best way is to create manual list for phone book source, import it to endpoints/Jabber once. After you need remove all info you don't need it and leave only one type of dialing.
After you need create another manual phone book which use this phonebook as source and set it on the systems.
I ran into something simliar once myself for a manual phonebook I created, it contained at the time only two entries, IP and H323. Both address types appeared in Jabber Video, but once I added a SIP address to the phonebook, it was then the only type that appeared.
I'm not sure if "Route Phone Book Entries" is what made the other two address types not show up once a SIP address was added, but I would assume it was.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...