Audiocodes MP11xFXS SIP v5.2 OmniPCXOfficeR7.0 IWR Ed01

Alcatel Applications Partner Program Inter-Working ReportPartner: AudioCodes Application type: Analog equipements SIP Gateway Application name: MP-112 FXS

The product and version listed have been tested with the Alcatel Communication Server and the version specified hereinafter. The tests concern only the inter-working between the Application Partner product and the Alcatel Communication platforms. The inter-working report is valid until the Application Partner issues a new version of such product (incorporating new features or functionality), or until Alcatel issues a new version of such Alcatel product (incorporating new features or functionality), whichever first occurs. ALCATEL MAKES NO REPRESENTATIONS, WARRANTIES OR CONDITIONS WITH RESPECT TO THE APPLICATION PARTNER PRODUCT. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, ALCATEL HEREBY EXPRESSLY DISCLAIMS ANY AND ALL REPRESENTATIONS, WARRANTIES OR CONDITIONS OF ANY NATURE WHATSOEVER AS TO THE APPLICATION PARTNER PRODUCT INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON INFRINGEMENT OR FITNESS FOR A PARTICULAR PURPOSE AND ALCATEL FURTHER SHALL HAVE NO LIABILITY TO APPLICATION PARTNER OR ANY OTHER PARTY ARISING FROM OR RELATED IN ANY MANNER TO THIS CERTIFICATE.

Alcatel Applications Partner Program Inter-working reportCopyright 2008 Alcatel, All rights reserved

Edition 1 Page 1

Tests identificationDate of the tests Alcatels representative Partners representative Alcatel Communication Platform (OmniPCX 4400/Enterprise, OmniTouch, OmniPCX Office, ...) Alcatel compatibility release Partners application version Environment (if it has a sense)Author(s): Reviewer(s): Historic Edition 1: creation of the document - 12-14-2007 R. Baumert E.Denis, R.Himmi

December 2007 Roland Baumert OmniPCX Office R7.0 / 005.001 F5.20A.025-002ACD

Business

Test resultsPassed Passed with restrictions Refused Postponed

Refer to the section 4 for a summary of the test results.


Edition 1 Page 2

Company Contact Information(Information provided by the partner)

Contact name: Title: Address 1: City: Zip: Country: Phone: Fax: Web address: E-mail:

Bertrand Goldfarb Sales Director 3, Avenue de la Source BOUGIVAL 78380 France +33 1 39 18 29 57 +33 1 30 82 20 12 http://www.audiocodes.com [email protected]


Edition 1 Page 3

TABLE OF CONTENTS1 2 3 4 INTRODUCTION.................................................................................................................................... 6 GLOSSARY ......................................................................................................................................... 6

1.1

APPLICATION INFORMATION .......................................................................................................... 7 TESTS ENVIRONMENT ....................................................................................................................... 8 GENERAL ARCHITECTURE .................................................................................................................. 8

3.1

5

4.1 4.2 4.3 4.4 4.5

SUMMARY OF TEST RESULTS ........................................................................................................ 9

5.1 5.2

TEST SCENARIOS ............................................................................................................................. 11

IMPORTANT REMARK:........................................................................................................................ 9 SUMMARY OF MAIN FUNCTIONS SUPPORTED ...................................................................................... 9 SUMMARY OF PROBLEMS ................................................................................................................... 9 SUMMARY OF LIMITATIONS ............................................................................................................. 10 NOTES, REMARKS ............................................................................................................................ 10 TEST PROCEDURE............................................................................................................................. 11 RESULT TEMPLATE .......................................................................................................................... 11

6

6.1 CONFIGURATIONS ASPECTS.............................................................................................................. 12 6.1.1 Objective ................................................................................................................................. 12 6.2 SET-UP AND ACCEPTANCE TESTS...................................................................................................... 13 6.2.1 Test objectives......................................................................................................................... 13 6.2.2 Test procedure ........................................................................................................................ 13 6.3 FAX ................................................................................................................................................ 14 6.4 DEFENCE AND PERTURBATION ......................................................................................................... 15 6.4.1 Test objectives......................................................................................................................... 15 6.5 MEDIA SPECIFICATION..................................................................................................................... 16 6.5.1 Test objectives......................................................................................................................... 16 6.6 BASIC CALLS ................................................................................................................................... 17 6.6.1 Test objectives......................................................................................................................... 17 6.6.2 Test procedure ........................................................................................................................ 17 6.7 TELEPHONIC SERVICES..................................................................................................................... 18 PROBLEM REPORTS ........................................................................................................................ 22 APPENDIX A: TESTDIRECTOR TEST LIST................................................................................. 24 APPENDIX B : APPLICATION DESCRIPTION ............................................................................ 30 10.1 10.2 10.3 10.4 10.5 11.1 11.2 APPENDIX C: AUDICODE CONFIGURATION ........................................................................ 37 IP SETTINGS .................................................................................................................................... 37 GENERAL PARAMETERS ................................................................................................................... 37 PROXY AND REGISTRATION.............................................................................................................. 38 AC SETS DIRECTORY NUMBERS ....................................................................................................... 38 SUPPLEMENTARY SERVICES ............................................................................................................. 39 SIP CONFIGURATION ....................................................................................................................... 40 ARS................................................................................................................................................. 41 Edition 1 Page 4

