16
ED 2.0 (2013.03.18)

ED 2.0 (2013.03.18)

  • Upload
    others

  • View
    1

  • Download
    0

Embed Size (px)

Citation preview

ED 2.0 (2013.03.18)

How to connect OfficeServ system through ‘OfficeServ DM(Device Manger)’.

1) Standalone mode

- Execute “osdm.exe” file .

2) Web browser mode

1) Run DM on your PC.

2) Select System -> Link Setup.

V4.60↑

Private network Public network

MP20

MP40 http(s)://System IP/dm/

http(s)://System IP

http(s)://System IP/dmp/

http(s)://System IP/dm_public/

MP20s

OS7100

OS7070

OS7030

http(s)://System IP

- osdm files need to be uploaded to the DM directory in a SD card.

But in case of OS7070, all files are already included.

• MP40/MP20 : osdm.jar, osdmhelp.jar, osdm.jnlp, osdm_public.jnlp

• MP20s/MP10a/MP11/7030 : osdm.jar, osdmhelp.jar

- Java6 is required for a normal operation of DM(V4.60 ↑)

3) You can make the connection list as below. - Enter the ‘Site name’ and ‘Destination IP address’. After then click “Apply” button.

4) Choose the site in the list for the DM connection.

5) After entering a password, OfficeServ DM screen will be shown as below.

■ For the ‘Public zone service’, IP type of OfficeServ system and MGI/OAS cards should be set to

‘Private with Public’

■ Programming

1) In DM 2.1.0, enter the system IP address.

2) In DM 2.1.2, set the system’s ‘IP Type’ to ‘Private with Public’.

3) In DM 2.2.2, enter the MGI card’s IP address and set its ‘IP Type’ to ‘Private with Public’.

1) Trunk type - To use the various PBX features of WE VoIP client, SIP & ISDN trunk are recommended. Because

main features of WE VoIP are operating on the MOBEX’s basic functional structure. With other trunk types, it will work as normal SIP client having a basic call function. 2) Group Conf. Cabinet assignment - For ‘Call move’ and ‘Smart routing’ service, one or more ‘Group Conf cabinet’ should be assigned in

DM 6.3.2 ‘Virtual Card Change’ option. 3) WE VoIP Client Expire Time - In DM 5.2.12 ‘SIP Extension Configuration’, set ‘SIP Expire Time’ to below 600 seconds. If it is set to over 600 seconds, the WE VoIP client will not try to register to the system any more. 4) G.729 codec is not supported yet - To use WE VoIP client with the OfficeServ system, do not use ‘G.729’ codec for MGI/OAS/Handset. 5) Remote dial service - This service is not commercially released. If you want the trial test, please contact your partners in

HQ first.

■ To use the WE VoIP client service, enter a license key to DM 2.1.4 (MMC860) as below.

- No SIP phone license is required.

1) Enter the User ID and Password in DM 2.7.2 (MMC842)

2) Login profile in DM 5.2.24 - Enter the mobile number This number will be used for making a unique name for both a mobile and login profile as below. <sec_mobile_01095303304.xml> <sec_login_01095303304.xml> - Check the public zone service option To use WE VoIP in public area(not in your office WIFI zone), this option should set to ‘Enable’. - Check the Scan 5G Only option For reducing a handover delay, a proper channel scanning method should be chosen considering your network environment. -

3) Mobile profile in DM 5.2.23 - AP SSID Basically, this should be identical to your local access point. If it differs from the SSID of local AP, WE VoIP client will not recognize that it is in a office where the OfficeServ system is located in and then will try to register with a public IP address of the system. - Public zone service Using an unpopular SSID is strongly recommended. When it is unfortunately same to other one in a public area, the public zone service will not work at that area.

■ Multi-ring service

In DM 4.2.1 ‘Station Pair’ option, make WE VoIP client

paired with a desk phone.

