sip trunk compatibility report - wiki...

20
30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC is pleased to verify that: OpenIP Has successfully met the standards for SIP Trunk compatibility With the NEC products listed below. SV9100 & SL2100 Platforms NEC Enterprise Solutions has performed Interoperability Testing with the Switch (es) and Provider/Service listed above on the date specified. Please always refer to the appropriate SIP Trunk Compatibility Report Index and the latest edition of a specific Compatibility Report on BusinessNet before considering connection. If a Provider is no longer mentioned in the Index then the Compatibility Report has been withdrawn and connection will no longer be supported by NEC Enterprise Solutions. Test Completion Date: 25 th October 2017 Test Location: Self-certification Name of Provider: Service Name OpenIP Website: https://www.openip.fr/ System Tested: SV9100 Software Version: V7.00.52 SIP Connection Mode: Test Plan Version: Registration Mode (IP Address) 5.0 Please refer to the following page(s) for further Information and Configuration Notes.

Upload: phamliem

Post on 17-Jun-2018

249 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 1 of 20

SIP Trunk Compatibility Report

NEC is pleased to verify that:

OpenIP

Has successfully met the standards for SIP Trunk compatibility

With the NEC products listed below.

SV9100 & SL2100 Platforms

NEC Enterprise Solutions has performed Interoperability Testing with the Switch (es)

and Provider/Service listed above on the date specified.

Please always refer to the appropriate SIP Trunk Compatibility Report Index and the

latest edition of a specific Compatibility Report on BusinessNet before considering

connection.

If a Provider is no longer mentioned in the Index then the Compatibility Report has

been withdrawn and connection will no longer be supported by NEC Enterprise

Solutions.

Test Completion Date:

25th October 2017

Test Location: Self-certification

Name of Provider:

Service Name

OpenIP

Website: https://www.openip.fr/

System Tested: SV9100

Software Version: V7.00.52

SIP Connection Mode:

Test Plan Version:

Registration Mode (IP Address) 5.0

Please refer to the following page(s) for further

Information and Configuration Notes.

Page 2: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 2 of 20

SIP Configuration Notes – OpenIP Use the specific configuration guide below as an example to configure an SV9100 PBX for connection

to the service described above via SIP trunks.

Recommended Software Versions

SV9100: SL2100

CCPU Version 7.00.52 / PC Pro Version 7.50.02 CCPU Version 1.04.01 / PC Pro Version 1.03.00

Initial Setup Wizard

The current PC Pro tool may have a SIP carrier quick install button for this carrier. This provides and

quick and easy method of setting up the required settings for this carrier.

If the current PC pro does not have the Quick set up button a future release will have it added.

For both the SV9100 and SL2100 platforms this can only be run for SIP Trunks when no physical Trunk

Cards are installed.

There is already an SL2100 Quick Install Guide that covers this on Businessnet, The SV9100 guide will

also be added but the steps are very similar.

To check if this SIP carrier has been added for quick install then see below if the SIP Carrier button is

not available then please follow the guide below to manually configure and for existing installations.

SV9100 SL2100

Page 3: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 3 of 20

Network Configuration

Public IP addresses can be assigned to the SV9100 and VoIP Gateways, then there should be no

network configuration required but If only one public IP address is assigned then NAT must be used

with Port Forwarding on the router and make sure that SIP ALG is disabled:

• Port 5060 should be forwarded to the IPLE IP address as per command 10-12-09. If using

multiple SIP Carriers then port 5062 should be used for the second profile in command 84-

14-06. This feature has not been tested. Not all carriers can change their signalling port so

best to check with the SIP carrier if required.

• Port 10020 to 10533 should be forwarded to the VoIP Gateway IP addresses as per command

84-26-01 for the SV9100 and ports 10020 to 10277 for the SL2100

• NAT Router should be enabled in PRG10-29-21 and the Public IP address should be entered

into PRG10-12-07.

System Programming

The following items should be changed – all other items are considered irrelevant and as such left as

default. Screenshots are for example purposes only and will have been taken from the PBX under test

but will apply to the other PBXs listed on the cover of the Compatibility Report.

Only differences in programming will be documented where necessary. For the SL2100 platform only

use 10-12-09 for both Ethernet and VOIPDB options.

