Hi. I have a 2600 (12.1(5)) hooked in to my CM with a T1PRI for calls. I have found out that if you call our unpublished yet accessible incomming "DID" number from the outside, you get a local dialtone, and it allows for outgoing calls with the 9T destination pattern. Also, I think my dial-peers may be a bit messy... can anyone help me with them?
May be the cause of your dialtone upon calling the DIDs.
Seems unnecessary - try removing it.
You should only need one dial peer for incoming called numbers. Just set it to a single "." and leave the "direct-inward dial" statement. This should clean things up and get rid of your tollfraud issue as well. Unless you have matching DIDs in your Call Manager, you will get some kind of 'out of service' message when calling in.
Also, a VOIP peer with a destination pattern like [1-6].. would cover all three of your proposed VOIP peers.
Assuming you are using Call Manager and you have a multi-server cluster, don't forget a VOIP peer pointing to your 'backup' Call Managers.
The problem is you are being too specific with the destination pattern.
The peers with destination pattern & incoming called number only covers 2... , 3... & 6... This leaves a gap whereby if a number outside these ranges is available on your PRI then it will not get DID to Call Manager. I would simplify to something like below and retry
dial-peer voice 1 pots
dial-peer voice 100 voip
destination-pattern .T (This will catch all incoming calls)
Since you have DID functionality from your PSTN the you can just define pots the handles your incoming call leg. Assuming, you get 4 digits from the PSTN and use this as local no. for your IP Phones, let say the digits you get from your PSTN varies from 83XX to 84XX.
You can configure you voice gateway something like this:
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
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...