TESTING............................................................................................................................................... 12

7 8 9 10

11

APPENDIX D: OMNIPCX ENTERPRISE CONFIGURATION............................................... 40


12 13

APPENDIX D: PARTNER ESCALATION PROCESS ............................................................... 42 APPENDIX E: AAPP PROGRAM, DOCUMENTATION AND TECHNICAL ASSISTANCE43

14 APPENDIX F: ALCATEL-LUCENT ESCALATION PROCESS IN CASE OF PROBLEM WITH A CERTIFIED EXTERNAL APPLICATION (REFERENCED IN THE AAPP) .................... 47


Edition 1 Page 5

1 IntroductionThe goal of these tests is to qualify an external application as an Alcatel Applications Partner Program solution for the Alcatel Communication Platform. The scope of the tests is the interoperability of the application with the Alcatel Communication Platform. It covers a basic or complex inter-working to ensure that services requested by the application and provided by the Communication Platform (and/or conversely) are properly completed. These tests do not verify the functional achievement of the application as well as they do not cover load capacity checks, race conditions and generally speaking any real customer's site conditions. The objective of these tests is mainly to validate the interworking with Fax machines in T38 and transparent mode connected behind AudioCodes MP112/FXS gateway that uses SIP protocol to work with OXO PBX R7.0..

1.1 GlossaryMF : Multifrequency numbering SIP : Session Initiation Protocol CLIP : Calling Line Identification Presentation CLIR : Calling Line Identification Restriction IP: Internet Protocol VoIP: Voice over IP FoIP: Fax over IP

RTP: Real time Transport Protocol

PSTN: Public switched telephone network

T.38: ITU standard for sending FAX across IP networks in a real-time mode


Edition 1 Page 6

2 Application informationApplication type: SIP Gateway for Analog equipments as Sets, Faxes or Modems. Application commercial name: AC MP-112/FXS Application version: Interface type: 5.20 (F5.20A.025.002) SIP

Brief application description: AudioCodes box plays as a gateway for Analog sets, Faxes or Modems equipments allowing them to access to IP based telephony networks accessed using SIP or H323 IP protocols (only SIP is concerned by this campaign report, also no Modem tests have been done). This solution allows in our business context a remote connectivity for such equipments working logically as local sets for the PBXs via the IP/Internet world. The AudioCodes MediaPack series (AC MP-xxx) for analog user/station interfaces (FXS Foreign Exchange Station) support 2 to 24 analog port connections allowing up to 24 simultaneous Voip communications. This product also supports following features (out of this tests scope) as: Call reports / Security using IPSec and IKE, SSL/TLS for SIPS and HTTPS, Radius authentication, NAT, Internal Firewall / Qos handling / SNMP supported / Management of several AC boxes using a unique management application: AudioCodes EMS server.


Edition 1 Page 7

3 Tests environment3.1 General architectureFigure 1 Tests environment

PSTN

Fax

OXO1

OXO2

L ANG711

Private SIP trunk PrivateSIP PrivateSIP

L AN

Fax

Analog Set

AudiCodes MP112

AudiCodes MP112

Analog Set

Fax

The objective of the tests was mainly to use one OXO node and one AudioCodes gateway playing with its analog sets/Faxes trough the Private SIP Trunking connectivity to OXO, also to test Breakin and out with equipments behind PublicSTNetwork. Some tests have also been done using the full connectivity of this platform (ie both OXO and Both AudioCodes equipments) mainly for simple calls, Forwarded and some Transfer calls.


Edition 1 Page 8

4 Summary of test results4.1 Important Remark:Concerning this campaign, functional feature tests concerning telephonic services that AudioCodes analog sets could activate (broker and corresponding situations, Transfers, Conferences) have actually not been tested because: - existing anomalies (the already found/known have not yet been corrected (It concerns Transfer problems) - these features are also actually not supported by OXO Product (R&D) when activated by AudioCodes analog sets. For these features the tests concerned the situation where the AudioCodes set are implied in (and not where these sets are activating services). The other tests concerned mainly FAX communications. Several points are related again in this report giving the current whole status of the subject.

4.2 Summary of main functions supportedThe main supported functions implied in the test campaign are: Installation and configuration of the AudioCodes gateway Compatibility with OXO SIP Private Trunking Basic communications (internal and external) Check telephonic features (Basic Call, Broker call, Transfer, Conference, Forwards with internal and/or external correspondents). Supports all kind of numbering Abbreviated Number, internal and external numbers) DDI number can be used for the AC Analog equipments, for incoming and outgoing calls. Access to the OXO Voice mail boxes and MF dialling for navigation Multi Frequency sending in conversation/connected state Different kind of Codec compressions can be used: G711, G729, G723. Fax G3 and SuperG3 Check.

