Integration VCS-C with CMA

[Anonymous]

Hi!

We have an VCS-C and a CMA with different devices, now, we have to join both systems. We have created neighbor zone in VCS-C and in CMA. The zone in VCS-C is active and we have created a search role to reach CMA. In CMA, we have created 1 site for VCS and an endpoint called gatekeeper-monitoring-check with VCS IP address. The relationship seems to work but when we make a call from VCS to CMA, a LRQ is sent to the CMA which seems to be proceding but the VCS receives a reject . We don't know if we need to configure anything else. Do you have any idea what could be happened?

Thanks in advance

[Anonymous]

Hi

What do you see in the LRQ from VCS?

I guess VCS sends <number>@sipdomain.com in the LRQ instead number. In that case you should remove @sipdomain.com in your search rule on VCS.

or you can use on your CMA's endpoints H323 name like that: <number>@sipdomain.com 

Regards

[Anonymous]

H Bazzuck,

We already have a search rule which remove @sipdomain in the VCS.  This what we see in the CMA:

Processing LRQ
Sending LCF
    'callSignalAddress'  0
        'ipAddress'  0
            'ip'  4  '10.250.10.4'
            'port'  1720
    'rasAddress'  0
        'ipAddress'  0
            'ip'  4  '10.105.203.248'
            'port'  1719
    'nonStandardData'  0
        'nonStandardIdentifier'  -555
            'h221NonStandard'  0
                't35CountryCode'  181
                't35Extension'  0
                'manufacturerCode'  9009
        'data'  46  'Type:LCF;CC:;AC:;Phone:;Ext:;DestIP:4174080266'
    'destinationInfo'  0
        '1'  0
            'e164'  9  '1234'

Thanks!

[Anonymous]

sorry, I missed this sentence in your the fist post:

 "we have created 1 site for VCS and an endpoint called gatekeeper-monitoring-check with VCS IP address."

it is a little bit strange.

You have to add VCS to Neighboring Gatekeepers in CMA (Admin  >  Gatekeeper Settings  >  Neighboring Gatekeepers)

and you shouldn't create any endpoints  with VCS IP address on CMA.

[simons3]

If you want to add a neighbor to CMA, remember to create a "dummy" or fake entry first. There is a bug which the first entry will not be seen by the CMA. After you create the 2nd real one to VCS, you can delete the first one. This has to do with code taken from the legacy product line which already had one in there as a result the indexes are off.

S.