unable to connect MCU 5310 when we are trying to Bridge getting "Error Unknown address error"

[Rob bakshi]

We are facing issues from one of US VC device MX 200 that they are unable to connect to the VC meeting as they get “unknown address error” when dialing through bridge in 5310.

Endpoint is in USA and Registered to India gatekeeper.

They are trying to join the Bridge call i.e is in MCU 5310

Please help me out to resolve the issue.

Regards,

Robin Chibber

[Wayne DeNardi]

Hi Robin,

Can you please priovide us with some more information on the topology and call details, such as:

Where is the MCU?  In the USA, or India?  Is the MCU registered to the same "gatekeeper" as the MX endpoint?  Is your "gatekeeper" a Cisco VCS, or something else?

What call protocol are you using?  SIP, H.323, or a combination of the two with Interworking being done?

Are you able to call the MX from the MCU, or does it not work in that direction either?

Are there any log messages you can provide from the endpoint?

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

[Rob bakshi]

Hi Wayne,

 MCU 5320 is in India and Registered to India VCS and the USA endpoint is also registered in India Gatekeeper...yes our Gatekeeper is Cisco VCS as for internal Network..WAN interface over MPLS network.

They are using both Protocols H.323 and SIP. Yes inter networking has been enabled in VCS.

They could not able to call to MCU.they are getting Error unknown address when they are trying point to point call then it's working for any location.

sure i will provide the logs once i will take from endpoint.

[Wayne DeNardi]

Thanks Robin,

How are they trying to call the MCU?  What address are they dialling?  Does the address that they're dialling match how the MCU is registered to the VCS?

Are other endpoints (in India) that are registered to the same VCS able to dial the same address the people in the US are dialling?

If the MCU is H.323 registered, does it work if you set the call type on the endpoint to H.323 as well (if it is registered as H.323) rather than leaving it as "Auto" which can often try via SIP first on a dual-registered endpoint?

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.