hybird Groundwire SIP interoperability test

Transcription

1 hybird Groundwire SIP Table of Contents 1.Test setup VoIP configuration of hybird PBX Configuration of Groundwire (softphone) Basic voice feature Test setup 1. The hybird IP PBX has BOSS version (from 2012/04/03) installed. 2. The second ISDN port (labeled S/U 2) of the hybird is connected to the provider telephone line. This port (per factory default) is jumpered as ISDN NT. This port is configured in test setup as ISDN Point to Multipoint. For ISDN configuration please refer to the device documentation. 3. The first analog port (labeled FXS 1) of the hybird is connected to a standard analog telephone (which is DTMF and CLIP capable). 4. One of the LAN ports of the hybird (in factory default all 4 Ethernet ports are bundled in Ethernet interface en1-0) is connected to a (Bintec) Access Point, which provides WLAN access and the IP network access to the PBX for VoWLAN mobile phones. The configuration of the Access Point and IP networking is not covered here. In the test setup the Bintec Access Point was configured via WLAN Controller inside the hybird. Please refer to the relevant device documentation how to setup IP networking and the WLAN (Controller). 5. A smart phone (in the test setup an Apple iphone 4) with the Groundwire is configured according to the WLAN settings of the Access-Point (for WLAN configuration of your smartphone please refer to its manual). 1 of 6 Final report

2 2. VoIP configuration of hybird PBX Note: See also screenshots in the ZIP archive for the sample setup PBX configuration. A (new) VoIP phone account is configured in GUI menu Numbering User Settings Users. The Internal Number (in sub page Numbers ) was choosen out of the list of free numbers and with Outgoing Signalisation (in sub page Outgoing Signalisation ) one of the configured MSNs of the above mentioned ISDN Point to Multipoint interface was selected. The VoIP phone thus uses this ISDN line and the choosen MSN for outgoing external calls. Password for IP Phone Registration (SIP account password) and PIN for Phone Access (e.g. for mailbox access) was set, too (in sub page Authorizations ). As well an user account for GUI access was created for the VoIP account so that the user can configure own account customizations without the need for administrative assistance. In GUI menu Numbering Call Distribution Incoming Distribution the previously choosen MSN for the VoIP account is now assigned to the internal number of the VoIP account. With that setting the VoIP phone is reachable from outside with that choosen MSN (external phone number) and in GUI menu Numbering Terminal Assignment VoIP the configured VoIP account is associated to a new device profile with Location LAN and Internal Numbers the configured phone number of the VoIP account. A VoIP codec profile does not necessarily need to be created as an internal standard profile is always available. A custom profile can be created in VoIP Settings Codec Profiles. In GUI menu Applications Voice Mail System General the Voice Mail System is enabled and a free Internal Number is given to the voice mailbox system (identical for all users). Finally in GUI menu Applications Voice Mail System Voice Mail Boxes the voice mailbox is configured for the VoIP account and the Check PIN option is enabled there. 2 of 6 Final report

3 3. Configuration of Groundwire (softphone) Tabular overview of relevant SIP settings: Groundwire SIP settings hybird equivalent Basic SIP account settings Name - recommended Groundwire settings User name (Benutzername) Password (Passwort) Domain (Domäne) arbitrary description of your SIP profile Internal Number (Interne Rufnummer) in GUI menu Numbering User Settings Users Numbers Softphone setting need to value configured in PBX. Password for IP Phone Registration (Passwort für IP- Telefonregistrierung) in GUI menu Numbering User Settings Users Authorizations Softphone setting needs to be less or equal to PBX setting. LAN IP address of the hybird. Display name (Angezeigter Name) In factory default this is the IP address of the LAN interface en arbitrary description of your SIP account Advanced SIP account settings Voic Number Internal Number (Interne Rufnummer) in GUI menu Applications Voice Mail 3 of 6 Final report

4 Codecs for WiFi DTMF Mode (DTMF-Modus) Call forwarding (Anrufweiterleitung) Expires System General Softphone setting need to value configured in PBX. Selected codecs in GUI menu VoIP Settings Codec Profiles Softphone codec settings needs to have at least one codec out of the codec list in PBX. DTMF in VoIP Settings Codec Profiles Per default in PBX and in Groundwire softphone all methods are on. You have to select at least RFC 2833 in Groundwire for best interoperability. - (However call forwarding in PBX is related) Optional softphone setting, which can be overruled by custom call forwarding rules in PBX. Client Registration Timer (Endgeräte- Registrierungstimer) in GUI menu VoIP Settings Options Softphone setting needs to be less or equal to PBX setting. 4 of 6 Final report

5 4. Basic voice feature All tests were done with all three devices (external ISDN phone, internal analog phone and internal VoWLAN soft phone). The tested call directions are (if applicable): 1. Internal VoIP to internal analog and vice versa if not noted otherwise. 2. Internal VoIP to external ISDN and vice versa if not noted otherwise. So in total 4 call directions for each test are checked (if not noted otherwise) and a test is declared if the tested feature worked in all tested cases. The test results are: Feature CLIP Call waiting (Anklopfen) Hold active call (Halten) Second call (Rückfrage) Alternate call (Makeln) Conference Blind call transfer Groundwire on hybird Caller was always internal VoIP and hold was always done by caller. Caller was always internal VoIP and second call was always done by caller. Caller was always internal VoIP and alternate call was always done by caller. Caller was always internal VoIP and conference was initiated always by caller with first call from VoIP to ISDN and second call to analog and afterwards vice versa. Partly : Blind transfer works only between internal called party phones (of course caller can be external). First call was from External ISDN to internal VoIP, 5 of 6 Final report

6 Attended call transfer Call forwarding by phone (not by PBX, which is something different and a standard hybird PBX functionality) Message waiting Access mailbox via RTP Inband Access mailbox via RFCs 2833/4733 Access mailbox via SIP Info which was transfered to internal analog. Second call was from internal analog to internal VoIP, which was transfered to external ISDN. Call transfer was always done by called internal VoIP. First call was from External ISDN to internal VoIP, which was transfered to internal analog. Second call was from internal analog to internal VoIP, which was transfered to external ISDN. Call transfer was always done by called internal VoIP. Partly : Call forwarding by phone only works to another internal called party phone First call was from External ISDN to internal VoIP, which was forwarded to internal analog. Second call was from internal analog to internal VoIP, which was forwarded to external ISDN. Call forwarding was always done by called internal VoIP. First call was from External ISDN to internal VoIP. Second call was from internal analog to internal VoIP. Error Error 6 of 6 Final report