I think that you are mixing two different concepts.
The user must have the new zone CAC restriction or all calls from this new zone can be affected. It is a bad idea that the user don't follow the CAC restriction from that zone.
Another think is try to route the user with address 9000 from a zone with different prefix. I think that you would need a server that controls where are the mobile users, like that you can do with Cisco Emergency responder. I don't know what options you have in this section.
If you have only a h323 network where the gk do the address resolution and call routing, and all endpoints (the polycom clients) are registered in it, you don't need anymore.
The endpoint it register with thier e164 number and when they call to another h.323 endpoint the gk resolves the address. No zone prefix is needed.
another thing is that the endpoints go through a gw and this gw do the call routing.
I think also that you can not use the zone subnet command to choose the zone for the endpoint. This command is for select what RRQ acepts but you need to configure in the endpoint the zone to register. Has you tried it? All my polycom endpoints go to the same zone and can not choose the zone
I need the zone subnet command because I need that endpoints goes into specific zone based on their IP address ( network ):
- network 10.45.0.0 / 16 --> zone 1
- network 10.46.0.0 / 16 --> zone 2
Then I made CAC based upon different bandwidth requirements into each zone.
What I still miss is a client notification when there isn't enought bandwith, or better:
A client-A into zone-1 make a call to client-B into zone-2.
- If the bandwidth requirement for that call falls outside limitation imposed for zone-1 ( interzone bandwidth ), client-A get notification for "congestion" as we wanted.
- If the bandwidth requirement for that call falls outside limitation imposed for zone-2 ( interzone bandwidth configured for zone-2 ), client-A cannot make the call BUT he doesn't get any notification .
It seems the the client get notification only if that notification came from their zone. I also tryied the command "bandwidth check-destination" but with no result.
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...