- When user receives an incoming call on a paired desk phone(or WE VoIP), a missed call will not happen on the WE VoIP(or a desk phone).

- Setting or clearing CFWD or DND options will be applied to both paired devices.

■ Single CID number service

In DM 4.2.1, enable the ‘Single CID Number’ option .

- When WE VoIP is paired with a desk phone having a primary number by ‘Single CID number’ option, the primary number & name will be delivered instead of the CID number of WE VoIP.

- This feature is supported on an internal call(including station group) only.

- For an external call, you can use ‘Send CLI Number’ option in DM 2.3.4 instead of ‘Single CID number’. - This CID number will not be shown on the SMDR log.

■ Seamless call move between a desk phone and WE VoIP client.

■ Restrictions Although other type of handsets can be paired with the WE VoIP client, there are two restrictions. 1) In case of SLI/WIP phones, ‘Call move’ is only supported by pressing a pre-assigned number for ‘MOVE’ feature code. 2) SIP phone/client except for WE VoIP client doesn’t support the ‘Call Move’ feature.

■ Programming

1) In DM 4.2.1 ‘Station Pair’ option, make WE VoIP client paired with a desk phone(IPP/DGP). 2) In DM 4.9.2 ‘Station Key’ option, make ‘MOVE’ feature key on a desk phone. 3) In DM 5.14.2, set the ‘Move Wait Time’ (Default : 20secs)

Desk phone WE VoIP WE VoIP Desk phone

When a user selects ‘MOVE’ key on a desk phone, WE VoIP client will be ringing. After then a user answers the call on WE VoIP client, the call in progress on the desk phone will be automatically disconnected.

When a user selects ‘MOVE’ key on a desk phone, WE VoIP client will be disconnected from the call in progress and it will be moved to the desk phone with no ringing.

■ Programming

1) In DM 2.7.5 ‘Mobile Extension’ , assign a trunk number and input a mobile number in the ‘outgoing digit’ option. 2) In DM 2.7.2 ‘SIP Phone Information’, enter the Mobex station number to the destination of ‘Call forward unreachable’ option. 3) In DM 2.8.0 ‘Numbering Plan’, assign any non-duplicated number to ‘MOVE’ key.

■ Handover from Wi-Fi to mobile network

When a user presses the button ‘To Mobile’ on WE VoIP client, the VoIP call in progress will be redirected from its Wi-Fi to mobile network. - Mobile phone will be ringing for establishing a mobile call. - The VoIP call will be hold during the manual handover.

■ Programming

1) In DM 2.7.5 ‘Mobile Extension’ , assign a trunk number and input a mobile number in the ‘outgoing digit’ option. 2) In DM 2.7.2 ‘SIP Phone Information’, enter the Mobex station number to the destination of ‘Call forward unreachable’ option. 3) In DM 5.14.2, set the ‘Call forward unreachable Time’. (Default : 5secs)

■ Case 1 : Plug-out

When a WE VoIP client is disconnected normally, an incoming call to the client will be transferred to a pre-assigned call number in the ‘Call forward unreachable’ option. ■ Case 2 : No response In case that a WE VoIP client does not respond(180/183 ringing) to an INVITE message from the OfficeServ system within a timer set in the ‘Call forward unreachable Time’ option, the call will \ be transferred to a pre-assigned call number in the ‘Call forward unreachable’ option.

■ Programming

1) In DM 2.7.2 ‘SIP Phone Information’, enter the Mobex station number to the destination of ‘Call forward unreachable’ option. 2) In DM 5.2.24 ‘Login Profile’, enter a mobile number that WE VoIP client is having.

■ Cost reduction by the smart routing service

When a user makes an external call via ‘Mobile’ button on WE VoIP client, the OfficeServ system checks if the dialed number has a corresponding extension number and the station’s status is idle. If exists, the call will be redirected in the system to pass through its own trunk line.

3G/4G

Office

Dialing to

A-mobile

number

A

AP Smart Routing

to A-ext.

number