4.3 Summary of problemsProblems found during this campaign FAX communication: Problem when a Fax is in a Queued situation. At the end of the current comm, the waiting Fax communication cannot be established. -> It seems to be an AudioCodes problem. FAX communication: In the architecture implying 2 OXO PBX, when an AudioCodes FAX is forwarded to another one, the caller Fax communication stays in a permanent Progress state. Same default occurs with analog sets. -> This is an OXO problem Transparent FAX communication: If configured so, OXO doesnt accept no transparent Fax requests (No adaptation to T38). (Enhancement request) Transparent FAX communication: If configured so, OXO doesnt accept the AudioCodes Fallback T38/G711 negotiation feature.


Edition 1 Page 9

An AudioCodes set (through SIP trunk) calls an ISDN destination with CLIR, => a Caller number is nevertheless generated to ISDN. => This is an OXO problem. An AudioCodes Forward to ISDN leads to an inaccessible call that can never be established => This is an OXO problem.

Still Open Problems found during previous campaign: Unsuccessful transfer from the Audiocode device if attribute Hold Format is 0000 ( default value ) Transfer failure when transferor is the called set and an Audiocode device

4.4 Summary of limitationsFound during this campaign

Limitations due to previous problems paragraph

Found during previous campaign; Successful transfer from the Audiocode device if parameter Hold Format is send only Conf call initiated by Audiocode not possible Call Back feature is not working/not possible. . A call back cannt be requested after calling an AC set which doesnt answer. . No Call Back is registered by OXO if an AC set calls an OXO set which doesnt answer, and the AC set cannt activate a Callback request. -> It is a normal limitation on SIP trunking, even if Private trunking. For Transfer features if more than 2 nodes or gateways are implied within, only OXO Heterogeneous SIP mode is supported (=> it is not working in Homogeneous mode)

4.5 Notes, remarks Anomalies crms1968 and 2211 are Closed / NTIA after meeting decisions Anomaly crms1916 concerning MF transmission has been corrected and validated Anomalies crms1861(Voip board reste) and 2026 Transfer Pb with Refer) are still open: In treatment


Edition 1 Page 10

5 Test Scenarios5.1 Test procedureStep Action N/A Result Origin of the problem Comment Step: a test may comprise multiple steps depending on its complexity. Each step has to be completed successfully in order to conform to the test. Step 0 when present represents the initial state for all the following steps. Action: describes which action to realize in order to set-up the conditions of the test. N/A: the step within this test is not applicable to this application. This has to be filled in only if the test is checked as mandatory in the applicability box. In that case, the column comment must indicate the reason of the non-applicability (e.g.: service not supported). Result: describes the result of the test from an external point of view. If it is positive, it describes which application's trigger was checked. If it is negative, it describes as precisely as possible the problem. Origin of the problem: this column has to be filled in when a problem occurs during the test. It must contain a high level evaluation of the localization of the responsibility: Alcatel or the Partner.

it is not intended during this test session to debug and fix problems.

5.2 Result templateThe results table must be formatted as indicated in the example below: Step 1 2 . action 1 . action 2 Action N/A Result OK OK OK X 5 . action 5 Origin of the problem Comment The application waits for PBX timer or phone set hangs up Relevant only if the CTI interface is a direct CSTA link No indication, no error message

3 4

. action 3 . action 4

NOK

it is not intended in this session to mention any Anomaly Report (the anomaly report will be mentioned in Paragraph 8 & Appendix A).


Edition 1 Page 11

6 TestingConvention: In the following chapters: AC may be used in place of AudioCodes The Analog set(s) connected to the AudioCodes gateway will be named AC set or AC set1, AC set2, or AC fax for a Fax machine. OXO Fax is a directly connected Fax to the OXO PBX.

6.1 Configurations aspects6.1.1 ObjectiveThis chapter gives principle information on configuration aspects and summaries the minimum well configurations on OXO and AC sides to be able for the AC sets to work well and easily for the EndUser. Configuration details examples are given in the Annexes. OXO Aspects: The VoIP feature is subject to Licenses. To configure analog sets to be working behind the AudioCodes gateway, a corresponding VoIP Trunk and Access have to be configured and trunk channels to be defined. The ARS (Automatic Routing Selection) mechanism is used to access to such sets. This implies the Internal Numbering Plan configuration for the AC sets Directory Numbers declared with use of ARS function. An ARS Prefix has to be defined for the Dialing numbers range, Prefix, Gateway address, Protocol and Codec configurations. Private configuration of the ARS entry is used in this topology. The Private Numbering Plan is used and has to be configured for the numbers the AC sets will have to dial. Barring and Link category have to be checked to allow the connectivity between the SIP end equipments and the trunk they use, and the other sets or trunks of the installation. The End of Numbering policy may to be adapted for trunk connectivity dialings. Transfer from External to External may be set in the System Particularities configuration.


