I am new in VoIP area (not in networking), so my first task is simple :-)
I have 1750 with VIC-2FXO connected to PABX (IP=192.168.1.91). I also have two ATA-186 in remote locations (IP1=192.168.2.99, IP2=192.168.3.99). I need to make it as simple as possible (from users standpoint of view):
- Incoming calls (from PABX) to port 2/0 directed to user1
- Incoming calls (from PABX) to port 2/1 directed to user2
- Outgoing calls (from user1) directed to port 2/0 ONLY
- Outgoing calls (from user2) directed to port 2/1 ONLY
- Only IP1=192.168.2.99 and IP2=192.168.3.99 could make calls to 1750 for VoIP connection
- Only IP=192.168.1.91 could make calls to ATA
I have no problems with 1st two tasks (using "connection plar opx 11", "destination-pattern 11" and "session target ipv4:192.168.2.99") -please, see config at the bottom of the message.
I was able to do setup where user1 pickups the phone, hears the tone from ATA, dials "9#" and hears the tone from PABX via port 2/0
It is not good solution, because after he dials "8#" he hears the tone from PABX via port 2/1 and users want to hear tone from PABX not dialing anything.
Is it the way to setup this configuration to allow user1 to pickup the phone and hear the tone from PABX via port 2/0 (not from ATA) not dialing anything? (Similar for user2)
Is it the way to solve task #5 without using ACL's? If ACL is the only solution, which ports do I need to open?
I have no idea how to configure ATA to allow calls only from 192.168.1.91
In your configuration IP address 192.168.1.91 has been assigned to which interface. And also in your configuration dial-peer voice 2 and 12 has the same session target of 192.168.1.99. Could you please elaborate the question in detail.
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...