OM Configurator? 1

[ThomasBB]

Hi,

After doing a few networking changes, I need to change the IP address of our "IP Dect Mobility Manager" as well. It seems like I'm unable to do it at the web-interface, and the manual speaks of a tool called OM Configurator that is needed to perform the change.

I am, however, unable to find a working mirror for the download. Can anyone be of assistance here?

Thanks!

 

[holdmusic34]

Couldn't find it on support.avaya.com. Further research indicates it may be discontinued. I have limited experience on Avaya DECT. I was burnt too badly back in the day by the NEC Drover PHSs and Kirk deployments that were never commissioned to have confidence in the technology. But Avaya do it pretty well.

I suspect that maybe one of your bases stations has been dedicated as the 'OM' which may now be called ADMM. Try browsing to your base stations on the network.
See below for the information I found from the linked document on page 11.

https://downloads.avaya.com/elmodocs2/ip_office/R3.2/ip_dect_install.pdf

Avaya DECT Mobility Manager Mode
In this mode, an IP Base Station functions as a regular IP Base Station. Additionally, it is responsible for
H.323 signalling between the IP DECT system, IP Office and a web management interface.
To designate a IP Base Station as the ADMM, assign an IP address to the IP Base Station DHCP
settings (see Avaya IP DECT Startup) or set the data via OM Configurator (see Static Local
Configuration of the IP DECT). If an IP Base Station is designated as the ADMM, it starts extra services
(for example, the Web Service to support the management interface).
Note
• It is possible to deactivate the DECT part of a IP Base Station. If the DECT Interface is
deactivated then the resources (CPU and memory) are available for the ADMM.
Note
• Avaya Power Over Ethernet adaptors (type 1151) are non-802.3af compliant, and therefore
cannot power the ADMM.
Avaya IP DECT Mobility Manager
The Avaya IP DECT Mobility Manager (ADMM) performs the following tasks:
• Signalling gateway (H.323 <-> DECT GAP).
• Media stream management.
• Manages synch over air functions between IP Base Stations.
• Facilitates system configuration modifications.
• Provides additional services, for example:
• Directory (LDAP or TFTP based).
• WML browser.
The ADMM must run on one of the IP Base Stations.

Maybe also try this:

https://support.avaya.com/downloads...ntId=C20090710164952637750123&productId=P0359

Avaya WinPDM Software

Depending on the URI configuration the ICR can be completely ignored.

If your URI is configured to use internal data then the IP Office will look into the user's SIP tab and if you have *'s it will look into ICR.

A madman with a taste for speed.

 

[ThomasBB]

Hey holdmusic34, thanks for replying!

We only have one base station, which serves 5 users. The base station is indeed set up as an ADMM, which perhaps could explain why I cant change the IP settings on it? I think perhaps the important quote here is this "or set the data via OM Configurator (see Static Local
Configuration of the IP DECT)." which to me indicates, that in order to do any 'Static' configuration, I need the OM Configurator... which is nowhere to be found :-(

 

[holdmusic34]

You can browse to a base station and the IP address of OMM should be configured in there.
OMM IP Address
The IP address of the OpenMobility Manager is specified here.
If only one base station is used, enter the IP address of that base station, e.g. 192.168.1.2
The user name and password are: omm

OpenMobility Manager (OMM)
To configure the OpenMobility Manager connect a web browser with the OMM IP address (example:

http://192.168.1.2)

https://downloads.avaya.com/css/P8/documents/100175335

Depending on the URI configuration the ICR can be completely ignored.

If your URI is configured to use internal data then the IP Office will look into the user's SIP tab and if you have *'s it will look into ICR.

A madman with a taste for speed.

 

[holdmusic34]

based on your reply you should be able to browse to the IP address of the based station and it should open OMM from there.
Like I said, I don't know DECT. it's just what I learnt in the last 5 minutes.

Depending on the URI configuration the ICR can be completely ignored.

If your URI is configured to use internal data then the IP Office will look into the user's SIP tab and if you have *'s it will look into ICR.

A madman with a taste for speed.

 

[ThomasBB]

Unfortunately there's no such thing, when I'm browsing to the base.

That said, I did actually find a working mirror of "OM_configurator.jar" here:

http://www.odicom.com.ua/download/detewe/opencom100/Release_8.06/061028_Rel_8/DeTeWe/

Now to see if I can figure out how it works

Thanks!

 

[tlpeter]

just download the latest admin software and it is still there in the folder "IPDECT"


BAZINGA!

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

 

[ThomasBB]

There's no such folder in my installation, I'm afraid.

 

[Pepp77]

Not in the installed folders but in the to be installed folders. Ie go to the install file for Admin and there is an IPDECT folder in there, however I cannot see an OM_configurator.jar file in the IPDECT folder on a 10.1 install folder I have.

| ACSS SME |

 

[intrigrant]

It must be configured with a java tool called "ADM_Configurator_1_1_13.jar", run it , fill in the MAC address of the (working) base and retrieve the data, adjust and send back.

 

[ThomasBB]

Thanks intrigrant. I did figure out how to use the tool. It seems like a very old-fashioned way of doing things. Also, the ADM_config file is indeed located in the installation-files, as tlpeter (and Pepp77) pointed out!

 

[tlpeter]

I recently installed the SIP-dect of Mitel (which basicly is the newer version of this system) and they still use the same stuff but it only looks a bit newer.


BAZINGA!

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

 

[ThomasBB]

I'm not sure if I should bump or create a new thread?

After changing the subnet of our network, I changed the settings via the tool here, but we're having issues with getting our DECT handsets to twin. They aren't receiving any calls.

I've set it up as such:

OMM IP ADDRESS: 192.168.22.240 (address of the base station)
OMM PORT NUMBER: 1720
PBX IP ADDRESS: 192.168.22.4 (address of call server)
PBX PORT NUMBER: 1719

I'm really unsure about the port numbers. Can anyone shed some light on this?