Howto:RealPresence Mobile - Polycom - SIP Testreport

From innovaphone wiki
Jump to navigation Jump to search

Summary

The Polycom RealPresence Mobile app supports H323 and SIP registration. This is the testreport for the client using SIP, we don't recommend the use of H.323 since the basic functionalities will not work properly with this protocol. Moreover the app is available for iOS and Android clients. Only the iOS version is tested, since innovaphone has an own Android softwarephone.

All tests were made in Standalone Mode' with an IPAD 4 device on iOS 7.

The tests for this product could not be completed since not all mandatory tests were passed. The Polycom RealPresence Mobile App is unable to perform HOLD and TRANSFER, which are mandatory features for a telephony system. It is limited to basic calls and a user talking on this device cannot be put on hold (when the device/App iss put ON HOLD, the held user doesn't hear MOH from the PBX).

Certification Status

The tests for this product could not be completed or not all mandatory tests were passed. See the Summary section for more details.

Testing of this product has been finalized January 10th, 2014.

Version

Firmware Version:

3.0.1-41989

innovaphone Firmware: v10 SR4

Test Setup

Testreport Terminals SIP or H323 1.PNG

Device Setup

Tested feature Result
Register Device w/o specific configuration (requires DHCP) Not tested
DHCP is default Ok
DHCP yields timeserver and time displays correctly Ok
SNTP config has TZ string for timezone/dst autoconfig Not tested
DHCP yields correct default gateway Ok
Device supports magic registration (e.g. by serial) Not tested
Fixed registrations works Ok
Device registers w/o Extension (just by name) Ok
Device registers by name with non-latin1 characters (e.g. UserÄÖÜ) Not tested
Device registers by extension Not tested
Device registers with password Not tested
Device registers multiple identities No
2nd GK is supported (mit SIP??) Not tested
Changing registrations between GK1 and GK2 (mit SIP??) Not tested
PBX redirect (UserObject on Master/Phone at Slave registered) Not tested
Physical Location (@PBX) correct? Not tested
Device supports STUN protocol Not tested
Device sends NAT - keepalive messages Not tested
Device usable in hosting scenarios? Not tested
Device refreshes the PBX registration Ok
Device supports SIP over TCP Yes
Device supports SRTP Not tested
Device supports SIPS (SIP over TLS) Not tested
Device supports HTTPS N/A
Device supports VAD (Voice activity detection) Not tested
Device supports Auto-Answer (needed when used with CTI client) Not tested
Supported menu languages Not tested

Test Results

Basic Call

Tested feature Result
call using g711a Ok
call using g711u Ok
call using g729 N/A
call using g722 Not tested
Overlapped sending N/A
Device sets up an early media channel for incoming calls N/A
Device sets up an early media channel for outgoing calls Ok
Device shows called id number Ok
Device shows called id name Ok
Device shows called id display info Ok
Fax using T.38 N/A
CGPN can be suppressed N/A
Reverse Media Negotiation Ok
Device shows CDPN/CGPN on incoming call Ok
Device shows CDPN/CGPN on outgoing call Ok
Device shows connected number No
Device shows diverting number No
Device supports distinctive ringing Not tested
Device supports asymetric codec negotiation Not tested
Device supports codec renegotiation during a conversation Not tested
Device shows correct display message in case of busy CDPN Ok
Device shows correct display message in case of not existing CDPN Ok
Device shows correct display message in case that the call is declined Ok, same as busy
3party conference possible N/A
Device supports display updates during call(needed for Directory Search object) No
Long Time Call (>30 min) works? OK
Registration redirecting works? Not tested
Incoming SRTP call - SRTP not enabled on DUT Not tested
Incoming SRTP call - SRTP enabled on DUT Not tested
Voice Quality OK? Ok

DTMF

Tested feature Result
DTMF tones sent correctly Ok
DTMF tones received correctly N/A

Hold/Retrieve

Tested feature Result
Device handles incoming hold/unhold correctly OK
Hold Party Hears MOH NOK (use "inactive" instead of "recvonly" when on hold)
Device can put a call on hold using correctly(inactive or sendonly) NOK (doesn't have HOLD option)


Transfer with consultation

Tested feature Result
Call can be transferred N/A (Don't have Transfer option)
Held end hears music on hold N/A

Not tested Not tested

Tested feature Voice Ok? MoH Ok?
inno1 calls inno2. inno2 transfers to testphone. Not tested Not tested
inno1 calls inno2. inno1 transfers to testphone. Not tested Not tested
inno1 calls testphone. inno1 transfers to inno2. Not tested Not tested
inno1 calls testphone. testphone transfers to inno2. N/A N/A
testphone calls inno1. inno1 transfers to inno2. Not tested Not tested
testphone calls inno1. testphone transfers to inno2. N/A N/A

Transfer with consultation (alerting only)

Tested feature Voice Ok? MoH Ok?
inno1 calls inno2. inno2 transfers to testphone. Not tested Not tested
inno1 calls inno2. inno1 transfers to testphone. Not tested Not tested
inno1 calls testphone. inno1 transfers to inno2. Not tested Not tested
inno1 calls testphone. testphone transfers to inno2. N/A N/A
testphone calls inno1. inno1 transfers to inno2. Not tested Not tested
testphone calls inno1. testphone transfers to inno2. N/A N/A

Blind Transfer

Tested feature Result
Call can be transferred N/A (Don't have Transfer Option
Held end hears dialling tone N/A


Tested feature Voice Ok?
inno1 calls inno2. inno2 transfers to testphone. Not tested
inno1 calls inno2. inno1 transfers to testphone. Not tested
inno1 calls testphone. inno1 transfers to inno2. Not tested
inno1 calls testphone. testphone transfers to inno2. N/A
testphone calls inno1. inno1 transfers to inno2. Not tested
testphone calls inno1. testphone transfers to inno2. N/A

Blind Transfer (alerting only)

Tested feature Voice Ok?
inno1 calls inno2. inno2 transfers to testphone. Not tested
inno1 calls testphone. testphone transfers to inno2. N/A
testphone calls inno1. inno1 transfers to inno2. Not tested

Broadcast Group & Waiting Queue

Tested feature Result
testphone makes call to a Broadcast Group. inno1 picks up. Not tested
inno1 makes call to a Broadcast Group. testphone picks up. Not tested
testphone makes call to a Waiting Queue. inno1 picks up before announcement is played. Not tested
testphone makes call to a Waiting Queue. inno1 picks up after announcement is played. Not tested
inno1 makes call to a Waiting Queue. testphone picks up. Not tested

Other Features

Directory

Tested feature Result
Device built-in directory N/A
Can be dialled from N/A
Does CLI resolution N/A
display update if directory object is used? N/A


Tested feature Result
External LDAP Server supported N/A
Can be dialled from N/A
Does CLI resolution N/A
display update if directory object is used? N/A

Keys

Tested feature Result
Device has speed dial keys N/A
Device has programmable function keys N/A
Device has partner keys N/A

CTI Features (with SOAP / TAPI / myPBX)

Tested feature Result
User Call - outgoing call Not Tested
User Connect - Answer incoming call Not Tested
User Reject - Reject alerting call Not Tested
User Disconnect - Disconnect active call Not Tested
User Hold - Put connected call on hold Not Tested
User Hold Retrieve - Retrieve call on hold Not Tested
User Transfer - Transfer with Consult Not Tested
User Transfer - Transfer with Consult (Alerting only) Not Tested
User Transfer - Blind Transfer Not Tested
3PTY - Make 3rd Party Call Not Tested
Connected Number Update on Display Not Tested

UC Features

Tested feature Result
Video calls possible? OK
Video conference possible? (max. amount of participants) Not Tested
Video Codecs H.264
enable/disable video during call OK
Set own presence possible? N/A
See presence of others possible? NOK
chat with mypbx client possible? N/A
chat with same vendor client possible? N/A
send IM - messages to phones possible? N/A

Configuration

Polycom® RealPresence™ Mobile is available via iTunes or Google Play.

http://www.apple.com/de/itunes/

https://play.google.com/store/apps/details?id=com.polycom.cmad.mobile.android.phone&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5wb2x5Y29tLmNtYWQubW9iaWxlLmFuZHJvaWQucGhvbmUiXQ

Once installed several SIP settings have to be carried out. After which, the user can start internal calls over the company network or a VPN connection and is thus also available as an internal subscriber on video over his mobile end device.


Necessary settings in Apple devices:

If a Polycom registration screen is displayed: Click “next” once and on the following page click “cancel”.

Innovaphone polycom start.jpg


Then under settings (cog wheel icon) > SIP settings

  • Activate SIP calls: on
  • Transport protocol: TCP
  • Register SIP: on
  • SIP-Proxy Server: IP address of the innovaphone PBX
  • SIP Registr. Server: IP address of the innovaphone PBX
  • Domains: IP address of the innovaphone PBX
  • SIP user name: User name innovaphone PBX
  • Authorisation name: User password innovaphone PBX
  • SIP password: Registration password of the SIP user


Innovaphone polycom ipad einstellungen.jpg


Then back to settings and click >finish <.

Innovaphone polycom darstellung.jpg

Related Articles

Polycom RealPresence Mobile Release Notes