OpenScape Business V2 - Unify...Certification valid for all OpenScape Business systems X3/X5/X8/S....

Open Scape Business V2 – How To: Configure SIP Trunk for OrangeBE 1

OpenScape Business V2

How to Configure SIP Trunk for ITSP Orange in Belgium


Table of Contents Information.............................................................................................................................................. 4

Trunk Configuration Data provided by OrangeBE ............................................................................... 4

Configuration Wizard .............................................................................................................................. 5

Internet Telephony .............................................................................................................................. 5

Define bandwidth (# Trunks) ............................................................................................................... 8

DID configuration .............................................................................................................................. 10

Additional Configuration ....................................................................................................................... 11

License ............................................................................................................................................... 11

Route configuration (optional) .......................................................................................................... 11

LCR changes ( optional) ..................................................................................................................... 12

Usage of Orange CPE device .................................................................................................................. 13

Management of the emergency calls .................................................................................................... 15

Mono-site configuration.................................................................................................................... 15

Multi-site configuration ..................................................................................................................... 15

Central break-out .......................................................................................................................... 15

Nomadic numbers ......................................................................................................................... 16

Widespread use of geographic numbers ...................................................................................... 16

External use of Nomadic Numbers ................................................................................................ 17

Customer obligations for the correct handling of emergency calls .................................................. 18

Fax ......................................................................................................................................................... 18

Known restrictions and hints ................................................................................................................. 19

Maintenance & Diagnostics................................................................................................................... 20

How to check the status of SIP connection with OrangeBE .............................................................. 20

Wireshark LAN traces ........................................................................................................................ 21


Table of History

Date Version Changes

13.10.2016 0.1 First version

17.03.2017 0.2 Final review

06.04.2017 1.0 Released

02.10.2017 1.01 Adapt document for Belgian ITSP Orange (OrangeBE)

Michel Lambrecht

16/11/2017 1.02 Release of document

Michel Lambrecht – Unify Belgium (part of the ATOS group)

+3224067325

[email protected]

17/11/2017 1.03 Document reviewed and released

Michel Lambrecht

mailto:[email protected]


Information The OrangeBE provider is available and released for Belgium with OpenScape Business. Please note that Orange is active in different countries, but Orange SIP Trunks in different countries have often different equipment. The certification of the OrangeBE is thus only valid for Belgium. We also did use as name OrangeBE so that it is clear this is the SIP trunk of Orange in Belgium.

The minimal OSBiz software version is osbiz_v2_R3.1.0_031

Certification valid for all OpenScape Business systems X3/X5/X8/S.

Trunk Configuration Data provided by OrangeBE

The configuration data (IP addresses etc) needed to setup the SIP trunk can be found on the OrangeBE document you will receive by Orange.


Configuration Wizard

Internet Telephony

Go to Central Telephony – “Internet Telephony“

The overview page appears for entering the location data. The most flexible type of configuration is to enter the Country code only. When you add later on extra DID numbers which have a different local area, then you have minimal impact, since the local area code is part of the DID number of the user.

Click [OK & Next].


Provider configuration and activation for Internet Telephony -> No call via Internet -> uncheck

Use County specific view: Belgium and select “OrangeBE”.

Activate Provider and click on [Edit].

On the next page you have to enter the IP addresses in the IP Address for registration and provider proxy (they are different for each customer)

Click [OK & Next].


In the next dialog the specific customer SIP Userdata will be configured.

Click on [Add].

The data provided on this page are used to fill the following fields:

Internet telephony station: Username is inserted here (e.g: + 3289550950)

Authorization name: Username is inserted here (e.g: + 3289550950)

Password: SIP Digest Password provided by Orange

Default number: Main number of connection. The default number is used as outgoing number when no DDI number is assigned to a station. (e.g: +3289550950). Usually the Lead Number is entered here.

Enter the relevant data and click [OK & Next].

Click [OK & Next]


Click [OK & Next] (no input needed)

Click [OK & Next]

Define bandwidth (# Trunks) The amount of simultaneous Internet (Assigned Lines) calls must be aligned with the Maximum Active Calls assigned to the Trunk Group on the OrangeBE provider side.

Fill in the available bandwidth, and distribute the amount of SIP channels. The bandwidth does not need to be exact, it can also have a higher value.

Click [OK & Next]


Fill in the special numbers. The emergency number in Belgium is 112. When you still have a local ISDN also, route it via ISDN. If there is only the Orange SIP Trunk, route it to the OrangeBE.

On next page status of ITSP is displayed.

Click [Next]

„Exchange Line Seizure“:

Select which trunk will access code 0. Enter the local area code without prefix digits (needed only when local area code was not entered in first step PBX number)

Click [OK & Next]

Overview with all configured „Outside line Seizure“ are displayed.

Click [OK & Next] and on the next page [Finish]


DID configuration

In the DID Section, the full DID will need to be entered without the country code.


Additional Configuration

License

Add the “S2M/SIP Trunk” license to the SIP-Trunk

Route configuration (optional)

The route configuration will be created automatically. It should look like below.

Best praxis is to enter the default Access Code in the field “Seizure code”, enter the Country code for the PABX number-incoming and select Location number.

Make sure you select as Digit transmission the “en-bloc sending”. The SIP protocol does not support digit by digit transmission.

Note: in normal conditions the OrangeBE will be Trk Grp 12, unless as in our case there was already another ITSP configured before, then it can also be Trk Grp 13 or so. This is however automatic chosen by the OSBiz ITSP wizard.


The route parameters:

These settings are shown more as reference. Normally the OSBiz ITSP wizard will set all these parameters to the correct values. In normal conditions, no manual intervention is needed here.

LCR changes ( optional) In V2R3 (and more recent) all necessary LCR rule will be created automatically.


Usage of Orange CPE device

Customer network

LAN WAN

Router

ITSP

Internet Access: TCP/IP at LAN

DNS = Router

Default Gateway = Router

ITSP has public IP-address

Static Route to ITSP via CPE DeviceInternetprovider

CPE

Device

No used

10.10.30.1 10.10.30.75

Orange SBC’s:212.224.148.85212.224.148.856

All IP-Addresses are examples only

Orange will deliver a so called CPE device to the customer. This device will be added in the same subnet as the OSBiz subnet. The IP address of the CPE can be adapted by Orange, so that the CPE can be added in an existing voice VLAN of the OSBiz.

Inside this subnet, there is a default gateway. The SIP and RTP/T.38 traffic to the OrangeBE provider however needs to be routed via the CPE device, all other traffic from OSBiz needs to be routed to the standard default gateway inside the subnet.

To be able to route the SIP/RTP/T.38 traffic for Orange via the CPE, you do need to add a static route in the OSBiz. The static route is added for the OrangeBE target IP address, with as gateway the IP address of the CPE device.

To do so, go to the Expert Mode -> routing

Here you have the default gateway, which needs to be configured with address of the internet router.


Traffic to the Orange SBC 212.224.148.85 needs to be routed via the CPE device with IP address 10.10.30.75.

In addition to the SBC used for SIP Registration/Callsignalling an additional IP address on the Orange SBC (in the example 212.224.148.86) may be used for RTP.

To be on the safe side a route to a Class C subnet should be added -> 212.224.148.0 with mask 255.255.255.0.


Management of the emergency calls

Mono-site configuration When you make an emergency call, the Orange network routes your call to the local emergency exchange

corresponding with your geographic location of your address. This routing is based on your physical location

in the Orange network. In this way we can avoid an emergency call meant for the 02 zone, being routed to

an emergency centre of the 03 zone.

In turn the emergency exchange uses your number to find out your address via the general telephone book

(White Pages). All number series that are linked to your telephone connection have been attributed to the

same address and appear as such in the telephone book.

Multi-site configuration If the Customer uses his telephone solution in several locations, there are several situations. Depending on

the situation, the Customer can use or not Orange VoIP Trunking Service to reach the Emergency centers.

Central break-out

The Customer has different sites and each site has its own range of phone numbers.


In this case, the Customer can use Orange VoIP Trunking to reach the Emergency centers. But it requires

that the Customer provides the necessary info and implements specific configurations on his IPBX (cf. section

‘Customer obligations for the correct handling of emergency calls’).

Nomadic numbers

Some geographic numbers are always used in a specific site of another geographic area. For example, a

number from the Brussels geographic zone (02) is always used in a Customer site in Antwerp (zone 3).

In this case, the Customer can use Orange VoIP Trunking to reach the Emergency centers. But it requires

that the Customer provides the necessary info and implements specific configurations on his IPBX (cf. section

‘Customer obligations for the correct handling of emergency calls’).

Widespread use of geographic numbers

Geographic numbers are used in several Customer sites.


In this case, the Customer can absolutely not use the Orange VoIP Trunking to reach the Emergency centers

as the Emergency centers will not know the address where the call is coming from.

External use of Nomadic Numbers

Geographic numbers are used outside the Customer sites (e.g. teleworking).

In this case, the Customer can absolutely not use the Orange VoIP Trunking to reach the Emergency services

as the Emergency services will not know the address where the call is coming from.


Customer obligations for the correct handling of emergency calls The Customer will provide complete and correct information to Orange at implementation and will take care

in in-life to advise Orange if there is any change.

o Addresses of all sites where calls to emergency services can be made (not possible in case of

widespread use of geographic numbers and in case of external use of nomadic numbers)

o List of all CLI numbers and the site location where every CLI number is used

On his IPBX, the Customer will put a specific configuration to handle calls to emergency services :

Called number: <969><ZIP-code><1XX>

Whereby

<969> Prefix defined by Orange.

<ZIP-code> Postcode of the site address – 4 digits.

Only Belgian postcodes are permitted. The provided postcode must correspond to the

address of the site where the call is made to the emergency services.

<1XX> The called emergency services number – 3 digits. Only valid emergency

numbers are permitted: 100, 101, 102, 103, 105, 106, 107, 108, 110, 112, 116, 119

Call number: <CLI number >

The CLI number is allocated to the Customer and passed on to Orange with a valid site

address.

The provided CLI number must correspond to the address of the site where the call is

made to the emergency services.

Besides this, the Customer shall inform all users (personnel and others appointed by the company) on the

regulations and possible restrictions for calls to emergency services, specifically in case of nomadic use,

widespread use and external use of CLI numbers.

The Customer shall test the implemented solution according to an Orange-defined test plan and shall

inform Orange of this.

Fax OrangeBE supports both fax via G.711 (transparent) as also T.38 fax. The provider supports T.38 in case the call started with a G.729 codec. G.711 fax is only supported when the call did start with the G.711 codec.

Tests however did point out that other combinations also did work fine without any problem.


Known restrictions and hints 1. When OpenScape Business does not send out any RTP packet for 5 minutes (for whatever

reason), Orange will disconnect the call.

2. Maximum long duration call is set to 4 hours by Orange. After this, they will disconnect the call.

3. OrangeBE can show the original external number in case an external call comes in at OSBiz (A to B), and the call is again external forwarded via the ITSP to an external C party. In this case Orange can show the original A number to the C party. The default OrangeBE profile is also configurated this way. To get this feature working, the customer however needs to sign (by preference in advance) a contract that he will not misuse the “CLIP no screening”. When the “CLIP no screening” agreement is not yet active such calls will be dropped by Orange by a SIP 403 Forbidden message. To disable the original A number in case of an external to external call transfer, you can implement following workaround: go to Expert mode -> Voice gateway -> Internet Telephony Service Providers -> OrangeBE -> Edit Internet Telephony Service Provider -> Show Extended SIP Provider Data. In case the “CLIP no screening” is not (yet) active, you need to disable the parameter “Diversion: From contains original CallingPartyNumber“

4. Whenever there is a configuration issue (e.g. From header not in DID range etc), Orange will reject an outgoing call by sending SIP 403 Forbidden response on the outgoing SIP INVITE message. You need to analyze in such cases if the SIP FROM header is part of the DID range etc.

5. SIP P-Asserted-ID header will always contain the head number. OrangeBE wants it this way. The OrangeBE predefined profile is already configured this way, so no additional actions needed. Remark only added in case you would start to analyze wireshark LAN traces.


Maintenance & Diagnostics

How to check the status of SIP connection with OrangeBE

“Status” provides information about the registration status of the ITSP. The ITSP registration can also be restarted here.

Also in expert mode -> traces -> customer trace log

You can easily see if the OSBiz did register towards the ITSP.


Wireshark LAN traces

Wireshark LAN traces can be easily made at Expert Mode -> Maintenance -> Traces

Then at Traces -> TCP dump

Select here “Start TCP Dump”. Now perform your test. After this, you select “Stop TCP Dump”, and you will see the TCP dump files as links which you can easily click and download.

The “Cleanup TCP Dump” will clean the TCP dumps.

Advised is to make TCP dumps when a limited amount of calls are active.

TCP dump will have by default names as “any.cap0” “any.cap1” etc. You can simple rename them with an extension “cap”. These files can be opened with the free tool called “Wireshark” which you can download at https://www.wireshark.org/

Once you open such a cap file, you can filter e.g. on the SIP protocol by just entering the keyword “sip” in the filter

https://www.wireshark.org/

OpenScape Business V2 - Unify...Certification valid for all OpenScape Business systems X3/X5/X8/S....

Documents

Transcript of OpenScape Business V2 - Unify...Certification valid for all OpenScape Business systems X3/X5/X8/S....