sip ethernet door intercom not registering 6

[Asoto22]

Hi I currently inherited the job of maintaining our Avaya ip500 phone system and have pretty much just basic understanding (add lines,users, extension,huntgroups, etc.)
My manager had purchased a door intercom from Cyberdata and I got as far as adding the sip license but when I configure the door intercom through the gui I give it a sip user id of 127 which is the extension I created in ip Office along with a password which is on both, our ip500 doesn't have a sip domain so I use the lan address as the sip server but when I connect and reboot the ip500 has connection problems and disconnects and reconnects every 20 seconds or so, then I have to take the door phone sip server off, in the home page for the door intercom it says Not registered with sip server, am I missing a control device or am I configuring it completely wrong? Any help would be greatly appreciated!

Angel

 

[tlpeter]

Can you make a monitor trace with default settings?
The password should not be the application password (under the user name) but a login code (telephony tab)

BAZINGA!

I'm not insane, my mother had me tested!

 

[hairlessupportmonkey]

On the Base Extn toggle "Force Authorisation" and merge.

ACSS - SME
General Geek

 

[Asoto22]

@tlPeter not sure how to run a monitor trace on this network, what program should I use?
but here is what the settings for the door intercom and the ip500
@hairlessupportmonkey when I went to toggle it was already checked, should I uncheck it? by the way awesome name!

Door Intercom
SIP Server:192.168.43.1 (which is the second lan, when I use 192.168.168.20 which is the lan1 the system does the restart every 20 seconds
Backup SIP Server 1:
Backup SIP Server 2:
Remote SIP Port: 5060
Local SIP Port: 5060
Outbound Proxy:
Outbound Proxy Port:0
SIP User ID:127
Authenticate ID:127
Authenticate Password:1234

Register with a SIP Server:checked

Re-registration Interval (in seconds):360

Unregister on Reboot:unchecked

Call disconnection
Terminate call after delay (in seconds):0
Note: A value of 0 will disable this function
RTP Settings
RTP Port (even):50000
Dial Out Settings
Dial out Extension:127
Extension ID:id127

ip500 Settings
Extension 127 is set as a HuntGroup
Ring mode: Collective
Overflow Mode: Group
Hold Music Source: no change
Agent's Status on No-Answer: None
Under user list is my extension ext 219 for testing purposes

 

[yankblan]

Your 127 has to be a USER not a HG....

http://interconnexionsld.ca/

 

[yankblan]

To clarify: create a user with 127, the associated extension will create itself when user 127 registers. Then u configure a hotline for your 127 that will dial the HG that has to answer the door.

http://interconnexionsld.ca/

 

[mforrence]

If trying to register as a SIP station, confirm that you have a 3rd party endpoint license. The SIP trunk license is not applicable if registering as a station. That said, you can likely make the device register as a trunk and still make it work - just different configuration.

 

[Asoto22]

Ok sorry for the late response back but we had put this in the back burner for a bit and now im back, I managed to setup the user as ext 127, set up login code under supervisor settings in the telephony tab, the extension is a sip extension (no ip in the voip tab), as for the intercom sip is set up as follows

sip server: 192.168.168.20
remote sip port: 5060
local sip port: 5060
outbound proxy: blank
Outbound proxy port: 5060
sip user id: 127
authenticate id: c3d
authenticate password: (password set up in login code under supervisor settings)

Register with a sip server: unchecked (when its checked it registers but after maybe 20 seconds the avaya system resets itself then comes back and 20 seconds later resets again and keeps doing this until I uncheck the register box)

re-registration interval (in seconds): 3600

unregister on reboot: unchecked

Dial out Extension: 128 (which is the huntgroup line)
Extension id: id128

I got as far as registering the intercom to the sip server and when I call the extension it connects and I can hear anyone thats near by the intercom but again it resets the avaya every 20 seconds, not sure what to check next, thanks for your time

 

[atcom]

Shouldn't the authenticate ID be the same as the user ID? (the extension #)

-----------------------------------

Calgary Telephone Systems, Avaya LG Asterisk (FreePBX) VOIP & TDM

 

[Asoto22]

I changed the user id in the intercom to the ext (127) and the avaya system gave me an error for wrong user name, I can't do it the other way and change the user in the avaya to 127 because it says the user name can't start with a number or symbol, I'm thinking it might have something to do with the re-registration but I'm not sure where on the avaya I would set the intervals

 

[gregl45]

in the IP Office give your user a name such as intercom. make the extension 127 and the log in code 127. In the CyberData the Primary server is your IP address of the IPO. User ID, User Auth, and Auth Password will all be 127. You will need a 3rd party endpoint license for this to work. I have set up several of these with no issues at all.

 

[holdmusic34]

I understand how hard it can be when you're thrown in to the deep end on something like this. However, that is why there are people who are trained to do this easily and also trained to diagnose why something may or may not be working. Would your boss

Tell your boss to get a vendor and let you concentrate on your real job. This has been over two months of hassling for a pretty easy extension add.
You've been told twice to get a third party IP endpoint license in the config. Greg and Mforrence. You have not confirmed this.
Please confirm if you have done this. To get one you will need to purchase through a vendor. You'll need your feature key dongle number.

If you can't run a monitor trace, as Tlpeter requested, and have the system tell you what's up there isn't much to say, other than to repeat: run a monitor trace and watch the thing attempt to authenticate against your system.
If you can't do this get a vendor to do it. Tell your boss you need a vendor.

Watching the endpoint fall over repeatedly and diagnosing from your config is pointless.

Good Luck

Kids, Kids, It's Avaya. You're both right.