Advanced Edit PRG Item Setting

Advanced

Items + VoIP +

General

Settings + IP

Addressing +

CCPU IPL IP

Network Setup

10-12-02 Default Subnet

Mask

Set according to customers network

requirements

10-12-01 IP Address Must be in a different network range to IPLE IP

Address (10-12-09) Must not be set as 0.0.0.0

10-12-03 Default

Gateway

Set according to customers network

requirements

10-29-21 NAT Router Enable if Router is configured for port forwarding

to modify the contact header from private to

public IP address

10-12-07 NAPT Router IP

Address

Enter the Public IP Address of the local SIP Trunk

network connection if NAPT is used

10-12-09 IPLE/VOIPDB IP

Address

Set according to customer’s network

requirements.

10-12-10 IPLE/VOIPDB

Subnet Mask

Set according to customers network

requirements

SV9100

Page 4: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 4 of 20

SL2100

Advanced Edit PRG Item Setting

Advanced Items + VoIP +

General Settings + IP

Addressing + IPL VoIP

Resource IP Addressing

84-26-01 VoIP

Gateway IP

Address

Set according to customers network

SV9100 & SL2100 requirements. This requires

1 x static IP address for the DSP resources

SV9100

SL2100

Page 5: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 5 of 20

Licensing

The SV9100 & SL2100 Platforms comes with 4 SIP Trunk licenses when either IPLE card is installed on

the SV9100 or the CPU-C1-A card for the SL2100 with 8 VOIP Channel licenses. Additional SIP Trunk

licenses will need to be ordered if more than 4 SIP Trunks are required. You get additional VOIP

Channels with each additional SIP Trunk license. Additional VOIP Channel licenses must be activated

in command 10-54-01 (Blade License Set Up). You can check the value in the Feature and Activation

page code 5103 and enter as below but note this value does not include the 8 that is included with

the IPLE only additional channels. You only need to manually enter the additional VOIP channels on

the SV9100 and the SL2100 automatically populates.

The SV9100 supports up to 400 SIP Trunks, 256 VOIP Channels (Single system)

The SL2100 supports up to 64 SIP Trunks, 128 VOIP Channels

Advanced Edit PRG License Code Quantity

Advanced Items + VoIP +

General Settings + VoIP

Configuration + Blade

License Setup

10-54-01 01 5103 Enter the value as per the feature

activation page code 5103.

Screen shot below is an example of a

customer having 10 VoIP Channels 8 + 2

SV9100

SL2100

Page 6: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 6 of 20

Advanced Edit PRG Item Setting

Advanced Items +

VoIP + Networking

+ SIP Trunks + SIP

Trunks Assignment

10-68-01 Trunk Type Set to SIP

10-68-02 SIP Trunk Start

Point

Enter the Trunk starting port. This may vary

depending on other Trunk cards installed and

must be from an un-allocated port.

10-68-03 Number of

ports

Enter the number of SIP Trunks required.

SV9100

Note: Netlinked system 00 should be used in a single system enviroment where Netlink is not activated. If

Netlink has been deployed then use netlinked system ID 01 to 50 depending where the SIP Trunks are

connected. This is only applicaple for the SV9100 platform as the SL2100 does not support Neltlink.

SL2100

Page 7: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 7 of 20

Advanced Edit PRG Item Setting

Advanced Items +

VoIP + Networking

+ SIP Trunks + SIP

Trunks Data Setup

14-18-01 Trunk Type Should be set to SIP

14-18-02 System ID Should match the Netlink system ID (SV9100

only) as per commands set in 10-68 above. Set

as 0 if Netlink is not configured.

14-18-05 SIP Profile Set to Profile 1 or an alternative profile if

multiple SIP Carriers are required. 6 profiles

available on both platforms. On the SV9100

when Netlink is configured, profile 1 can be

used independently on each node.

SV9100

SL2100

Page 8: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 8 of 20

Advanced Edit PRG Item Setting

Advanced Items +

VoIP + Networking

+ SIP Trunks + SIP

Trunks General

Settings + SIP

Trunks Basic

Settings

84-14-06 SIP Trunk Port Set to 5060

84-14-07 Session timer value Set to 0

84-14-08 Minimum session

