Is it the default behaviour for a C20 that is registering to a VCS (7.1) to register with it's hostname as one of the alternative Aliases?
I have my Codec that points to VCS with a SYSTEM Name of UL-c90-1. I have it's "E.164 Alais" set to be 3004 and its "h323 id" set to be firstname.lastname@example.org. As you can see below from the VCS registeres this H.323 device under 3 alias. Is the "System Name" suppose to register like that? My thoughts are that it's suppose to be just the E.164 and the h323 ID.
Is there a way to prevent it from using the System name as a possible H.323 route?
So there is no method that you have found to prevent the C-Series from registering this extra Alias for h.323. The reason being is that I have my SIP URI set to be "system name"@example.com and it seems as though a lot of calls between C-series endpoints are being interworked because when calls are being setup to the SIP URI of ULemail@example.com it matches my rule 48 which strips everything after the @ symbol for searching calls registered with just e.164. Since UL-c90-1 is a valid alias i find the call is being routed as an h.323 call instead of continuing to the next rule that routes based on full SIP URL firstname.lastname@example.org
I hope your following my logic as I read through the paragraph above its tough to explain.
In a nutshell it would be great if there was a way to just make the c-series not register it's system name as an alternate e.164 alias.
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...
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 discusses the bas...