innovaphone wiki - User contributions [en]

Howto:Avoid "lazy" registrations when using different nodes

2008-02-21T15:30:13Z

Vcvoipar: /* Correction */

==Applies To==
This information applies to

* all PBX Version 6



==More Information==

Registering clients on a multi-node PBX can - under certain circumstances - result in unpredictable behavior when using only numbers and not names.

Example:

PBXxy with NodeA and NodeB.

'''NodeA has prefix 97'''
'''NodeB has prefix 98'''

UserA is already defined on PBX for NodeA -> 97.11
UserB is already defined on PBX for NodeB -> 98.22

I'm lazy, so I configure only the number in the phones, not the names.

Up to this point, all works ok.

UserA and UserB are registered ('''Phone 1 "UserA 11"'''; '''Phone 2 "UserB 22"''').

Now, I configure another client on a new phone in NodeA, also again only the number, not the name:

'''Phone 3 --> 97.34'''

Aware! UserC is not yet configured in the PBX.

What happens?

The third phone registers as NodeA! ('''Phone 3 "NodeA 97"''').
From this point on, the whole NodeA works totally unpredictable - and mostly wrong.

So, please use '''names and numbers''' or '''names alone''' when dealing with different nodes.

It won't be a problem for small configuration scenarios, but it can be a problem with bigger rollouts.



[[Category:Faq|{{PAGENAME}}]]

Howto:Avoid "lazy" registrations when using different nodes

2008-02-21T15:29:22Z

Vcvoipar: /* More Information */

==Applies To==
This information applies to

* all PBX Version 6



==More Information==

Registering clients on a multi-node PBX can - under certain circumstances - result in unpredictable behavior when using only numbers and not names.

Example:

PBXxy with NodeA and NodeB.

'''NodeA has prefix 97
NodeB has prefix 98'''

UserA is already defined on PBX for NodeA -> 97.11
UserB is already defined on PBX for NodeB -> 98.22

I'm lazy, so I configure only the number in the phones, not the names.

Up to this point, all works ok.

UserA and UserB are registered ('''Phone 1 "UserA 11"'''; '''Phone 2 "UserB 22"''').

Now, I configure another client on a new phone in NodeA, also again only the number, not the name:

'''Phone 3 --> 97.34'''

Aware! UserC is not yet configured in the PBX.

What happens?

The third phone registers as NodeA! ('''Phone 3 "NodeA 97"''').
From this point on, the whole NodeA works totally unpredictable - and mostly wrong.

So, please use '''names and numbers''' or '''names alone''' when dealing with different nodes.

It won't be a problem for small configuration scenarios, but it can be a problem with bigger rollouts.



[[Category:Faq|{{PAGENAME}}]]

Howto:Avoid "lazy" registrations when using different nodes

2008-02-21T15:28:16Z

Vcvoipar: First "Beware-of" Entry

==Applies To==
This information applies to

* all PBX Version 6



==More Information==

Registering clients on a multi-node PBX can - under certain circumstances - result in unpredictable behavior when using only numbers and not names.

Example:

PBXxy with NodeA and NodeB.

NodeA has prefix 97
NodeB has prefix 98

UserA is already defined on PBX for NodeA -> 97.11
UserB is already defined on PBX for NodeB -> 98.22

I'm lazy, so I configure only the number in the phones, not the names.

Up to this point, all works ok.

UserA and UserB are registered (Phone 1 "UserA 11"; Phone 2 "UserB 22").

Now, I configure another client on a new phone in NodeA, also again only the number, not the name:

Phone 3 --> 97.34

Aware! UserC is not yet configured in the PBX.

What happens?

The third phone registers as NodeA! (Phone 3 "NodeA 97").
From this point on, the whole NodeA works totally unpredictable - and mostly wrong.

So, please use '''names and numbers''' or '''names alone''' when dealing with different nodes.

It won't be a problem for small configuration scenarios, but it can be a problem with bigger rollouts.



[[Category:Faq|{{PAGENAME}}]]

Howto:Setting time and date without using an NTP

2008-02-21T14:22:12Z

Vcvoipar: /* Known Problems */

==Applies To==
This information applies to

* All gateways, V6



===Problem Details===
Sometimes it is temporarely impossible to access a NTP-server. Here' s a short possibility to set time and date via the web interface.

===System Requirements===
In the simpliest manner a working PBX - or any other accessible Innovaphone gateway running under V6

===Configuration===

Simply use the following syntax in your webbrowser:

http://<ip-of-your-Innovaphone-gateway>/!time%20%20dd.mm.yyyy-hh:mm

Example: http://10.10.10.120/!time%20%2021.02.2008-15:05

===Known Problems===
None

===Related Articles===

http://wiki.innovaphone.com/index.php?title=Howto:How_to_obtain_the_current_time_for_innovaphone_devices_using_NTP

[[Category:Howto|{{PAGENAME}}]]

Howto:Setting time and date without using an NTP

2008-02-21T14:20:56Z

Vcvoipar: /* Known Problems */

==Applies To==
This information applies to

* All gateways, V6



===Problem Details===
Sometimes it is temporarely impossible to access a NTP-server. Here' s a short possibility to set time and date via the web interface.

===System Requirements===
In the simpliest manner a working PBX - or any other accessible Innovaphone gateway running under V6

===Configuration===

Simply use the following syntax in your webbrowser:

http://<ip-of-your-Innovaphone-gateway>/!time%20%20dd.mm.yyyy-hh:mm

