AST and Dual registration SIP/H.323

[fondog2]

Hello to all,
System, Session on 7.1.3.4 and CM's on 6.3 with an upgrade coming soon. I have been searching and also asked Avaya but still don't have a resolution yet.

Issue:
We build H.323 phones for every user, build them in CM. Then we get requests for people who work sometimes from home so then build a SIP phone use the existing extension and check the box for dual registration of SIP and H.323. One of the features that is strange is EC500. If you press the button to enable or disable the light stays on all the time from the SIP station. But you can see it enable/disable when you status the station in CM. I have verified the private/public unknown, off pbx station mapping (OPS), added the extension number, +1 full 10 digit and 10 digit number to the communication address field in System Manager and verified the station is registering with AST, Primary and Secondary. This only happens to some phones not all. I did stare and compares nothing is different between the them. The only thing I can think of is something with the group codes that were built in the 46xxsettings file for locations with time differences but I can't see anything that stands out.

Does anyone have any idea where to look to resolve this? Any ideas would be greatly appreciated.

Thank you,

 

[kyle555]

Can you turn EC500 on and off from the SIP phone? If so, and the problem is only doing it from H323, I'd say it's because EC500 isn't explicitly mentioned in the list of features supported by dual registration.

 

[fondog2]

Kyle555,
Yes it turns the feature on and off from the SIP phone. But it doesn't turn the light on and off. The light stays on. H.323 side is fine.

 

[kyle555]

what if you turn EC500 off and try other "toggle" features - like a send-calls key that should light up when enabled and turn off when disabled? and/or call forwarding.

Does the toggle feature toggle the lamp properly? If not, you have a PPM problem. If so, you have a feature incompatibility problem.

I believe the general use case for SIP on top of H323 was for Equinox softphones on iOS and Android.

Your home working users that use a SIP phone - is that a deskphone as a remote worker through a SBC? Presuming they use VPN, one-x as a h323 softphone would work. Otherwise, if those people have dedicated cubes at work, maybe make their deskphones SIP. You're certainly comfortable enough to do SIP hardphones

 

[fondog2]

Kyle555,
I would love to do them as SIP but some of the features don't work on SIP like they do on H.323. Abbreviated dial is one of them. I have a work around for it but then you have to do a custom label too. Yes the at home phones go through our SBC. I see them in the traces pushing 10 digits instead of the 5 in the traces so as I stated I added those in as E.164 and the 10 digit in the communication address of System Manager. We use give our users hard phones (9611's). The on net use DHCP as H.323 the SIP we manually program with the external IP and change the signalling to SIP. No One-X or Equinox. Some of our users heads would explode if they gave them One-X.