05-09-2012 04:53 AM - edited 03-17-2019 11:09 PM
Hi Experts,
Just a quick Question, Has anybody implemented integration of VCS with Avaya Communications Managers to allow Avaya VOIP Calls to Cisco Endpoints ( Audio Only).
Is it possible? If yes, How is it possible and what are the requirements and necessary configurations required? Only SIP/H323 Trunk?
Looking forward for your Valuable Inputs.
Warm Regards,
Saurabh Gupta
05-10-2012 01:17 AM
Hi
I have seen an old, unofficial howto for how to connect a Nortel CS1000 to the VCS. Maybe that could help?
Configuration for VCS to work with Nortel CS1000:
This example has Nortel CS1000 with a SIP trunk to VCS. The domain of the CS1000 is nortel-dplab.com
Calls to VCS from Nortel arrive with a prefix ‘58’ that is stripped.
Most calls work, however there are a couple of known limitations and problems:
Limitations:
Problems:
When it comes to a Deployment Guide for Nortel there are currently no official ones. This is an un-official working guide taken from the Forums (http://forums.na.tandberg.int/forums/showthread.php?t=3516&highlight=nortel+vcs&page=2 )
Rough working guide to CS1K SIP trunk (use at own risk!). This assumes the Nortel guy is present - DON'T TOUCH THE PHONE SYSTEM!
Tested with Nortel i2000 series phones and i2050 soft-phone.
Tested with TANDBERG MXP, Polycom VSX/Viewstation, Netmeeting, xMeeting
CS1000 Release 5.5
VCS X3.1
These steps assume you have a working CS1000 environment, with SIP Peer Networking running, ESN's for each CS1000 that trunks to VCS.
Nortel Config:
1 - Create a steering code (CDP steering code or UDP location code) that routes calls to the VCS.
2 - For UDP, create a CDP L0 domain for the TANDBERG VCS. For CDP, select the L0 domain the VCS will be a member of.
3 - Setup a Gateway Endpoint for the VCS call signalling IP address, configured as Static SIP.
4 - Create a routing pattern on the L0 domain that contains the VCS, and if INAC (access code) is required, build the route pattern accordingly.
Nortel Side Complete.
VCS Config:
1 - Create a neighbor zone on the VCS for the CS1000
2 - Turn SIP on, transport TCP, H.323 off and point to the CS1000 (or multiple CS1000's)
3 - Turn "Searches automatically responde to:" to "On"
4 - Turn "Empty INVITE allowed:" to "Off"
5 - Set your route pattern to begin with either the UDP access code (numeric) or the CDP steering code (numeric) you previously configured on the CS1000 for the VCS.
Note, if using Uniform Dialing Plan (UDP), you will need to add a phone-context to the outgoing dialed string. This is accomplished with a regex transform set to replace.
For example, if my INAC/CDP Steering code was '99', and the phone-context on the CS1000 side is "nortel@nortel.com", a zone match/xform would be:
Pattern String: ^99(\d+) (any number starting with 99)
Replace String: 99\1;phone-context=nortel@nortel.com
6 - Create a transform on the VCS to strip the "phone-context" field for inbound calls to the VCS from the CS1000 (assume the DN Prefix on the CS1000 routing entries field was '99' and the phone-context is "nortel@nortel.com")
Pattern: ^99(\d+);phone-context=nortel@nortel.com(.*)
Replace: \1
7 - Force the VCS to route all traffic for this zone, including Media, via the CLI:
"xConf Zones Zone (n) Neighbor SIP MediaRouting Mode: Latching
Note, Latching media results in a higer success of DTMF in my limited testing. Still, DTMF from CS1000 phones to MXP endpoints does not work. DTMF from MXP to CS1000 services does work however.
05-10-2012 09:03 PM
Your tining is perfect
We're in the process of implementing Avaya VoIP so the above should make life a lot easier for me.
Brilliant.
/jens
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide