This is usual because the gateway has been assigned to a Route patterns. Check your route patterns and see which one this gateway has already been assigned to. Remove the gateway and then you can add it to a route group
Please rate all useful posts
"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
aokanlawon is correct (+5), to quickly see which route patterns use this GW directly (not a good practice) you can use dependency records (upper right corner drop box) assuming you have dependency records enabled via enterprise parameters.
thank you so much all , i found the issue , the sub unit wasn't in a device pool , it eas in none device pool ,and when i change the device pool coinfiguration for this port , the decice appeared in the list
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...