hybird Media5-fone pro SIP Table of Contents 1.Test setup...1 2.VoIP configuration of hybird PBX...2 3.Configuration of Media5-fone (softphone)...3 4.Basic voice feature...6 1. Test setup 1. The hybird IP PBX has BOSS version 7.10.3 (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 two preinstalled softphone VoIP clients Media5-fone and Groundwire is configured according to the WLAN settings of the Access-Point (for WLAN configuration of your smartphone please refer to its handbook). 1 of 7 Final report
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 7 Final report
3. Configuration of Media5-fone (softphone) Tabular overview of relevant SIP settings: Media5-fone SIP settings hybird equivalent Basic SIP account settings Title (Titel) - recommended Media5-fone settings User name (Benutzername) Password (Passwort) 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. SIP server settings Address (Adresse) LAN IP address of the hybird. Reg. Timer (sec). In factory default this is the IP address 192.168.0.250 of the LAN interface en1-0. Client Registration Timer (Endgeräte- Registrierungstimer) in GUI menu VoIP Settings Options Softphone setting needs to be 3 of 7 Final report
Advanced settings (Erweitert) Display name (Namensanzeige) - less or equal to PBX setting Auth. Name Number (Nummer) Subscribe MWI (Einschreiben MWI) DTMF method (DTMF- Methode) Codecs WiFi arbitrary description of your mailbox Internal Number (Interne Rufnummer) in GUI menu Applications Voice Mail System Voice Mail Boxes, which is identical the same setting in GUI menu Numbering User Settings Users Numbers Softphone setting need to value configured in PBX Internal Number (Interne Rufnummer) in GUI menu Applications Voice Mail System General Softphone setting need to value configured in PBX - Switch on message waiting indication in softphone DTMF in VoIP Settings Codec Profiles Per default in PBX all methods are on. You have to choose RTP Inband (RTP Eingangssignalband) in Media5-fone for best interoperability. Selected codecs in GUI menu VoIP Settings Codec Profiles 4 of 7 Final report
Softphone codec settings needs to have at least one codec out of the codec list in PBX. 5 of 7 Final report
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 Media5-fone 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. 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. 6 of 7 Final report
Call transfer was always done by called internal VoIP. Attended call transfer Note: Blind transfer from internal (analog) to external (ISDN) needs external number without trailing zeros. This is a known Elmeg bug/feature. 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 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. Not testable Media5-fone does not support call forwarding. First call was from External ISDN to internal VoIP. Second call was from internal analog to internal VoIP. Works including PIN access. Error Media5-fone does not send RTP EVENT data package for PIN access. Error hybird does not accept PIN, altough it seems to be correctly transmitted via SIP INFO data packages. 7 of 7 Final report