timer value

Set as 1800

84-14-09 Called Party Info This setting need to be set as “Request

URI”

84-14-10 URL Type Leave set as default value “SIP-URL”

84-14-11 URL/To Header

Setting Information

Leave set as default value “proxy server

domain”

84-14-15 100rel Setting Sets whether 100rel for early media is

supported. Leave set as default “use

default setting”.

20-25-02 Progress Indication

Information

Element Detection

Set to enable for ring back tone for SIP to

SIP calls when not provided by the SIP

carrier

SV9100

SL2100

Page 9: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 9 of 20

Advanced Edit PRG Item Setting

Advanced Items + VoIP +

Networking + SIP Trunks +

SIP Trunks General

Settings + SIP Trunks

CODEC Settings

84-13-01 G.711 Maximum

Audio Frame Size

Set audio frames size as required

default value is 20ms as only option

offered by the carrier

84-13-28 Audio Capability

Priority

Set to G.711 Fixed as only codec

supported

SV9100

SL2100

Page 10: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 10 of 20

Advanced Edit PRG Item Setting

Advanced Items + VoIP +

Networking + SIP Trunks

+ SIP Trunks General

Settings + SIP Trunks

DTMF Settings

84-34-01 DTMF

Relay

Mode

Set to RFC2833

84-34-02 DTMF

Payload

Size

Set as 101 as per the 200ok SIP/SDP message

from the SIP Carrier

SV9100

SL2100

Page 11: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 11 of 20

Advanced Edit PRG Item Setting

Advanced Items + VoIP

+ Networking + SIP

Trunks + SIP Trunks

General Settings + SIP

Trunks Incoming Line

Type

14-01-01 Trunk Name Label Trunks

14-05-01 Trunk

Group/Priority

Assign to Trunk Groups and set priority. You

must remove all unused Trunks from the group

selected.

22-02 Incoming Call

Trunk Setup

Set to DID

Easy edit page the same for both platforms

Trunk to Trunk call forwarding is supported with this SIP Carrier. Please make sure that only the

required Trunks and Extensions are enabled for this service and toll restriction programming is in

place to prevent toll fraud when enabled.

Advanced Edit PRG Item Setting

Advanced Items +

VoIP + Networking +

SIP Trunks + SIP

Trunks General

Settings + SIP Trunk

Call Divert + Trunk to

Trunk Settings

14-01-13 Trunk To Trunk

Transfer

Enable for each line required

14-01-24 Trunk to Trunk

Outgoing ID

Through Mode

Enable if the CLI of the caller needs to be

sent to the divert destination. This feature

has been tested successfully.

14-01-45 Transfer CLI Set to HELD party CLI if you would like to

pass the incoming callers CLI when

transferring the call externally. The

Outgoing CLIP of the extension is replaced

by the CLIP of the caller. (default setting is

Own CLI) This feature has not been tested.

84-14-17 Call Forward

Moved Temporarily

This feature is not supported by OpenIP

Easy edit page the same for both platforms

Page 12: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 12 of 20

Advanced Edit PRG Item Setting

Advanced Items + VoIP +

Networking + SIP Trunks +

SIP Trunks General Settings

+ SIP Trunk Call Divert +

Trunk to Trunk COS

20-11-12 Call Forward Off

Premise

Enable for the required class of service.

We recommend using a new COS for the

required extensions.

20-11-29 Transfer CLI (Class

Of Service)

Enable for the required Class Of Service

if SIP carrier supports flexible CPN.

Enable if 14-01-45 is set to HELD Party

CLI

Easy edit page the same for both platforms

Advanced Edit PRG Item Setting

Advanced Items + VoIP +

Networking + SIP Trunks + SIP

Trunks General Settings + SIP

Trunk Call Divert + Trunk to

Trunk COS Assignment

21-06 Mode COS Assign the Class Of Service enabled for

call of premise to the required

extensions only.

Easy edit page the same for both platforms

Page 13: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 13 of 20

Advanced Edit PRG Item Setting

Advanced Items + VoIP +

Networking + SIP Trunks + SIP

Trunks General Settings + SIP

Trunk Call Divert + Trunk to

Trunk Outgoing Route

21-03 Trunk Group

Routing For

