Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version 3

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Content Zone

Introduction

At the heart of the sipXecs/openUC system is a pure SIP Proxy environment. This causes a lot of phone vendors to have issues with sipXecs due to imcomplete or missing SIP stack functionality. Therefore it is imperative that phones are put through a stringent series of tests to verify that they are compatible with sipXecs/openUC.

Purpose of This Page

The purpose of this page is to provide a template for a vendor to copy to their personal wiki space for modification. Once the vendor has performed certification tests then a post to the sipXecs user mailing list with a link to the page in the vendor's personal space should be posted.

Testing Caveats

Note

These tests are intended to be performed with an Audiocodes Gateway and a certified ITSP, such as voip.ms

Note

At least 3 phones (of the type being certified), referred to as phone A, phone B, and phone C, and one Polycom SoundPoint IP 450/550/560/650/670, referred to as phone D

Note

Full certification be eZuce requires a provisioning plugin. This can be written by the vendor by following the procedures in the Managed Phones Plugin section.

Verified Status

All items in this table must pass if the device is to be considered as Verified status

Test #Item to TestExpected ResultActual ResultPassFailCapture of Valid ResultNotes 
Basic Functionality
1aRegister phone to SIP domain using SRV record, UDP transportPhones should successfully register, load balancing should occur on sipXecs/openUC system      
1bRegister phone to SIP domain using SRV record, TCP transport Phones should successfully register, load balancing should occur on sipXecs/openUC system      
2Phone should support codecs G.711a/u and G.729Calls made and received with G.711a/u and G.729 should complete successfully      
3Phone has capability to subscribe to message waiting indicator servicePhone should properly subscribe to message waiting indicator service and a message waiting indicator lamp should light and extinguish when messsage are left and erased (see step 7 below)      
Internal Only Scenarios
4Place outbound call from phone A to phone B (internal)Call should be answered on phone, verify audio is present on both phones. The call should complete successfully.      
5Place outbound call from phone A to phone B (internal). Place call on hold for 10 seconds. Retrieve call from hold.Call should be answered on phone, verify audio is present on both phones, placed on hold for 10 seconds, and retrieved from hold. Verify audio is present on both phones. The call should complete successfully.      
6Place outbound call from phone A to phone B (internal). Perform blind transfer to phone C. Answer call on phone CCall should be answered on phone. Transfer should complete successfully, verify audio is present on both phones. The call should complete successfully.      
7Place outbound call from phone A to phone B (internal). Perform attended transfer to phone C. Answer call on phone C, then complete transfer..Call should be answered on phone. Transfer should complete successfully, verify audio is present during all phases of the call. The call should complete successfully.      
8Place outbound call from phone A to phone B (internal) but do not answer the call. The call should be answered by the voicemail system. Leave a voicemail, then hang up.The message waiting indicator (MWI) notification lamp should illuminate on the receiving phone      
9aPlace outbound call from phone B to the voicemail pilot number (default extension 101). Log into voicemail.Call should be answered by voicemail system. Verify DTMF (keypresses) are functioning properly by logging into voicemail system. The call and DTMF keypresses should complete successfully. DO NOT TERMINATE THE CALL      
9bCheck voicemail messages, delete new voicemail messageMessage waiting indicator (MWI) notification lamp should be extinguished. DO NOT TERMINATE THE CALL      
9cRecord a new personal greeting. This is to ensure that audio is being received by the voicemail systemPersonal greeting should be recorded. The call should complete successfully.      
10Place outbound call from phone A to auto attendant (default extension 100). Dial the extension for phone B to initiate a transfer.Call should be answered by the auto attendant system. Verify DTMF (keypresses) are functioning properly by entering an extension. The call should then be transferred to phone B. Answer the call on phone B. The call and DTMF keypresses should complete successfully.      
11aAdd Phones A, B, and C as speed dials with presence monitoring to phone D.Phone D should reboot with 3 BLF entries monitoring phones A, B, and C     If presence indication is not working this indicates a problem with the way the phones handle dialog events. Please refer to http://tools.ietf.org/html/rfc4235 for information about properly constructing dialog events 
11bPlace outbound call from phone A to phone B (internal)The presence indicator for phone A should be solid red (indicating on the phone). The presence indicator for phone B should be blinking green (indicating ringing)      
11cOn phone D, press the blinking green presence indicator for phone B to intercept the call with directed call pickupPhones A and D should now be on a call. Phone D should indicate a solid red presence indication for phone A. DO NOT TERMINATE THE CALL      
11dOn phone D initiate a conference with phone B (with phone A still communicating with phone D).3-way conference should be established with phones A, B, and D. Phone D should indicate a solid red presence indication for phones A and B.      
11eTerminate the conference call

Phone D should not have any presence indicators for any phones lit up at this point. The call should complete successfully.