Howto:2N - VoiceBlue Lite - Testreport: Difference between revisions
(16 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
==Summary== | ==Summary== | ||
In the first place 2N VoiceBlue Lite is a GSM to SIP Gateway with a support up to 4 SIM cards. There also basic Mobility Extension features implemented and may in addition to main functions are used in parallel. A software for mobile phones to assist Mobile Extension features is also available. | In the first place 2N VoiceBlue Lite is a GSM to SIP Gateway with a support up to 4 SIM cards. There also basic Mobility Extension features implemented and may in addition to main functions are used in parallel. A software for mobile phones to assist Mobile Extension features is also available. | ||
'''A fix for the [[Howto:2N_-_VoiceBlue_Lite_-_Testreport#Minor_Bugs|minor bug]] from vendor is pending.''' | |||
==General Information== | ==General Information== | ||
Line 7: | Line 9: | ||
* Vendor: 2N | * Vendor: 2N | ||
* Version: 2.00n | * Version: 2.00n | ||
* Firmware: 02.07.35b02 | * Firmware: 02.07.35i19 (first test done with older Firmware 02.07.35b02) | ||
* innovaphone Firmware: V7 hotfix5 | * innovaphone Firmware: V7 hotfix5 | ||
==Current test state== | ==Current test state== | ||
{{Template:Compat Status "tested"}} | |||
<!--{{Template:Compat Status "in progress"}}--> | |||
<!-- {{Template:Compat Status "certified"|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}}--> | <!-- {{Template:Compat Status "certified"|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}}--> | ||
<!-- {{Template:Compat Status "tested"}} --> | <!-- {{Template:Compat Status "tested"}} --> | ||
<!-- {{Template:Compat Status "rejected"}} --> | <!-- {{Template:Compat Status "rejected"}} --> | ||
Testing of this product has been finalized October 6th, 2009. | |||
==Configured Scenario== | ==Configured Scenario== | ||
Line 61: | Line 63: | ||
<center>[[Image:2N VoiceBlue Lite Configuration 02.png]]</center> | <center>[[Image:2N VoiceBlue Lite Configuration 02.png]]</center> | ||
; GSM outgouing groups : Set CLIR to "Disable (CLIP - on)". | ; GSM outgouing groups : Set CLIR to "Disable (CLIP - on)". Our experience is that in Norway Delay for alerting has to be set to 2 seconds. With only one second there is no ringtone. | ||
<center>[[Image:2N VoiceBlue Lite Configuration 03.png]]</center> | <center>[[Image:2N VoiceBlue Lite Configuration 03.png]]</center> | ||
Line 80: | Line 82: | ||
===Installation & Configuration of the innovaphone components=== | ===Installation & Configuration of the innovaphone components=== | ||
< | The GSM GW is registered on the gatekeeper GW3: | ||
<center>[[Image:2N VoiceBlue Lite Configuration 09.png]]</center> | |||
LCR Routing from and into the PBX: | |||
<center>[[Image:2N VoiceBlue Lite Configuration 10.png]]</center> | |||
No special configuration in the PBX is required, mobile extension user is registered directly to the user object. | |||
==Product Test== | ==Product Test== | ||
Line 273: | Line 284: | ||
*Call form mobile to GSM GW | *Call form mobile to GSM GW | ||
*Dial 101# | *Dial 101# | ||
* | *101 accepts the call | ||
*Dial 7* | *Dial 7* | ||
*Dial 102# | *Dial 102# | ||
Line 327: | Line 338: | ||
==Minor Bugs== | ==Minor Bugs== | ||
<!--all major bugs should be fixed when the product is certified. However if there are some minor problems(that will be fixed in a upcoming release), this is the place to mention them--> | <!--all major bugs should be fixed when the product is certified. However if there are some minor problems(that will be fixed in a upcoming release), this is the place to mention them--> | ||
== | ; No spaces in the username of Mobile Extension allowed: PBX User Object field ''Name'' must be without spaces, in order to be able to register the Mobile Extesion from 2n VoiceBlue Lite. The space is not escaped according RFC 3261 (19.1.4 URI Comparison) : should be <code>One%20Number</code>, but is <code>One Number</code>. Therefore registration is possible, but further SIP interop is broken(e.g. calls to busy subscribers, see the next Bug). | ||
< | ; No busy tone to Mobile Extension : if the PBX user is busy and is called by the Mobile Extension user, the call is just terminated without busy tone. If the username of Mobile Extension include a space, the call is terminated with <code>403 Forbidden</code> by the PBX, instead to be terminated with <code>486 Busy Here</code>. | ||
===Fixed in Version 02.07.35i19=== | |||
; Wrong SIP To-tag after 407: The SIP tag in "To:" Header is broken after <code>407 Proxy Authentication Required</code> was sent from the PBX. Affects call transfer from Mobile Extension to internal user. Workaround: remove password on PBX User Object. | |||
===Solved by workaround=== | |||
; SIP Registeration Timeout : The default Registration Timeout of 600 sec. for the SIP Registration is not updated when the PBX defines another timeout in 200 OK after REGISTER. Workaround in the configuration of 2n VoiceBlue Lite: set register timeout to 120 manually. | |||
[[Category:Compat|{{PAGENAME}}]] | [[Category:Compat|{{PAGENAME}}]] |
Latest revision as of 12:05, 23 April 2010
Summary
In the first place 2N VoiceBlue Lite is a GSM to SIP Gateway with a support up to 4 SIM cards. There also basic Mobility Extension features implemented and may in addition to main functions are used in parallel. A software for mobile phones to assist Mobile Extension features is also available.
A fix for the minor bug from vendor is pending.
General Information
- Product name: Mobility Extension
- Vendor: 2N
- Version: 2.00n
- Firmware: 02.07.35i19 (first test done with older Firmware 02.07.35b02)
- innovaphone Firmware: V7 hotfix5
Current test state
The tests for this product have been completed.
Testing of this product has been finalized October 6th, 2009.
Configured Scenario
Description
Mobile Extension Features
In addition to the SIP registration at the PBX as a GSM Gateway, it is possible to define Mobile Extensions registered via SIP separately to the particular user object on the PBX. In this way the calls to the user object on the PBX also signalled to ther mobile phone and the calls from the users mobile phone, dialed via 2 stage dialing, are placed to the PBX via this SIP registration.
Access to the fixed-phone-like functions from any registered mobile phone(in addition to the PBX DTMF-Features) via DTMF Features of the GSM GW:
- call hold/resume
- swap between the calls
- transfer
- blind transfer
Tested Call Flows
- Normal user outbound to GSM
- A call from a PBX user routed via LCR to the GSM network via GSM GW
- Inbound to normal user
- A call from GSM network to an internal PBX user
- Inbound to Mobility Extension user
- A call from any PBX user or from outside the PBX to the Mobility Extension user(One Number)
- Mobility Extension to normal user
- A call from mobile phone of the Mobility Extension user via GSM GW into the PBX to an internal PBX user
Important Components
Server Requirements
- no server components required
Product Setup
Installation & Configuration of the vendor hardware
- System parameters
- Set IP address, SIM PIN Number and DTMF codes. Use "+" for the "End of dialing" if you intend to use PBX based DTMF features.
- SIP parameters
- "SIP registration expires" must be set to 120s(see minor bugs). Set DTMF RFC2833.
- GSM outgouing groups
- Set CLIR to "Disable (CLIP - on)". Our experience is that in Norway Delay for alerting has to be set to 2 seconds. With only one second there is no ringtone.
- GSM incoming groups
- Set "Accept incoming calls + dialtone".
- Network list
- Set prefixes according your GSM provider.
- LCR table
- Configuration example for straightforward LCR.
- GSM basic parameters
- Set "Generate busy tone to GSM".
- Mobile Extension
- Define PBX User Name under Name, PBX User Number under User and PBX User Password under Password. The parameter Name must be one word without spaces. Password must be configured. Set users mobile phone number under CLIP.
Installation & Configuration of the innovaphone components
The GSM GW is registered on the gatekeeper GW3:
LCR Routing from and into the PBX:
No special configuration in the PBX is required, mobile extension user is registered directly to the user object.
Product Test
SIP Interop Test Results
For more information on the test procedure, please read the following wiki article: SIP Interop Test Description.
Basic Call
calls between mobile phone via GSM GW and innovaphone phones (both directions).
Tested feature | Result |
---|---|
call using g711a | Yes |
call using g711u | Yes |
call using g723 | Nok |
call using g729 | Yes |
Overlapped sending | Not supported |
Early media channel | Yes |
Fax using T.38 | Not supported |
CGPN can be supressed | Yes |
Reverse Media Negotiaton | Yes |
Codec Renegotiaton | Yes |
Long time call possible(>30 min) | Not tested, should work(no sessions expired timer) |
Voice Quality OK? | Yes |
Direct Dial In
Tested feature | Result |
---|---|
Inbound(GSM GW-> innovaphone) | Not supported |
Outbound(innovaphone -> GSM GW) | Not supported |
DTMF
DTMF via RFC2833 is supported and must be activated on the GSM GW. Tested from mobile phone via GSM GW to innovaphone pbx and vice versa.
Tested feature | Result |
---|---|
DTMF tones sent to GSM correctly | Yes |
DTMF tones received from GSM correctly | Yes |
Hold/Retrieve
Tested between mobile phone via GSM GW and innovaphone phones. Tested in both directions.
Tested feature | Result |
---|---|
Call can be put on hold | Yes |
Held end hears music on hold / announcement from PBX | Yes |
Held end hears music on hold | Yes |
Transfer with consultation
innovaphone phone transfers mobile call (via GSM GW) and vice versa. Call returns works only when innovaphone phones transfers call (pbx feature).
Tested feature | Result |
---|---|
Call can be transferred | Yes |
Held end hears music on hold | Yes |
Call returns to transferring device if the third
Endpoint is not available |
Yes |
Transfer with consultation (alerting only)
innovaphone phone transfers mobile call (via GSM GW) and vice versa. Call returns works only when innovaphone phones transfers call (pbx feature).
Tested feature | Result |
---|---|
Call can be transferred | Yes |
Held end hears music on hold or dialing tone | Yes |
Call returns to transferring device if the third
Endpoint is not available |
Yes |
Blind Transfer
Tested between mobile phone via GSM GW and innovaphone phones in both directions.
Tested feature | Result |
---|---|
Call can be transferred | Yes |
Held end hears dialing tone | Yes |
Broadcast Group & Waiting Queue
Calls from mobile phone (via GSM GW) to innovaphone pbx.
Tested feature | Result |
---|---|
Mobile phone can make a call to a Broadcast Group | Yes |
Mobile phone can get a call from a Broadcast Group | Yes |
Mobile phone can make a call to a Waiting Queue | Yes |
Mobile phone can get a call from a Waiting Queue | Yes |
Announcement if nobody picks up the call | Yes |
Mobility Features available via DTMF on ViceBlue Lite
Call Hold
Default DTMF code 7*.
Put on hold with *7, retrieve with 9#.
Transfer
Default DTMF Code <Number>#
- Call form mobile to GSM GW
- Dial 101#
- 101 accepts the call
- Dial 7*
- Dial 102#
- 102 accepts the call
- Hang up
- 101 and 102 are connected
Blind Transfer
Default DTMF Code #<Number>#
- Call form mobile to GSM GW
- Dial 101#
- 101 accepts the call
- Dial 7*
- Dial #102#
- 102 alerting
- Hang up manually (9# doesnt work)
Folow Me
Enable/disable calls on user object from PBX to GSM.
SMS at No Answer
Enable/disable SMS via GSM to the number of mobile phone.
Mobility Features available via PBX DTMF Features
A DTMF Digit # is used on the GSM GW to provide the end of dialing as default seting, but it also used in the PBX DTMF Feature Object.
- Solution 1 (used for tests)
- Change or disable "End of dialing" Digit to "+" and reduce the "Timeout for entering DTMF" on GSW GW.
- Solution 2
- Change PBX DTMF Features to use * instead of #.
Tested feature | Result |
---|---|
Enable/Disable CFs | Yes |
Pickup Group | Yes |
Park/Unpark | Yes |
Call Completion Busy | Yes |
Join Group | Yes |
Minor Bugs
- No spaces in the username of Mobile Extension allowed
- PBX User Object field Name must be without spaces, in order to be able to register the Mobile Extesion from 2n VoiceBlue Lite. The space is not escaped according RFC 3261 (19.1.4 URI Comparison) : should be
One%20Number
, but isOne Number
. Therefore registration is possible, but further SIP interop is broken(e.g. calls to busy subscribers, see the next Bug). - No busy tone to Mobile Extension
- if the PBX user is busy and is called by the Mobile Extension user, the call is just terminated without busy tone. If the username of Mobile Extension include a space, the call is terminated with
403 Forbidden
by the PBX, instead to be terminated with486 Busy Here
.
Fixed in Version 02.07.35i19
- Wrong SIP To-tag after 407
- The SIP tag in "To:" Header is broken after
407 Proxy Authentication Required
was sent from the PBX. Affects call transfer from Mobile Extension to internal user. Workaround: remove password on PBX User Object.
Solved by workaround
- SIP Registeration Timeout
- The default Registration Timeout of 600 sec. for the SIP Registration is not updated when the PBX defines another timeout in 200 OK after REGISTER. Workaround in the configuration of 2n VoiceBlue Lite: set register timeout to 120 manually.