SX10 - H.323 configuration not persistent

[Isaac Li]

Hello,

I have upgraded my SX10 codec to CE8.2.1 for the H323 protocol.  It's been working fine until I restarted the codec -- all H323 configurations are gone.  I have checked "Persistent" mode for the "Configurations".  

Have tried CE8.3.1 but the problem still exists.  

Could this be a CES8 bug?  Anyone experienced this before?

[Patrick Sparkman]

Can you tell us more about how the endpoint is deployed and configured?

Is it registered to CUCM, VCS, or standalone?

[Justin Ferello]

First, if this unit is registered to CUCM; then there is nothing you can do unless you want to make it so CUCM cannot "manage" the endpoint.  If so, see the next option.

Second, if the unit is not registered to CUCM; then you must go into the Advanced Config > Provisioning > Mode and change this from Auto/CUCM to "off" or "TMS".

One of the above methods will resolve your issue.

Thanks,
Justin

[Ammar Saood]

yes one of my customer has the same bug.

h323 setting are non-persistent.

even we performed factory reset. the unit is registered to VCS. as soon as your restart the device the h323 setting vanishes.

everything else is there.

[Justin Ferello]

Ammar,

Did you check the provisioning mode to make sure it is not set to Auto or CUCM?

Thanks,
Justin

[Ammar Saood]

i will double check it . we intalled 1x sx20 and 1x sx10. same firmware same settings n both registered to VCS.

sx20 settings are persistent but sx10's h323 settings are not.

will update you about provisioning mode.

[Sushant Sharma]

can you please clarify where is your endpoint is registered.

Is it registerd to Cucm or expressway-C 8.9X.

[andersonassuncao]

I have a SX10 registered on cucm, but i want to have h323 mode enable to receive h323 calls, I put the configuration provisioning on SX10 to CUCM POST, but any apply or restart on SX10, h323 mode is disabled by CUCM.

Is there any way to keep persistent configuration and put h323 mode to on with sx10 registered on cucm?

thanks

[Patrick Sparkman]

When you register endpoints to CUCM, H323 is disabled as it's a SIP only.  You could enable H323 on CUCM registered endpoints, but when the endpoint restarts and contacts CUCM for it's configuration it will be disabled again.  If you need to make H323 calls, you'll need to utilize a VCS/Expressway to interoperate between H323 and SIP protocols.  If the reason you're trying to enable H323 is for IP dialing, then you'll also need to utilize VCS/Expressway, see: Dial IP Addresses from Endpoints Registered to CUCM with VCS / Expressway Configuration Example.

[andersonassuncao]

Hi Patrick,

   the reason is only to receive calls, i don't want to make calls, i only want to receive from old H323 endpoints, but as you said, if i chose register on cucm, i will not be able to have h323 enable to receive the calls, i will need to use VCS. old h323 equipments does not work with domain, only ip address.

   and I'm not able to use VCS, because i have cisco meeting server and i'm not able to make addhoc calls with CMS and VCS. i'm in a trouble.

thanks

[Wayne DeNardi]

What is the "old H323 equipment" you are referring to?  Brand/Model/etc.  Is the "old H323 equipment" part of your network, or belong to someone else?

Most H.323 equipment and software (since H.323 version 5 was released in July 2003) should be able to accept a H.323 Annex O dial string which can include a domain, and something that might look like a SIP URI, but still be a H.323 address, and most H.323 gatekeepers should support this.