Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
10350
Views
15
Helpful
25
Replies

VCS Search Rules and Polycom

Go to solution
Rod.Blackie
Level 1
Level 1

‎02-02-2012 02:26 AM - edited ‎03-17-2019 10:46 PM

Hi Netpro's

I have an interesting problem. Since upgrading from v4 to v7 I can't dial polycom systmes that have the format IP##Alias (90.12.132.12##9016)

I have a search rule on my VCSE that looks like this (rule name=polycom test ! source=any ! mode=alias pattern match ! pattern type=regex ! pattern string=(^.*)##(.*) ! pattern behaviour=leave ! on match=continue ! target=trav-zone

When I use the locate tool the IP##Alias is routed correctly - brilliant no problems....

However when I use the same search rule on my VCS it doesn't route out via the traversal zone. Instead the local zone picks it up and the call can't be placed from my local endpoints.

I can place IP calls ok, I can place alias@IP calls ok - just not IP##alias calls...

Below is the print out from the failed locate look up on the VCS and I've attached my search rules - can anyone shed some light for me please?

  • Search (16)
    • State: Completed
    • Found: True
    • Type: H323 (LRQ)
    • CallRouted: True
    • CallSerial Number: ab2dc1bc-4d87-11e1-ae81-0010f31a4464
    • Tag: ab2dc298-4d87-11e1-a06f-0010f31a4464
    • StartTime: 2012-02-02 10:21:28
    • Duration: 0.48
    • Source (1)
      • Authenticated: False
      • Aliases (1)
        • Alias (1)
          • Type: H323Id
          • Origin: Unknown
          • Value: xcom-locate
      • Zone (1)
        • Name: LocalZone
        • Type: Local
    • Destination (1)
      • Alias (1)
        • Type: H323Id
        • Origin: Unknown
        • Value: 90.80.109.47##9016
    • SubSearch (1)
      • Type: Transforms
      • Action: Not Transformed
      • ResultAlias (1)
        • Type: H323Id
        • Origin: Unknown
        • Value: 90.80.109.47##9016
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • ResultAlias (1)
          • Type: H323Id
          • Origin: Unknown
          • Value: 90.80.109.47##9016
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • ResultAlias (1)
            • Type: H323Id
            • Origin: Unknown
            • Value: 90.80.109.47##9016
          • SubSearch (1)
            • Type: Search Rules
            • SearchRule (1)
              • Name: traversal-ALIAS
              • Zone (1)
                • Name: Nuvia-trav-zone
                • Type: TraversalClient
                • Protocol: H323
                • Found: False
                • Reason: Destination not found
                • Gatekeeper (1)
                  • Address: 86.12.153.205:6001
                  • Alias (1)
                    • Type: H323Id
                    • Origin: Unknown
                    • Value: 90.80.109.47##9016
            • SearchRule (2)
              • Name: Polycom Test
              • Zone (1)
                • Name: Nuvia-trav-zone
                • Type: TraversalClient
                • Protocol: H323
                • Found: False
                • Reason: Destination not found
                • Gatekeeper (1)
                  • Address: 86.12.153.205:6001
                  • Alias (1)
                    • Type: H323Id
                    • Origin: Unknown
                    • Value: 90.80.109.47##9016
            • SearchRule (3)
              • Name: default-01
              • Zone (1)
                • Name: LocalZone
                • Type: Local
                • Protocol: H323
                • Found: True
                • Gatekeeper (1)
                  • Address: 10.118.6.22:0
                  • Alias (1)
                    • Type: H323Id
                    • Origin: Unknown
                    • Value: 90.80.109.47##9016
1 person had this problem
Labels:
Preview file
23 KB
0 Helpful
25 Replies 25

Go to solution
Paulo Souza
VIP Alumni
VIP Alumni
In response to Paulo Souza

‎02-02-2012 07:32 AM

Rod,

If you put here the "network logs" and "event logs" I will be able to try find out the reason why VCS is showing "

"unidentified reason" in the history.

Regards,

Paulo Souza

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
0 Helpful

Go to solution
Rod.Blackie
Level 1
Level 1
In response to Paulo Souza

‎02-02-2012 07:35 AM

Ok Paulo I will however I will wait 5 minutes before testing as I've been trying so many things the logs will be full of nonsense.

Thanks

0 Helpful

Go to solution
Rod.Blackie
Level 1
Level 1
In response to Paulo Souza

‎02-02-2012 07:34 AM

Hi Paulo

Thats correct it is (NOW) acting as it should. The remote end isn't anything to do with my company. Its a Polycom endpoint that sits behind a Gateway.

Why can't we configure our Tandberg - Sorry Cisco kit to forward the 90.80.109.47##9016 address so that the Polycom system picks it up?

Thanks.

0 Helpful

Go to solution
Paulo Souza
VIP Alumni
VIP Alumni
In response to Rod.Blackie

‎02-02-2012 07:44 AM

Rod,

You you have a gateway in fard end, you can do this:

Create a Neighbor Zone towards the remote gateway "90.80.109.47".

Then you create a search rule and point it to that new Neighbor Zone.

I think that, by doing this, you will be able to route the call correctly. But Don't forget to change the translation that you actually have in VCS-C, which Andreas suggested.

Regards,

Paulo Souza

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".

Go to solution
Rod.Blackie
Level 1
Level 1
In response to Paulo Souza

‎02-02-2012 07:58 AM

Hi Paulo

I don't have any control over the Polycom system. The funny thing is that we used to be able to call 90.80.109.47##9016 systems when we were running 5.2 on the VCS. Somethings changed in V7x that stops us calling those endpoints. This new rule that's been created as per Andreas suggestions was never part of the 5.2 config - calls just used to route out ok.

I've attached the logs showing a calls thats been placed from our MCU to 90.80.109.47##9016

Thanks.

Event Log

Feb 2 15:45:30          tvcs: Event="Call Rejected" Service="H323" Src-ip="10.118.6.24" Src-port="64403" Src-alias-type="H323" Src-alias="MCU" Src-alias-type="E164" Src-alias="72" Dst-alias-type="H323" Dst-alias="90.80.109.47##9016" Call-serial-number="eef02890-4db4-11e1-b576-0010f31a4464" Tag="eef029b2-4db4-11e1-99a1-0010f31a4464" Protocol="TCP" Response-code="Bad Request" Level="1" UTCTime="2012-02-02 15:45:30,003"

Feb 2 15:45:30          tvcs: Event="Search Completed" Service="H323" Src-alias-type="H323" Src-alias="MCU" Src-alias-type="E164" Src-alias="72" Dst-alias-type="H323" Dst-alias="90.80.109.47##9016" Call-serial-number="eef02890-4db4-11e1-b576-0010f31a4464" Tag="eef029b2-4db4-11e1-99a1-0010f31a4464" Detail="found:FALSE, searchtype:Setup" Level="1" UTCTime="2012-02-02 15:45:30,002"

Feb 2 15:45:29          licensemanager: Level="INFO" Detail="License granted" local_call_id="eef02890-4db4-11e1-b576-0010f31a4464" lic_type="traversal" UTCTime="2012-02-02 15:45:29,773"

Feb 2 15:45:29          tvcs: Event="Search Attempted" Service="H323" Src-alias-type="H323" Src-alias="MCU" Src-alias-type="E164" Src-alias="72" Dst-alias-type="H323" Dst-alias="90.80.109.47##9016" Call-serial-number="eef02890-4db4-11e1-b576-0010f31a4464" Tag="eef029b2-4db4-11e1-99a1-0010f31a4464" Detail="searchtype:Setup" Level="1" UTCTime="2012-02-02 15:45:29,757"

Feb 2 15:45:29          tvcs: Event="Call Attempted" Service="H323" Src-ip="10.118.6.24" Src-port="64403" Src-alias-type="H323" Src-alias="MCU" Src-alias-type="E164" Src-alias="72" Dst-alias-type="H323" Dst-alias="90.80.109.47##9016" Call-serial-number="eef02890-4db4-11e1-b576-0010f31a4464" Tag="eef029b2-4db4-11e1-99a1-0010f31a4464" Protocol="TCP" Auth="YES" Level="1" UTCTime="2012-02-02 15:45:29,756"

Feb 2 15:45:29          tvcs: Event="Search Completed" Service="H323" Src-alias-type="H323" Src-alias="MCU" Src-alias-type="E164" Src-alias="72" Dst-alias-type="H323" Dst-alias="90.80.109.47##9016" Call-serial-number="eef02890-4db4-11e1-b576-0010f31a4464" Tag="eef029b2-4db4-11e1-99a1-0010f31a4464" Detail="found:TRUE, searchtype:ARQ" Call-routed="YES" Level="1" UTCTime="2012-02-02 15:45:29,732"

Feb 2 15:45:29          tvcs: Event="Search Attempted" Service="H323" Src-alias-type="H323" Src-alias="MCU" Src-alias-type="E164" Src-alias="72" Dst-alias-type="H323" Dst-alias="90.80.109.47##9016" Call-serial-number="eef02890-4db4-11e1-b576-0010f31a4464" Tag="eef029b2-4db4-11e1-99a1-0010f31a4464" Detail="searchtype:ARQ" Level="1" UTCTime="2012-02-02 15:45:29,600"

Feb 2 15:44:42          syslogd 1.5.0: restart (remote reception).

Network Log

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,763" Module="network.search" Level="INFO": Detail="Considering search rule 'default-01' towards target 'LocalZone' at priority '103' with alias '90.80.109.47##9016'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,762" Module="network.search" Level="INFO": Detail="Considering search rule 'Polycom Test' towards target 'Nuvia-trav-zone' at priority '99' with alias '9016@90.80.109.47'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,760" Module="network.search" Level="INFO": Detail="Considering search rule 'traversal-ALIAS' towards target 'Nuvia-trav-zone' at priority '50' with alias '90.80.109.47##9016'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,760" Module="network.search" Level="INFO": Detail="Search rule 'local URI' did not match destination alias '90.80.109.47##9016'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,760" Module="network.search" Level="INFO": Detail="Search rule 'default' did not match destination alias '90.80.109.47##9016'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,760" Module="network.search" Level="INFO": Detail="Search rule 'Traversal-IP' did not match destination alias '90.80.109.47##9016'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,760" Module="network.search" Level="INFO": Detail="Search rule 'DNS search rule' did not match destination alias '90.80.109.47##9016'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,757" Module="network.h323" Level="INFO": Dst-ip="10.118.6.24" Dst-port="64403"

Detail="Sending H.225 Proceeding "

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,755" Module="network.h323" Level="INFO": Src-ip="10.118.6.24" Src-port="64403"

Detail="Received H.225 Setup H.323v5 Bandwidth:4032kbps DestAlias:90.80.109.47##9016 DestCSAddr:['IPv4''TCP''10.118.6.22:1720'] Vendor:Codian"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,732" Module="network.h323" Level="INFO": Dst-ip="10.118.6.24" Dst-port="2222"

Detail="Sending RAS ACF SeqNum=24772 Bandwidth=4032Kb/s CS address=10.118.6.22:1720 DestAlias='90.80.109.47##9016' "

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,732" Module="network.h323" Level="INFO": Src-ip="86.12.153.205" Src-port="6001"

Detail="Received RAS LCF SeqNum=60804 DestAlias='9016@90.80.109.47' CS address=86.12.153.205:1720 RAS address=86.12.153.205:1719 Bandwidth=4032Kb/s "

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,723" Module="network.h323" Level="INFO": Src-ip="86.12.153.205" Src-port="6001"

Detail="Received RAS RIP SeqNum=60804 Delay=60000"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,720" Module="network.h323" Level="INFO": Dst-ip="86.12.153.205" Dst-port="6001"

Detail="Sending RAS LRQ SeqNum=60804 DestAlias='9016@90.80.109.47' Bandwidth=4032Kb/s SrcAlias='MCU' Hopcount=15 "

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,719" Module="network.h323" Level="INFO": Src-ip="86.12.153.205" Src-port="6001"

Detail="Received RAS LRJ SeqNum=60803 Reason='not registered' AdditionalCauseCode='destination not found' "

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,625" Module="network.sip" Level="INFO": Src-ip="127.0.0.1" Src-port="5060" Detail="Receive Response Code=200, Method=NOTIFY, To=sip:David.Dunn@nuvia.co.uk, Call-ID=8d7168e8461ac44f@10.118.26.17"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,624" Module="network.sip" Level="INFO": Dst-ip="127.0.0.1" Dst-port="25000" Detail="Sending Response Code=200, Method=NOTIFY, To=sip:David.Dunn@nuvia.co.uk, Call-ID=8d7168e8461ac44f@10.118.26.17"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,624" Module="network.sip" Level="INFO": Src-ip="10.118.26.17" Src-port="1652" Detail="Receive Response Code=200, Method=NOTIFY, To=sip:David.Dunn@nuvia.co.uk, Call-ID=8d7168e8461ac44f@10.118.26.17"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,610" Module="network.h323" Level="INFO": Src-ip="86.12.153.205" Src-port="6001"

Detail="Received RAS RIP SeqNum=60803 Delay=60000"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,607" Module="network.h323" Level="INFO": Dst-ip="86.12.153.205" Dst-port="6001"

Detail="Sending RAS LRQ SeqNum=60803 DestAlias='90.80.109.47##9016' Bandwidth=4032Kb/s SrcAlias='MCU' Hopcount=15 "

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,606" Module="network.search" Level="INFO": Detail="Considering search rule 'default-01' towards target 'LocalZone' at priority '103' with alias '90.80.109.47##9016'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,604" Module="network.search" Level="INFO": Detail="Considering search rule 'Polycom Test' towards target 'Nuvia-trav-zone' at priority '99' with alias '9016@90.80.109.47'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,603" Module="network.search" Level="INFO": Detail="Considering search rule 'traversal-ALIAS' towards target 'Nuvia-trav-zone' at priority '50' with alias '90.80.109.47##9016'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,603" Module="network.search" Level="INFO": Detail="Search rule 'local URI' did not match destination alias '90.80.109.47##9016'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,603" Module="network.search" Level="INFO": Detail="Search rule 'default' did not match destination alias '90.80.109.47##9016'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,603" Module="network.search" Level="INFO": Detail="Search rule 'Traversal-IP' did not match destination alias '90.80.109.47##9016'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,603" Module="network.search" Level="INFO": Detail="Search rule 'DNS search rule' did not match destination alias '90.80.109.47##9016'"

Feb 2 15:45:29          tvcs: UTCTime="2012-02-02 15:45:29,599" Module="network.h323" Level="INFO": Dst-ip="10.118.6.24" Dst-port="2222"

Detail="Sending RAS RIP SeqNum=24772 Delay=60000"

VCS-C Search

Search (200)

State: Completed

Found: True

Type: H323 (ARQ)

CallRouted: True

CallSerial Number: eef02890-4db4-11e1-b576-0010f31a4464

Tag: eef029b2-4db4-11e1-99a1-0010f31a4464

StartTime: 2012-02-02 15:45:29

Duration: 0.13

Source (1)

Authenticated: True

Aliases (1)

Alias (1)

Type: H323Id

Origin: Endpoint

Value: MCU

Alias (2)

Type: E164

Origin: Endpoint

Value: 72

Zone (1)

Name: LocalZone

Type: Local

Path (1)

Hop (1)

Address: 10.118.6.24

Destination (1)

Alias (1)

Type: H323Id

Origin: Unknown

Value: 90.80.109.47##9016

SubSearch (1)

Type: Transforms

Action: Not Transformed

ResultAlias (1)

Type: H323Id

Origin: Unknown

Value: 90.80.109.47##9016

SubSearch (1)

Type: Admin Policy

Action: Proxy

ResultAlias (1)

Type: H323Id

Origin: Unknown

Value: 90.80.109.47##9016

SubSearch (1)

Type: FindMe

Action: Proxy

ResultAlias (1)

Type: H323Id

Origin: Unknown

Value: 90.80.109.47##9016

SubSearch (1)

Type: Search Rules

SearchRule (1)

Name: traversal-ALIAS

Zone (1)

Name: Nuvia-trav-zone

Type: TraversalClient

Protocol: H323

Found: False

Reason: Destination not found

Gatekeeper (1)

Address: 86.12.153.205:6001

Alias (1)

Type: H323Id

Origin: Unknown

Value: 90.80.109.47##9016

Zone (2)

Name: Nuvia-trav-zone

Type: TraversalClient

Protocol: SIP

Found: False

Reason: Internal Server Error

Gatekeeper (1)

Address: 86.12.153.205:7001

Alias (1)

Type: H323Id

Origin: Unknown

Value: 90.80.109.47##9016

SearchRule (2)

Name: Polycom Test

Zone (1)

Name: Nuvia-trav-zone

Type: TraversalClient

Protocol: H323

Found: True

Gatekeeper (1)

Address: 86.12.153.205:6001

Alias (1)

Type: H323Id

Origin: Unknown

Value: 9016@90.80.109.47

VCS-E SEARCH

Search (201)

State: Completed

Found: False

Reason: Unreachable destination

Type: H323 (Setup)

CallSerial Number: ef07c0e0-4db4-11e1-b5b8-0010f31a4570

Tag: eef029b2-4db4-11e1-99a1-0010f31a4464

StartTime: 2012-02-02 15:45:29

Duration: 0.22

Source (1)

Authenticated: False

Aliases (1)

Alias (1)

Type: H323Id

Origin: Unknown

Value: MCU

Alias (2)

Type: E164

Origin: Unknown

Value: 72

Zone (1)

Name: Nuvia-trav-zone

Type: TraversalServer

Destination (1)

Alias (1)

Type: H323Id

Origin: Unknown

Value: 9016@90.80.109.47

SubSearch (1)

Type: Transforms

Action: Not Transformed

ResultAlias (1)

Type: H323Id

Origin: Unknown

Value: 9016@90.80.109.47

SubSearch (1)

Type: Admin Policy

Action: Proxy

ResultAlias (1)

Type: H323Id

Origin: Unknown

Value: 9016@90.80.109.47

SubSearch (1)

Type: FindMe

Action: Proxy

ResultAlias (1)

Type: H323Id

Origin: Unknown

Value: 9016@90.80.109.47

SubSearch (1)

Type: Search Rules

CallsToUnknownIPAddresses (4)

Mode: Direct

Found: True

Zone (1)

Name: DefaultZone

Type: Default

Protocol: H323

Found: False

Reason: Unreachable destination

Gatekeeper (1)

Address: 90.80.109.47:1720

Alias (1)

Type: H323Id

Origin: Unknown

Value: 9016@90.80.109.47

SearchRule (1)

Name: LocalZoneMatch

Zone (1)

Name: LocalZone

Type: Local

Protocol: H323

Found: False

Reason: Not Found

Gatekeeper (1)

Address: 86.12.153.205:0

Alias (1)

Type: H323Id

Origin: Unknown

Value: 9016@90.80.109.47

Zone (2)

Name: LocalZone

Type: Local

Protocol: SIP

Found: False

Reason: Not Found

Gatekeeper (1)

Address: 86.12.153.205:0

Alias (1)

Type: H323Id

Origin: Unknown

Value: 9016@90.80.109.47

0 Helpful

Go to solution
awinter2
Level 7
Level 7
In response to Rod.Blackie

‎02-02-2012 07:59 AM

Rod,

using the "90.80.109.47##9016" syntax for dialing an H323 device is not a standards-based way of doing things, this is Polycom's approach to extension dialling which the VCS does not understand without modifying the alias to an 'Extension@IP' format.

Assuming that the 90.80.109.47 device receives the H225 SETUP message from the VCS-E, what does it do with the SETUP message? Is there a way which you can configure this far end device to strip off the '@90.80.109.47' portion of the dialled number and route the call to the 9016 extension?

Regards

Andreas

Go to solution
Paulo Souza
VIP Alumni
VIP Alumni
In response to awinter2

‎02-02-2012 08:10 AM

Rod,

I made a test here with my VCS Expressway. The fard end is really a G323 Gateway/Gatekeeper. I sent to it a LRQ message and it answered with a LCF message.

I created a neighbor zone to that gateway and asearch rule point to that neighbor zone, see:

Note that fard end gateway does not answer to SIP messages, so I think it's just a H323 gateway. That's why it did not accept the URI 9016@90.80.109.47.

Note another thing: Into search rule configuration, I will send just the 9016 alias to far end gateway. I tried to send the whole address "90.80.109.47##9016", but the gateway is not expecting receive it. It's expecting receive just the alias 9016.

Try to do that test, see if it works.

Regards

Paulo Souza

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
0 Helpful

Go to solution
Rod.Blackie
Level 1
Level 1

‎02-02-2012 08:11 AM

Andreas / Paulo

Firstly many thanks for your help on this - its appreciated.

From what you are saying there is an underlying issue when trying to directly call Polycom systems located behind gateways in that Cisco/Tandberg systems will not be able to contact them unless some transform / search rule is set up on the Polycom gateway to strip the extension@IP format.

Is this correct?

Thanks

Rod

0 Helpful

Go to solution
Paulo Souza
VIP Alumni
VIP Alumni
In response to Rod.Blackie

‎02-02-2012 08:33 AM

Rod,

It's not correct.

The Cisco VCS Solution has features enough to work with most of the video conference system actually.

In your case, you should only create a neighbor zone to route the call correctly, because the far end is not and enpoint, it's a H323 gateway. I just did a test right now from a client registered to VCS-E, it worked, I am able to call the remote endpoint.

Please, use the below search rule, don't pay attention to the previous serach rule that I sent.

Regards,

Paulo Souza

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".

Go to solution
Rod.Blackie
Level 1
Level 1
In response to Paulo Souza

‎02-02-2012 08:42 AM

Paulo

Thank you very much - you've made my sore head disappear.. I could hug you for your efforts.I can not place calls to the Polycom system.

Thanks again to you and Andreas.

Rod

0 Helpful

Go to solution
Paulo Souza
VIP Alumni
VIP Alumni
In response to Rod.Blackie

‎02-02-2012 08:59 AM

Rod,

You have created the neighbor zone, right? Ok. Then you need to contact the administrator of the Polycom system and question him what pattern you must to send in the call request, weither be only "9016", or "90.80.109.47##9016" or everything else. Then you have to manipulate the routing and send to another system what it is expecting to receive. That's all.

I am happy for help you.

regards,

Paulo Souza

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
0 Helpful
Customers Also Viewed These Support Documents