I think that the optimum way to do this would be to ask your carrier/provider to re-map 8420000 to point towards 2987135. We do this type of change all the time. Make sure you indicate to them the number of simultaineous calls you wanted routed to 2987135 in this method.
If I understand you correctly here is my thoughts.
The when someone calls 842000 telco is remapping this to 2987000 and hunting across the other numbers. The problem is that the number getting passed to the circuit is 2987000 not 842000. With that said if you can't get the telco involved I don't think anything can be done. If you can then do this have them not do a roll on the number 842 and included that in your did block. That way you'll see 842000 come in on the circuit at that point you can add a translation partern in cm to send it where every it needs to go.
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...