Trunks

Set to the required Trunk Group as the

outgoing route for Trunk to Trunk calls.

Easy edit page the same for both platforms

Page 14: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 14 of 20

SIP Trunks Message Customization options can only be set using PC Pro or Web pro not using Phone

handset programming.

Advanced Edit PRG Item Setting

Advanced Items + VoIP

+ Networking + SIP

Trunks + SIP Trunks

General Settings + SIP

Trunks Message

Customization

84-39-03 Option 3: Outgoing

INVITE Message

FROM Header User

Part

Set to Mode 1: Use Calling Party

Information

84-39-04 Option 4: Outgoing

INVITE Message

FROM Header

Display Part

Set to Mode 2: Use Calling Party

Information

84-39-05 Option 5: Outgoing

INVITE Message P-

Asserted-Identity/P-

Preferred-Identity

Usage

Set to Mode 2: Use P-Asserted-Identity

Header Using Caller Party Information

84-39-06 Option 6: Re-INVITE

without SDP

Behaviour

Set to Mode 1: Accept Re-INVITE w/out

SDP, Send 200OK Message

84-39-09 Option 9: Outgoing

Invite Message From

Header Tag

Parameter Behaviour

Set to Mode 1: Both the same.

SV9100

SL2100

Page 15: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 15 of 20

Advanced Edit PRG Item Setting

Advanced Items + VoIP +

Networking + SIP Trunks

+ SIP Trunks - Carrier

Mode (IP Address) + SIP

Carrier Mode (IP

Address) - System

Information Setup

10-28-01 Domain

Name

Enter the Domain name as requested by the

SIP Carrier for example “voip-centrex.net”

10-28-02 Host Name Enter the Host name as requested by the

SIP Carrier for example “testIP”

10-28-05 Domain

Assignment

Set to IP Address

SV9100

SL2100

Page 16: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 16 of 20

Advanced Edit PRG Item Setting

Advanced Items +

VoIP + Networking +

SIP Trunks + SIP

Trunks - Carrier

Mode (IP Address) +

SIP Carrier Mode (IP

Address) - Server

Setup

10-29-01 Outbound Proxy Enable

10-29-02 Inbound Proxy Enable

10-29-03 Default Proxy IP

Address

Enter the Sip Proxy IP as provided by

the SIP Provider

10-29-05 Register Mode Set to manual (enabled)

10-29-06 Registrar IP Address Enter the SIP Registrar IP Address as

provided by the SIP Provider

10-29-14 SIP Carrier Choice Set to 0 (Default)

10-29-15 Registration Expiry

Time

Set to 180 seconds

10-29-16 Register Sub Mode Set to disabled

10-29-19 Keep Alive by

OPTION Message

Lease set as disabled as not required

10-29-22 Default Gateway Required only if using multiple

gateways. R4 feature licence required.

Use 10-12-03 if only a single gateway is

required. (SV9100 only)

10-29-21 NAT Router Enable if Router is configured for port

forwarding to modify the contact

header from Private to Public IP

address. This should be Enabled

10-29-24 NAPT Router IP

Address

Required only if using multiple

gateways as you need to enter the

WAN IP of the network connection.

Use 10-12-07 if only a single network

connection is used. (SV9100 only)

84-14-17 Call Forward Moved

Temporarily

This feature is not supported by the

SIP provider

SV9100

Page 17: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 17 of 20

SL2100

Advanced Edit PRG Item Setting

Advanced Items + VoIP +

Networking + SIP Trunks +

SIP Trunks - Carrier Mode

(IP Address) + SIP Carrier

Mode (IP Address) -

Primary Authentication

Information

10-36-01 Registration Enable ID 00

10-36-02 User ID Enter User ID as provided by the

SIP Provider

10-36-03 Authentication

User ID

Enter Authenticated User ID as

provided by the SIP Provider

10-36-04 Authentication

Password

Enter Authenticated Password as

provided by the SIP Provider

SV9100

SL2100

Page 18: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 18 of 20

Advanced Edit PRG Item Setting

Advanced Items + VoIP

+ Networking + SIP

Trunks + SIP Trunks -

Carrier Mode (IP

Address) + SIP Carrier

Mode (IP Address) -

