cisco vcs Interworking No permission

[Firdaush Ginowrie]

Hello,

Call details on the VCS-E :

marnove02 - Call details

Bandwidth node	Default zone
Source alias 1	HDX_Systeam (H323Id)
Source alias 2	54271 (E164)
Target alias 1	74002 (E164)
Protocol	H323
Address	IP
Encryption type	None
Reason	No permission
Cause	Interworked
Additional cause	Insufficient privilege

It's due to an inbound call from an endpoint behing Polycom infras.

How do you interpret the "reason" ?

Regards,

Firdaush

[Patrick Sparkman]

Where is the other endpoint located, is it registered to your VCS-C or VCS-E?

I've seen some instances where interworking will fail if the call is going through the VCS-E and it's set to interwork registered endpoints only, which is the default setting.  What happens if you set interworking on the VCS-E under Configuration > Protocols > Interworking, to on instead of registered only?

[Firdaush Ginowrie]

There is no endpoint registration neither on the VCS-C nor the VCS-E.

The interworking is alreaty set ON.

[Lawrence James · Accepted solution]

Is this correct Neither endpoint is registered to your VCS-C or VCS-E?

[Firdaush Ginowrie]

YES

[Lawrence James]

Can the near end (NE) system call the far end Polycom (FE) by Alias?

Can they call  each other by IP?

What happens in each case?

Have you looked at your Traversal Zone? Did your VCS Control even see the call?

[Firdaush Ginowrie]

Hello Lawrence,

Can the near end (NE) system call the far end Polycom (FE) by Alias?

Reply: Call is made through TMS by calling IP@domain.com

Can they call  each other by IP?

Reply: NO

Have you looked at your Traversal Zone? Did your VCS Control even see the call?

The VCS see the call.

487 Request terminated