how do i know if my phone is registered via SIP versus H.323?

[learningSkype]

all, i'm trying to use SIP when connecting my softphone to my PBX, a CM running 6.3. i'm able to go into the settings tab in One-X communicator and change the protocol to SIP under Telephony. when i click on Log In, the phone registers and SIP remains grayed out on the app. but does that mean i'm registered as a SIP phone? the PBX doesn't tell me when i stat the station and SMGR doesn't show the status so i'm not sure.

does anyone know a surefire way to know and confirm that i'm registered using the SIP protocol?

 

[Wanebo]

Look in System Manager under Session Manager/System Status/User Registrations

 

[kyle555]

SIP phones: SMGR-->Session Manager-->System Status-->User Registrations
h323 phones: stat the station on CM
SIP phones register to SM.
H323 phones register to CM

 

[learningSkype]

thanks, exactly what i thought.

 

[learningSkype]

so even though my One-X app shows that i'm using SIP i'm not really registered as a SIP phone because i see the phone in CM.

 

[learningSkype]

forgot to ask this question but it's important. when i add the Session Managers in my server list, what IP's am i using from the session managers?

do i use the SIP Entity IP Address or do i use the Manangement Access IP address or do i use the hostname of each Session Manager?

 

[kyle555]

SIP entity, not management.

Dunno why your one-x is acting up. Usually once you change protocol between sip/h323 and hit OK, it has to restart.

When it's SIP, it should have entries for a domain as well as server list.

If it's not, then I'd look at your Windows installation. Most stuff I believe is in c\programfilesx86\avaya as well as c\users\you\appdata\locallow or roaming

Maybe there's some permission problem where it's not saving the changes you make.

C:\Program Files (x86)\Avaya\Avaya one-X Communicator\installConfig.xml has some good stuff and SIP would be: <SignalProtocol>2</SignalProtocol>

In the One-X installer bundle, there's a onexcuiadmin.exe. If you open that, and click Features on the left, and then click "open" and open that installConfig.xml file I referenced above, you have a GUI menu to edit and save that file. Generally you'd use that to tweak mass deployments and make the installConfig.xml look the way you'd like and push to everyone's PC. Maybe running that as admin and changing that file to SIP there might get you better results.

Any chance you didn't install in the default directory? Maybe on like some network share and you might have permission problems? Maybe run one-x as admin and try changing to SIP and see if that changes your installConfig.xml?