Multiple Authentication

Information

10-36-01 Registration Enable ID 01 to 31 if required for

additional accounts assigned to user ID

00 (primary account)

10-36-02 User ID Enter additional User ID as required

10-36-03 Authentication

User ID

Enter additional Authentication User

ID as required

10-36-04 Authentication

Password

Enter additional Authenticated

Password as required

SV9100

SL2100

Page 19: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 19 of 20

Advanced Edit PRG Item Setting

Advanced Items + VoIP +

Networking + SIP Trunks +

SIP Trunks - Carrier Mode

(IP Address) + SIP Carrier

Mode (IP Address) - Calling

Party Number for

Extensions

21-19 SIP Extension

CPN Number

Enter the full number including the

area code

If using multiple profiles you need to

enter the CPN number required for

each profile. On the SV9100 on profile

1 is displayed in easy edit so use

system data command 21-19 instead.

SL2100 shows all profiles.

SV9100

SL2100

Page 20: SIP Trunk Compatibility Report - Wiki OpenIPwiki.openip.fr/sites/default/files/20171109_certification_sv9100... · 30th October 2017 Page 1 of 20 SIP Trunk Compatibility Report NEC

30th October 2017

Page 20 of 20

Comments / Known Limitations

• DDIs can be configured if required, using the same procedure as for ISDN trunks

• SIP calls are sent “en bloc”. This means that the External Call Interdigit timer (PRG21-01-03)

must expire before the call is set up. This can be reduced, but will have an impact on ISDN

trunks also. The user can dial # to indicate “end of dialling” instead if required.

• Trunk to Trunk diverting has been tested with the feature CPN (calling party number) Pass-

through (14-01-24) and is supported. Calling Party CLIP will be sent in the P=Asserted Identity

Header in the Invite of the outbound call to the forwarding destination.

• Registration expiry timer must be set to 180 in 10-29-15. Registration should refresh every 90

seconds.

• Open IP support G.711 & G.729 Voice codecs.

• T.38 Fax is not supported. Fax over G.711 has not been tested so we are unable to confirm if

Fax over IP is supported.

• DTMF over SIP Trunks has been fully tested with an Auto Attendant that the digits are sent as

an RTPEVENT only.

• This report is based on the SV9100 and is also compatible for the SL2100. Some screen shots

maybe slightly different depending on feature support.

NEC Enterprise Solutions cannot be held responsible for any regulatory non-compliance resulting from

the use of this service.

Document History

Version Date Description

5.0

15/09/17

SIP Compatibility Report released based on the test results

provided with tests at OpenIP

TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT SHALL NEC ENTERPRISE SOLUTIONS BE LIABLE FOR PERSONAL INJURY

OR ANY INCIDENTAL, SPECIAL, DIRECT, INDIRECT OR CONSEQUENTIAL DAMAGES WHATSOEVER, INCLUDING WITHOUT

LIMITATION, DAMAGES FOR LOSS OF PROFITS, LOSS OF DATA, BUSINESS INTERRUPTION OR ANY OTHER COMMERCIAL

DAMAGES OR LOSSES ARISING OUT OF OR RELATED TO YOUR USE OF THIS REPORT, HOWEVER CAUSED REGARDLESS OF THE

THEORY OF LIABILITY (CONTRACT, TORT OR OTHERWISE) AND EVEN IF NEC ENTERPRISE SOLUTIONS HAS BEEN ADVISED OF THE

POSSIBILITY OF SUCH DAMAGES, DUE TO THE POSSIBILTY OF PROVIDERS MAKING SYSTEM CHANGES WHICH PROCEED THE

COMPATIBILITY TESTING DETAILED IN THIS REPORT.

IN NO EVENT SHALL NEC ENTERPRISE SOLUTIONS TOTAL LIABILITY TO YOU FOR ALL DAMAGES (OTHER THAN AS MAY BE

REQUIRED BY APPLICABLE LAW IN CASES INVOLVING PERSONAL INJURY) EXCEED THE AMOUNT OF SEVENTY FIVE POUNDS

(£75).

THE FOREGOING LIMITATIONS WILL APPLY EVEN IF THE ABOVE STATED REMEDY FAILS OF ITS ESSENTIAL PURPOSE.