VCS-E Traversal and non Traversal License Comsuption

[ansosa]

Hi all

I would like to know the exact number of licenses for a single call in the following scenario (Not SIP-to H323 necessary…)

Endpoint->Gatekeeper-> (Neighbored Zone) VCS-E ->(Traversal Zone)VCS-C->Endpoint

From my understanding we need the following licenses

For VCS-E: One Non Traversal + One Traversal Call license

For the VCS-C: One Non Traversal + One Traversal Call license

Is this Right?

Thanks for your Help

[Martin Koch]

GK = 1 (local call)

VCS-E (1 Traversal Call)

VCS-C (1 Traversal Call)

If you have more you most likely have some looping in your network (which can happen by findme, searchrules / transforms / ...)

or something is not optimal within your cluster if you have one.

[ansosa]

Hi Martin, Thanks a lot for your quick answer, I will Check for Loopings following your hints.

Regards.

[Martin Koch · Accepted solution]

What do you see now?

A screenshot of the active calls and the call details / search history of the calls would be handy to see.

Do you use a cluster?

[Tomonori Taniguchi]

Assume call scenario is H323 only as you include Gatekeeper in call flow.

Endpoint->Gatekeeper-> (Neighbored Zone) VCS-E ->(Traversal Zone)VCS-C->Endpoint

- GK: 1 x call license

- VCS-E: 1 x traversal call (H323 native call)

- VCS-C: 1 x traversal call (H323 native call)

(License consumption on VCS-C is still same even VCS-C is in cluster configuration.)

Here is overview of license consumption on VCS-E.

Note, from X7.0, VCS-E may handle non-traversal call by using traversal call license if non-traversal call license is not available.

For VCS-C, any call between VCS-E via traversal zone will consume 1 traversal call (if call via B2BUA, might have additional call license consumption depend on call setup scenario).