I know that the statement from Cisco is that they do not support inbound caller-id when using FXO ports with MGCP, however, this is a really big safety issue for a lot of clients. I have many schools running Cisco voice systems with only FXO connectivity to the PSTN (PRI is far too expensive for their deployments). In a school environment, caller-id is an important safety feature when faced with things like bomb threats, etc. Most school systems in this area can not/do not employ staff with enough skills/knowledge to be able to manage an IOS environment. This makes an H.323 gateway configuration problematic, particularly when talking about needing to route calls to different end points based upon port, when connecting PA systems to the voice system via FXO, etc. Is there ANY way to make the inbound caller-id work with MGCP? This seems like a MAJOR flaw in Cisco's product. All phone systems have had this capability for years. Why would Cisco feel that they have no obligation to make this work? It's simply a matter of updating software. Isn't that one of the benefits of a VoIP system (the fact that it can be modified with new software updates)? This is a particularly annoying problem for me, as I have yet to find a TAC engineer that can help me to put an H.323 configuration in place that functions as one particular client needs it to. Each time a TAC engineer attempts to help with the process, we experience a long outage of PSTN connectivity, and the end result is that I have to delete the H.323 configuration, and then reconfigure everything back to MGCP. WHAT CAN BE DONE TO RESOLVE THIS?!?!?
Thank you for any assistance that you might be able to provide.