Edition 1 Page 12

6.2 Set-up and acceptance tests6.2.1 Test objectivesCheck the installations and configuration aspects to bring the platform working. Check the acceptance through simple incoming and outgoing calls

6.2.2 Test procedureStep 1 1 Action OXO configuration checks for SIP trunk and AC gateway configuration Configuration with Option mechanism AC -> OXO, OXO -> AC, Both Simple call between OXO and AC Release before answering Calling Line Presentation to the analog AC sets in incoming ringing phase N/A ResultOK

Origin of the problem

Comment

OK

1 1 1

OK OK OK


Edition 1 Page 13

Test objectives Step 1 1 1 1 1

6.3 FAXFax transmission in T.38 mode with G3 and Super G3 fax machines Fax transmission in Transparant mode (G711) Fax In waiting situation Fax forwarding All communications mainly between 1 OXO and 1 AC, also using 1 AC and 2 OXO, also in the full config AC1 OX1 OX2 AC2 Action N/A ResultOK OK OK OK

Simple G3 fax transmission Transmission with fax super G3 Transmission of complex sheets (6)


Comment

1 1 1 1 1 1 1 1 1 1

Simple Transparant G711 Fax / both ways / between 1OXO and 1AC Faxes Simple Transparant G711 Fax / both ways / in more complex architectures: 1 or 2 OXO and/or 1 or 2 AC Faxes OXOTransparant G711 Fax receiving a T38 request Transparant Fax with AC Fallback Call a Busy Fax , both ways Waiting Fax on a current fax comm Call a Forwarded Fax Call a Fax through ISDN Break-in in T38 Call a Fax through ISDN Break-in in Transparant Call a Fax through ISDN Break-out in T38 Call a Fax through ISDN Break-out in Transparant Redundancy Check OXO and AC with values 0 to 2

OK but

NOK NOK OK NOK NOK OK OK OK OK OK

OXO OXO AC

All the systems have to be configured coherently to be working Call failure (1) Call failure (1) Call failure (1)

OXO

Call failure (1)

(1) See the Summary of Problems for details (chap 4.3)


Edition 1 Page 14

6.4 Defence and perturbation6.4.1 Test objectives Step 1 1 1 1 1 1 Check the behaviour in case of perturbation Action SIP out of order Trunk busy Trunk not available IP link failure IP link rerouting No distant resources available N/A ResultOK OK OK OK OK OK


Comment

Not tested in this campaign Not tested in this campaign


Edition 1 Page 15

6.5 Media Specification6.5.1 Test objectivesCheck the different cases of negotiation regarding the communication establishment and the impact of some configuration parameters Step 1 1 1 Codec Framing VAD Signalling TCP / UDP Action Codec Negotiation VAD Check the case of VAD negotiation Framing Use Case of different packet size for voice ( 20ms, 30ms, 40ms ) Signaling TCP-UDP SIP Signaling only transmitted in UDP mode by OXO Forced Prack ( Compliance with RFC 3262 ) Trunk authentication x N/A ResultOK OK


Comment

NOK

Crms 20876 In Trtmt

1

OK

1

OK

1

Configurable in AC gateway only: Disabled, Supported or Required


Edition 1 Page 16

6.6 Basic Calls6.6.1 Test objectivesCheck the difference cases of simple incoming and outgoing call. During the call, some points are checked : tones display before and after the conversation release the called / calling party at first type of the device : analog set, ua set ( 4035 ), IP Phone ( 4038/ 4068 ), SIP set CLIP / CLIR Call back

6.6.2 Test procedureRemark: All tests made in both ways / mainly between 1AC 1OXO / but also with 1 and 2 AC 2OXO /.

Step 1 3 4 5 Basic call

Action

N/A

ResultOK OK


Comment

Release before answer Basic call with Authentication Call an unregistered set and busy set OXO set in Do not disturb / AC set in DND PSTN break-in call PSTN incoming call to a AC set PSTN break-out call Call from a AC set to an external PSTN party Call with attendant The second party is an attendant

xOK but if queued

6 7 8 9

???? Pb si attente sur AC : pas de tona sur PS OXO

OK OK

OK

OK


Edition 1 Page 17

10 11

CLIP / CLIR Check the display with / without Identity secret Call Back on no reply Check the notification on non reply call and call back the sender Call Back on busy Check the notification on non reply call and call back the sender

OK But

Problem for break out to ISDN

X

12

X

Check the features available in local mode and during the conversation. They mainly consist Forwarding Put on hold Call parked This feature is only activated from a non SIP set ( by prefix code ) Broker call Early attended transfer and attended transfer DTMF transmission Voice Mail handling Conference Pre announcement

6.7 Telephonic services

Difference has been done between :

