I have centralized our in/out pstn lines at one location. At every other location I have on or two backup pots trunks to be used by srst in case of T1 or Call Manager failure. They are also used for 911 calls so that the e911 center gets the correct address to respond to.
One location is using an old main incomming pots trunk for their backup line. Their main incomming phone number was changed 10 years ago, but the old number was kept active for those who just don't seem to update their phone lists.
Lately, the attendants have been surprised, and a little bit panicky, to be receiving calls showing up on their callerid display (7960 phone) as being from 9911. These calls are coming in from the backup pots lines. How do I change the display to something less conspicuous?
Here are the pertinent configurations (3660 & CM 3.3):
I beleive that the reason why the calls appear to be coming from 9911 is because there is no dial peer configured specifically for inbound call legs. While trying to match the call to an inbound call leg, the router finally defaults to any dial-peer associated with the source port, which in your case is 1004.
And in the abssnce of any ANI information, the destination pattern of the inbound call leg is used. To prevent this, create another dial peer that includes the command "incoming called-number .". This will match on the inbound call leg and the calls will come in with a blank ANI.
If you want to put an ANI on those calls, you can enter it as a destination pattern on that inbound call leg. Just make sure that it doesn't effect the routing of your other calls.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.