×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

How to remove @domain from VCS H.323 call payload ?

Unanswered Question
Nov 13th, 2014
User Badges:

Hi

I have a VCS-C and VCS-E setup and wish to call an external Polycom VBP that is not using @domain in

its gatekeeper registrations.

Is there any way to alter/transform only the call payload to E.164 only, but yet retain the full [email protected]

for call routing ?

I believe Polycom VBPs call it ' Send parsed ANNEX O string Outbound '.

I have a large number of sites that work this way and I am trying to avoid asking all of them to manipulate their incoming

strings.

Thoughts ? :)

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Jens Didriksen Fri, 11/14/2014 - 13:29
User Badges:
  • Blue, 1500 points or more

This from their release notes; "In certain solutions with older 
VBP VOS it may be desired to revert the outbound ANNEX O [email protected] string to be modified and sent as the user portion only. This option is only needed when dialing ANNEX O destinations to VBP VOS 7.2.2 from VBP VOS 11.2.x systems."

So doesn't look like it applies to your deployment? What happens if you use [email protected]_address instead of domain?

Another option would be to neighbour your VCS-E with the VBP, use a prefix to send all calls to that destination directly to that neighbour zone; i.e. if the address is [email protected], and you add a prefix, say, #01, you would dial #0112345, then strip #01 so it'll only use 12345 for the call proper..

/jens

Please rate replies and mark question(s) as "answered" if applicable.

 

rouellette Fri, 11/14/2014 - 13:41
User Badges:

Thanks for the reply !

A Polycom solution is feasible, but I would prefer to fix the issue at the single source (Cisco VCS-E)

The Polycom sites I speak of, are often technically weak and independent, so making changes to each site (over 100) is a lot of work and coordination, not to mention the disruption of service.

Nonetheless, I thank you for your input :) 

Jens Didriksen Fri, 11/14/2014 - 14:08
User Badges:
  • Blue, 1500 points or more

"A Polycom solution is feasible, but I would prefer to fix the issue at the single source (Cisco VCS-E)"

Neighbouring will do that, but it looks like you'll have to create a lot of neighbour zones, which might not, in your case, be practical either.

/jens

Please rate replies and mark question(s) as "answered" if applicable.

 

Actions

This Discussion