Example: http://10.10.10.120/!time%20%2021.02.2008-15:05

===Known Problems===
None



http://wiki.innovaphone.com/index.php?title=Howto:How_to_obtain_the_current_time_for_innovaphone_devices_using_NTP

[[Category:Howto|{{PAGENAME}}]]

Howto:Setting time and date without using an NTP

2008-02-21T14:19:14Z

Vcvoipar: Setting date and time on Innovaphone gateways without the use of an NTP server

==Applies To==
This information applies to

* All gateways, V6



===Problem Details===
Sometimes it is temporarely impossible to access a NTP-server. Here' s a short possibility to set time and date via the web interface.

===System Requirements===
In the simpliest manner a working PBX - or any other accessible Innovaphone gateway running under V6

===Configuration===

Simply use the following syntax in your webbrowser:

http://<ip-of-your-Innovaphone-gateway>/!time%20%20dd.mm.yyyy-hh:mm

Example: http://10.10.10.120/!time%20%2021.02.2008-15:05

===Known Problems===
None

http://wiki.innovaphone.com/index.php?title=Howto:How_to_obtain_the_current_time_for_innovaphone_devices_using_NTP

[[Category:Howto|{{PAGENAME}}]]

Howto:Howto add various GAP Mobile Phones to innovaphone IP DECT Gateways

2008-02-08T14:00:26Z

Vcvoipar: Conversion from IPUI to IPEI mechanism for Gigaset handsets (and some other handset types too)

With the possibility to add various DECT Handsets to the innovaphone IP DECT Gateways, you need the IMEI number which is stored in the Handset.

There are several ways to get this information, some are described here.

Applies To
This information applies to

* IP 1500

* IP 600

==More Information==
===Problem Details===
Obtaining the IMEI number of DECT Handsets isn’t easy sometimes, because many manufactures don’t deliver this information to the customer.

To workaround this problem, there are needed several manufacturer depending steps to proceed.

Below you can find some hints for different DECT handsets.

===Configuration===

===IP50===

Open the battery tray and lift out the battery. Underneath the battery there is a sticker with the IMEI number in following format:

00077 xxxxxxx x

The IMEI itself contains only the first to blocks, just delete the last number and put it in the IMEI field. Don’t delete the blank in the middle.

Or press *99984* on the Handset- Displays the serial number

===IP52, IP54===

The IMEI number is provided by the handset when trying to register at the base station.

Or press *99984* on the Handset

Displays the handset item number, serial number, production week/year, hardware pcs and software no

===Astra Office 1xx===

After a "longclick 2" a short number will appear, which contains Hex Characters.

===Siemens Gigaset===

The sequence *#06# will put out Hex Character also.

The Gigaset-Output is an IPUI-Number (International Portable User Idendity),
there is a way to tanslate it to IPEI/IMEI:

An example:
The IPUI of the Gigaset Handset is 0 01BF 582AB (hex)

IPEI Coding is:

EEEEE PPPPPPP C

E = EMC (Equipment Manufacturer's Code) in dec.
P = PSN (Portable Equipment Serial Number) in dec.
C = valuation code, not used in Innovaphone DECT environment

The conversion:

01BF (hex) --> 447 (dec).
fill up with leading zeros --> 00447 (EMC)

582AB (hex) --> 361131 (dec).

agein: fill up with leading zeros --> 0361131 (PSN)

=> IPEI is 00447 0361131

And, for confusing reasons :-)

IMEI = International Mobile Equipment Identity
IPEI = International Portable Equipment Identity

...but don't care about that in realistic scenarios

For those handsets you’ll need another facility to read out the IMEI.

When registering or even trying to do so, all handsets are transferring their individual IMEI number to the basestation. With an IP1500 with some addons or an IP600 you will be able to read out the IMEI by yourself.

The secret is to set the log level on the basestation to 3. The nearly all messages are written in the log.

===IMEI logging with an IP1500===

First, you will have to get the dect.zip, which you can find in the ICE Folder on download.innovaphone.com.

In this Zipfile, there's a tool called CCFP Admin.

Install it.

You'll also need a PC and a "null modem kabel".

Just connect your PC with the serial cable to the IP1500, and start CCFP Admin.

In the Menubar, set the log level to 3.

Then, just view the Log while you try to register your phone.

It should show up as a failed registering attempt in the log.

But you'll also find, next to the "failed to register" message, the IMEI of this device.

Take this IMEI number and paste it into User configuration und DECT.

===IMEI logging with an IP600===

With an IP600 it is much easier.

Just connect via IP to your IP600 and open the Java configuration applet.

On the left, expand the tree “DECT Interface” and highlight the GW-DECT entry.

In the right frame there is an pull down menu for the “DECT/ISM loglevel”, set it to 3.

Save and Activate the settings.

Open the Syslog and try to register a handset. The remaining steps are the same as on the IP1500.

===IMEI logging with an IP1200===

The easiest way.

Just try to subscribe the handset and the IP1200 will accept this subscriptions as "anonymous" subscription.

Using the "magic registration" known from the PBX you cann add the handset simply by dialing the number which it should get.

Be sure to set the option "Allow anonymous" under Configuration->DECT->System and erase any AC code one field above.

If subscribed anonymously, you could also gather the IPEI because under Administration->DECT->Unknown Users you'll find a list of anonymous subscribed users together with the corresponding IPEI.

[[Category:Howto|{{PAGENAME}}]]