08-24-2011 05:52 PM - edited 03-17-2019 10:27 PM
Scenario:
Can successfully place calls through Polycom VBP (video border proxy) from MXP endpoint via straight alias....
format: numeric prefix followed by ip address....xxxx@<ipaddress of vbp>
Scenario:
Can successfully place calls through Polycom VBP (video border proxy) from from Codian-4210 MCU
once vbp is set up as gateway on MCU and gateway is selected when adding participant to conference.
To the point...how can I dial from TMS to connect one of my endpoints through the vbp via alias in a schedule conference???
Not 100% sure of far end topology, but I would assume there's a gateway behind the vbp or built into it?
08-28-2011 08:41 PM
I set up a manual address book in TMS, and created an entry for the site. In the entry I used the dial string of xxxx@
When building conference, once manual entry is added as participant, TMS gives error of: No route possible between participants.
???
08-28-2011 11:46 PM
Could you try to set "Use Flat H.323 Dialling Plan When Routing Call" (TMS > Administrative Tools > Configuration > Conference Settings) to yes.
TMS Online help:
Use Flat H.323 Dialling Plan When Routing Calls
The Flat H.323 Dial Plan option is used to disable the Gatekeeper neighbor checking logic in call routing.
On: Configures Cisco TMS to assume a 'flat' dial plan, where all aliases can be dialed without prefixes no matter which Gatekeeper a device is registered to. When set to On, no Gatekeeper comparison is done in call routing. This is useful for situations where Cisco TMS is not managing the Gatekeepers so the neighbor checking can not be performed, or where Gatekeepers are not direct neighbors to each other (hierarchical or multi-legged paths).
Neighbor Zone prefixes read from Gatekeepers are not used in call routing when this option is set to On.
Off: Cisco TMS determines if gatekeepers are compatible by checking if the call participants are registered to the same gatekeeper or the gatekeepers are direct neighbors. Cisco TMS determines if an alias can be reached between gatekeepers and to insert E.164 dialing prefixes for neighbor zones if required by the gatekeeper's configuration. If Cisco TMS fails this neighbor check, it is assumed the call can not be made with H.323 aliases and alias options will not be given as a valid call routes.
Please vote the answers and set them to answered if they are.
Please remember to rate helpful responses and identify
08-29-2011 01:11 PM
Setting was/is set to Yes. (Use Flat H.323 Dialling Plan When Routing Call)
Thanks for your reply and effort to help
Any other ideas?
09-12-2011 08:41 PM
Mark,
I think you have to set the dial string to xxxx##
Polycom doesn't use @ in the uri, they use ## .
-AA
09-13-2011 05:55 PM
Thanks so much for the reply Ahmed, but changing the dial string did not resolve the issue.
Any other advice?
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