1) the features the AC sets can be implied in (all the telephonic features that have been activated by OXO sets) 2) and the features the AC sets can activate themselves (note that these cases are not actually supported by OXO product (R&D) . 1) Features the AC sets can be implied in (all the telephonic features that are activable by OXO sets) and AC sets situation cases (Busy, Forwarded , in DND, Out Of service, also features that AC sets can activate in OXO (be in comm with the voice mail of an OXO set, send DTMF, and so on ...). Alcatel Applications Partner Program Inter-working reportCopyright 2008 Alcatel, All rights reserved

Edition 1 Page 18

Step 1 1 1 1 1 1

Action AC set suffers a Hold AC set suffers a Retrieve AC set suffers a Hold followed by a Release AC set makes a call and suffers a Transfer while in Conversation AC set suffers a Transfer as Called set in ringing state AC set suffers a Transfer as Called set in Conversation state AC set suffers Transfers for comms routing through both OXO and/or another AC set AC set suffers a Conference on 1 OXO node AC set suffers a Conference on 2 OXO nodes OXO set calls a Busy AC set without waiting OXO set calls a Busy AC set with waiting OXO set calls an OOS AC set OXO set calls an AC set in DND state OXO set calls a Forwarded AC set - to another OXO set - to another AC set - to an ISDN destination - Forwarded Unconditional - on Busy - on No Answer ISDN DDI access to an AC set or Fax Operator calls AC sets AC set calls OXO sets on OXO1, on OXO2 through OXO1 connectivity AC set calls the operator AC set with DDI number calls an external telephonic destination through ISDN (Break out) AC set calls a Forwarded OXO set to the Voice mail

N/A

ResultOK OK OK OK OK


Comment

CLIP & CLIR OK CLIP & CLIR OK CLIP & CLIR OK

OK But

1 1

CLIP & CLIR OK Test Only OK in Heterogeneous OXO SIP mode Only OK in Heterogeneous OXO SIP mode

OK OK but

1 1 1 1 1

OK NOK OK OK

Xxxx PBPB

OK

1 1 1 1 1 1

OK OK

CLIP to the AC set OK

OK OK OK But

CLIP OK

CLIR Pb for break out

1

OK


Edition 1 Page 19

2 1 1

AC set sends DTMF to the OXO Voice Mail and navigate within AC set sends DTMF to an ISDN destination AC set calls Oos, DND, unavailable destinations

OK OK OK

CLIP OK => call back from VM possible

2) Features the AC sets can activate themselves (note that these cases are not actually supported by OXO product (R&D) : REMARK: This test Reporting is a simple copy of the preceeding Report of Document [3]. No new investigation has been done in this last campaign due to the fact that the known anomalies have not been corrected. Step 4 6 7 Action AC set puts an OXO set on Hold / Resume Broker call N/A ResultNOK NOK

Origin of the problem OXO

Comment

Attended Transfer (**)Early attended transfer (**) Conference

OK (*)

8 11

OK (*)

NOK

Only if attribute sendonly configured on MP112 Feature OK but no MOH on OXO side No compliance MP112 and OXO between both products

( * ) If parameter Hold Format = 0.0.0.0: with MP112, the transfer fails and the call is released

1st case: The transferor is the calling set Transferor MP AC Transferee UA IP Phone MP AC Transfer target UA IP Phone MP AC UA IP Phone MP AC UA Result OK OK OK OK OK OK Origin of the problem Comment

OK


Edition 1 Page 20

UA or IP Phone

UA IP Phone MP AC

IP Phone MP AC MP AC UA IP Phone MP AC

OK OK OK OK OK OK

2nd case: The transferor is the called set Transferor MP AC Transferee UA IP Phone MP AC UA or IP Phone UA IP Phone MP AC Transfer target UA IP Phone MP AC UA IP Phone MP AC UA IP Phone MP AC MP AC UA IP Phone MP AC Result OK OK OK OK OK NOK NOK OK OK OK OK OK Origin of the problem Comment

MP112 MP112

No REFER emitted


Edition 1 Page 21

7 Problem ReportsThis paragraph lists at least the main problem reports still open on the subject (severity Critical, Major) with the following fields : Identifier, severity, project, headline, state, priority and eventually system and some descriptions can be added. These anomalies may be found by other teams than Validation, but it is important to list them here to be as exhaustive as possible on anomalies information. New Anomalies :

Identifier crms00099735

Severity

Project

Headline Pb for Fax in waiting position at end of current Fax call. The waiting call fails Bad SIP field contents in case of Forwarding => Bad caller ID display and callback not possible Problem in case of Forwarding using SIP links: The caller stays "In Progress" forever ! Working in G711 Fax mode, OXO doesn' t accept any T38 Fax communication => limited working: Enhancenment Request OXO Config. with Fax in G711, rejects AudioCodes Fax codec negociation, => Fax transm fails OXO: Bad SIP Media attribute in case of Hold feature: sendreceive instead of receiveonly OXO: Forward to ISDN

State InAnalysis By AC :

System AC

4_minor

alz

crms00099749

3_major

alz

InAnalysis

OXO

crms00099786

3_major

alz

InAnalysis

OXO

crms00100280

4_minor

alz

InAnalysis

OXO

crms00100211

4_minor

alz

InAnalysis

OXO

crms00103546

4_minor

alz

InAnalysis

OXO

crms00104805

3_major

alz

InAnalysis

OXO


Edition 1 Page 22

leads to an Inaccessible call (done by an AudioCodes set in SIP trunking) crms00104816 4_minor alz OXO: An AudioCodes set New (trough SIP trunk) calls an ISDN desti with CLIR => A caller N* is generated to ISDN. OXO

Older anomalies satus:

Identifier Crms00020876

Severity

Project

Headline call released when no matching between framings from OXO and MP112 No moh when MP112 set on hold with sendonly attribut MP112-SIP-OXO : VOIP reset after second hookflash code on analog set behind MP112 Transfer failure with MP112 in SIP trunking when transferor is the called set

State In Treatment

System OXO

4

alz

Crms00021750

alz

Corrected / Closed In Treatment

OXO

Crms00001861

3

alz

OXO

Crms00002026

4

oem

In Treatment

OXO

Ignored anomalies: Identifier crms00001968Severity Project

Headline MP112-SIP-OXO : no Codec send in ACK after second hook-flash an analog set on MP112 MP112-SIP-OXO : communication is broken with set on MP112 on forward on busy/no answer

State NTIA

System AC

3_major

alz

crms00002211

4_minor

alz

NTIA

AC


Edition 1 Page 23

8 Appendix A: TestDirector test listThis appendix will give an extract of Test-director with the campaigns related to the test report, the list of the tests_name, their level and their status (Failed, Passed, NoRun, Postponed, NotCompleted). This extract must list the following Test-Director fields per Test-Director campaign in testlab : One table per Plan-subject with Plan-Test Name, Plan-Description, Plan-Level, PlanPriority,Status, FR_id_list, Feature_target, System_config, Topo_version. The listed tests can be limited to the failed one according to the information needed by the test report recipient and the visible fields must contain at least the Plan-test Name and their Status.


Edition 1 Page 24

Plan: Test Name B_08_01_ACC_0 05_sip_gen -Basic Call B_08_01_ACC_0 06_voip_gen -Release call before answer B_08_01_ACC_0 10_sip_gen -PSTN break-out call B_08_01_ACC_0 10x1_sip_gen -PSTN break-out CLIR call B_08_01_ACC_0 11_sip_gen -PSTN break-in call B_08_01_ACC_0 11x1_sip_gen -PSTN CLIR break-in call B_08_01_ACC_0 60_voip_gen -codec negotiation B_08_01_ACC_0 61_sip_gen -VAD negotiation B_08_01_PERT_ 013_sip_gen -busy Set B_08_01_ACC_0 63_voip_gen -set framing B_08_01_ACC_0 81_voip_gen -forced prack SIP set B_08_01_ACC_0 22_voip_gen -basic VoIP do not disturb B_08_01_ACC_0 50_voip_gen -Authentication B_08_01_ACC_0 12_sip_gen--Call with OP B_08_01_ACC_0 13_sip_gen --Call with OP and immediate transfer B_08_01_ACC_0 14_sip_gen --Call with OP and

Plan: Description Check the basic call from a SIP set towards a non SIP set Reverse flow is performed as well It is to check the basic call from a SIP set towards a non SIP set but the callee does not reply Reverse flow is performed as well

Plan: Level Mandat ory Mandat ory

Status Passed Passed

The aim of this set is to make calls from a SIP set to a Mandat set belonging to the PSTN network. ory The aim of this set is to make calls from a SIP set with secret identity enabled to a set belonging to the PSTN network. The aim of this set is to make calls from a set belonging to PSTN to a SIP set

Passed

Recom Failed mended Mandat ory Passed

The aim of this set is to make calls from a set belonging Recom Passed mended to PSTN to a SIP set The calling set is in secret identity mode Objective is to analyze the codec negotiation with different compression algorithms during a call with a SIP device. The VAD negotiation is analyzed independently of the codec used. The aim of this test is to see the behavior of a call when the called is busy Objective is to make calls with different framing values between the SIp set and the system Objective is to acknowledge the message 1xx for safety exchange on the SIP device Objective is to test the behavior of the system when a SIP phone has activated the do not disturb feature Objective is to test the authentification mecanism during the registration process Check SIP call with access to an attendant Recom Passed mended Recom Passed mended Recom Passed mended Mandat ory Mandat ory Failed Passed

Recom Passed mended Recom N/A mended Mandat ory Passed

Check SIP call with access to attendant followed by an Recom Postpo immediate transfer without monitoring mended ned

Check SIP call with access to an attendant. The transfer is done in supervised mode

Recom Postpo mended ned Edition 1 Page 25


Plan: Test Name supervised transfer B_08_01_PERT_ 010_sip_gen -out of order SIP set B_08_01_ACC_0 43_voip_gen -Voice -Mail B_08_01_ACC_0 20_voip_gen -internal immediate forwarding B_08_01_ACC_0 25_voip_gen-basic VoIP put on hold B_08_01_ACC_0 19x1_sip_gen -Call with progress B_08_01_ACC_0 35_voip_gen -basic VoIP SIP conference B_08_01_ACC_0 07_sip_gen -- Call back B_08_01_ACC_0 42_voip_gen -basic VoIP DTMF B_08_01_ACC_0 44_voip_gen -Message notification B_08_01_ACC_0 45_voip_gen -Voice -Mail_recall B_08_01_ACC_0 20x1_voip_gen -internal no-reply and busy forwarding B_08_01_ACC_0 21_voip_gen -external immediate forwarding B_08_01_ACC_0 25x1_voip_gen-basic VoIP called put on hold B_08_01_ACC_0

Plan: Description

Plan: Level

Status

A set makes a call with a SIP set "out of order"

Recom Passed mended Mandat ory Mandat ory Mandat ory Passed

This test is used to check access to a Voice Mail from a SIP Device with message deposit by using DTMF signaling A SIP set is forwarded to another extension on the same System. An other set calls the SIP forwarded set. Objective is to test the behavior of the system when a SIP phone is on hold state and the call is resuming

Postpo ned Postpo ned

Supple No Run The aim is to check a call toward specific equipment mentary with switching before connection (ie. speaking clock, 3010 call-card service, Voice guide when busy Mobile ) A SIP set makes a conference with 2 other parties. Recom Postpo mended ned Mandat ory No Run Passed

Check the recall feature after a non reply call

This test is used to check the right transmission of DTMF Mandat ory in the SIP signaling. One of the device is a sip set

This test is used to check the Voice mail notification on Recom N/A a SIP device mended After a Voice message deposit on a SIP set, the sender of the message is called back by the Voice mail Supple Passed mentary

A SIP set is forwarded to another extension on the same Recom Passed mended System. Forwarding mode: forwarding on no reply forwarding on busy An other set calls the SIP forwarded set. A SIP set is forwarded to another extension on an other system. An other set calls the SIP forwarded set. Objective is to test the behavior of the system when the non SIP phone is on hold state and the call is resuming Objective is to test the behavior of the system during a Recom Failed mended

Mandat ory Mandat

Inconcl usive Inconcl


Edition 1 Page 26

Plan: Test Name 26_voip_gen-basic sip VoIP broker call B_08_01_ACC_0 30x2_voip_gen -basic VoIP sip transfer

Plan: Description broker call. Both calling and called sets are sip sets

Plan: Level ory

Status usive

Objective is to test transfer between a non SIP extension Recom Inconcl mended usive in conversation mode and an other user. The type of the 1st called set may be of any type: - ua set - ip phone - sip set At least one of the called party is a SIP device Transfer is performed in both unsupervised and supervised mode Objective is to test transfer between a non SIP extension Mandat in conversation mode and an otherSIP user. The type of ory the 2nd called set may be of any type: - ua set - ip phone - sip set At least one of the called party is a SIP device Transfer is performed in both unsupervised and supervised mode Objective is to test the behavior of the system during a broker call The sip set is called but it starts the inquiry call and the broker call This test aims at checking the voice quality between 2 set and one of them is a SIP set Mandat ory Inconcl usive

B_08_01_ACC_0 30x1_voip_gen -basic VoIP non sip transfer

B_08_01_ACC_0 27_voip_gen-basic VoIP called broker call B_08_01_QOV_0 01_voip_gen -Voice quality B_08_01_QOV_0 02_voip_gen -Voice Mail quality B_08_01_ACC_0 15_sip_gen -CLIR over IP B_08_01_ACC_0 31x1_voip_gen -basic VoIP ext called transfer

Inconcl usive

Recom Passed mended

This test aims at checking the voice quality during a call Recom Passed mended with a Voice mail. One of the set is a SIP set Check the end-to-end Secret Identity feature with a SIP set Objective is to test transfer between a SIP extension in conversation mode and an other user. The transfer is initiated by the called party and performed with an external party Transfer is performed in both unsupervised and supervised mode A simple fax is sent by using the T.38 protocol A complex multi pages fax including images is sent by using the T.38 protocol Objective is to test transfer between a SIP extension in conversation mode and an other user. The transfer is initiated by the called party and performed with an external party Mandat ory Passed

Recom Postpo mended ned

C_04_01_ACC_0 01_foip_gen -single fax C_04_01_PERF_ 002_foip_gen -long and complex fax B_08_01_ACC_0 31x1_voip_gen -basic VoIP ext called transfer

Mandat ory

Passed

Recom Passed mended Recom Postpo mended ned


Edition 1 Page 27

Plan: Test Name

Plan: Description Transfer is performed in both unsupervised and supervised mode

Plan: Level

Status

B_08_01_ACC_0 55_voip_gen -Signalling TCPUDP C_09_01_ACC_0 04_foip_gen -trunk private_break-in C_09_01_ACC_0 05_foip_gen -trunk private_break-out C_09_01_ACC_0 08_foip_gen -immediate forwarding over IP_2 ways

Objective is to test the SIP signalling on UDP and TCP A fax is sending from PSTN between 2 systems connected through a Sip trunk A fax is sending on PSTN between 2 systems connected through a Sip trunk.

Recom N/A mended Mandat ory Mandat ory Passed

Passed

Mandat Objective : ory ========= A setA on System A is diverted to a systemB setB through an IP link. A setB of system B then calls the diverted set on System A over IP. Objective is to check the right functionning of diversion. Mandat Objective : ory ========= A setA on System A is diverted to a systemB setB through an IP link. A setB of system B then calls the diverted set on System A over IP. Objective is to check the right functionning of diversion. A fax is sending between 2 systems connected through a Sip trunk FAX machines are of type super G3 Some faxes are sending between 2 systems connected with a Sip trunk. Faxlab tool is used to simulate different type of faxes Check the basic call from a set towards an other set located on an other system through a SIP trunk This test is used to check the right PSTN incoming transmission of DTMF through the SIP trunk Mandat ory Mandat ory Mandat ory Mandat ory

Failed

C_09_01_ACC_0 09_foip_gen -immediate forwarding over IP

Failed

C_09_01_ACC_0 01x1_foip_gen -super G3 trunk public C_09_01_ACC_0 03_foip_gen -trunk - multi-fax B_09_01_ACC_0 05_sip_gen -trunk-Basic Call B_09_01_ACC_0 42x3_voip_gen -trunk--VoIP DTMF_Break-in from PSTN B_09_01_ACC_0 42x4_voip_gen -trunk--VoIP DTMF_Break-out on PSTN E_10_50_ACC_0 01_foip_fax call in G711Transparant FAX C_04_01_ACC_0

Passed

Passed

Passed Passed

This test is used to check the right PSTN outgoing transmission of DTMF through the SIP trunk

Mandat ory

Passed

A fax is sending through the AudioCodes box with the protocol G711. A fax on system A is forwarded to another fax

Mandat ory Recom

Passed

Inconcl


Edition 1 Page 28

Plan: Test Name 08_foip_gen -Fax local forwarding C_03_01_PERT_ 006_foip_gen -Redundancy handling

Plan: Description

A_13_01_015_SI P-Calls Authentication A_13_01_016_SI P-Calls & Reg different Authentications

machine on system A. A fax of System B sends then a fax to the forwarded fax machine on System A. We aim at checking the good reception of the fax. Goal is to see the impact of the redundancy Mandat parameter on the fax transmission and the possibility ory to receive a fax even if some packets were lost thanks to T4 redundancy Tools ==== A spy tool (e.g. RadCom) on IP network is needed to monitor the IP traffic. An other tool (e.g. Net Disturb) is also needed to steal some IP packets during fax transmission between Office and system B Mandat SIP-Calls Authentication check. ory SIP-Calls & Reg different Authentications check. Mandat ory

Plan: Status Level mended usive

Passed

N/A N/A


Edition 1 Page 29

9 Appendix B : Application descriptionThe following screen shots give information on the used AudioCodes configurations. These are examples, so the displayed information are not exhaustive or/and other manner to configure the systems may exist. Refer to chapter 6.1 where configurations principles are discussed.

General AudioCodes configurations:AudioCodes IP configuration in Quick Setup:


Edition 1 Page 30

AudioCodes Endpoints configuration in Protocol Management/Endpoint Phone Numbers :

Routing Table in Quick Setup/Tel to IP Routing Table :


Edition 1 Page 31

General configuration in Protocol Management :


Edition 1 Page 32

FAX configurations in Advanced Configuration/Media Settings :

Coders configuration in Quick Setup


Edition 1 Page 33

DTMF Configuration in Protocol Management/Protocol Definition

Services configuration in Protocol Management/Advanced Parameters :


Edition 1 Page 34

Other services configuration in Protocol Management/Advanced Parameters :


Edition 1 Page 35

Tel

IP Source Numbers in Protocol Management/Manipulation Tables :

Note : for sending NDS number when AC set call an external prefixe


Edition 1 Page 36

10 Appendix C: Audicode ConfigurationREMARK : These configurations examples are copies of the previous Report of same subject, no specifiic evolution has been added.

10.1 IP Settings

10.2 General parameters

Fax Signaling method : T38 relay

Documents

Audiocodes MP11xFXS SIP v5.2 OmniPCXOfficeR7.0 IWR Ed01