When i configure AAR on a Callmanager 5.1.3 you need to configure for each phone the External Phone Number Mask that contains the number to reroute over PSTN. Unfortunally this full number is being presented on the top of the phone displays rather than the short DN. Is there a way to present the DN Number instead and having AAR configured?
There are essentially two options, each with its own drawbacks:-
The first option will only technically work if your DNs match your DIDs, for example the last four digits of DID match the last four of the DN assigned to the line.
If this is the case then you can configure the external phone mask on the line to be only the actual DN and not the full E.164 number. Then within the AAR group configure the prefix including trunk access with the remaining digits of the full number. eg. DN is 6789 and DID 01234 123456789, the external phonemask would be 6789, and the AAR prefix would be 90123412345
The second alternative or work-around to display the DN is only applicable if your DIDs do not match you DNs and you have translations to transform the incoming number to DN. eg DID is 01234 12346789, DN is 1789.
Simply configured the external phone mask with the complete number, and then configure the line text to be the DN. The full number will still appear at the top of the phone display, but you will also have the extension number indicated on the line.
Both options has been considered already, but unfortunally they are not suitable for this customer. The last 4 digits of DID do not match comletely with the DN, only the last 3 digits from 4. Option 2 has been suggested to the customer, but this is not accepted for a unknown reason. As this was a migration from version 4.0.2a to 5.1.3 they are stating that this has been configured with the short DN on top previously and they want it to have it exactly the same way. Is there another way to configure PSTN rerouting after 4 calls going over the WAN? The H323-gateway configs have not been changed during migration.
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...