can`t register h323 device on vcs-c

[born.jason]

Hi,

damn, so many open issues for me at the moment. Sorry for disturbing all you guys. :-)

I try to register a MX300 or EX90 on a VCS-C. I have created a local database account for the devices and on the endpoints i use as gatekeeper the VCS-C. But this is all i got:

H323

Number:

00493057574609

ID:

H-609

Gatekeeper:

192.168.40.124

Status:

Rejected

The trange thing is if i look on VCS-C in the Eventlog i don`t see any entry for this devices. I have tried it with an MCU and i saw "registration rejected" in eventlog from VCS-C but for those devices i see nothing in the event log.

does it matter if the devices registered with SIP also on a CUCM?

Any suggestion?

Cheers

Jason

[Martin Koch]

I would either do a registration on cucm (just sip) or a dual registration with h323 and sip just towards the vcs.

Regards using the VCS I would recomend to read up on the various deployment and admin guides

http://www.cisco.com/en/US/products/ps11337/products_installation_and_configuration_guides_list.html

If you do not use authentication the local database would not be needed.

[Tomonori Taniguchi · Accepted solution]

You should not configure MX300/EX90 to register on both UCM and VCS as SIP UA as these SIP UA only support single SIP profile configuration.

This is very depend on your conference deployment, but you should register those SIP UA on either UCM or VCS and have SIP trunk between those two call control in order to routing the call, or as Martin mention already register those SIP UA on UCM. Then also register on VCS as H.323 Endpoint.

Please note, if you have E20 or other SIP UA that support multiple SIP Profile configuration, you may register such SIP UA on both UCM and VCS but as different SIP UA (and select SIP line when initiating the call to determine which SIP proxy to be used).

[Martin Koch]

Hi Tomonori!

I had the feeling that the provisioning of the CUCM can conflict with trying to set other options manually.

So I would only use it either towards the CUCM or towards the VCS but not on both at the same time.

[Tomonori Taniguchi]

Martine, yes correct, most of case SIP UA won’t able to register both VCS and UCM due to different way to managing SIP UA on those call control (that what I mention in above).

[born.jason]

What you guys think is best practice? Only use CUCM SIP or register all on VCS and communicate with neighbor zones to CUCM?

I what case should i use which solution?

What do you thing are the advatages if i can use H323 and SIP ?

[Martin Koch · Accepted solution]

As we do not know your deployment, your uses devices, software versions and needs its not easy

to say as it can become very specific.

If you have modern endpoints which can register to cucm then it is definitly not wrong to go that way.

I would say sip is becoming more and more important and the h323 part is just going to be interworked

on the vcs for b2b (business 2 business) calls or old style of endpoints.

If you run old software / hardware the vcs deployment with a neigbor zone might be a good idea.

Internally with cucm I do not see any advantages on using h323 for telepresence.

On b2b calls you might want to be able to supoprt h323 as your external contacts might still use

that and you might still hit some h.320 isdn sites, ... but that is then done via the infrastructure (vcs)

and you need not to worry about the endpoints which still are sip and only registered to the CUCM.