TG0069 Sip PDF

TROUBLESHOOTING GUIDE TG0069 Ed.
12
OmniPCX Enterprise Nb of pages :152 Date : 23rd April 2014
SUBJECT : Session Initiation Protocol (SIP)
CONTENTS
1. INTRODUCTION .......................................................................... 7
2. DOCUMENT HISTORY ................................................................. 7
3. REFERENCES ............................................................................ 7
4. ABBREVIATIONS AND NOTATIONS............................................. 7

4.1 Abbrevations .......................................................................................... 7
4.2 Notations ............................................................................................... 7
5. PROTOCOL ................................................................................ 8
5.1 SIP Overview .......................................................................................... 8
5.2 SIP Terminology ...................................................................................... 8
5.3 SIP structure ........................................................................................... 9
5.4 SIP Messages .......................................................................................... 9
5.5 SIP Transaction, Dialog & Session .......................................................... 10
5.5.1 Transaction ..................................................................................................... 10
5.5.2 Dialog ............................................................................................................. 11
5.5.3 Session ........................................................................................................... 11
5.6 SIP Addressing ...................................................................................... 11
6. SIP LICENSING ......................................................................... 12
7. INTERWORKING WITH OXE ...................................................... 13
8. SIP OXE IMPLEMENTATION ...................................................... 13

8.1 RFCs implemented on OXE .................................................................... 13
1
8.1.1 SIP .................................................................................................................. 13
8.1.2 RTP, T38 & DTMF (used for SIP) ....................................................................... 14
8.2 SIPMOTOR processes ............................................................................ 14
8.3 OXE duplication .................................................................................... 15
8.4 The OXE contains the following compoments: ........................................ 15
8.4.1 Registrar......................................................................................................... 15
8.4.2 Proxy .............................................................................................................. 15
8.4.3 Gateway.......................................................................................................... 17
8.4.4 Dictionnary ..................................................................................................... 17
8.4.5 SIP users ........................................................................................................ 17
8.4.6 SIP External Voice Mail ................................................................................... 18
8.5 Overview of Interaction between Components ....................................... 19
8.6 Network number rules .......................................................................... 19
8.7 Overview of Remote Extension feature ............................................... 19
8.8 Overview of G711 Transparent Fax and T38 fallback G711 feature ..... 20
8.8.1 The T38 only procedure .................................................................................. 20
8.8.2 The G711 only procedure ................................................................................ 20
8.8.3 The T38 to G711 Fallback procedure ............................................................... 21
8.9 Overview of Private SIP Transit mode feature ...................................... 22
8.10 SIP parameters explanation / under the object SIP: ................................ 25
8.10.1 SIP Trunk Group ............................................................................................. 25
8.10.2 The local SIP gateway ..................................................................................... 26
8.10.3 The external SIP gateways .............................................................................. 27
8.10.4 Timer usage for SIP Trunking (Trunk Categoy, by default 31).......................... 30
8.10.5 The SIP proxy ................................................................................................. 30
8.10.6 SIP Registrar ................................................................................................... 31
8.10.7 SIP Dictionnary ............................................................................................... 32
8.10.8 SIP Authentication........................................................................................... 32
8.10.9 Quarantined IP Addresses .............................................................................. 32
8.10.10 Trusted IP Addresses ................................................................................... 32
8.10.11 SIP To CH Error Mapping............................................................................. 33
8.10.12 CH To SIP Error Mapping............................................................................. 33
8.11 SIP parameters explanation / under the object USERS: ........................... 33
8.11.1 SIP Device ...................................................................................................... 33
8.11.2 SIP Extension (or SEPLOS) ............................................................................. 34
8.12 SIP parameters explanation / under the object SIP Extension: ................. 35
8.13 SIP parameter explanation / under the object External Voice Mail: .......... 35
2
8.14 SIP parameters explanation / under the object System:........................... 36
9. IP DOMAINS, CODECS AND PCS ............................................... 37

9.1 IP domains rules ................................................................................... 37
9.2 System law for PCM codec ..................................................................... 37
9.3 Codecs on SDP (before OXE R11) ........................................................... 37
9.3.1 Initial offer : the offer sent in an initial INVITE................................................ 37
9.3.1 Initial answer : the answer to an initial offer on incoming call ....................... 38
9.4 Codecs on SDP (from OXE R11) ............................................................. 38
9.4.1 Initial offer : the offer sent in an initial INVITE................................................ 38
9.4.2 Initial answer : the answer to an initial offer on incoming call ....................... 39
9.5 How to manage the type of codec negotiation from OXE R11? ................ 40
9.6 How to manage the SDP transparency override from OXE R10.1? ........... 40
9.7 PCS ...................................................................................................... 40
10. CONTENTS OF A SIP MESSAGES (GENERAL VIEW) .................. 41

10.1 The HEADER ......................................................................................... 41
10.2 The BODY ............................................................................................. 43
11. EXAMPLES OF COMMON SIP FLOWS ....................................... 44

11.1 Registration .......................................................................................... 44
11.2 De-registration ..................................................................................... 47
11.3 Simple call establishement .................................................................... 48
12. TROUBLESHOOTING ................................................................ 51

12.1 SIPMOTOR processes ............................................................................ 51
12.2 SIPMOTOR memory used ...................................................................... 52
12.3 Check the SYSTEM and SIPMOTOR backtraces/alarms ............................ 52
12.3.1 Backtraces ................................................................................................... 52
12.3.2 Alarms ......................................................................................................... 53
12.4 SIP traces.............................................................................................. 55
12.4.1 SIPMOTOR traces ........................................................................................... 55
12.4.2 Call Handling traces........................................................................................ 57
12.4.3 Tcpdump / Network traces .............................................................................. 58
12.5 Maintenance commands ....................................................................... 59
12.5.1 sip ............................................................................................................... 59
12.5.2 trkstat .......................................................................................................... 59
12.5.3 trkvisu ......................................................................................................... 60
3
12.5.4 sipaccess ..................................................................................................... 61
12.5.5 sipgateway .................................................................................................. 61
12.5.6 Sipdump ...................................................................................................... 62
12.5.7 sipextgw ...................................................................................................... 70
12.5.8 sippool ........................................................................................................ 71
12.5.9 sipdict .......................................................................................................... 72
12.5.10 sipauth ........................................................................................................ 73
12.5.11 sipregister ................................................................................................... 73
12.5.12 csipsets ........................................................................................................ 75
12.5.13 csipview com ............................................................................................... 76
12.5.14 csiprestart .................................................................................................... 76
12.5.15 sipextusers................................................................................................... 77
12.6 Link between SIPMOTOR traces and Call Handling traces ....................... 77
12.6.1 Call Handling / SIPMOTOR links implementation ........................................ 77
12.6.2 General view ............................................................................................... 78
12.6.3 neqt link between SIPMOTOR and Call Handling traces .......................... 78
12.7 Information in the SIPMOTOR traces ...................................................... 79
12.8 Follow a call on the SIPMOTOR trace ..................................................... 80
12.9 Traces analyses .................................................................................... 82
12.9.1 Incoming SIP call using a SIP Trunk Group: SIPMOTOR point of view ............ 82
12.9.2 Incoming SIP call using a SIP Trunk Group: Call Handling point of view ......... 91
12.9.3 Incoming SIP call in case of SIP extension: SIPMOTOR point of view ............. 96
12.9.4 Incoming SIP call in case of SIP extension: Call Handling point of view ........ 106
12.10 Main call flows explanation ................................................................. 112
12.10.1 Forwards ................................................................................................... 112
12.10.2 Transfer ..................................................................................................... 114
12.10.3 UPDATE on Early Media ............................................................................ 117
12.11 Configuration issues ........................................................................... 119
12.11.1 SIP configuration rule ................................................................................ 119
12.11.2 SIP alarms generated on OXE.................................................................... 120
12.11.3 Common SIP issues ................................................................................... 122
12.11.4 SIP Device issues ....................................................................................... 126
12.11.5 SIP extension issues ................................................................................... 127
12.11.6 SIP External Gateway Issue........................................................................ 127
11.13 Summary for SIP issue analyse ............................................................ 128
13. SYMPTOMS, DIAGNOSIS AND SOLUTIONS ............................. 129

13.1.1 Outgoing Call Cancel sent by OXE after 180 w SDP ............................... 129
4
13.1.2 Telephone-event are not provided on SDP offer ........................................ 129
13.1.3 Loss of communication with SIP External Voicemail ................................... 129
13.1.4 Impossible to let a message when routing via SIP Automated Attendant... 129
13.1.5 When call is transfer from a Third Party Server, after few seconds, a Re-Invite
is sent by OXE to reroute RTP to a GD card ................................................................ 129
13.1.6 Incoming call from a SIP Third Party Server is rejected by OXE with a SIP Error
488 Not Acceptable Here ........................................................................................... 129
13.1.7 Incoming call is not recognized as INTERNATIONAL ................................. 130
13.1.8 When we attempt to register on SIP External Gateway, OXE answers by a SIP
error 482 Loop Detected ........................................................................................ 130
13.1.9 When we attempt to register our SIP External Gateway with an external SIP
Proxy, SIP Proxy answers by a SIP error 416 Unsupported URI Scheme .................. 131
13.1.10 Incoming call doesnt transit via Trunk Group configured on SIP Ext Gw ... 132
13.1.11 Wrong caller number sent in case of forward ........................................... 132
13.1.12 Diversion/History-Info header is not present ............................................. 132
13.1.13 SIP-Trunking Name is displayed on calling phone set when call is established
133
13.1.14 From header doesnt have the national format ......................................... 133
13.1.15 Incoming and outgoing fax communications impossible through SIP Gw .. 133
13.1.16 No Re-Invite with T38 offer sent by OXE .................................................... 133
13.1.17 External call with secret identity over SIP Provider fails ............................. 134
13.1.18 On SIP outgoing call, dynamic ports are used instead of port 5060 .......... 134
13.1.19 A "+" character is added on calling number when ISDN call is routed to SIP134
13.1.20 Diversion Field doesnt have the canonical form ....................................... 134
13.1.21 Leg1 and leg2 are external set, when OXE user performs a blind transfer, it
doesnt work .............................................................................................................. 135
13.1.22 SingleStep Transfer with REFER, no referred-by in the following INVITE ... 135
13.1.23 Major alarm szSdpMessage > 1000 is present on sipalarm.log ................ 136
13.1.24 SIP-Trunking Bad routing and bad display from time to time trough SIP trunk
136
13.1.25 SIPMOTOR goes to "Degraded mode enabled" state.................................. 136
13.1.26 A Diversion header is added in case of single step transfer after a consultation
call 137
13.1.27 Incoming calls from SIP Provider are rejected by SIPMOTOR after upgrade
from R9.0 to R10.1 ..................................................................................................... 138
13.1.28 Remote extension issue in ringing phase................................................... 139
13.1.29 Overflow on Remote Extension impossible when SIP Extension seen Out of
Service 139
13.1.30 Country Code is not added on Calling Number when call is performed since a
GSM 139
13.1.31 Call Back issue on Open Touch ................................................................. 140
13.1.32 only 62 simultaneous calls are sent out of the OXE, all other calls are released
5
141
BEFORE CALLING ALCATEL-LUCENTS SUPPORT CENTER ............... 142
NOTE ........................................................................................... 142
14. ANNEXE: REGISTER / INVITE WITH OR WITHOUT

AUTHENTICATION .................................................................. 143
14.1 Register of set ..................................................................................... 143
14.1.1 Classical management of SIP on the OXE .................................................. 143
14.1.2 Register of set without authentication ........................................................ 144
14.1.3 Register of set with authentication ............................................................. 144
14.2 INVITE of set....................................................................................... 145
14.2.1 INVITE of set without authentication.......................................................... 145
14.2.2 INVITE of set with authentication............................................................... 145
14.3 Register of an external gateway .......................................................... 146
14.3.1 Register of an external gateway without authentication ............................ 146
14.3.2 Register of an external gateway with authentication ................................. 149
14.4 INVITE of an external gateway with authentication ............................... 152
6
OmniPCX Enterprise
TROUBLESHOOTING GUIDE No. 0069 Session Iniation Protocol (SIP)
1. INTRODUCTION
This Troubleshooting Guide deals with SIP (Session Initiation Protocol) and its implementation in OmniPCX
Enterprise (OXE), which allows the OXE to connect to SIP phones, SIP trunks and SIP
applications like external Voicemail.
The goal is of this document is to explain the functioning of the SIP, to facilitate the troubleshooting
and resolution of issues related to SIP
2. DOCUMENT HISTORY
Ed01: first edition
Ed02: add Traces analyses chapter
Ed03: add chapter 12 and update 7.11 section
Ed04: update SIP Device issues chapter
Ed05: update chapter 12
Ed06: update 7.7.3 chapter, add new chaper Timer Usage for SIP Trunking
Ed07: add Restriction on Support of Re-Invite wo SDP, see 7.7.3 chapter
Ed08: add new section ANNEXE: Register / INVITE with or without authentication
Ed11: R9.1 obsolete, update of the document for R11 (new SIP parameters, RFCs, licences)
Ed12: R10.x obsolete, update of the document for R11.0.1 (new SIP parameters)
3. REFERENCES
OmniPCX Enterprise Technical Documentation
4. ABBREVIATIONS AND NOTATIONS
4.1 Abbrevations
OXE : OmniPCX Enterprise
SIP : Session Initiation Protocol
URI : Uniform Resource Identifier
4.2 Notations
We suggest to pay attention to this symbol, which indicates some possible risks or gives important
information.
Ed. 12 7 TG0069
OmniPCX Enterprise
5. PROTOCOL
5.1 SIP Overview

The SIP protocol is designed to establish, to maintain and to end multimedia sessions between different
parties. This protocol is based on the HTTP 1.1
SIP does not provide an integrated communication system. SIP is only in charge of initiating a dialog
between interlocutors and of negotiating communication parameters, in particular those concerning the
media involved (audio, video). Media characteristics are described by the Session Description Protocol
(SDP). SIP uses the other standard communication protocols on IP: for example, for voice channels on IP,
Real-time Transport Protocol (RTP) and Real-time Transport Control Protocol (RTCP). In turn, RTP uses
G7xx audio codecs for voice coding and compression.
SDP MEDIA
Application CODING
Layer SIP RTP/RTCP
Transport Layer TCP UDP
Network Layer IP
5.2 SIP Terminology
User Agent (UA)
o User Agent Client (UAC): Initiator of the SIP requests

o User Agent Server (UAS): Receiver of the SIP requests (end point)
A SIP equipment can be UAC or UAS according to the direction of the call
Call Direction
Alice Bob
UAC UAS
Call Direction
Alice Bob
UAS UAC
Registrar: A registrar is a server that accepts REGISTER requests and places the information it
receives in those requests into the location service for the domain it handles.
The OmniPCX Enterprise incorporates the function of registrar.
Location Service: A location service is used by a SIP redirect or proxy server to obtain information
about a callee's possible location(s). It contains a list of bindings of address-of-record keys to zero
or more contact addresses.
The OmniPCX Enterprise incorporates the function of location service.
Proxy, Proxy Server: An intermediary entity that acts as both a server and a client for the purpose of
making requests on behalf of other clients. A proxy server primarily plays the role of routing, which
Ed. 12 8 TG0069
OmniPCX Enterprise
means its job is to ensure that a request is sent to another entity "closer" to the targeted user.
Proxies are also useful for enforcing policy (for example, making sure a user is allowed to make a
call). A proxy interprets, and, if necessary, rewrites specific parts of a request message before
forwarding it. The SIP proxy is the central actor and first contact for any SIP end user device that
wants to initiate a request.
Note: In the OmniPCX Enterprise, the logical functions of registrar, location service and proxy server
are co-located and running on the OmniPCX Enterprise call server (CPU/CS/AS) board. The
OmniPCX Enterprise proxy server is stateful (it remembers transaction state), call-stateful (stays in
the signaling path) and forking (it can redirect requests to multiple destinations).
The name of the SIP domain handled by an OXE node is its node name concatenated with the DNS
local domain name defined in SIP/SIP gateway. The main IP address can be substituted wherever
appropriate.
Redirect Server: Provides the client with information about the next hop or hops that a message
should take and then the client contacts the next hop server or UAS directly. OmniPCX Enterprise
does NOT provide a redirect server.
Gateway: A gateway is a SIP user agent that provides a bridging function between the SIP world and
other signaling and telephony systems.
5.3 SIP structure
The SIP is based on the RFC 3261 (previous RFC 2543). Its implementation is the following:
Application Session, dialog

Traitement of the services
Transaction user
Transaction Treatment, retransmission of messages
Transport Emission, reception of the messages
Syntax/Encoding Analyse of the messages (Parsing)
UDP TCP Transport protocol
5.4 SIP Messages

The main types of requests are:
REGISTER: message sent by an agent to indicate his current address. This information can be
stored in the location server and is used for call routing.
INVITE: message sent systematically by the client for any connection request.
ACK: message sent by the client to confirm (acknowledge) the connection request.
BYE: terminates a call, RTP packet exchange is stopped.
CANCEL: terminates a call currently being set up.
Ed. 12 9 TG0069
OmniPCX Enterprise
SUBSCRIBE - NOTIFY: message used to subscribe to/notify an event (for example: new voicemail
message).
REFER: message requesting an agent to call an address (used for transfers).
UPDATE: message sent to change the SDP information in early dialog or confirmed dialog.
MESSAGE: message used to send a message.
OPTIONS: Requests information about the capabilities of a caller, without setting up a call. Also
used for supervision purpose between two UAs.
PRACK: (Provisional Response Acknowledgement): PRACK improves network reliability by adding
an acknowledgement system to the provisional Responses (1xx). PRACK is sent in response to
provisional response (1xx).
The remote endpoint answers with a response of one of the following types (main messages answered by
OXE):
1xx: informational (transaction in progress).

o The 100 Tyring is particular regarding the other informational answers, used to avoid
retransmission of INVITE.
o The 180 Ringing is used for ring back tone (RBT).
o The 183 Progress is used to broadcast voice guides.
2xx: success (transaction completed successfully).
o 200 OK indicates the request was successfull
o 202 Accepted indicates that the request has been accepted for processing, but the
processing has not been completed
3xx: forward (the transaction is terminated and prompts the user to try again in other conditions).
o 301 Moved Permanently
o 302 Moved Temporarily
4xx: The request contains bad syntax or cannot be fulfilled at the server.
5xx: The server failed to fulfill an apparently valid request
6xx: The request cannot be fulfilled at any server
Regarding the unsuccessfull answers, for their meaning, use the RFC 3261.
5.5 SIP Transaction, Dialog & Session
5.5.1 Transaction
The transactions have to separated:

The INVITE transaction
The INVITE transaction is composed of three ways
INVITE sends from the client to the server
Answers send from the server to the client
Client must send an ACK
If these three steps are respected, a INVITE transaction is done
Ed. 12 10 TG0069
OmniPCX Enterprise
Example
UAC UAS
| INVITE |
|--------------->|
| 100 Trying |
|<---------------|
| 180 Ringing |
|<---------------|
| 200 OK |
|<---------------|
| ACK |
|--------------->|
An INVITE transaction (with all the information from this INVITE) can be called a leg.
The Non-INVITE transaction

The Non-INVITE transaction is composed of two ways
Request sends from the client to the server
Answers send from the server to the client
No ACK
If these three steps are respected, a Non-INVITE transaction is done
Example
UAC UAS
| Option |
|--------------->|
| 200 OK |
|<---------------|
5.5.2 Dialog
Dialogs are created through the generation of non-failure responses. When an INVITE is answered with a
200 Ok, the dialog is opened.
A dialog is identified by :
o a call identifier
o a local tag
o a remote tag
5.5.3 Session
A session is open for audio or video exchanges. The UAC and UAS receives the information to open a RTP
flow, in that case, the session is opened.
5.6 SIP Addressing

SIP entities are identified using SIP URIs (Uniform Resource Identifier). A SIP URI is of the form of
sip:username@host, similar to an email address, typically containing a username and a host name delimited
by @ (at) character. The host part can be an IP address, the name of a machine, or a Fully Qualified Domain
Name (FQDN), i.e. the name of a domain. The username part can be a telephone number.
Ed. 12 11 TG0069
OmniPCX Enterprise
Examples for SIP URIs:
sip:[email protected]
In OmniPCX Enterprise, the more specific term URL (Uniform Resource Locator) is generally used instead of
URI, since OXE is more concerned about location aspects rather than identification aspects.
For OXE uses on the username part numbers and no names.
6. SIP LICENSING
Here the next licenses for SIP (under spadmin):
177 M SIP users = 13/ 25

...
185 SIP Gateway = 1
...
188 SIP network links = 45
...
345 M SIP extension users = 8/ 25
...
386 UC as a Service = 0 From R11
The license 177 corresponds to the maximum number of SIP users (SIP Extension & SIP Device).
The license 185 corresponds to the use of the SIP on the OXE (activation).
The license 188 corresponds to the maximum number of SIP Calls available all the SIP elements
(SIP calls thru Trunk group and SIP extension).
The license 345 corresponds to the maximum number of SIP Extension users.
The license 386 corresponds to the activation of the UCaaService.
o When UCaaS lock is 0: control of SIP Trunking call establishment is not modified and uses
existing SIP Network Links lock; new system option is not considered, whatever its value
(current OXE behavior)
o When UCaaS lock is not 0, SIP Network Links is no more considered but is replaced with
a new system option Number of SIP Trunks (UCAAS)
A new system option Number of SIP Trunks (UCAAS) is added from R11 under System / Other
System Params / SIP Parameters and replaces the lock 188 when lock 386 is activated. Customers
or Carriers can allocate a number of SIP Trunks Channels for all SIP External Gateways configured
on the system. Voicemail and OpenTouch calls are not considered.
In case of SIP Registered (aka SIP Device), license are taken at proxy level (for some use cases like a
SIP Device calls SIP Voicemail) and counted against license #188 ; so that for UCaaS systems it is
better to have license #188 greater than 0
Another information link to SIP is important, the PARAMAO 3 used for the creation of the SIP Trunk Group
(under cfgUpdate):
5 Trunks : 5000
This value is calculated according to the number of Trunk Groups managed via ACTIS (including SIP).
Ed. 12 12 TG0069
OmniPCX Enterprise
7. INTERWORKING WITH OXE

Alcatel-Lucent Enterprise provides support:
- for non AAPP/ALU applications, a SIP ISDN or SIP ABC trunk group can be used only under control
of TC1820 : Alcatel-Lucent OmniPCX Enterprise SIP Trunking with 3rd Party ( IVR & Contact
Center ) guideline. This guideline provides configuration and topologies supported by ALE.
- for SIP Carrier, interworking with OXE must be validated by Christophe Haettinger and ALE
Technical Support team. A survey must be filled by the carrier and according to the answers, an
interworking test campaign will be proposed
8. SIP OXE IMPLEMENTATION
8.1 RFCs implemented on OXE
8.1.1 SIP
RFC 2543 (obsolete by RFC 3261,3262, 3263,3264, 3265): SIP: Session Initiation Protocol
RFC 2782: A DNS RR for specifying the location of services (DNS SRV)
RFC 2822: Internet Message Format
RFC 3261: SIP: Session Initiation Protocol
RFC 3262: Reliability of Provisional Responses in SIP (PRACK)
RFC 3263: SIP: Locating SIP Servers
RFC 3264: An Offer / Answer model with SDP
RFC 3265: SIP-Specific Event Notification
RFC 3311: The SIP UPDATE Method (session timer only)
RFC 3323: Privacy Mechanism for the Session Initiation Protocol (SIP)
RFC 3324: Short term requirements for network asserted identity
RFC 3325:Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within
Trusted Networks
RFC 3265: SIP-specific Event Notification
RFC 3515: The Session Initiation Protocol (SIP) Refer method
RFC 3891/3892: The Session Initiation Protocol (SIP) 'Replaces' Header/ Referred-By Mechanism
RFC 3398: Integrated Services Digital Network (ISDN) User Part (ISUP) to SIP Mapping
RFC 3966: The telephone URI for telephone numbers : since R11 only TEL URI is supported
RFC 4497: Inter-working between SIP and QSIG
RFC 5373: Requesting Answering Modes for the Session Initiation Protocol
RFC 4244: An Extension to the Session Initiation Protocol (SIP)for Request History Information
RFC 3326: The Reason Header Field for the Session Initiation Protocol (SIP)
RFC 3428: Session Initiation Protocol (SIP) Extension for Instant Messaging (partial)
RFC 3608: Service Route header
RFC 3327: Path Header
RFC 1321: Authentication for Outgoing calls
RFC 2246: The TLS Protocol Version 1.0
RFC 3268: Advanced Encryption Standard (AES) Cipher suites for Transport Layer Security (TLS)
Ed. 12 13 TG0069
OmniPCX Enterprise
RFC 3280/5280: Internet X.509 Public Key Infrastructure Certificate and Certificate
Revocation List (CRL) Profile
RFC 3842: A message Summary and Message Waiting Indication Event Package
RFC 4028: The session timers in the Session Initiation Protocol
RFC 3960: Early Media (partial): Gateway model not supported
RFC 4568: Session Description Protocol (SDP) Security Descriptions for Media Streams
RFC 5806: Diversion Indication in SIP
RFC 3725 : Invite without SDP (3pcc in SIP)
RFC 3966 : The tel URI from R11
RFC 5009 : The P-Early-Media header from R11
8.1.2 RTP, T38 & DTMF (used for SIP)
RFC 2617: HTTP Authentication : Basic and Digest Access Authentication

RFC 2833/4733: DTMF Transparency. RFC 2833 replaced by RFC 4733
RFC 1889/1890: RTP : A transport protocol for Real-Time applications
RFC 2198: RTP Payload for Redundant Audio data
RFC 3550: RTP: A Transport Protocol for Real-Time application (audio only)
RFC 3551: RTP Profile for Audio and Video Conferences with Minimal Control (audio only)
RFC 3711: The Secure Real Time. Supported on A-LU IP Phone and Softphone
RFC 3362: T38 ITU-T Procedures for real time Group3 Fax Relay / communications over IP
RFC 3711: The Secure Real-time Transport Protocol (SRTP) (media integrity)
8.2 SIPMOTOR processes

In the OmniPCX Enterprise, the logical functions of registrar, location service, proxy server and gateway are
co-located in the process called sipmotor, running on the CPU7/CS2/AS board.
You may use the linux ps command to verify that the SIP processes are running :
Example:
(1)OXE> ps -edf | grep sip
root 2202 801 0 2011 ? 00:00:00 [#sipmotor]
root 2203 2202 0 2011 ? 00:00:00 [sipmotor_tcl]
root 2204 2202 0 2011 ? 00:00:00 [sipmotor]
root 2205 2202 0 2011 ? 00:00:00 [sipmotor_dump]
root 2206 2202 0 2011 ? 00:00:00 [sipmotor_presen]
All processes can be forced to reset with the command:

dhs3_init -R SIPMOTOR, this command stops properly the SIPMOTOR processes and restarts
them.
(1)OXE> dhs3_init R SIPMOTOR
They will be automatically relaunched after a few seconds.
The following commands can be used as well:

killall sipmotor, this command kills the SIPMOTOR processes and restarts them.
kill -9 father pid, this command kills the SIPMOTOR processes and restarts them.
Ed. 12 14 TG0069
OmniPCX Enterprise
Remarks:
If no licenses about SIP are present, the SIPMOTOR processes are not running.
If Lock 386 different than 0 and System parameter Number of SIP trunks (UCaaS) is equal to 0, the
SIPMOTOR processes are not running
8.3 OXE duplication

In case of OXE duplication, the SIPMOTOR is completely started on the Stand-By CPU, but acting as Stand-
By (cannot handle the SIP requests). The Main CPU puts the Stand-By CPU up to date about the SIP
contexts (Calls, registrations, subscriptions, etc...). In case of CPU switchover, the SIP calls are maintained
and the registration and subscriptions are kept.
In Case of spatial redundancy with dual subnetworks (2 main IP addresses), the SIP uses the FQDN of the
OXE (nodename + DNS local domain name) for the SIP messages and also for the responses of the SIP
messages. In that case, the remote SIP equipment must use it. The use of external DNS server is
recommended to resolve this FQDN.
8.4 The OXE contains the following compoments:
8.4.1 Registrar
Registers the SIP terminals addresses (Location Service)
The REGISTRAR is contained in the localize.sip file under /tmpd. If for any reasons you need to
clear all entries in the registrar database, remove this file and then restart the SIPMOTOR:
(1)OXE> rm /tmpd/localize.sip
(1)OXE> dhs3_init -R SIPMOTOR
8.4.2 Proxy
Entity between the Client and the Server, the proxy is used to route the SIP requests.
The call can be routed between 2 SIP terminals. For instance, if Alice calls Bob (both are SIP), Alice
sends a SIP request to the proxy, and the proxy sends this request to Bob.
The proxy can be used only for the authentication of the SIP equipment for Registration or SIP
request.
o The proxy can modify the request by adding information like a Via, Record-route, etc...
INIVTE with leg1 INVITE with leg1

Alice Proxy Bob
UAC UAS
The INVITE is the same on each proxy sides, to get this behavior, and the UAC manages the IP address of
the OXE SIP proxy as the Outbound proxy
Here is an example:
UAC IP address: 172.27.143.184
proxy IP address: 172.27.143.186
UAS FQDN: oxe-ov.alcatel.fr (IP address: 172.27.141.151)
Ed. 12 15 TG0069
OmniPCX Enterprise
Fri Jun 29 14:08:10 2012 RECEIVE MESSAGE FROM NETWORK (172.27.143.184:5060 [UDP])
----------------------utf8-----------------------
INVITE sip:172.27.143.186 SIP/2.0
Via: SIP/2.0/UDP 172.27.143.184:5060;rport;branch=z9hG4bKPjX7-GJh79mg04nEbZ0yxYsWP3MCiy4C4H
Max-Forwards: 70
From: <sip:[email protected]>;tag=BJ2er-g.ONc2M.MQJ9qO.wfpLyp8qfQ3
To: <sip:[email protected]>
Contact: <sip:[email protected]:5060>
Call-ID: L9TrfBGqqYwgo6CR.c9YtaiyulB9OGVU
CSeq: 23308 INVITE
Route: <sip:oxe-ov.alcatel.fr;transport=udp;lr>
Route: <sip:[email protected];transport=udp>
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: 100rel, norefersub
User-Agent: OmniTouch 1.5.13.7
Content-Type: application/sdp
Content-Length: 283
The OXE SIP proxy receives an INVITE with the information Route corresponding to the final end point for
the SIP call. In that case, the OXE SIP proxy acts like a proxy (not a back to back). Due to this, the proxy
sends the following INVITE to the final SIP endpoint.
Fri Jun 29 14:08:10 2012 SEND MESSAGE TO NETWORK (172.27.141.151:5060 [UDP]) (BUFF LEN = 1130)
----------------------utf8-----------------------
INVITE sip:[email protected];transport=udp SIP/2.0
Route: <sip:oxe-ov.alcatel.fr;transport=udp;lr>
Record-Route: <sip:172.27.143.186;lr;transport=UDP>
Via: SIP/2.0/UDP
172.27.143.186;branch=z9hG4bK1053e27e7fdda06c573798bc91cd12a29c49e03527107ccdabde727c92e5b987
Via: SIP/2.0/UDP 172.27.143.184:5060;received=172.27.143.184;rport=5060;branch=z9hG4bKPjX7-
GJh79mg04nEbZ0yxYsWP3MCiy4C4H
Max-Forwards: 69
From: <sip:[email protected]>;tag=BJ2er-g.ONc2M.MQJ9qO.wfpLyp8qfQ3
Call-ID: L9TrfBGqqYwgo6CR.c9YtaiyulB9OGVU
CSeq: 23308 INVITE
Allow: PRACK,INVITE,ACK,BYE,CANCEL,UPDATE,SUBSCRIBE,NOTIFY,REFER,MESSAGE,OPTIONS
Supported: 100rel,norefersub
User-Agent: OmniTouch 1.5.13.7
Content-Length: 283
Session-Expires: 1800
The proxy adds some information on the INVITE sent to the final SIP end point, but the INVITE is the same
as the one received (same Call-ID, same FROM, same TO, same TAGs, etc...)
o The REQUEST-URI has been modified according to the information from the Route from
the first INVITE.
INVITE sip:[email protected]
o Information added:
Via: SIP/2.0/UDP 172.27.143.186; branch=z9hG4bK1053e27e7fd
Correponding to the proxy identification
Record-Route: <sip:172.27.143.186;lr;transport=UDP>
Correponding to the path for the answers (the answers must be sent to this
IP address)
Corresponding to the session timer used on the proxy
Ed. 12 16 TG0069
OmniPCX Enterprise
The Proxy can be used as a Back-to-Back. In that case, on each side, two different legs will be
found:
INVITE with leg1 INVITE with leg2

Alice Proxy Bob
UAC UAS UAC UAS
Two different INVITEs on each proxy sides.
There are no specific information on the INVITE because the proxy acts as an UAS for the caller and an
UAC for the called party.
8.4.3 Gateway
Entity between SIP world and legacy world, the gateway is used to establish a call from a SIP equipment to
an ISDN link, to a legacy set, etc and vice versa.
Do not confuse the SIP gateway with the OmniPCX Enterprise media gateway boards:
o The SIP gateway is a logical entity that resides within the call server (CS) and is responsible
for the SIP signaling for the conversation setup,
o The media gateway boards (GD, GA, INTIP) are the physical devices where the media
session will be established when calling to a classic PBX set.
There is one and only one internal SIP gateway. But there can be many different external SIP
gateways (we will come back to this in a later section).
The SIP gateway is associated to a SIP trunk group. Although there can be many SIP Trunk Groups,
there is only one SIP trunk group which is associated to the local SIP gateway. We call this special
trunk group the local SIP trunk group.
8.4.4 Dictionnary
Contains the SIP users created on the OXE, it is the database that holds the mapping between SIP URLs
and PBX directory numbers (MCDUs). Each registered SIP terminal is automatically added to the
dictionnary. Classic PBX terminals are added only if a SIP URL is defined for them in the user management.
Most of the time you shouldnt do anything with the Dictionnary. Everything will be handled
automatically. You need to access the SIP Dictionnary configuration only for configuration of aliases.
8.4.5 SIP users
On the OXE , there are two types of SIP users:
SIP Device
o A SIP device is considered as an external SIP user. It means that the SIP device is linked to
the local SIP gateway and uses its configuration
o The phone features are limited
SIP Extension(or SEPLOS)
Ed. 12 17 TG0069
OmniPCX Enterprise
o A SIP extension is considered as an internal SIP user. It means that the SIP extension can
access to some OmniPCX Enterprise services and phone features
o It can use some OmniPCX Enterprises prefixes, can be declared as a room set, etc
o The available phone features depends also on the SIP phone itself.
o A SIP extension is attached to a virtual UA board, like an IPtouch.
On OXE, it is necessary to understand that a SIP extension user is different from the SIP phone associated
to this user.
For instance:
- If the SIP phone is forwarded, it doesnt mean that the user is forwarded.
- If the user is forwarded, it doesnt mean that the SIP phone is forwarded.
It is very important to remember this behaviour.
The declaration of a SIP user binds the information configured in the SIP set with the information stored into
the database of the OmniPCX Enterprise.
If you dont fill in the SIP part in the OmniPCX Enterprise user configuration, the default values will be :
URL User Name = MCDU of the user.
URL Domain = SIP domain name of the OmniPCX Enterprise, i.e. the SIP set is considered as
registered on the OmniPCX Enterprise.
This is usually exactly what we want so you shouldnt modify anything here.
After the creation of the user a corresponding entry will automatically be added to the SIP Dictionnary.
Note: The value for the URL (<username>@<domainname>) configured on the SIP set and in the OmniPCX
Enterprise SIP Dictionnary MUST match. This can be an issue if you modified one of these parameters by
hand and not the other one.
8.4.6 SIP External Voice Mail
On the OXE, it is possible to connect external voice mail, as the OmniTouch 8440, to be able to manage it
and use it. The local SIP gateway must be managed first.
Enhancement with OXE R11: Device ringing when SIP VoiceMail is Out of Service
Behavior before R11: if any set is forwarded to an SIP External Voicemail and if that SIP Voicemail is
Out of Service, the call is disconnected
Enhancement from R11: When the SIP External Voicemail is Out of Service, the last set which has
activated the forward is ringing. It works in local, network and with external (SIP trunking for
example). For external calls, this feature will allow the terminal to ring till the trunk overflow timer and
after which it will overflow to the entity of the last set which is forwarded to SIP Voicemail that is Out
of Service
Ed. 12 18 TG0069
OmniPCX Enterprise
8.5 Overview of Interaction between Components

The following diagram shows the relationship between the functional SIP modules in OmniPCX Enterprise :
sip : [email protected]
is reachable at
Dictionnary Registrar phone2.alcatel-lucent.com
sip : [email protected]
is reachable at
phone1.alcatel-lucent.com
Gateway Proxy
Legacy
set sip : [email protected] sip : [email protected]
phone1.alcatel-lucent.com phone2.alcatel-lucent.com
8.6 Network number rules

The OXE uses network (or subnetwork or routing tables) for different applications. The network must be
unique for each application. It is very important for SIP to respect the following configuration:
The ABC-F network uses its own network number (managed in System parameter).
The VPN uses different network numbers according to the configuration.
The local Hybrid Link (for CCD) uses its own network number.
The local SIP gateway must use a dedicated network number. Do not use a network number used by
another application.
Each external ABC-F gateways use their own network numbers.
These rules must be enforced to avoid SIP issues.
8.7 Overview of Remote Extension feature

Enhancement with OXE R11: Overflow to associate set if REX user is unavailable
Behavior before R11: when the mobile set of a Remote Extension user receives a call from OXE and
the mobile is in one of the following states (swithed off, busy, Out of Coverage area, Out of Service,
the REX user may reject the call), OXE will receive a DISCONNECT message from the REX is
unavailable due to the above mentioned reasons. When an Associate Set is managed in OXE for the
Remote Extension, on receiving a DISCONNECT message, the behavior in OXE depends on the
value of a system parameter System -> Descend Hierarchy -> Other System Parameters ->
Descend Hierarchy -> External Signaling Parameter -> Review/Modify -> Listen to guide on
DISCONNECT
According to the existing implementation of Remote Extension, when the parameter Listen to guide
on DISCONNECT is set to:
Ed. 12 19 TG0069
OmniPCX Enterprise
o TRUE the incoming call to Remote Extension overflows to its Associate Set only after no
answer timer expires.
o FALSE the incoming call to Remote Extension overflows to its Associate Set immediately
Enhancement from R11: When REX user is configured as Non-Tandem set, then the call will
overflow to the associate set of the REX immediately irrespective of the value of parameter Listen to
guide on Disconnect. Whenever REX user is configured as Tandems secondary set, the overflow
will depend upon the state when the DISCONNECT message is received. If OXE receives a
DISCONNECT message before ALERT, the call will not overflow to the associate Set immediately
but will overflow only after the call no answer timer. If OXE receives the DISCONNECT message
after ALERT, the call will overflow to the associate set of the REX immediately
8.8 Overview of G711 Transparent Fax and T38 fallback G711 feature
In a FAX over IP communication, when a SIP External Gatway is involved, the transmission is done through
T38 Procedure. From OXE R11, the G711 procedure for fax communication is implemented, as well as a
Fallback procedure from T38 to G711.
With this feature, OXE will support two more procedures. For SIP calls, FAS support will be done in 3 modes:
o The T38 only procedure
o The G711 transparent procedure
o The T38 to G711 Fallback procedure (In a first step, fax will try to establish with T38, if remote side
doesnt support it, it will fallback to G711 mode)
The configuration of the above options is made in the corresponding External Gateway parameter (Fax
procedure type).
Remark: this feature is applicable for the INTIP3/MG3 couplers only
8.8.1 The T38 only procedure
If the configuration parameter is T38 only, the existing behavior applies only T38 mode will be supported. If
the remote party doesnt support this mode, the call will be disconnected. IP > Fax Parameters > T38 Only
option is kept for compatibility with the previous releases.
8.8.2 The G711 only procedure
After initial call establishment, no signalling should be received for FAX. FAX should be received/sent in
G711.
Step1: If the initial call is established with G711 and the IP coupler in front of the FAX are
INTIP3/MG3couplers, OXE can detect the FAX sent by SIP External Gateway in G711 mode.
Step2: If OXE receives a Re-INVITE with T38 parameters, the negotiated codec and the IP coupler type is
checked and based on that, the acceptance of the call is decided:
- Case 1: codec is G729/G723. Call proceeds in T38 mode
- Case 2: codec G711 and INTIP3/MG3 coupler. When OXE receives Re-INVITE with T38 and if the
initial call is with G711, OXE sends 488 Not Acceptable Here to the SIP External Gateway. This is
because, since configuration of Fax mode is G711 Only, Media Gateway prepared to send/receive
the FAX in G711 transparent so Media Gateway is no more able to switch back to T38.
Else, Fax is transmitted in G711 Transparent mode
Step3: If OXE receives a Re-INVITE with G711 parameters, FAX is transmitted in G711 Transparent mode
Remark: at the sending of 488 Not Acceptable Here, some carriers may continue the Fax tranmission in
G711 transparent mode.
Ed. 12 20 TG0069
OmniPCX Enterprise
OXE INVITE: SDP (G711) SIP Carrier
180 ringing
200 OK : SDP (G711)
ACK
Fax communication starts in G711 mode
At this moment, at the reception of Fax
RE-INVITE : SDP (T38) signal thru G711 flow, step2 can happen
488 Not Acceptable Here At the reception of the SIP error:

Fax communication continues in G711 mode - either transmission is aborted
- either transmission continues in G711
RE-INVITE : SDP (G711) mode
- or step3 happens
200 OK : SDP (G711)
Fax communication continues in G711 mode
8.8.3 The T38 to G711 Fallback procedure
If the SIP External Gateway configuration parameter is T38 to G711 Fallback and if the IP Couplers in front
of FAX are INTIP3/MG3 couplers and if the initial call is established with G711, OXE will try to establish the
FAX in T38 mode. If the remote SIP Party is not able to support FAX in T38 mode, it will send Error
message. This will result in OXE to switch the FAX to G711 Mode.
Outgoing call
If OXE receives a RE-INVITE with T38 parameters, the call will proceed in T38. If OXE receives FAX call in
G711, it will directly detect and handle it.
Incoming call
Step1: When OXE detects a T38 FAX call, it sends Re-INVITE with T38 parameters as usual.
Step2: If the SIP Carrier accepts it and 200 OK is received with T38 parameters, then call proceeds in T38
mode.
Else if the SIP Carrier does not accept it and sends an Error response, the following cases are
envisaged:
- Case 1: If the negotiated codec is G711 and the IP couplers are INTIP3/MG3 couplers, then OXE
will switch to G711 mode.
- Case 2: If the coupler in front of FAX is other than INTIP3/MG3 coupler, or if the negotiated codec
is G729/G723, the call is disconnected.
Remark: If OXE is in transit position, the Error response will be relayed transparently.
Ed. 12 21 TG0069
OmniPCX Enterprise
OXE Carrier
INVITE : SDP (G711)
180 RINGING
200 OK : SDP (G711)
ACK
Fax communication starts in G711 mode
At this moment, OXE detects T38 mode
RE-INVITE : SDP (T38)
4xx / 5xx Response At the reception of Re-INVITE (T38),
ACK Carrier can:
- either accepts it with a 200 OK
Fax communication in G711 mode (T38)
- or sends an error response
OXE switches to
G711 mode
8.9 Overview of Private SIP Transit mode feature

SIP Calls are handled by the OXE through the following software modules:
The SIPMOTOR, it is in charge to relay and receive SIP request to or from the SIP Call handling
The SIP Call Handling, it provides a protocol gateway between SIP and Q931
The Call Handling, it is the legacy part of the OXE, which handled the generic telephony features
rd
It appears that, for instance, a call from an OT SIP device cannot call a SIP ABC-F 3 Party application
through OXE
Enhancement with OXE R11.0.1: Possibility to reach or being reachable from Open Touch by using
an OXE routing prefix, or also, between two OXE routing prefixes
Behavior before R11.0.1: for instance, when a call from an OT SIP device was performed at
rd
destination of a 3 Party Application (through SIP-ABC trunking), OXE uses the mode 4.2 and
generates a 301 Moved Permanently response. In some cases, if direct Trunk Group is not
available to reach remote application, the call fails.
Enhancement from R11.0.1: a Private SIP Transit Mode is added on the OXE management and can
take three different values
Ed. 12 22 TG0069
OmniPCX Enterprise
o Proxy or redirect mode (prior functioning)
o Mixed mode (default value), 301 Moved Permanently
Ed. 12 23 TG0069
OmniPCX Enterprise
o Full Call Handling mode
When an INVITE arrives to the SIP Motor, depending on its origin (UAC or calling user) and its destination, it
can be handled in four different ways :
mode 1 : Call Handling delivery
The call is delivered to the SIP Call Handling, and finally delivered to the Call Handling itself. This is the
most usual way. In this case, the call inherits of various collateral features such as barring, metering, general
call routing, and so on.
mode 2 : CAC SIP Call handling
The call is delivered to the SIP Call Handling, and remains in the SIP Call Handling, which relays the call
through the SIP Motor. The call may be redirected as described in mode 4.1, and mode 3 would then apply.
mode 3 : Stateless proxy behavior
The call is directly relayed to the destination SIP End Point. The Call Handling is not involved in the call,
which remains in the OXE as a proxy call.
mode 4 : Redirect proxy behavior
The call is first delivered to the SIP Call Handling ; there is then two different modes :
o mode 4.1 : 305.Use Proxy

A 305.Use Proxy is sent back from the SIP Call Handling to the SIP Motor, which acts at that time
as a Stateless Proxy (mode 3).
o mode 4.2 : 301.Moved permanently

A 301.Moved Permanently is sent back from the SIP Call Handling to the SIP Motor, and is relayed
to the UAC. Consequently, the call is no more handled by the OXE. In other words, the UAC
Ed. 12 24 TG0069
OmniPCX Enterprise
(calling user) is in charge to reach directly the destination user, by analyzing the Contact headers
URI of the 301.Moved Permanently.
8.10 SIP parameters explanation / under the object SIP:
8.10.1 SIP Trunk Group
WARNING : If you add additional SIP access to your SIP trunk group you MUST reboot the
call server, if you don't the newly added access will show F (free) in trkstat command BUT
they won't be used by the Call Server until next reboot.
The SIP Trunk Group is mandatory if you want to use the Local SIP gateway or an external SIP gateway (not
necessary for SEPLOS users).
The Trunk Group is used to give channels for SIP calls. According to its type and configuration, the available
features are different.
Remark: for non AAPP/ALU applications, a SIP ISDN or SIP ABC trunk group can be used only under
control of TC1820 : Alcatel-Lucent OmniPCX Enterprise SIP Trunking with 3rd Party ( IVR & Contact
Center ) guideline. This guideline provides configuration and topologies supported by ALE.
Remark: for SIP Carrier, interworking with OXE must be validated by Christophe Haettinger and ALE
Technical Support team. A survey must be filled by the carrier and according to the answers, an interworking
test campaign will be proposed
Maximum number of SIP Trunk Groups : 300

Maximum number of pair of accesses per SIP Trunk Group : 16
Different types of SIP trunk Groups are available on OXE:
o The SIP ABCF Trunk Group.

992 simultaneous communications (62 per pair of access)
o The SIP ISDN Trunk Group.

o The Mini SIP ABCF Trunk Group.

o The Mini SIP ISDN Trunk Group.

Level of service depending on used trunk group :

o Call transfer
ISDN :Using re-INVITE in the opened dialog.
ABC-F :Via REFER, referred-by and replaces .
o Call forward
ISDN :Done internally.
ABC-F :Redirecting with 3xx. New call has to be performed by remote party.
o Call barring
ISDN :Same as ISDN.
ABC-F :No barring.
To create a SIP Trunk Group, go under /Trunk Groups
Ed. 12 25 TG0069
OmniPCX Enterprise
Trunk Group Type : Select T2 for all the different types of SIP Trunk Group
Trunk Group Name : Manage a name for the SIP Trunk Group
Number Compatible With : Keep -1 everytime, dont manage another value
Remote Network : Enter a Remote network number, for an ABCF TG, use the dedicated number, for ISDN TG
keep 255 (idem as legacy T2 ISDN Trunk group)
Node number : Enter the node number of your OXE
Q931 Signal variant : - For an ABCF SIP Trunk group, select ABC-F
- For an ISDN SIP Trunk Group, select ISDN
Number Of Digits To Send : Keep 0 everytime, dont manage another value
T2 Specification : - Select SIP for a SIP Trunk Group (ISDN or ABCF)

- Select Mini SIP for a Mini SIP Trunk group (ISDN or ABCF)
Public Network COS : According to the value manage, the OXE will use the rights of the associated category
DID transcoding : This parameter is set to True only in case of ISDN SIP Trunk Group (or Mini SIP ISDN Trunk
Group)
Associated Ext SIP gateway : Enter the external SIP gateway used if there is no DCT managed on the ARS route, the DCT
from the ARS route is used in priority From R10.1
To create a SIP Trunk Group, go under /Trunk Groups/Trunk Group
IP Compression Type : - Default means only the system algorithm used on SDP
- G711 means the use of the sytem algorithm and the PCM with the system law
Parameter disappears from R11
Trunk COS : According to the value manage, the OXE will use the rights of the associated category
IE External Forward : Select Diverting leg information if you want to use the History-Info or Diversion header From
R10.1
Max ABCF-IP and SIP connections : Maximum number of simultaneous voice connections allowed for this trunk group. 0 (default
value) means no limitation. This parameter applies only to ABCF-IP and SIP trunk groups.
Trkstat tool is updated to indicate the value in real time (Max. Voice calls). From R11.0.1
To create a SIP Trunk Group, go under /Trunk Groups/Trunk Group/Virtual accesses for SIP
Number of SIP Accesses : Enter the number of SIP accesses needed on the SIP TG (value from 2 to 32)
8.10.2 The local SIP gateway
Used for the local SIP users (SIP Device) and the external Voice mail
To manage the Local SIP gateway, go under /SIP/SIP Gateway
SIP Subnetwork : Corresponds to the local SIP network (different than the ABC-F network and used only for the
local SIP gateway).
SIP Trunk Group : Corresponds to the SIP Trunk group (better to use an ABCF SIP Trunk group)
IP Address : Corresponds to the IP address of the CPU (autofill)
Machine name Host : Corresponds to the nodename associated to the main IP address (managed via netadmin -
autofill).
SIP Proxy Port Number : Corresponds to the SIP port number (by default 5060).
Ed. 12 26 TG0069
OmniPCX Enterprise
SIP Subscribe Min Duration : Corresponds to the minimum duration of a SIP subscription (for message waiting indication or
for result of a transfer).
SIP Subscribe Max Duration : Corresponds to the maximum duration of a SIP subscription (for message waiting indication or
for result of a transfer).
Session Timer : Corresponds to the timer value to supervise an active SIP session. A RE-INVITE or UPDATE
message is sent before SIP Session Timer expiry (for all SIP elements).
Min Session Timer : Corresponds to the mimimum session timer value accepted by the OXE. When a SIP call is
established, the session timer is negociated between the two parties.
Session Timer Method : Corresponds to the method used for session timer, the OXE sends a RE-INVITE or an
UPDATE message.
DNS local domain name : Corresponds to local DNS suffix used for SIP. The FQDN of the OXE is the nodename + this
domaine name (mandatory in case of spatial redondancy).
DNS type : Corresponds to the DNS mode (A or SRV).
SIP DNS1 IP Address : IP address of the first DNS server. Dont manage the CPU IP address
SIP DNS2 IP Address : IP address of the second DNS server. Dont manage the CPU IP address
SDP in 18x : Used to put SDP information on th 18x sent by the OXE.
Cac SIP-SIP : To allow or not, the domains control in SIP to SIP communications.
INFO method for remote extension : Using the INFO method for DTMF in case for the Nokia Call Connect (NCC) only.
Dynamic Payload type for DTMF : Payload value used for DTMF, default value 97 (used by the SIP device for instance).
8.10.3 The external SIP gateways
Maximum number of External Gateways : 1000

Maximum number of External Gateway Pool : 5
Maximum number of External Gateway per Pool : 2
Used to connect external SIP equipments // applications (SIP provider, Call centre application, etc).
SIP External Gateway ID : Id of the gateway
Gateway Name : Name given to the gateway
SIP Remote domain : IP address or FQDN of the remote SIP equipment (if FQDN, need to use a DNS server)
PCS IP Address : PCS IP address used to backup this gateway in case of link failure with the CPU
SIP Port Number : SIP port number used to send SIP messages on the remote gateway
SIP Transport Type : Transport type for SIP messages (UDP or TCP)
Belonging Domain : Used to define the domain part of the URI (FROM and PAI) on the SIP message
Registration ID : Registration id used on the user part if the remote gateway needs it
Registration ID P_Asserted : Used the registration ID on the P_Asserted Identity (PAI)
Registration timer : Timer used for registration (0 = no registration)
SIP Outbound Proxy : Send the messages (INVITE and REGISTER) on this address
Supervision timer : Used to supervised the remote gateway (OPTION message sent)
Trunk group number : SIP trunk group used for this SIP gateway
Pool Number : Can associate 2 external SIP gateways in one pool (Load Balancing)
Ed. 12 27 TG0069
OmniPCX Enterprise
Outgoing realm : Realm of the remote gateway (Outgoing messages authentication)
Outgoing username : Username from the remote gateway (Outgoing messages authentication)
Outgoing Password : Password from the remote gateway (Outgoing messages authentication)
Incoming username : Username used by the remote gateway (Incoming messages authentication)
Incoming Password : Password used by the remote gateway (Incoming messages authentication)
RFC 3325 supported by the distant : PAI supported for Outgoing calls
DNS type : DNS requests types (A or SRV)
SIP DNS1 IP Address : IP address of the first DNS server Dont manage the CPU IP address
SIP DNS2 IP Address : IP address of the second DNS server Dont manage the CPU IP address)
SDP in 18x : Used to put SDP information on the 18x sent by the OXE. Recommended value is False when
PRACK/UPDATE methods are not supported by remote domain
Minimal authentication method : Used to activate or not the authentication (DIGEST or SIP none)
INFO method for remote extension : Using the INFO method for DTMF in case of remote extension
Send only trunk group algo : Used to send only the algorithm managed on the SIP TG Parameter disappears from R11
To EMS : Used to activate the RFC4916 (Add specific fields for identification on EMS)
To EMS parameter must be set to false
SRTP : Used in case of SIP TLS to select the RTP mode (secured or not)
Routing Application : - False: SDP sets on the SIP messages (INVITE, 200ok...)
- True: No SDP on the SIP messages, this parameter is used for some specific configuration for
carriers
Ignore inactive/black hole : Only for SIP ABC-F.

- False means that the receipt of a Re-INVITE, whose SDP indicates either inactive or c=0.0.0.0
is handled as an Hold request.
- True means that the same kind of Re-INVITE leads the RTP flow towards the remote party to
be cut.
Contact with IP address : In case of spatial redundancy with dual subnetworks, the IP address of the main Call Server is
put on the Contact field instead of the FQDN of the OXE
Dynamic Payload type for DTMF : Corresponds to the payload value for DTMF must be the same than value from the remote SIP
equipment.
100 REL for Outbound Calls : - Not supported : Outbound INVITE doesnt indicate 100Rel parameter.
- Supported : Default Value. Outbound INVITE indicates 100Rel in Supported header.
- Required : Outbound INVITE indicates 100Rel in Required header.
100 REL for Incoming Calls : - Not requested : Default value. 18x response triggered from OXE doesnt indicate 100Rel in
Require header.
- Required mode1 : 18x response triggered from OXE indicates 100Rel in Require header
only if it provides SDP.
- Required mode2 : 18x provisional response triggered from OXE indicates 100Rel in Require
header.
Gateway type : Use to define if the remote SIP gateway is un Open Touch or not, keep default configuratiuon if
it is not a Open Touch
Re-Trans No. for REGISTER/OPTIONS : Number of retransmission of SIP REGISTERs/OPTIONs messages, from 1 to 10
P-Asserted-ID in Calling Number : - If True, Calling Number is filled from P-Asserted-ID header
- If False, Calling Number is filled from FROM header.
Trusted P-Asserted-ID header : Octet3a_Calling is filled based on this parameter (Used, only when there is P-Asserted-ID
header)
Ed. 12 28 TG0069
OmniPCX Enterprise
Diversion Info to provide via : In the Outbound INVITE the selected Header is added to provide information about Call
deflection/forward. The OXE can use History-Info (RFC 4244) or Diversion (RFC 5806)
Proxy identification on IP address : - if True, a dynamic DNS cache per SIP External Gateway is handled by OXE to store the IP
address(es) where Register and further INVITE may be sent. At the beginning of the procedure,
this DNS cache is empty. From R10.1
Outbound calls only : - if False, the existing procedure applies.

- If True, the External Gateway is skipped during the lookup procedure of the origin of the call.
The way to determine the origin of an inbound call, e.g. the External Gateway it comes from, is
made in such a way that in that topology, the lowest External Gateway, in term of numbering, is
chosen. From R10.1
SDP relay on Ext. Call Fwd : In case of SIP trunk to SIP trunk call rerouting (essentially external to external call forward), in
order to adapt specific SIP profile, OXE offers the possibility to transit SDP answers received in
180 or 183 on outgoing leg only in 180 answer on incoming leg.
- Default : normal procedure apply. SDP can transit with 183 message depending on call flow.
- 180 only : any SDP received in 180 and 183 on outgoing leg will not transit on incoming leg in
183 provisional answer but only in 180 ringing one. From R10.1
SDP Transparency override : if TRUE, the SDP offer received from SIP leg1 is enhanced towards SIP leg2 in the following
way:
- G729 only received from SIP leg1, a G729/G711 offer is relayed to SIP leg2
- G729 is not received from SIP leg1, in that case, the original offer received might be single
(G711 A or G711 Mu) or multiple (G711 A + G711 Mu, or G722 + G711 ) G729 is added in
the offer provided to leg2 From R10.1 More details on section 9.6
RFC 5009 supported / Outbound call : support of the P-Early-Media header in the SIP-ISDN call, can be configured at:
- Not supported: for outgoing call, P-Early Media header will not be included
- Mode1: for outgoing call, P-Early-Media: Supported header will be added in INVITE
method. If OXE receives a provisional response without P-Early-Media in this message or
before, the SDP, if any, in the provisional response will not be connected to OXE user
- Mode 2: for outgoing call, P-Early-Media:Supported header will be added in INVITE
method. If OXE receives a provisional response without P-Early-Media in this message or
before, the SDP, if exists, in the provisional response will be connected to OXE user From
R11
Nonce caching activation when authentication is activated on SIP Carrier side, then depending on this parameter value:
- No: the OXE does not provide any Authorization header, neither in Register, nor in INVITE
- Yes: the OXE provides in each REGISTER and INVITE an Autorization header, containing
the last nonce received from the carrier, and increments the associated nonce counter
accordingly From R11
Fax procedure type choose the mode of Fax transmission :

- T38 only: Fax will be transmitted in T38 mode. If the remote party did not support this
mode, the call will be disconnected
- G711 only: if the initial call is established with G711 Mode and if the IP Coupler of the
compressor is NGP coupler, Fax will be established with G711. Otherwise, Fax will be
established in T38.
- T38 to G711 fallback: the FAX will try to establish in T38 Mode. If the remote party does
not support T38 mode, it will send Error message. In this case, if the initial call is
established with G711 and the IP coupler of the compressor is NGP coupler, FAX will
switch to G711 Mode. Otherwise, call will be disconnected. From R11 More details on
section 8.7
Trusted From header : Octet3a_Calling is filled based on this parameter (Used only when there is no P-Asserted-ID
header). To be used when calling number is found in FROM header and should be considered
as trusted by the system.
Support Re-invite without SDP : - if True, the OXE will send a RE-INVITE without SDP to provide transfer, depending on the
OXE release:
From R10.1, it applies to transfer of two SIP ISDN remote parties.
From R10.1.1, it applies to transfer of two SIP ISDN remote parties, and to SIP
TLS / sRTP.
From R11, it applies to each transfer involving at least one SIP ISDN remote part.
- if False, the OXE will send a REINVITE with SDP.
Restriction with R10.x : When PRACK is supported, this parameter must be set to False
Type of codec negotiation : this is the type of format of SDP offer for outgoing calls on this gateway:
Ed. 12 29 TG0069
OmniPCX Enterprise
- Default: everything is allowed

- Single codec G711, only G711 is offered (sometimes with G722)
- Single codec G729, only G729 is offered
- From domain, if coming from a restricted domain, only G729 is offered, else a list is offered
From R11 More details on section 9.5
Registration on proxy discovery : - if True, used when SIP Carrier provides more than one outbound proxy. As soon as, on
carrier side a switch happens from one proxy to another, calls can be neither delivered to OXE,
nor accepted by the carrier as long as a new registration is not triggered by OXE. From R11
DNS SRV/Call retry on busy server : - if 0, the receipt of 486 Busy Here response from the relevant external gateway launches the
release procedure.
- if different than 0, and DNS SRV is supported, the relevant external gateway re-launches the
INVITE to the next IP@ of the current DNS cache.
- Else, the release procedure applies. From R11.0.1
Unattended Transfer for RSI : - if False, the normal mechanism service remains and the signaling path is kept between OXE
and Carrier as a transit call.
- if True, in case where incoming call is coming from SIP-ISDN and route select occurs when
call is established (play guide), if target transfer is reachable through SIP-ISDN, REFER method
is used and the OXE leaves the signaling path.
- Else, the normal mecanishm with RE-INVITE occurs. From R11.0.1
Redirection functionality : This parameter applies only for customers with a private SBC.
- If True, all incoming calls whose destination indicates another node of the network, are
rerouted to the SBC with a 301 Moved Permanently response, to avoid the use of the IP-ABCF
link. The SBC must be able to resolve the contact Domain Part which is hardcodec like this:
oxe_node_xx where xx is the remote node number
- If False, all incoming calls are handled by the local node, whatever the location of the
destination user. From R11.0.1
Attended Transfer - If True, the REFER method applies for SIP offnet/offnet attended transfer and the OXE leaves
the signalling path.
- If False, the RE-INVITE method applies for SIP offnet/offnet attended transfer and OXE
remains in the signalling path. From R11.0.1
8.10.4 Timer usage for SIP Trunking (Trunk Categoy, by default 31)
This only applies to SIP Trunking Call Handling where generic timers are used
Timer Value Meaning

Timer T302 15s Related to SETUP_ACK
Timer T303 10s Related to Call Process
Timer T304 90s Related to INFO
Timer T305 4s Related to Disconnect
Timer T308 4s Related to Release Complete
Timer T309 90s
Timer T310 20s Related to ALERT
Timer T313 4s Related to Connect_ACK
Timer T306 6s Related to BYE
Timer T314 2s
Timer T383 5s
Timer T389 8s
Timer T392 1s
Timer T397 5s
8.10.5 The SIP proxy
Used to activate some parameters linked to the Proxy (SIP authentication for instance)
SIP initial time-out : This attribute specifies the initial value in milliseconds of the request/reply SIP message
retransmission timeout corresponding to T1. Default value 500ms
SIP timer T2 : This attribute specifies the maximum time in milliseconds between two SIP message
retransmissions. Default value 4000ms
Ed. 12 30 TG0069
OmniPCX Enterprise
Dns Timer overflow : Timer used to overflow from DNS 1 to DNS 2
Timer TLS : This attribute is used to define the keep alive for TLS
Recursive search : This attribute is used to define the behavior of the proxy on reception of a redirection message.
(NOT CURRENTLY USED)
- YES: the proxy handles redirection.
- NO: the proxy leaves the caller to handle redirection.
Minimal authentication method : Activation of the Proxy authentication

- SIP none, there is no authentication
- SIP Digest, the authetication is validated
Authentication realm : Corresponds to the authentication SIP domain on the OXE
Only authenticated incoming calls : Activation of the SIP authentication for incoming calls
Framework Period : Indicates the basic time for an observation period before to put the IP address in quarantine (3s by
default).
Framework Nb Message By Period : Indicates the maximum number of received messages during the time of the observation
periods which may put the IP address in quarantine (25 messages by default).
Framework Quarantine Period : Indicates the periods number before to put the IP address in quarantine (1800s by default)
TCP when long messages : This parameter is used when UDP is used as transport protocol, to allow or not the use of TCP for
long messages. This parameter applies to external gateways, SIP extensions, SIP devices and SIP
external voice mails.
- True (default value): TCP is used, rather than UDP, when the message size is higher than the
maximum size (1300 bytes)
- False: UDP is used, whatever the size of messages.
Retransmission number for INVITE : This Attribute corresponds to the number of INVITE retransmission, from 1 to 6
SIP timers explanation:
Timer Value Meaning

Timer 1 500 ms Round-trip time (RTT) estimate
The maximum retransmit interval for non-INVITE requests
Timer 2 4000 ms
and INVITE responses
Timer 4 5000 ms Maximum duration a message will remain in the network
Timer A Initially T1 INVITE request retransmit interval, for UDP only
Timer B 64 *T1 INVITE transaction timeout timer
Timer C > 3 min Proxy INVITE transaction timeout
32s for UDP
Timer D Wait time for response retransmits
0s for TCP
Timer E Initially T1 Non-INVITE request retransmit interval, UDP only
Timer F 64 *T1 Non-INVITE transaction timeout timer
Timer G Initially T1 INVITE response retransmit interval
Timer H 64 *T1 Wait time for ACK receipt
T4 for UDP
Timer I Wait time for ACK retransmits
0 s for TCP
64* T1 for UDP
Timer J Wait time for non-INVITE request retransmits
0 s for TCP
T4 for UDP
Timer K Wait time for response retransmits
0 s for TCP
8.10.6 SIP Registrar
Used to manage the registration timers
SIP Min Expiration Date : Minimum lifetime of a record accepted by the Registrar (in secondes). Default value 1800.
SIP Max Expiration Date : Maximum lifetime of a record accepted by the Registrar (in secondes). Default value 86400.
Ed. 12 31 TG0069
OmniPCX Enterprise
The minimum value must not be under 420 (7 minutes). The REGISTER must not be used as
a keep alive mechanism. 900 (15 minutes) is a minimum acceptable value.
8.10.7 SIP Dictionnary
Corresponds to the SIP users created on the OXE, this dictionnary is fill up automatically when a SIP user is
created, entries on this dictionnary can be created manually if needed (Not used), but the purpose of this
object is to be able to modify one entry already created or to add aliases
Directory Number : Corresponds to the directory number of Station, Network number or Vmail number.
Alias No. : Can create different alias for the same directory number
SIP URL Username : User part of the URL. SIP identifies users by their URLs (Universal Resource Locator), composed of
a user part and a domain part (user@domain).
SIP URL Domain : Domain part of the URL. SIP identifies users by their URLs, composed of a user part and a domain
part (user@domain). If the domain part is omitted on creation of a set, the domain part of the
installation URL is used (SIP/SIPgateway).
SIP URL Type : Corresponds to the user type (SIP extension or SIP Device).
SIP URL Origin : Corresponds to the origin node.
8.10.8 SIP Authentication
Used to modify the password of a entry created automatically (SIP user for instance)
Directory Number : Directory number of the entry selected (not modifiable)
SIP Authentication : SIP login associated to the entry (not modifiable)
SIP Passwd : Enter a new password if needed
Confirm : Confirmation of the new password entered
8.10.9 Quarantined IP Addresses

Used to put the IP addresses of the SIP equipments you want to put in quarantined manually, SIP messages
from these addresses are dropped silently.
8.10.10 Trusted IP Addresses

Used to put the IP addresses of the SIP equipments not affected by the quarantined mechanism. If after
management the communication with this SIP equipments is still rejected by the OXE, restart the
SIPMOTOR processes.
Ed. 12 32 TG0069
OmniPCX Enterprise
8.10.11 SIP To CH Error Mapping

Used to link the error SIP messages to the ISDN Q850 causes, for each error SIP message, you select one
Q850 cause
A default configuration is done. Without specific needs, no modifications have to be made.
Bad request Request terminates
Unauthorized Not acceptable here Unallocated number
Payment required Server internal error User busy
Forbidden Not implemented No user responding
Not found Bad gateway Call rejected
Method not allowed Service unavailable Invalid number format
Not acceptable Server timeout No circuit
Proxy authentication required Version not supported Temporary failure
Request timeout Busy everywhere Bearer cap. not implemented
Conflict Decline Incompatible destination
Gone Does not exist anywhere Others
Length required Not accept
Request entity
...
8.10.12 CH To SIP Error Mapping

Used to link the ISDN Q850 causes to the error SIP messages, for each Q850 cause, you select error SIP
message.
A default configuration is done. Without specific needs, no modifications have to be done.
Unallocated number Channel type not implemented

No route to specify transit NW Req facility not implemented
No route to destination Only Rest Digi Info Becap Avail
France Specific Option not implemented
Denmark Specific Invalid call reference value
Channel unacceptable Identified channel does not exist
Call awarded - deliv in estab channel Susp Call Exists But Call Ident
Not found
Reserved MLPP Call Identity in use Gone
Normal call clearing No call suspended
Temporarily unavailable
User busy Call having req call ID cleared Address Incomplete
No user responding Japan Specific
Busy here
No answer from user Incompatible destination
Not acceptable here
Call rejected Invalid transit network selection
Server internal error
Number changed Invalid message
Not implemented
Nonselected user clearing Mandatory info element missing Bad gateway
Destination out of order Msg type non-exist or not impl
Service unavailable
Invalid number format Message not compat with call state Decline
Facility rejected Info element non-exist or not impl
Others
Response To STATUS INQUIRY Invalid info element content
Normal unspecified Recovery on timer expiration
No circuit Protocol error
Network out of order Interworking
Temporary failure
...
8.11 SIP parameters explanation / under the object USERS:
8.11.1 SIP Device
The SIP Device is used for voice SIP calls and FAX SIP calls. The SIP Device is considered as an External
SIP user, so the features are limited (same as SIP TG)
SIP Device creation
Directory Number : Corresponds to the directory number of the SIP Device
Set Type : Select SIP device for the type of set

URL UserName : The user name corresponds to the SIP Device directory number - autofill
Ed. 12 33 TG0069
OmniPCX Enterprise
URL Domain : Corresponds to the OXE domaine name (nodename) - autofill

SIP Authentication : The user name corresponds to the SIP Device directory number autofill
External Gateway Number : Used in case of Open Touch configuration. Defines the external Gateway number to reach the OT
Gateway type : Used in case of Open Touch configuration. Defines the gateway type to reach the OT
In normal use, only the Directory Number and the set type are managed, the other parameters can
be modified only if needed
The SIP device is linked to the local SIP gateway
The local SIP gateway must be managed and is in service to be able to make and receive calls
With the current Linux OS, OXE has a limitation in handling more than 1000 data equipment if it
is connected in the same sub-network. So we need to have a seperate VLAN in between to
handle this. OXE CS must be placed under separate subnet and the IP Phones distributed over
different other subnets
All unnecessaries subscriptions must be deactivated on SIP Devices when service is not
available on OXE. Example: Voicemail notifications
8.11.2 SIP Extension (or SEPLOS)
The SIP Extension is used only for voice calls. It is considered as an Internal SIP user so it is possible to use
phone features and facilities from the OXE.
It is not necessary to manage the local SIP gateway if you want to use it. Only the proxy has to be (for
authentication)
SIP Extension creation
Directory Number : Corresponds to the directory number of the SIP Extension
Set Type : Select SIP extension for the type of set
URL UserName : The user name corresponds to the SIP Extension directory number - autofill
URL Domain : Corresponds to the OXE domain name (nodename) - autofill
SIP Authentication : The user name corresponds to the SIP Extension directory number autofill
Other SIP extension parameters
- Under /users/ IP SIP Extension:
Set Type : Type of set displayed (SIP extension or SIP device)
IP Address : IP address of the SIP equipment displayed (information retrevies from the registrar)
- Under /users/ SIP Extension Parameters:
Phone COS : Corresponds to the SIP phone class of service and not the normal phone class of service
(explanation later)
The SIP extension can be created as a business user or room user in case of hospitality. One
of the difference it that in case of business mode, the SIP extension is multiline (not
manageable) and in case of room mode , the SIP extension is monoline.
Ed. 12 34 TG0069
OmniPCX Enterprise
8.12 SIP parameters explanation / under the object SIP Extension:

Used to manage some specific phone features for SIP extension
Display UTF-8 : Used to display UTF-8 name, if the SIP phone is compatible,
- if True, the OXE will send the name in UTF-8 to the SIP Phone
- if False, the OXE will send the normal name to the SIP phone
Display call server information : Display information on the set display, for instance if the set is fowarded by using an OXE prefix
- if True, the OXE will send a SIP message MESSAGE
- if False, the OXE will not send this SIP message
The SIP phone must be compatible with the SIP messages or they will be rejected (405 message).
Keep Alive : Used to implement the keep alive mechanism between the OXE to the SIP phone, if the SIP phone
is compatible
- if True, the OXE will send an OPTION message to the SIP phone
- if False, the OXE will not send this OPTION message
The keep alive timer is managed on the IP Quality Of Service COS, assoicated to the IP domain of the SIP Extension user
(seen later)
Send NOTIFY instead of MESSAGE : Used to send the synamic state of the SEPLOS SIP message MESSAGE or with a NOTIFY
SIP message
8.13 SIP parameter explanation / under the object External Voice Mail:
Go under /Applications/ External Voice Mail
Voice Mail Dir.No : Corresponds to the directory number of the External Voice Mail.
Sub Type : - Private (default value): The via header is not used to determine the origin of incoming calls.
- Public: the via header is used to determine the origin of incoming calls when other headers do not
match.
URL UserName : Corresponds to the Voice Mail directory number.
URL Domain : Corresponds to the nodename of the OXE.
PCS IP Address : Corresponds to the IP address of the PCS to secure this external SIP Voice Mail.
SIP Authentication : Corresponds to the login used for the authentication to the external SIP voice mail
SIP Passwd : Corresponds to the password used for the authentication to the external SIP voice mail
Register On Line Number : Directory number used to access the voice mail service in record mode. This number is dialed
automatically when the 'Rec.' key is pressed on a set.
Register URL (Username) : User part of the URL used for access to the voice mail service in record mode.
Register URL (Domain) : Domain part of the URL used for access to the voice mail service in record mode.
Register Authentication : Corresponds to the login used to control access to the external voice mail service in record
mode.
Register Password : Corresponds to the password used to control access to the external voice mail service in record
mode.
External Gateway Number : Used to manage an entity (SIP Device or External Voice Mail) behind a Proxy. If different from -1, it
is used as an Outbound Proxy: outgoing calls are routed to it via its RemoteDomain (Gateway Id)
and its Outbound Proxy. Registration (REGISTER) and supervision (OPTIONS) are still configurable.
From R10.1.1: when OpenTouch is involved, its mandatory to declare a SIP External Gateway here
Subscription on registration : Used if the Subscription is done in the same time than the Registration or in two different messages.
Must be set to TRUE for some SIP External Voicemail like 8440 OT to activate MWI feature
Ed. 12 35 TG0069
OmniPCX Enterprise
8.14 SIP parameters explanation / under the object System:

Go under /System/Other System Param./SIP Parameters
Packetization times per codec : - If True , a couple of ptime/maxptime information is available for each codec.
- If False , a single couple of ptime/maxptime information is available for all codecs.
Via Header_ Inbound Calls Routing : - If False (default value): The via header is not used to determine the origin of incoming calls.
- If True: the via header is used to determine the origin of incoming calls when other headers do not
match with the RemoteDomain of an External Gateway.
Hardwareless for OTBE : NOT CURRENTLY USED From R10.1
Local resources : NOT CURRENTLY USED From R10.1
Loose Route with RegID : The possibility is offered to accept the call if route header only contains a URI with OXE_address
without user part.
- If True, INVITE without RegID in route header is re-routed to the destination corresponding to
ReqURI domain part.
- If False, INVITE is accepted. From R10.1
Reject unidentified proxy calls : As an exceptional procedure for inbound calls, if the origin of the call cannot be determined, either by
looking up the SIP dictionary, or through any other procedure (call does not comes from a SIP
External Gateway), and if the Source @IP doesnt belong to the trusted @IP list the call is either
delivered to the Call Handling on the Main Gateway, or rejected with a 403.Forbidden response.
- If it is set to True, such calls are rejected with a 403.Forbidden response.
- If it is set to False, the call is delivered to the Call Handling on the Main Gateway. From R10.1
Hotel doorcam application : In some hotels, there is a camera at the door of the suite and when somebody rings at the door, it
activates the camera and the guest can see on his SEPLOS the video of the visitor. This parameter
allows this telephone-services
- If it is set to True, if the calling party is a SIP Device or an ABC-F SIP Trunk user and the called
party is a SEPLOS or an ICE user and then if a video media is detected, the call is sent to Call
Handling From R10.1
Transfer : Refer using single step

- If True, new INVITE without Referred-By is provided
- If False, new INVITE with Referred-By is provided From R10.1
Number of SIP Trunks (UCaaS) In a UCaaS configuration, this system option replaces the lock 188 (SIP network links). It means that
the number of SIP calls to the SIP network is checked with this system option. From R11
More details in section 6.
Enhanced codec negotiation If all nodes are in Release 11 (value: Network type) or in standalone configuration (value: local type).
To deactivate renegotiation in case of transfer (value: Not available). From R11
G722 for SIP Trunking This parameter must be set to TRUE when G722 is supported by remote domain. From R11
From header for anonymous calls From J1.410.63/ K1.400.33

It can take two different values : anonymous (Default value) or SIP Trunk Group name. When the
default value is anonymous, the From header is [email protected]. If customer wants
to have the trunk group name he has to change the default value.
Private SIP transit mode Up to Release 11, all calls between OT, SIP Devices, 3rd party Application (External Voicemail, IVR)
or IP-PBX are handled by the OXE in proxy mode (no P-Alcatel-CSBU header added, 301 moved
permanently generated in some cases)
- Mixed Mode (default value), these kinds of calls are handled by the OXE Call Handling
- Full Call Handling Mode, all calls are handled by the OXE Call Handling
- Proxy or Redirect Mode, these kinds of calls are handled only by the sipmotor From R11.0.1
Go under /System/Other System Param./System Parameters
SRTP TLS offer answer mode : - If True: SRTP according to SDP offer/answer model
- If False: SRTP Oxe centralized SRTP mode
TLS signaling possible : - If True: TLS signaling allowed for SIP gateways / TLS signaling and SRTP allowed for SIP sets
- If False: TLS signaling not possible for SIP gateways / TLS signaling and SRTP not possible for
SIP
Ed. 12 36 TG0069
OmniPCX Enterprise
Accept Mu and A laws in SIP : OXE is using only in G711 the system law for all SIP calls (inbound calls), thanks to this parameter,
the OXE is able to accept the G711calls using the other law for inbound calls on external SIP
gateways only.
Go under /System/Other System Param./External Signaling Parameters
NPD for External Forward : - If -1: redirection information is sent

- If configured with NPD number used by SIP ISDN Trunk: see the calling name presentation on the
set display of called phone in case of forward
Calling Name Presentation : - If False: Calling Number is not sent

- If True: display name to external calls is sent
9. IP DOMAINS, CODECS AND PCS
9.1 IP domains rules

A SIP equipment can belong to an IP domain. According to this configuration, it is able to use some
behaviours from its IP domain (see the TC1277 for IP domain configuration and restrictions)
The first thing to know it is that a SIP equipment doesnt belong to an IP domain if its IP address is not
managed. It doesnt belong in the IP domain 0 as well (except for the SIP extension users acting like
IPtouch). In case no configuration is done, the call with an Alcatel-Lucent equipment is always an extra
domain call.
9.2 System law for PCM codec

Default behavior: the system is accepted only the PCM codec of its law. If the system is using the A law, only
PCMA will be accepted and used, PCMU will be rejected.
The following parameter must be managed:
/System/Other System Param./System Parameters/Accept Mu and A laws in SIP

False (default): only the system law is accepted
True: the two laws are accepted
9.3 Codecs on SDP (before OXE R11)

When a SIP call is done, the OXE manages the SDP according to the following information:
9.3.1 Initial offer : the offer sent in an initial INVITE
The codec list proposed in an initial SDP offer is built according to the algorithm of the outgoing SIP Trunk
Group. The outgoing SIP Trunk Group is the one managed in ARS route or Network/Routing number, NOT
the one managed on the External SIP Gateway.
This codec list is ordered taking into account calling user extra domain compression law.
Exception : if the caller is a SIP device or a SIP trunk, the codec list is in the same order as the one received
from the calling party.
SIP trunk algo must be understood as the best algorithm supported on the trunk or the higher
bandwidth consumption supported on the trunk :
Ed. 12 37 TG0069
OmniPCX Enterprise
SIP trunk algorithm : default

- The Trunk Group has low capacity. Only G729/G723 is possible.
SIP trunk algorithm : G711

- The Trunk Group supports high bandwidth calls and as a consequence low bandwidth calls
too. Both G711 and system codec (G729/G723) can be used.
Initial SDP offer content, general case (calling party is not a SIP device nor a SIP trunk).
Trunk Group compression Intra/Extra IP domain
SDP
type algorithm
Default With Compression System algorithm only (G729 for instance)
Default Without Compression System algorithm only (G729 for instance)

System algorithm (G729 for instance) in first position
G711 With Compression
and PCM (A or MU) in the second position
PCM (A or MU) in first position and system algorithm
G711 Without Compression
(G729 for instance) in the second position
9.3.1 Initial answer : the answer to an initial offer on incoming call
Pre-requisite :
The SIP equipment must at least propose one codec supported by OXE in its offer.
OXE Trunk Group used for incoming calls (managed in External SIP Gateway) must be managed
with algo=G711.
OXE always answers with one codec only :

The one proposed in a by the SIP equipment in case of mono-codec offer.
The best one in case of multicodec offer, taking into account :
- SIP equipment list order (calling party prefered codec).
- Called party extra-domain codec.
The answer may be sent in 18x and/or 200OK depending on SDP in 18x management.
OXE initial SDP answer summary (incoming trunk group algo = G711).
SIP equipment SDP Offer Intra/Extra IP domain algorithm Codec use

G729, G711 With Compression G729
G729, G711 Without Compression G729
G711, G729 With Compression G729
G711, G729 Without Compression G711
G711 With Compression G711
G711 Without Compression G711
For SEPLOS users, the OXE is acting as an IPtouch.
9.4 Codecs on SDP (from OXE R11)

When a SIP call is done, the OXE manage the SDP according to the following information:
9.4.1 Initial offer : the offer sent in an initial INVITE
From OXE R11:

The IP compression type disappears in trunk group with SIP specificity. It wont be shown in mgr menu and
will be internally initialized to G711.
In external gateways:
Ed. 12 38 TG0069
OmniPCX Enterprise
- the boolean Send only trunk algo disappears.

- a new field Type of codec negotiation is created with the following values : default, from domain,
single codec G711, single codec G729.
The codec list proposed in an initial SDP offer is built according to the IP Domain algorithm and the type of
codec negotiation value.
SIP trunking on OXE is able to deal with G722, G711, G729 and G723
The following table shows how the SDP offer is constructed for an outgoing call:
Type of codec negotiation,

Offer on INVITE Default From Domain Single codec Single codec G729
G711
Calling set
Restricted domain G729/G711 (2) G729 G711 (1) G729
Non restricted domain G711/G729 G711/G729 G711 G729
Non restricted domain and G722/G711/G729 G722/G711/G729 G722/G711 G729

allowing G722
(1): a transcoding will be necessary. Two compressors will be taken on OXE when answer is received
(2): a transcoding will be necessary if the SIP codec answer is G711
Remarks:
- G722 is still proposed at first in codec offer
- UPDATE/Re-INVITE offer is transparently relayed without codecs modifications
- For an On Hold, previous negotiated codec is used
9.4.2 Initial answer : the answer to an initial offer on incoming call
The following table shows how the SDP offer is constructed for the answer of an incoming call when OXE
receives on INVITE SDP offer (G722/G711/G729):
Type of codec negotiation,

Offer on 200 OK Default From Domain Single codec Single codec G729
G711
Calling set
Restricted domain G729 G729 G711 (1) G729
Non restricted domain G711 G711 G711 G729
Non restricted domain and G722 (2)/G711 G722 (2)/G711 G722 (2)/G711 G729
allowing G722
(1): a transcoding will be necessary. Two compressors will be taken on OXE when answer is received
(2): G722 codec is available on IPTouch EE, 80x2 series devices
Ed. 12 39 TG0069
OmniPCX Enterprise
9.5 How to manage the type of codec negotiation from OXE R11?
Thanks to this survey, you can find the good configuration for the OXE SDP offer:
1) Do all the voice endpoints support at least G729A codec?

If yes: type of codec negotiation is from domain
Else
2) Do all the voice endpoints support G711 only?
If yes: type of codec negotiation is G711 only
If no: type of codec negotiation is default
9.6 How to manage the SDP transparency override from OXE R10.1?
Thanks to this survey, you can find the good configuration for the OXE SDP offer:
1) Do all the SIP External applications support both G729 and G711?
If yes: SDP transparency override is False
Else
2) Does SIP Carrier support same codec like SIP External application?
If yes: SDP transparency override is False
If no: SDP transparency override is True
9.7 PCS
The SIP is totally operational on PCS; it is able to secure all types of SIP elements, but the connected SIP
device must be tested to ensure that it will be able to connect and work on the PCS.
In case of spatial redundancy, the nodename managed on the PCSs must be the same as the
one managed on the CPUs.
Ed. 12 40 TG0069
OmniPCX Enterprise
10. CONTENTS OF A SIP MESSAGES (GENERAL VIEW)
On the SIP messages, we can find different information. According to the type of message, the information
can change or can be adapted.
For instance, with an INVITE we can have this:
INVITE sip:[email protected]:5060;user=phone SIP/2.0

Via: SIP/2.0/UDP 172.27.142.64:5060;branch=z9hG4bK3047297329
From: "31031"<sip:[email protected]:5060;user=phone>;tag=c0a80101-17193256
To: <sip:[email protected]:5060;user=phone>
Call-ID: [email protected]
CSeq: 1 INVITE
Max-Forwards: 70
HEADER Supported: timer, P-Early-Media, replaces
Require: 100rel
Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,SUBSCRIBE,NOTIFY,UPDATE,REFER,REGISTER,INFO
Contact: <sip:[email protected]:5060;transport=udp;user=phone>
User-Agent: THOMSON ST2030 hw5 fw2.72 00-1F-9F-16-4F-03
Allow-Events: refer,dialog,message-summary,check-sync,talk,hold
Content-Length: 203
v=0
o=MxSIP 4219058434975324735 4219058434975324736 IN IP4 172.27.142.64
s=SIP Call
c=IN IP4 172.27.142.64
t=0 0
m=audio 6000 RTP/AVP 8 0 18 101
a=rtpmap:8 PCMA/8000
BODY a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:18 annexb=no
a=fmtp:101 0-15
a=ptime:20
a=mptime:20 20 30 20 -
a=sendrecv
Between the Header and the Body, you have everytime an empty line
10.1 The HEADER

The header contains the information to establish a SIP dialog between the UAC and the UAS.
Here the main information given:
- The Request-URI:
INVITE sip:[email protected]:5060;user=phone SIP/2.0
The initial Request-URI of the message SHOULD be set to the value of the URI in the To field, except if the
recipient (To field) is forwarded.
Request-URI: forward destination
To: forwarded set
- The From:
From: "31001"<sip:[email protected]:5060;user=phone>;tag=c0a80101-17193256
Ed. 12 41 TG0069
OmniPCX Enterprise
The From header field indicates the logical identity of the initiator of the request.
- The To:
To: <sip:[email protected]:5060;user=phone>
The To header field first and foremost specifies the desired "logical" recipient of the request.
- The Call-ID:
The Call-ID header field acts as a unique identifier to group together a series of messages. It MUST be the
same for all requests and responses sent by either UA in a dialog.
- The CSeq:
CSeq: 1 INVITE
A CSeq header field in a request contains a single decimal sequence number and the request method. The
CSeq header field serves to order transactions within a dialog, to provide a means to uniquely identify
transactions, and to differentiate between new requests and request retransmissions. Two CSeq header
fields are considered equal if the sequence number and the request method are identical.
- The Max-Forwards:
Max-Forwards: 70
The Max-Forwards header field serves to limit the number of hops a request can transit on the way to its
destination.
- The Via:
Via: SIP/2.0/UDP 172.27.142.64:5060;branch=z9hG4bK3047297329
The Via header field indicates the transport used for the transaction and identifies the location where the
response is to be sent.
- The Contact:
Contact: <sip:[email protected]:5060;transport=udp;user=phone>
The Contact header field provides a SIP URI that can be used to contact that specific instance of the UA for
subsequent requests. Contact header field MUST be present and contain exactly one SIP URI in any request
that can result in the establishment of a dialog.
- The Supported and/or Require
Supported: timer, P-Early-Media, replaces
If the UAC supports (requires) extensions to SIP that can be applied by the server to the response.
o If the UAS receives a supported option tags, it is able to use them if needed.
o If the UAS receives a required option tags, it must use them or reject the request
Other information can appear on header according to the SIP equipment type, to know the meaning of them,
check the SIP RFCs
Ed. 12 42 TG0069
OmniPCX Enterprise
10.2 The BODY

The body contains the message or information used to openan RTP connection (codec, IP address, etc)
v=0
o=MxSIP 4219058434975324735 4219058434975324736 IN IP4 172.27.142.64
s=SIP Call
c=IN IP4 172.27.142.64
t=0 0
m=audio 6000 RTP/AVP 8 0 9 18 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:9 G722/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=fmtp:101 0-15
a=ptime:20
a=mptime:20 20 20 20 20 -
a=sendrecv
SDP session description consists of session-level sections.
Each session-level starts by a letter, corresponding to an information for RTP channel negociation (in voice
cases)
In that example, we have the following information given:
v= : corresponds to SDP version
o= : corresponds to the originator of the session

o MxSIP = username
o 4219058434975324735 = sess-id, forms a globally unique identifier for the session
o 4219058434975324736 = sess-version, is a version number for this session description
(increased in case of SDP modification)
o IN = Internet connection type (thru IP network)
o IP4 = IP V4 is used for IP addressing
o 172.27.142.64 = IP address of the SIP equipment (for RTP connection)
s= : corresponds to the session name
c= : corresponds to the connection data

o IN = Internet connection type (thru IP network)
o IP4 = IP V4 is used for IP addressing
o 172.27.142.64 = IP address of the SIP equipment (for RTP connection)
t= : corresponds to the start and stop times for this session (t= <start time> <stop time>)
o t= 0 0 means that the timing is not used in that case
o This field is mandatory on SDP
m= : corresponds to the media description

o audio = media type (audio, video, text,)
o 6000 = port number used to sent the media stream
o RTP/AVP = transport protocol, in that case, it is RTP
o 8 0 9 18 101 = payloads (codecs)
a= : corresponds to SDP attributes

o a=rtpmap:8 PCMA/8000 = codec PCMA available on this SIP equipment
o a=rtpmap:0 PCMU/8000 = codec PCMU available on this SIP equipment
o
Ed. 12 43 TG0069
OmniPCX Enterprise
o a=rtpmap:101 telephone-event/8000 = payload for DTMF

o a=fmtp:18 annexb=no = no VAD available for this call (annexb)
o a=ptime:20 = packet time (framing)
o a=mptime:20 = maximum ptime accepted
o a=sendrecv = direction of the call, in that case both directions
The SDP is generated according to the SIP equipment. Each SDP is different for each type of SIP equipment
and type of SIP call.
11. EXAMPLES OF COMMON SIP FLOWS
11.1 Registration
In an OmniPCX Enterprise context, the call server (CS) takes the role of the SIP registrar. Registration is
necessary to bind a given SIP URL to a physical address. External SIP sets register on the registrar with a
SIP REGISTER request.
Note that there may be a short delay of several seconds between the time the REGISTER message is
received and the time the registrar database is updated.
Without authentication:
31026 . . . . . OXE
(SIP set) (Registrar)
IP=172.27.141.210 FQDN=oxe-ov.alcatel.fr
| |
| (1) REGISTER |
|------------------->|
| (2) 200 OK |
|<-------------------|
----------------------utf8-----------------------
REGISTER sip:oxe-ov.alcatel.fr SIP/2.0
Via: SIP/2.0/UDP 172.27.141.210:22362;branch=z9hG4bK-d87543-826b1a28d80c8c6b-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:[email protected]:22362;rinstance=70dae25b3c1e2541>
To: "31026"<sip:[email protected]>
From: "31026"<sip:[email protected]>;tag=e2704074
Call-ID: MDMxYzVkZjBiNWY0NTlmODAwMTk2MTdkNzczZjkwOTM.
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
User-Agent: SIP Phone
Content-Length: 0
-------------------------------------------------
o The To header field contains the address of record (SIP URI) whose registration is to be
created. In the example oxe-ov.alcatel.fr is the domain (OXE main IP address or FQDN)
and 31026 the user name.
o The Contact header field contains the physical address (IP address and port) of the record
whose registration is to be created. In the example it is 172.27.141.210:22362. Note that
if port number would not have been specified it would have been taken as 5060 by default.
If any other port number than 5060 is used, it must have to be specified (here 22362).
o The Expires field corresponds to the maximum time of registration on the REGISTRAR, the
SIP equipment msut send a new REGISTER message to stay on, if not, it will be removed
from it.
The registrar answers with a 200 OK response upon successful registration.
Ed. 12 44 TG0069
OmniPCX Enterprise
With authentication:
31026 . . . . . OXE
| |
|(1) REGISTER |
|-------------------->|
|(2) 401 Unauthorized |
|<--------------------|
|(3) REGISTER |
|-------------------->|
|(4) 200 OK |
|<--------------------|
The first REGISTER is sent without the authentication parameters and the OXE sends a 401 Unauthorized
message to ask the SIP equipment for the authentication parameters
----------------------utf8-----------------------
SIP/2.0 401 Unauthorized
WWW-Authenticate: Digest qop="auth",nonce="a4c9e550459f63fd80764dc69609c482",realm="oxe-ov"
To: "31026" <sip:[email protected]>;tag=da389f6e785d72b8910a0f2310d68fcc
From: "31026" <sip:[email protected]>;tag=e2704074
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 172.27.141.210:22362;received=172.27.141.210;branch=z9hG4bK-d87543-826b1a28d80c8c6b-
1--d87543-;rport=22362
Content-Length: 0
-------------------------------------------------
o The WWW-Authenticate field corresponds to the OXE information about authentication:The

information Digest corresponds to the challenge type
o The information qop corresponds to the "quality of protection" values supported by the
server. The value "auth" indicates authentication.
o The information nonce corresponds to control the integrity of the authentication information
received by the SIP equipment.
o The information realm corresponds to the SIP authentication domain, only one can be
managed on the OXE.
The Register with the authentication information :
----------------------utf8-----------------------
Via: SIP/2.0/UDP 172.27.141.210:22362;branch=z9hG4bK-d87543-e14134135a40db7d-1--d87543-;rport
Max-Forwards: 70
CSeq: 2 REGISTER
Expires: 3600
Authorization: Digest username="31026",realm="oxe-
ov",nonce="a4c9e550459f63fd80764dc69609c482",uri="sip:oxe-ov.alcatel.fr",response="dde0d45f751288517
8806dc1b4321b19",cnonce="e53a2b8923348db7",nc=00000001,qop=auth,algorithm=MD5
Content-Length: 0
-------------------------------------------------
Ed. 12 45 TG0069
OmniPCX Enterprise
When the registration timer is too brief
31026 . . . . . . . . . . OXE
| |
|(1) REGISTER |
|------------------------------>|
|(2) 423 Registration Too Brief |
|<------------------------------|
|(3) REGISTER |
|------------------------------>|
|(4) 200 OK |
|<------------------------------|
When the expires is too small compares to the OXE one, the OXE returns the message 423 Registration
Too Brief, with its timer, in that case, the SIP equipment sends a new REGISTER with the timer received.
----------------------utf8-----------------------
Max-Forwards: 70
CSeq: 1 REGISTER
Expires: 60
-------------------------------------------------
o The Expires value is equal to 60 in that case, and the minimum value managed on the
OXE is 1800
----------------------utf8-----------------------
SIP/2.0 423 Registration Too Brief
Min-Expires: 1800
To: "31026"<sip:[email protected]>;tag=85d8c7828811c12691305052d6ef7f9a
CSeq: 1 REGISTER
Content-Length: 0
-------------------------------------------------
o The information Min-Expires correponds to the minimun registration timer value of the
OXE (manage on the REGISTRAR object)
----------------------utf8-----------------------
Max-Forwards: 70
CSeq: 1 REGISTER
Expires: 1800
Content-Length: 0
-------------------------------------------------
o The new REGISTER received on the OXE has the value 1800 (the one from the message
423)
Ed. 12 46 TG0069
OmniPCX Enterprise
11.2 De-registration
31026 . . . . . OXE
| |
| (1) REGISTER |
|------------------->|
| (2) 200 OK |
|<-------------------|
When a SIP equipment is stopped, before it has to send a REGISTER message to be removed from the
OXE REGISTRAR, for this, it has to send a REGISTER with an Expires = 0
----------------------utf8-----------------------
Max-Forwards: 70
CSeq: 1 REGISTER
Expires: 0
Content-Length: 0
-------------------------------------------------
o On the REGISTER, we have the Expires = 0 and the Contact, this contact is used by the
REGISTRAR to know which physical IP address to remove for this URI (in case of forking).
o If the Contact is received with a *, the REGISTRAR must removed all the Contact
associated.
In case of duplication, when the Main CPU receives a REGISTER, the SIPMOTOR sends this REGISTER to
the Stand-BY CPU with the next message:
----------------------utf8-----------------------
Via: SIP/2.0/UDP 172.27.141.210:22362;received=172.27.141.210;branch=z9hG4bK-d87543-e14134135a40db7d-
1--d87543-;rport=22362
Max-Forwards: 70
Contact: <sip:[email protected]:22362;rinstance=70dae25b3c1e2541>;expires=3600
To: "31026" <sip:[email protected]>
From: "31026" <sip:[email protected]>;tag=e2704074
CSeq: 2 REGISTER
Expires: 3600
Allow: INVITE
Allow: ACK
Allow: CANCEL
Allow: OPTIONS
Allow: BYE
Allow: REFER
Allow: NOTIFY
Allow: MESSAGE
Allow: SUBSCRIBE
Allow: INFO
Content-Length: 0
User-Agent: Alcatel-main Registrar
-------------------------------------------------
Ed. 12 47 TG0069
OmniPCX Enterprise
11.3 Simple call establishement

The following diagram shows the messages sent from a SIP equipment to an OXE user (Not a SIP one)
UAC UAS
31026 OXE 31004
(caller). . . . . . . (proxy). . . . . . . . . . . . . .(callee)
| | |
| INVITE | |
|-------------------->| |
| 100 Trying | |
|<--------------------| |
| | Process to contact the callee |
| |<------------------------------->|
| 180 Ringing | |
|<--------------------| |
| 200 OK | |
|<--------------------| |
| ACK | |
|-------------------->| |
| Media Session |
|<=====================================================>|
| BYE | |
|-------------------->| |
| 200 OK | |
|<--------------------| |
1) The SIP equipment sends an INVITE to the OXE
Mon Jun 25 11:10:17 2012 RECEIVE MESSAGE FROM NETWORK (172.27.141.210:63016 [UDP])
----------------------utf8-----------------------
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 172.27.141.210:63016;branch=z9hG4bK-d87543-4c3f8f26d532b437-1--d87543-;rport
Max-Forwards: 70
From: "31026"<sip:[email protected]>;tag=e9708b0f
Call-ID: MzI0MjQ4MmQ5NjMzZTVmZTlmYTE5NTVhMGNiZWI0ODQ.
CSeq: 1 INVITE
Content-Length: 417
v=0
o=- 6 2 IN IP4 172.27.141.210
s= SIP Phone
c=IN IP4 172.27.141.210
t=0 0
m=audio 52694 RTP/AVP 18 101
a=fmtp:18 annexb=no
a=fmtp:101 0-15
-------------------------------------------------
o The INVITE can contain SDP or not. If there is no SDP, the ACK (after the 200ok) sent must
contain the SDP information
2) The SIP equipment receives a provisional answer from the OXE (100 Trying)
o The 100 Trying is a provisional message sent by the OXE, this message is generated by the
SIPMOTOR directly, it can be considered as an automatic answer of an INVITE to avoid
retransmission from UAC.
Ed. 12 48 TG0069
OmniPCX Enterprise
3) The SIP equipment receives a provisional answer from the OXE (180 Ringing or 183 Session Progress)
Mon Jun 25 11:10:18 2012 SEND MESSAGE TO NETWORK (172.27.141.210:63016 [UDP]) (BUFF LEN = 815)
----------------------utf8-----------------------
SIP/2.0 180 Ringing
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE
Contact: sip:oxe-ov.alcatel.fr
User-Agent: OmniPCX Enterprise R10.0 j1.410.45
To: "31004" <sip:[email protected]>;tag=bb28096d41c595340f577a538bf30d54
From: "31026" <sip:[email protected]>;tag=e9708b0f
CSeq: 1 INVITE
Via: SIP/2.0/UDP 172.27.141.210:63016;received=172.27.141.210;branch=z9hG4bK-d87543-88163a3aa534591a-
1--d87543-;rport=63016
Content-Length: 0
-------------------------------------------------
o The 180 Ringing (or 183 Progress Session) is a provisional message sent by the OXE, this
message is used to inform the caller that the remote party is ringing. This message can contain
SDP to provide the Ring back tone RBT). If theres no SDP, the RBT must be played locally on
the system that initiated the call.
4) The SIP equipment receives a 200ok answer from the OXE

----------------------utf8-----------------------
SIP/2.0 200 OK
Supported: replaces,timer,path,100rel
Session-Expires: 1800;refresher=uas
P-Asserted-Identity: "IPtouch 172.27.142.64" <sip:[email protected];user=phone>
To: "31004" <sip:[email protected]>;tag=bb28096d41c595340f577a538bf30d54
From: "31026" <sip:[email protected]>;tag=e9708b0f
CSeq: 1 INVITE
Via: SIP/2.0/UDP 172.27.141.210:63016;received=172.27.141.210;branch=z9hG4bK-d87543-88163a3aa534591a-
1--d87543-;rport=63016
Content-Length: 242
v=0
o=OXE 1340615417 1340615418 IN IP4 172.27.141.151
s=abs
c=IN IP4 172.27.142.64
t=0 0
a=sendrecv
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=ptime:20
a=maxptime:40
-------------------------------------------------
o The 200ok is used to open the SIP dialog (in that case), when the called party hang up, the OXE
sends this 200ok with a SDP to provide the RTP information for connection.
Ed. 12 49 TG0069
OmniPCX Enterprise
6) The SIP equipment sends a ACK to the OXE

----------------------utf8-----------------------
ACK sip:oxe-ov.alcatel.fr SIP/2.0
Via: SIP/2.0/UDP 172.27.141.210:63016;branch=z9hG4bK-d87543-342bae0b06436266-1--d87543-;rport
Max-Forwards: 70
To: "31004"<sip:[email protected]>;tag=bb28096d41c595340f577a538bf30d54
From: "31026"<sip:[email protected]>;tag=e9708b0f
CSeq: 1 ACK
Content-Length: 0
-------------------------------------------------
o The ACK is used to confirm the dialog. The ACK must contain a SDP if there is no SDP on the
INVITE
7) The SIP equipment can send or receive a BYE, when the call is stopped
o The BYE is used to stop the dialog
8) The SIP equipment can send or receive a 200ok, to confirm the BYE
Ed. 12 50 TG0069
OmniPCX Enterprise
12. TROUBLESHOOTING
This section provides step-by-step instructions and troubleshooting actions when you run into trouble.
When a SIP issue is present on the OXE, it is necessary to find the cause of this trouble.
To find the cause of the trouble, it is necessary to investigate.
Regarding the issue, different ways of investigation are possible.
SIP call not possible

Voice problem
Fax transmission problem
DTMF issue
SIPMOTOR crash
...
Before to start, here are some explainations about the SIPMOTOR functionning and the traces in case of SIP
calls.
12.1 SIPMOTOR processes

The first step is to check if all the SIPMOTOR processes are running well on the OXE.
For this, you can use the command ps -edf | grep sip.

root 2202 801 0 2011 ? 00:00:00 [#sipmotor]
root 2203 2202 0 2011 ? 00:00:00 [sipmotor_tcl]
root 2204 2202 0 2011 ? 00:00:00 [sipmotor]
root 2205 2202 0 2011 ? 00:00:00 [sipmotor_dump]
root 2206 2202 0 2011 ? 00:00:00 [sipmotor_presen]
In normal functionning, the system displays the sipmotor processes. There are 5 processes and the owner of
the processes is root (before the R9.1, the owner was mtcl). According to the OXE release/version, the
number of processes can be different.
If the command gives you this result:

root 2033 822 0 Feb22 ? 00:00:00 /DHS3bin/servers/sipmotor
root 2139 2033 0 Feb22 ? 00:00:07 /DHS3bin/servers/sipmotor
mtcl 11942 10204 0 09:40 pts/0 00:00:00 grep sip
In that case, you dont have the good number of processes, you can make a double bascul or a reboot the
CPU must be performed (shutdown -r 0).
If you run the command, and you get the following result:

root 2033 822 0 Feb22 ? 00:00:00 [#sipmotor <defunct>]
mtcl 12400 10204 0 09:53 pts/0 00:00:00 grep sip
Ed. 12 51 TG0069
OmniPCX Enterprise
In that case, the SIPMOTOR processes have been restarded (automatically or manually), but the
configuration of the SIP is not well done, so the configuration must be checked:
- The configuration of the SIP trunk group, used on the local SIP gateway (node number,
etc).
- The configuration of the local SIP gateway is well done (good SIP trunk group used, etc).
Remark: After modifications, the OXE must be rebooted (shutdown -r 0).
12.2 SIPMOTOR memory used

When a problem is present on SIP, it is important to check the use of memory for the SIPMOTOR.
For this, run the command top -p PID of the SIPMOTOR.
10:35am up 3 days, 19:49, 1 user, load average: 9.00, 9.00, 9.00
1 processes: 1 sleeping, 0 running, 0 zombie, 0 stopped
CPU states: 0.0% user, 0.0% system, 0.0% nice, 100.0% idle
Mem: 901304K av, 275124K used, 626180K free, 0K shrd, 4752K buff
Swap: 1052216K av, 2180K used, 1050036K free 177596K cached
PID USER CLS PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
27956 root FIFO 99 -12 3996 3996 3616 S.< 0.0 0.4 0:00 #sipmotor
The information to check are the %CPU and %MEM:

- If they are increasing when the traffic is more and more higher and decreasing when the
traffic is going down, it seems that there is no issue present about memory leak.
- If they are increasing continously, even if there is no traffic, in that case a problem is
present, and a SR must be opened for analyse.
When memory leak is present, swap partition incidents are also generated. If the following message is
present, check with the command top to see if the SIPMOTOR is using too much memory.
20/03/12 15:15:24 000002M|---/--/-/---|=2:2071=Swap partition 24 per cent full
12.3 Check the SYSTEM and SIPMOTOR backtraces/alarms
12.3.1 Backtraces
excvisu
The excvisu can be used to see if system backtraces have been generated by the OXE.
To know if the backtrace is about SIP, check the following information:
- SIPM, it means that the backtrace is on the SIPMOTOR itself.

==============================
There is a new exception. Its address is : 0XBFFFF118 in SIPM. Monitel time : 024283. Date : Tue Apr
6 10:46:40 2010
Application-exception no 11 in SIPM, PC=0xbffff118:3221221656 --> _end
* SIPM Backtrace: 0x081631c8:135672264 --> CResponse::create
* SIPM Backtrace: 0x08185ce0:135814368 --> CTransProceedingState::createResponse
* SIPM Backtrace: 0x08152c09:135605257 --> CTransaction::createResponse
* SIPM Backtrace: 0x0814d3bf:135582655 --> CDialog::createResponse
* SIPM Backtrace: 0x0816ab94:135703444 --> CCall::makeGenericResponse
* SIPM Backtrace: 0x080e8f8b:135171979 --> CMotorCall::makeResponse
* SIPM Backtrace: 0x080e642e:135160878 --> CMotorCall::emitServerFailureMessage
- Backtrace for SIP Extension, the subtype information contains SIP_EXTENSION

==============================
There is a new exception. Its address is : 0X092EEAA3. Monitel time : 1961696. D
ate : Thu Feb 21 18:45:46 2008
Applicative-Error-Backtrace, thread 1371, PC=0x092eeaa3:154069667, eqt=1380, ser
v=0 --> Kb_Interro
Eqt type=POS_NUM, cr=4, cpl=0, der_us=0, term=12, subtype = SIP_EXTENSION
* Backtrace: 0x082f9c8e:137337998 EBP 0x01856e94 --> egzis_li
Ed.* 12
Backtrace: 0x08ae2b6b:145632107 EBP 0x01856ea852--> testprio TG0069
OmniPCX Enterprise
- If the address start by cr=19 the backtrace can be linked to the SIP Trunk Group, the cr=19
corresponds to the virtual shelf for the IP-Link, so the Backtrace could be for another feature
using the IP-Link, use the command trkvisu to see if the position (cr + cpl + term)
corresponds to the SIP Trunk Group.
==============================
There is a new exception. Its address is : 0X093C1E26. Monitel time : 250434. Date : Tue Mar 20
09:18:48 2012
Application-exception no 5, thd 1176, PC=0x093c1e26:154934822, eqt=13517, serv=0 --> __CHECK__
Eqt type=JONCT, cr=19, cpl=0, der_us=0, term=2
* Backtrace: 0x08333369:137573225 EBP 0x01826db8 --> nuphmult
* Backtrace: 0x08990328:144245544 EBP 0x01826ddc --> process_ccbs_exec_poss
* Backtrace: 0x08999135:144281909 EBP 0x01826e30 --> analyse_facilite_abc
* Backtrace: 0x08999a05:144284165 EBP 0x01826e3c --> analyse_facilite
* Backtrace: 0x087fc81d:142592029 EBP 0x01826e4c --> arr_ipns
* Backtrace: 0x08836851:142829649 EBP 0x01826e7c --> sui_arr_q931
* Backtrace: 0x08836b09:142830345 EBP 0x01826eac --> arr_q931
sipmotor.crash
Under /tmpd, there is a file called sipmotor.crash containing the SIPMOTOR crash information (file
includes on the Infocollect).
(1)OXE> more /tmpd/sipmotor.crash

sipmotor.crash generated at Tue Oct 19 09:15:42 2010
1287472542 -> [CMotorCallManager::insertCallwithEqt] CMotorCall 1911 inserted.4NzQyZjY2NTI2ZT
1287472542 -> [quoteString] => "31017"onse]Trying to find the right dialogte = Terminated, cu
1287472542 -> 1186[CMotorCall::inviteBuildFromAssertedId] no P_Asserted_Identity c33435cb1ed7
1287472542 -> 1186[CMotorCall::setFilterUsedMode] To be traced = 0undterminated reason : None
If the sipmotor.crash file increase after SIP calls, to see which calls are causing this, make SIPMOTOR
traces, all the information present in this file, are taken from the SIPMOTOR, and seen on the traces.
12.3.2 Alarms
On the OXE, some SIP incidents can be generated. Heres the explanation of each one.
5800: X SIP trunk group put into service.

This incident is used to inform that the SIP trunk group X is put in service.
5801: X SIP trunk group put out of service.

This incident is used to inform that the SIP trunk group X is put out of service.
If the trunk group is automatically put out of service by the OXE (without human action) open a SR for
analysis.
5812: SIP external gateway Y is in service.

This incident is used to inform that the SIP gateway Y is in service.
5813: SIP external gateway Y is out of service.

This incident is used to inform that the SIP external gateway Y is put out of service.
If the external SIP gateway is automatically put out of service by the OXE (without human action) open a SR
for analysis.
The state of the SIP Trunk Group and the external SIP gateway are linked:
- If the SIP Trunk Group associated to the SIP external gateway is out of service, the SIP
external gateway is out of service too.
Ed. 12 53 TG0069
OmniPCX Enterprise
- If the external SIP gateway is out of service, the SIP trunk group associated is out of service
also, except if this SIP Trunk Group is associated to another external SIP gateway which is
in service.
- If all the external SIP gateway associated to one SIP Trunk Group are out of service, the SIP
Trunk group will be out of service.
5814: Critical failure in SIP component.

5815: Major failure in SIP component.
5816: Minor failure in SIP component.
These 3 incidents give an information about a problem during SIP exchanges (Registrations, Calls, etc...).
To get more information about thes incidents, go under /tmpd/ and open the sipalarm files.
(1)cpua_ov> ll sipal*
-rw-rw-rw- 1 root tel 15658 Feb 23 09:54 sipalarm.log
-rw-rw-rw- 1 root root 20456 Nov 10 11:48 sipalarm1.log
-rw-rw-rw- 1 root tel 20529 Nov 10 12:30 sipalarm2.log
-rw-rw-rw- 1 root tel 20529 Nov 10 13:28 sipalarm3.log
-rw-rw-rw- 1 root root 20553 Nov 2 09:17 sipalarm4.log
-rw-rw-rw- 1 root root 20553 Oct 30 15:29 sipalarm5.log
The sipalarm.log file corresponds to the current one.
To make the link between the incident and an entrie in the sipalarm file, check the date and time of the
incident with incvisu:
01/14/11 15:46:02 000001M|---/--/-/---|=2:5816=Minor failure in SIP component
then check in the sipalam file the entry at that time:
> 01/14/11 - 15:46:02 Minor alarm

[receiveInviteEvent] Call: eqt: 1674 INITIAL_STATE failed to emit an Invite message.
In that case, the SIPMOTOR was not able to send an INVITE (lake of licenses for instance).
When the incidents 5814, 5815 and 5816 are generated and if you have some problems on the OXE, a SR
can be opened with the information from the command incvisu and the sipalarm files (or send the
Infocollect).
Ed. 12 54 TG0069
OmniPCX Enterprise
12.4 SIP traces

The OXE has different levels of traces to get information from the different elements (SIPMOTOR, Call
handling, IP).
The traces can be run on the Main CPU and on the Stand-By CPU.
12.4.1 SIPMOTOR traces
The SIPMOTOR traces are used to make traces at the sipmotor level. The motortrace command can be
used to set the level of trace you need.
motortrace (v5.2.0) verbosity = 00000000

Correct usage is:
motortrace trace-level To set the current trace level.
motortrace +T_TRACE To add a single level to the current trace.
motortrace -T_TRACE To remove a single level to the current trace.
T_MOTOR, T_SIP, T_PKT_IN, T_PKT_OUT, T_IPC_IN, T_IPC_OUT, T_INTERNAL_DESTR,

T_LOG, T_DEBUG, T_FW, T_DB, T_US, T_MOTOR_TEST, T_TRANSPORT, T_ADNS
trace-level :
0 : No trace (only Alarm)
1 : Basic trace (T_PKT_IN|T_PKT_OUT|T_IPC_IN|T_IPC_OUT)
2 : Medium trace (T_MOTOR|T_SIP|T_PKT_IN|T_PKT_OUT|T_IPC_IN|T_IPC_OUT)
3 : All traces
4 : Medium trace dupli (T_MOTOR_TEST|T_SIP|T_PKT_IN|T_PKT_OUT|T_IPC_IN|T_IPC_OUT)

5 : All traces + dupli
6 : All traces + T_TRANSPORT + T_ADNS
7 : All traces + T_INTERNAL_STRUCT
8 : Medium trace options (T_MOTOR|T_SIP|T_PKT_IN|T_PKT_OUT|T_IPC_IN|T_IPC_OUT|T_OPTIONS_OPTIM)
9 : All traces + options
c : Configuration
Traces will be directed to the window, where traced is executed (TL).
Current level of trace is:
sipmotor trace-level 0 (No trace).
The trace-level is the most used options for motortrace traces, the other are mostly used by the R&D (if
needed).
According to the level of traces, the information given are different.
o select 0 to get no SIP traces. Only the alarms are displayed

o select 1 to get only the SIP messages and the information given by the Call Handling
o select 2 to get more information given. Compared to the level 1, we can see for instance the
SIPMOTOR checking the external SIP gateway associated to the INVITE received.
o select 3 to get all the SIP traces. This level is the most used.
o select 4 to get the level 2 traces + the duplication information (SIP exchanges between the
Main and the Stand-By CPUs)
o select 5 to get the level 3 traces + the duplication information (SIP exchanges between the
Main and the Stand-By CPUs)
o select 6 to get all the traces + the transport trace (network) + the DNS information
o select 7 to get all the traces + the internal structure of SIP in SIPMOTOR
o select 8 to get the level 2 traces + options
o select 9 to get all the traces + all options
When you increase the level for the traces, you also increase the size of the traces.
Ed. 12 55 TG0069
OmniPCX Enterprise
The command traced is used to output the traces. Some options are possibles:
If you use traced &, the trace is running in background.
If you use traced >/tmpd/name_of_the_file.log, the results of the traces is put in a file.
If you use traced -1 <file name> -s <files size> -f <number of files> -d, to make rotating trace.
Example of rotating traces command usage: traced -1 /tmpd/traced -s 10000000 -f 50 -d
o the files traced-00, traced-01, etc are saved in /tmpd
o file size is 10000000 i.e. 10 MB
o number of files is 50, i.e. traced-00 (newest) to traced-49 (oldest); when the limit is reached,
the oldest file is erased, tracd-48 is renamed traced-49,etc and the new traces are put in
traced-00
o -d: process running as a daemon (background task)
(1)OXE> motortrace 3
motortrace (v5.2.0) verbosity = 0037b524
sipmotor trace-level set 3 (All traces).
(1)OXE> traced
** UNIX-trace-daemon started ... (static user group No 1) **
traced started ...
Make a CTRL + C to stop the trace or killall traced when the trace is running in background.
The level of traces must be put back motortrace 0 after traces are taken to avoid memory leak.
If for some reason there is no output/display with traced, use sipdump option 1 to unfreeze
this situation
More details about sipdump command on 12.5.6
o The option c can be used to display all the SIP configuration (local)
(1)OXE> motortrace c
motortrace (v5.2.0) verbosity = 0037b524
sipmotor trace-level set c (data dump).
Proxy parameters.
=================
sip stack version 4.0.006.022
initial_timeout 500
timer_t2 4000
recursion 0
min_auth_method 0 NONE=0 DIGEST=2
auth_realm cpua
sipDnsTimerPrimSecond 5000
onlyAuthIncomingCalls 1
quarantine and trusted addresses:
nb_msg_by_period 25
period 3
framework_quarantine_period 1800
Gateway parameters.
===================
url_install 172.27.141.151
url_gw
url_hostname oxe-ov
num_ss_reseau 1
num_faisc 10
proxy_address not used
DNS_localDomName alcatel.fr
DNS_type 0 dnsa=0, dnssrv=1
DNS_primaire Unused
DNS_secondaire Unused
prack_required 0
out_proxy 0 AUCUN=0 INTEGRE=1 EXTERNE=2
proxy_port 5060
proxy_transport 1 TCP=0 UDP=1
sipSubsMinDuration 1800
sipSubsMaxDuration 86400
sipSessionTimer 1800
sipMinSessionTimer 900
SessionTimerMethod 1 re-invite=0, update=1
Ed. 12 56 TG0069
...
OmniPCX Enterprise
12.4.2 Call Handling traces
Call Handling traces can be provided in case of issue. There is a permanent link between the Call Handling
and the SIPMOTOR, so the issue may be found in the the Call Handling traces and not in the SIPMOTOR
traces.
The SIPMOTOR traces and the Call Handling traces must be done simultaneously.
Here is the basic Call Handling trace commands done on the OXE.
(1)OXE> tuner km
(1)OXE> tuner all=off
(1)OXE> tuner clear-traces
(1)OXE> trc i
+--------+-------+--------+--------+---------+---------+----------+------+
| filter | desti | src_id | cr_nbr | cpl_nbr | us_term | term_nbr | type |
+--------+-------+--------+--------+---------+---------+----------+------+
| 0 | | | | | | | |
| 1 | | | | | | | |
| 2 | | | | | | | |
| 3 | | | | | | | |
| 4 | | | | | | | |
| 5 | | | | | | | |
| 6 | | | | | | | |
| 7 | | | | | | | |
+--------+-------+--------+--------+---------+---------+----------+------+
(1)OXE> tuner +cpu +cpl +at +time hybrid=on
(1)OXE> actdbg all=off
Thu Feb 24 10:41:42 CET 2011
(1)OXE> actdbg sip=on
Thu Feb 24 10:41:52 CET 2011
(1)OXE> mtracer -a
Traces Analyser activated
mtracer started ...

(858432:000001) MTRACER host (172.27.141.149, OXE), version: R9.1-i1.605-23-fr-c0
Depending on theMTRACER
(858432:000001) issue, itnum:
is possible to add
002, time: options for10:42:16,
2011/02/24 traces. Forloss:
instance,
0% if you are not
able to dial an
ARS prefix from a SIP device, you can add ars=on in the actdbg command line. The Call Handling traces
must be adapted to the issue.
Here is an example of trace asked by R&D:

(1)OXE> tuner km
(1)OXE> tuner clear-traces
(1)OXE> tuner all=off
(1)OXE> trc init
(1)OXE> actdbg all=off
(1)OXE> tuner +at +tr +xtr +s
(1)OXE> tuner +cpu +cpl
(1)OXE> tuner hybrid=on
(1)OXE> actdbg sip=on csip=on fct=on isdn=on abcf=on ext=on rtp=on cnx=on comp=on voip=on ccdn=on
cstarout=on
(1)OXE> mtracer -a -u -g
Three actdbg options are linked to SIP:

sip, corresponding to sip (globals SIP traces).
csip, corresponding to the SEPLOS terminals.
nsip, corresponding to NOE-SIP terminals
Ed. 12 57 TG0069
OmniPCX Enterprise
12.4.3 Tcpdump / Network traces
The tcpdump or network traces can be used to check if the problem is from the network or the network layer
of the CPU. Tcpdump must be run under root account.
The network traces are very usefull when you have issue about one way call, DTMF, FAX, etc
The tcpdump or network traces must be done simultaneously with the SIPMOTOR and the Call
Handling traces.
(1)OXE> su root
Password:
[root@OXE tmpd]# tcpdump -s 2000 -w trace.cap

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 2000 bytes
Running the tcpdump with the option -s 2000 and the option -w trace.cap is used to be able to open this
trace with wireshark (http://www.wireshark.org/).
Rotating traces can be used with the following syntax:

[root@OXE tmpd]# tcpdump -C 10 -w /tmpd/mytcpdump.cap -W 10 -s 2000 &
-C corresponds to the size of the file (10 corresponds to 10 Megabytes)

-W corresponds to the number of files
More options are available.
Ed. 12 58 TG0069
OmniPCX Enterprise
12.5 Maintenance commands

This chapter explains all the SIP maintenance commands available on OXE.
12.5.1 sip
=====================================================================
| T O O L S A V A I L A B L E F O R S I P P U R P O S E |
=====================================================================
trkstat : Shows the trunks states in a trunk group

trkvisu : Shows the trunks parameters in a trunk group
sipacces : Shows the SIP trunk group numbers and the related accesses
sipgateway : Shows the main SIP gateway parameters

sipdump : Shows the main SIP gateway internal resources
sipextgw : Shows the external SIP gateways parameters

sippool : Shows the external SIP gateways membership of pools
sipdict : Shows the SIP dictionnary records

sipauth : Shows the SIP authentification records
sipregister : Shows the SIP end points IP address registered
csipsets : Shows the list of configured SIP extension

csipview com : Shows the list of SIP extension in communication
csiprestart : Reset the dynamic datas (CH + CC) of blocked SIP extension
sipextusers : Shows the SIP devices with gateway
The command sip gives all the commands related to SIP.
12.5.2 trkstat
+==============================================================================+
| S I P T R U N K S T A T E Trunk group number : 10 |
| Trunk group name : SIP_local |
| Number of Trunks : 62 |
+------------------------------------------------------------------------------+
| Index : 1 2 3 4 5 6 7 8 9 10 11 12 13 |
| State : F F F F F F F F F F F F F |
+------------------------------------------------------------------------------+
| Index : 14 15 16 17 18 19 20 21 22 23 24 25 26 |
+------------------------------------------------------------------------------+
| Index : 27 28 29 30 31 32 33 34 35 36 37 38 39 |
+------------------------------------------------------------------------------+
| Index : 40 41 42 43 44 45 46 47 48 49 50 51 52 |
+------------------------------------------------------------------------------+
| Index : 53 54 55 56 57 58 59 60 61 62 |
| State : F F F F F F F F F F |
+------------------------------------------------------------------------------+
| F: Free | B: Busy | Ct: busy Comp trunk | Cl: busy Comp link |
| WB: Busy Without B Channel| Cr: busy Comp trunk for RLIO inter-ACT link |
| WBD: Data Transparency without chan.| WBM: Modem transparency without chan. |
| D: Data Transparency | M: Modem transparency |
+------------------------------------------------------------------------------+
The command trkstat + SIP Trunk Group number gives the B channels used on the SIP Trunk group
associated to a gateway.
Ed. 12 59 TG0069
OmniPCX Enterprise
12.5.3 trkvisu
****************** data in Trunk_Group structure ****************
******** data REMOTE TRUNK

TrunkName = SIP_local
discrLogId = -1 ton_a_used = 0 em_repfix = 0
privLine = 0 reservop = 0 reserauto = 0
Trunksearchs = 0 ftranscom = 0 frondier = 0
typTrunk : (6) => T2-SIP
Next_Trunk = -1 nbdigitsem = 0 tab_proto = -1
var IPNS = 1
node_number = 1
network_number = 10
trunk_reg_sig = 0
special_it_par_quantum = 1
cat_restrictionService_in = 10, cat_restrictionService_out = 10
Priority ===> Level= 0, Mode= 0, Preemption= 0
mpt1343 = 0, callbackTrunkbusy = 1 rerouting = 0
******** data Link
cat_signa = 31 ch_channelb = 1 overflow_it = 1 access_turn = 1 network_mode = 0
+--------------------------------------------------------------------------------------------
| ocupjonc for SIP TG
+--------------------------------------------------------------------------------------------
| SIP Trunk group information on TX side
| i = 0, min = 0, max = 62
| (num_crist - num_cpl - num_term) = (19-0-1)
| last it used = 0, monlap = 30, network_mode = 0 nbr_trunk_created = 62
| nbr_trunk_busy : start = 0 arrived = 0 mixed = 0
| it_reserved : start = 0 arrived = 0 mixed = 62
| it_max_Q0 : Start = 0 arrived = 0 mixed = 62
| it_max_Q1 : Start = 0 arrived = 0 mixed = 0
| access_level2 = CONNECT2
+--------------------------------------------------------------------------------------------
| outservice | res | Busy | nulog |trans|neqtdyn|E64 RN64 EN64| OVPN | neqph | adr
+--------------------------------------------------------------------------------------------
| FREE | no | free | 5001 | 1 | -1 | 0 0 0 | 0 | 2314 |SIP Trunk 1
...
| FREE | no | free | 5062 | 1 | -1 | 0 0 0 | 0 | 2376 |SIP Trunk 62
+--------------------------------------------------------------------------------------------
+--------------------------------------------------------------------------------------------
| SIP Trunk group information on GX side
| (num_crist - num_cpl - num_term) = (19-0-0)
| monlap = 29, mode_reseau = 1 nbr_jonc_cree = 62
| Trunks from nulog 5063 (neqph 2250) to nulog 5124 (neqph 2312)
+--------------------------------------------------------------------------------------------
index_max = 125 ; nbjonc = 62

cristal = 0 1 2 3 4 5 6 7 8 9 10 11
LastTrunkused = 0 0 0 0 0 0 0 0 0 0 0 0
cristal = 12 13 14 15 16 17 18 19
LastTrunkused = 0 0 0 0 0 0 0 62
LastTrunkUsed common = 0 idx_rfo = 0 channel_reserv = 0
dert0_used = 0 dert0mixt_used = 0 dert0wo_used = 0
******** data TRUNK_LOCAL

a_paying = 0 Trunkdisa = 0 itpermnt = 1 trans_num = 0
tr_q23 = 0 reach_boss = 0 secretcode = 0 ach_film = 1
accesscode = 0 gp_d_Hold = 0 categ_ptt = 31 blf etat = 1
entity_nr = 0 nb_digit_used = 0 Trunkdissu = 0 dto_about = 0
reused_channelb = 0 number_to_be_added : .
mode_ddi = 0 refptt = / / nbchminp = 0
x25used = 0
vpnRate = 50 vpnCostLimit = 0 immTrkForVpn = 1
businessPercent = 0 nbACDCall = 0 tax_nds = 1
send_prog = 1 ip_qual_prof = Profile #1
t2spec = S_SIP compression_type = 0 (0: Default [ie : G729], 1 : G711)
d_channel_hyb = 0
Ed. 12 60 TG0069
OmniPCX Enterprise
The information given are the same compared to a normal T2 trunk group. This command can be used to
find the equipment of a SIP Trunk Group, or the neqt.
A SIP Trunk group has two sides, the TX (USER) and GX (NETWORK). When a call is done on a SIP
Trunk Group, the call is leaving on the SIP TG and comes back on the same SIP TG; it is like an internal SIP
loop.
12.5.4 sipaccess
+------------------------------------------------------------------------------+
| 1 | SIP Trunk Group Access |
+------------------------------------------------------------------------------+
| TG Nb | 10 | 12 | 11 | 186 | 187 |
| | | | | | |
| Access | User - Net | User - Net | User - Net | User - Net | User - Net |
+------------------------------------------------------------------------------+
| 1 | 30 - 29 | 33 - 32 | 35 - 34 | 37 - 36 | 39 - 38 |
| 2 | . . . | 41 - 40 | . . . | . . . | . . . |
| 3 | . . . | . . . | . . . | . . . | . . . |
| 4 | . . . | . . . | . . . | . . . | . . . |
| 5 | . . . | . . . | . . . | . . . | . . . |
| 6 | . . . | . . . | . . . | . . . | . . . |
| 7 | . . . | . . . | . . . | . . . | . . . |
| 8 | . . . | . . . | . . . | . . . | . . . |
| 9 | . . . | . . . | . . . | . . . | . . . |
| 10 | . . . | . . . | . . . | . . . | . . . |
| 11 | . . . | . . . | . . . | . . . | . . . |
| 12 | . . . | . . . | . . . | . . . | . . . |
| 13 | . . . | . . . | . . . | . . . | . . . |
| 14 | . . . | . . . | . . . | . . . | . . . |
+------------------------------------------------------------------------------+
The command sipacces gives the access numbers used for each SIP TG.
In that case, for the TG number 10 with 2 accesses managed, the OXE uses the accesses 30 for TX and 29
for GX, these accesses numbers can be found with the command trkvisu (search for monlap).
In the previous example, for the TG number 12 with 4 accesses managed, the OXE uses the accesses 33
and 41 for TX then 32 and 40 for GX.
12.5.5 sipgateway
+-----------------------------------------------------------------------+
| SIP Gateway |
+-----------------------------------------------------------------------+
Machin name : oxe-ov
IP Address : 172.27.142.53
Subnetwork number : 10
SIP Trunk Group : 10
DNS Informations :
DNS local domain name : alcatel.fr
+-----------------------------------------------------------------------+
| Trusted IP Address List |
+-----------------------------------------------------------------------+
Trusted IP Address 1 : 172.27.145.128
+-----------------------------------------------------------------------+
| Quaranted IP Address List |
+-----------------------------------------------------------------------+
The command sipgateway gives the information about the local SIP configuration.
Ed. 12 61 TG0069
OmniPCX Enterprise
The following information are diplayed:
o Machine name corresponds to the nodename managed under netadmin.

o IP address corresponds to the main IP address of the main CPU.
o Subnetwork number correponds to the network associated to the local SIP gateway.
o SIP Trunk Group correponds to the SIP TG associated to the local SIP gateway.
o DNS local domain name correponds to the DNS suffix managed on the local SIP gateway.
o Trusted IP Addresses List corresponds to the IP addresses managed on the Trusted IP
Addesses
o Quaranted IP Addresses List corresponds to the IP addresses managed on the
Quarantined IP addresses.
12.5.6 Sipdump
!!! WARNING : sipdump option 5 should ONLY be used on OXE release j2.603.20.e or higher : risk
of sipmotor restart with previous releases.
The sipdump tool gives information about SIP calls and the SIP gateway. Its useful in order to know in which
state the SIP calls are, to know which calls are handled by the SIP gateway, to release a call, to know the
inactive calls, etc
It allows to define some filters in order to display the traces of SIP calls according to SIP calls characteristics
(From, To, P_Asserted, Request URI headers).
Activation:
Set a trace level very low (set by motortrace lowest trace level by motortrace 0), and disable filters.
Run the traced & command.
Run the command sipdump.
For better view, run sipdump and traced in different telnet sessions.
A Call corresponds to a SIP voice call, but also for a subscription, notify, etc
Sometimes, choices must be done twice to get the outputs.
R10x/R11
SIP Gateway resources menu
1 - Dump the gateway management datas

2 - Dump a call
3 - Display the number of calls
4 - Display the calls-neqt mapping
5 - Display the calls list
6 - Display the detailed calls list
7 - Release a call
8 - Display subscription list
9 - Display calls through a gateway
10 - Display calls in a trunk group
11 - SIP traces filters
12 - Display registred users
13 - Display CPU-SSM connections
14 - Display memory allocation
15 - Display IP cache from ext gw
0 - Exit
Ed. 12 62 TG0069
OmniPCX Enterprise
1 Dump the gateway management datas :
Wed Jan 4 14:48:42 2012 Gateway Management Datas

Wed Jan 4 14:48:42 2012 -------------------------------------------
Wed Jan 4 14:48:42 2012
Wed Jan 4 14:48:42 2012 Use of licences : Yes
Wed Jan 4 14:48:42 2012 UCaaS mode : No (From R11)
Wed Jan 4 14:48:42 2012 Number of initial licenses : 20
Wed Jan 4 14:48:42 2012 Number of available licences : 15
Mon Jun 4 12:48:42 2012 Number of initial Tls licenses : 5
Mon Jun 4 12:48:42 2012 Number of available Tls licences : 5
Wed Jan 4 14:48:42 2012
Wed Jan 4 14:48:42 2012 Main server : Yes
Wed Jan 4 14:48:42 2012 Degraded mode : No
- Main server corresponds to the role of the CPU (Main or Stand-By).
- Use of licenses means that the OXE is using SIP, license point of view.
- Number of initial licenses corresponds to the number of licenses bought.
- Number of available licenses corresponds to the number of licenses remaining. The difference
with the Number of initial licenses give the number of licenses used when this choice is done.
- Number of initial Tls licenses corresponds to the number of licenses bought for TLS.
- Number of available Tls licenses corresponds to the number of licenses remaining for TLS. The
difference with the Number of initial Tls licenses give the number of licenses for TLS used when
this choice is done.
- Main server gives the role of the CPU where you run the sipdump command.
- Degraded mode is used when the SIPMOTOR reaches a threshold of SIP contexts treatment, in
that case, the SIPMOTOR switches in degraded mode to reject all the incoming SIP messages by
a 503 response, with a "Retry-After" header, is sent to the UAC. This is used to avoid SIPMOTOR
crash.
2 Dump a call
Enter the Neqt of the SIP equipment + Dialogid, to know them, use the choice 4 before.
1325686751 -> Wed Jan 4 15:18:56 2012 -------------------------------------------
Wed Jan 4 15:18:56 2012 Call Dump
Wed Jan 4 15:18:56 2012 -------------------------------------------
Wed Jan 4 15:18:56 2012
Wed Jan 4 15:18:56 2012 Neqt : 968-1
Wed Jan 4 15:18:56 2012 Call ID : [email protected]
Wed Jan 4 15:18:56 2012 Current state : COMPLETED_STATE
Wed Jan 4 15:18:56 2012 From : sip:[email protected];user=phone
Wed Jan 4 15:18:56 2012 To : sip:[email protected];user=phone
Wed Jan 4 15:18:56 2012 External VM: : FALSE
Wed Jan 4 15:18:56 2012 Sip Device: : FALSE
Wed Jan 4 15:18:56 2012 Ext. Gateway : Not used
Wed Jan 4 15:18:56 2012 Session Timer : INVITE method
Wed Jan 4 15:18:56 2012 -------------------------------------------
Wed Jan 4 15:19:07 2012 -------------------------------------------
Wed Jan 4 15:19:07 2012 Neqt - Call mapping
Wed Jan 4 15:19:07 2012 -------------------------------------------
Wed Jan 4 15:19:07 2012
Wed Jan 4 15:19:07 2012 Active Calls (1 / 1)
Wed Jan 4 15:19:07 2012 Eqt = 968 dialogId = 1 <-> Call ID =
[email protected]
Wed Jan 4 15:19:07 2012 State = COMPLETED_STATE
Wed Jan 4 15:19:07 2012
Wed Jan 4 15:19:07 2012
Wed Jan 4 15:19:07 2012 Unactive Calls (0 / 1)
Wed Jan 4 15:19:07 2012 -------------------------------------------
Ed. 12 63 TG0069
OmniPCX Enterprise
- The Current statecorresponds to the status of the call:

PROCEEDING_STATE : the call is in progress (ringing for instance).
COMPLETED_STATE : the call is established.
TERMINATED_STATE : the call is finished.
- From and To correspond to the caller and the callee.
- External VM : False means that it is not an external SIP Voice mail.
- Sip Device: False means a SIP extension user (SEPLOS).
- Ext. Gateway corresponds to the external SIP gateway used for the call.
- Session Timer corresponds to the method used for it according to the local SIP gateway
management:
UPDATE Method: use UPDATE message to refresh the session.
INVITE method: use RE_INVITE message to refresh the session.
- Active Calls correponds to the SIP calls established

Only COMPLETED_STATE is visible.
- Unactive Calls corresponds to the SIP calls over or in progress:

Unactive + PROCEEDING_STATE, corresponds to a SIP call in progress.
Unactive + TERMINATED_STATE, corresponds to a SIP call over, but its SIP
context is still present on the SIPMOTOR. The maximum duration of the context in
the SIPMOTOR is 32 seconds, during this period, the SIPMOTOR will delete it. If
the SIP call context is still present after this delay, the SIPMOTOR will not be able to
remove it by itself, a restart of the SIPMOTOR must be done.
When a restart of the SIPMOTOR is performed, all the SIP call contexts are lost, that means
that the calls are not known by the SIPMOTOR anymore.
3 Display the number of calls

1325752599 -> Thu Jan 5 09:36:39 2012 stack data.
Thu Jan 5 09:36:39 2012 ==========

Thu Jan 5 09:36:39 2012 Calls : 1 current (4 max) / 59052 total
Thu Jan 5 09:36:39 2012 Dialogs : 1 current (6 max) / 59083 total
Thu Jan 5 09:36:39 2012 Transactions : 1 current (6 max) / 59240 total
Thu Jan 5 09:36:39 2012 Requests : 1 current / 59301 total
Thu Jan 5 09:36:39 2012 Response : 0 current / 309 total
Thu Jan 5 09:36:39 2012 DNS requests : 0 current (0 max) / 0 total / 0 foundInCache / 0
failed / 0 totalPutinBlackList
- Corresponds to the number of SIP calls, but also SIP dialogs, SIP transactions, etc
4 - Display the calls-neqt mapping.

Thu Jan 5 10:19:59 2012 -------------------------------------------
Thu Jan 5 10:19:59 2012 Neqt - Call mapping
Thu Jan 5 10:19:59 2012 -------------------------------------------
Thu Jan 5 10:19:59 2012
Thu Jan 5 10:19:59 2012 Active Calls (1 / 1)
Thu Jan 5 10:19:59 2012 Eqt = 968 dialogId = 2 <-> Call ID =
[email protected]
Thu Jan 5 10:19:59 2012 State = COMPLETED_STATE
Thu Jan 5 10:19:59 2012
Thu Jan 5 10:19:59 2012
Thu Jan 5 10:19:59 2012 Unactive Calls (0 / 1)
Thu Jan 5 10:19:59 2012 -------------------------------------------
Ed. 12 64 TG0069
OmniPCX Enterprise
- Corresponds to the Active and Unactive calls present on SIPMOTOR, for the sipdump choice 2,
it is necessary to have the Neqt and the dialogid, here we have them for each call.
5 - Display the calls list.
Thu Jan 5 10:25:54 2012 -------------------------------------------
Thu Jan 5 10:25:54 2012 List of Calls
Thu Jan 5 10:25:54 2012 -------------------------------------------
Thu Jan 5 10:25:54 2012
Thu Jan 5 10:25:54 2012 Call ID = [email protected]
Thu Jan 5 10:25:54 2012
Thu Jan 5 10:25:54 2012
Thu Jan 5 10:25:54 2012 -------------------------------------------
- List the Active and Unactive SIP calls on the SIPMOTOR. Recommended in case of licence
consumming issue.
6 - Display the detailed calls list.

Thu Jan 5 10:29:41 2012 Detailed list of Calls from Stack
Thu Jan 5 10:29:41 2012 -------------------------------------------
Thu Jan 5 10:29:41 2012 102 [CCallManager] Dump - 1 CCall instance(s)
[1137] Call ID : [email protected]
CCall 1137
Call-ID : [email protected]
isClosed : no
onlyInitialDialog : no
==========================================================
InitialDialog client :
--------------------
CDialog 1537
isClosed : no
isProxy : no
isRouted : no
State : Initial
Initial method : INVITE
Session-Timer :
isProxy : no
supported : I support
Min-SE : 900
Session-Expires : 1800
Refresher : I refresh
Warning timer : stopped
Session timer : stopped
Refresh method :
Route set : Contact : sip:[email protected]:36128;rinstance=98cedca3f085d785
Messages :
----------------------------------------
out:INVITE [2012/01/05 10:19:54 CET]
in:180 (INVITE) [2012/01/05 10:19:54 CET]
in:200 (INVITE) [2012/01/05 10:19:55 CET]
----------------------------------------
--------------------------------------------------------
Transactions :
------------
CTransaction 2138
State : Proceeding
isClient : yes
isCancelable : no
isRouted : no
isProxy : no
Initial request : INVITE (38)
Last response : 180 (6)
Final response : None
Ack request : None
Timers in progress : None
--------------------------------------------------------
...
Ed. 12 65 TG0069
OmniPCX Enterprise
- This choice is used to view the different exchanges details for the SIP transactions.
- For each transaction, we have 3/4 groups of information (3 for call in progress, 4 for
established/closed):
SIP call information with the Call ID and the state of the call:
- Closed (isClosed= yes)
- In progress (onlyInitialDialog=yes)
- Established (isClosed= no and onlyInitialDialog=no)
InitialDialog client: this part corresponds to the information on the SIP message
received or sent to establish a SIP transaction (INVITE, SUBSCRIBES, etc).
Transaction: this part corresponds to the status of the transaction itself (type of
transaction, last message, etc).
Dialogs: this part corresponds to the dialog information.
7 - Release a call.
- Enter the Neqt number and the DialogId, use the choice 4 to find them.
Thu Jan 5 12:05:45 2012 -------------------------------------------
Thu Jan 5 12:05:45 2012 Neqt - Call mapping
Thu Jan 5 12:05:45 2012 -------------------------------------------
Thu Jan 5 12:05:45 2012
Thu Jan 5 12:05:45 2012 Eqt = 968 dialogId = 1 <-> Call ID =
[email protected]
Thu Jan 5 12:05:45 2012
Thu Jan 5 12:05:45 2012
Thu Jan 5 12:05:45 2012 -------------------------------------------
Thu Jan 5 12:05:51 2012 ALARM: [receiveSuccessfulEvent] Call:
[email protected] eqt: 968 TERMINATED_STATE failed to emit
- An incident 5816 is seen on the OXE and the alarm is visible on the sipalarm
a Successful message.
files.
Thu8Jan
- Display subscription list.
5 12:05:51 2012 ALARM: CPU main
Thu Jan 5 12:11:33 2012 -------------------------------------------
Thu Jan 5 12:11:33 2012 sipmotor Subscription Map
Thu Jan 5 12:11:33 2012 key [email protected]@message-summary
Thu Jan 5 12:11:33 2012 call no 1153
Thu Jan 5 12:11:33 2012 call Id NTUyZjA1ZmFiYTQ1MDI3N2U2ZTE1NzFkY2ZjZmM2MmQ.
Thu Jan 5 12:11:33 2012 delay 3600
Thu Jan 5 12:11:33 2012 -------------------------------------------
Thu Jan 5 12:11:33
- The 2012 Number ofcan
subscription Subscription (s) :of1 voice mail, for instance to be able
be used in case to be
Thu Jan 5 12:11:33 2012 end of sipmotor Subscription Map
Thu Jan 5 notified if a message has been deposited on the voice mailbox.
12:11:33 2012 -------------------------------------------
9 - Display calls through a gateway.
- Enter the External Gateway number.
Thu Jan 5 13:41:14 2012 -------------------------------------------
Thu Jan 5 13:41:14 2012 Call ID :
[email protected]
Thu Jan 5 13:41:14 2012 Current state : COMPLETED_STATE
Thu Jan 5 13:41:14 2012 From : sip:32000@toto;user=phone
Thu Jan 5 13:41:14 2012 To : sip:[email protected];user=phone
Thu Jan 5 13:41:14 2012 Session Timer : UPDATE method
Thu Jan 5 13:41:14 2012 -------------------------------------------
Thu Jan 5 13:41:14 2012 Number of Calls through this Gateway (151) : 1 (Active calls:
1)
Thu10
Jan 5 13:41:14
- Display calls in2012 -------------------------------------------
a trunk group.
- Enter the SIP trunk group number (ISDN or ABCF).
Trunk Group Number : 10
Display of trunk groups Menu
1 - Display calls through any one gateway using the trunk group(10)
2 - Display calls through all the gateways using the trunk group(10)
0 - Previous menu
Ed. 12 66 TG0069
OmniPCX Enterprise
- Select 1 or 2, if 1 enter the SIP gateway number (0 to 999).

Thu Jan 5 13:49:50 2012 -------------------------------------------
Thu Jan 5 13:49:50 2012 Call ID :
[email protected]
Thu Jan 5 13:49:50 2012 Current state : COMPLETED_STATE
Thu Jan 5 13:49:50 2012 From : sip:32000@toto;user=phone
Thu Jan 5 13:49:50 2012 To : sip:[email protected];user=phone
Thu Jan 5 13:49:50 2012 Gateway : 151
Thu Jan 5 13:49:50 2012 Session Timer : UPDATE method
Thu Jan 5 13:49:50 2012 -------------------------------------------
Thu Jan 5 13:49:50 2012 Number of Calls in this Trunkgroup (10) : 1 (Active calls: 1)
Thu Jan 5 13:49:50 2012 -------------------------------------------
11 - SIP traces filters.
This functionality allows setting up to five filters on SIP gateway calls. A filter is composed of the following
elements:
- Filter string: String to search into the SIP calls headers the user wants to trace.
- From Field: If the field is set true, the user traces the SIP calls according to the
content of From header. In this case, if the SIP call From header contains the filter
string defined for the filter, the SIP call will be traced.
- To Field: If the field is set true, the user traces the SIP calls according to the content
of To header.
- P_Asserted field: If the field is set true, the user traces the SIP calls according to the
content of P_Asserted header.
- Request-URI field: If the field is set true, the user traces the SIP calls according to
the content of the Request URI.
Display conditions:
- SIP call traces will be displayed if the SIP call matches at least one of the five filters
of the array.
- A SIP call matches to a filter if it fills one of the conditions of the filter.
SIP traces filters menu
1 - Display the traces filters

2 - Add a traces filter
3 - Update a traces filter
4 - Remove a traces filter
5 - Remove all traces filters
0 - Previous menu
o 1 - Display the traces filters.
--------------------------------------------------------------------------------
| Nb | Filter | From | To | P_Asserted | Request URI |
|-------------------------------------|------|------|------------|-------------|
| 1 | ... | ... | ... | ... | ... |
|-------------------------------------|------|------|------------|-------------|
| 2 | ... | ... | ... | ... | ... |
|-------------------------------------|------|------|------------|-------------|
| 3 | ... | ... | ... | ... | ... |
|-------------------------------------|------|------|------------|-------------|
| 4 | ... | ... | ... | ... | ... |
|-------------------------------------|------|------|------------|-------------|
| 5 | ... | ... | ... | ... | ... |
--------------------------------------------------------------------------------
Ed. 12 67 TG0069
OmniPCX Enterprise
o 2 - Add a traces filter.

String to filter ? (31 car. max) :
From field ? (y/n) :
To field ? (y/n) :
P_Asserted Field ? (y/n) :
Request URI field ? (y/n) :
- Enter which information to filter (the filters are not case sensitive), and define on
each field to apply the filter.
--------------------------------------------------------------------------------
|-------------------------------------|------|------|------------|-------------|
| 1 | alcatel-lucent.com | Yes | Yes | Yes | Yes |
|-------------------------------------|------|------|------------|-------------|
| 2 | genesys.com | Yes | Yes | Yes | Yes |
|-------------------------------------|------|------|------------|-------------|
| 3 | ... | ... | ... | ... | ... |
|-------------------------------------|------|------|------------|-------------|
| 4 | ... | ... | ... | ... | ... |
|-------------------------------------|------|------|------------|-------------|
o 3 - Update a traces filter.

- Enter the filter number, in this case, only the filter 1 is managed.
From field ? (y/n) : y
To field ? (y/n) : y
P_Asserted Field ? (y/n) : n
Request URI field ? (y/n) : y
- The filter string can not be modified, only on which field it is used.
--------------------------------------------------------------------------------
|-------------------------------------|------|------|------------|-------------|
| 1 | alcatel-lucent.com | Yes | Yes | No | Yes |
|-------------------------------------|------|------|------------|-------------|
|-------------------------------------|------|------|------------|-------------|
| 3 | ... | ... | ... | ... | ... |
|-------------------------------------|------|------|------------|-------------|
| 4 | ... | ... | ... | ... | ... |
|-------------------------------------|------|------|------------|-------------|
| 5 | ... | ... | ... | ... | ... |
--------------------------------------------------------------------------------
o 4 - Remove a traces filter.

- Enter the filter number, only this one will be removed (1 for instance).
--------------------------------------------------------------------------------
|-------------------------------------|------|------|------------|-------------|
| 1 | ... | ... | ... | ... | ... |
|-------------------------------------|------|------|------------|-------------|
|-------------------------------------|------|------|------------|-------------|
| 3 | ... | ... | ... | ... | ... |
|-------------------------------------|------|------|------------|-------------|
| 4 | ... | ... | ... | ... | ... |
|-------------------------------------|------|------|------------|-------------|
| 5 | ... | ... | ... | ... | ... |
--------------------------------------------------------------------------------
Ed. 12 68 TG0069
OmniPCX Enterprise
o 5 - Remove all traces filters.

- If you choose this option, all the filters will be removed.
Example: The traces must be done when alcatel-lucent.com is present on the To or the From field
and/or genesys.com on the From or the P_Asserted fields .
The result is the following:
--------------------------------------------------------------------------------
|-------------------------------------|------|------|------------|-------------|
| 1 | alcatel-lucent.com | Yes | Yes | ... | ... |
|-------------------------------------|------|------|------------|-------------|
| 2 | genesys.com | Yes | ... | Yes | ... |
|-------------------------------------|------|------|------------|-------------|
| 3 | ... | ... | ... | ... | ... |
|-------------------------------------|------|------|------------|-------------|
| 4 | ... | ... | ... | ... | ... |
|-------------------------------------|------|------|------------|-------------|
| 5 | ... | ... | ... | ... | ... |
--------------------------------------------------------------------------------
When you will make a SIP trace (motortrace + traced), the OXE will display the SIP exchanges and
information according to the filter management.
If you run the motortrace command and if a filter is set, the following messages will be displayed:
motortrace (v5.2.0) verbosity = 00800004
The sipmotor traces level can not be changed
because some traces filters are set.
Please, remove them (with sipdump) before updating the traces level.
Do not forget to remove all the filters after use.
12 - Display registred users.

Thu Jan 5 15:12:34 2012 -------------------------------------------
Thu Jan 5 15:12:34 2012 Detailed list of Registred users
Thu Jan 5 15:12:34 2012 -------------------------------------------
Thu Jan 5 15:12:34 2012
Thu Jan 5 15:12:34 2012 *************************************************
[CServRegistrar] Dump local registrar base
Address of record : 32003
contact : sip:[email protected]:46470, , 1611sec, 0.5
-------------------------------------------------
Registrar statistics :
Number of users recorded : 1
Number of users having multiple contacts : 0
Number of contacts using UDP transport : 1
Number of contacts using TCP transport : 0
*************************************************
Thu Jan 5 15:12:34 2012 -------------------------------------------

o Compared to the sipregister command, here there are statistics about the Registrar.
- Number of users recorded corresponds to the number of SIP equipments registered

on the OXE Registrar.
- Number of users having multiple contacts corresponds to the SIP equipments with
multiple contacts, used in case of forking.
- Number of contacts using UDP transport corresponds to the number of contact
using UDP.
- Number of contacts using TCP transport corresponds to the number of contact using
TCP.
Ed. 12 69 TG0069
OmniPCX Enterprise
12.5.7 sipextgw
This command is used with options:
o sipextgw -l gives the external SIP gateways created and their states.
====================================================================
| R E G I S T E R E D S I P E X T E R N A L G A T E W A Y S |
====================================================================
IN SERVICE SIP external gateways list :

186
OUT OF SERVICE SIP external gateways list :

187
Here the external SIP gateway 186 is in service and the external SIP gateway 187 is out of service.
o sipextgw -g external gateway number gives the configuration of this external SIP gateway.
====================================================================
| S I P E X T E R N A L G A T E W A Y Nb 186 |
====================================================================
Gateway Name : SIMUL_SIP_ABCF
Gateway Type : Standard type
State : IN SERVICE
Belong to pool number : -1
Use trunk group number : 186 (ABC-F)
Remote domain : 172.27.143.186
Port number : 5060
Transport : UDP
SRTP : RTP only
Prack : NO
Clir : YES
SIP info enable : NO
Authentication method : NONE
SDP in 180 messages : NO
Payload : 97
Outgoing username :
Outgoing password : *****
Incoming username :
Incoming password : *****
Local domain name :
Local user name :
Realm name :
Outbound proxy :
Supervision timer : 0
Registration timer : 0
DNS type : DNS A
Primary DNS IP address : 000.000.000.000
Secondary DNS IP address : 000.000.000.000
PCS IP address : 000.000.000.000
Retransmission number
of REGISTER/OPTIONS : 2
Service route index : -1
P-Asserted-ID : FALSE
TrustedPAssIDHeader : TRUE
TrustedFromHeader : FALSE
Outbound calls only : FALSE
ReInviteWoSDP : TRUE
Diversion Info to
provide through : History Info
Proxy ident. on IP addres: FALSE
Regist. on proxy discovery: FALSE
SDP relay on Ext. Call Fwd : Default
RFC 5009 supported / Outbound call : Not Supported
FAX Procedure Type : T38 only
Type Of Codec Negotiation : Default
Ed. 12 70 TG0069
OmniPCX Enterprise
This command is used to get a quick view of the configuration given to this exteranl SIP gateway.
o sipextgw -s external gateway number gives information if the external SIP gateway is used
on a Command table (ARS) or/and a Routing Number Table.
====================================================================
| E X T E R N A L G A T E W A Y Nb 187 A R E A S |
====================================================================
Found in ARS ==> dialling command table number : 187
Not found in ROUTING tables
Here is the external SIP gateway 187 used on the command table 187.
====================================================================
| E X T E R N A L G A T E W A Y Nb 186 A R E A S |
====================================================================
Not found in ARS tables
Found in ROUTING table number : 12
Here is the external SIP gateway 186 used on the Routing table 12.
12.5.8 sippool
This command is used to the external SIP gateways associated to the same pool.
+-----------------------------------+
| | | |
| pool Nb | GW 1 | GW 2 |
| | | |
+-----------------------------------+
| 00 | 187 OOS | L 186 |
| 01 | . . . | . . . |
| 02 | . . . | . . . |
| 03 | . . . | . . . |
...
| 296 | . . . | . . . |
| 297 | . . . | . . . |
| 298 | . . . | . . . |
Here are the external SIP gateways 186 and 187 in the same pool, the pool number 0.
o "L" shows the latter gateway used from the pool.

o "OOS" means that the related gateway is OUT OF SERVICE.
Ed. 12 71 TG0069
OmniPCX Enterprise
12.5.9 sipdict
o sipdict -l is used to list the sip users.

SIP DICTIONNARY, dim = 128, nb records = 16
+----------+----+----------------------------------------------+----+-----+------+------+------+-----+
| | | | | | | | Ext. | |
| mcdu | i | url |Type| Org | idx1 | idx2 | gw | Reg |
+----------+----+----------------------------------------------+----+-----+------+------+------+-----+
| 31020 | 0 | 31020@ oxe-ov | 3 | 1 | 12 | 0 | -- | -- |
| 31021 | 0 | 31021@ oxe-ov | 3 | 1 | 15 | 1 | -- | -- |
| 39002 | 0 | 39002@ oxeb-ov | 3 | 2 | 3 | 4 | -- | -- |
| 31853 | 1 | 31853@ opentouch-ov | 2 | 1 | 14 | 10 | 1 | No |
| 31022 | 0 | 31022@ oxe-ov | 3 | 1 | 1 | 11 | -- | -- |
For each user directory number,the next information are present:

- the mcdu corresponds to the directory number of the SIP user.
- the i is used to see if the SIP user is linked to an external SIP gateway (0=no,
1=yes)
- the dim corresponds to the size of the dictionnary, if the number of the SIP users
created is greater than 128, the OXE add one more 128 to have 256, if the number
is greater than 256, the OXE add one more 128 to have 384, etc...the maximum is
128*80.
- the url corresponds to the SIP url known by the OXE.
the user 39002 is from another node (oxeb-ov).
- the type corresponds a SIP device or SIP extension:
1 is an external SIP voice mail.
2 is SIP device.
3 is SIP extension.
- the org corresponds to the origin node.
- the idx1 and idx2 are assigned to the SIP users during creation and used
internally.
- the Ext.gw is used in case of Open Touch configuration, only for SIP device.
The user 31025 is using it, and it is know by the OXE by 31853@oxe-ov
and [email protected] on OXE.
172.27.143.186 is the SIP Remote domain managed on the external SIP
gateway 186.
- the Reg is used to see if the user is registered on the external SIP gateway.
o sipdict -i is used to list the sip users by using the idx1 (or pos).
SIP DICTIONNARY, dim = 128, nb records = 16
+------+----------+----+------------------------------------------------------+----+------+-----+
| | | | | | Ext. | |
| pos | mcdu | i | url par index |Type| gw | Reg |
+------+----------+----+------------------------------------------------------+----+------+-----+
| 12 | 31852 | 0 | 31852@ oxe-ov | 1 | -- | -- |
| 15 | 31853 | 0 | 31853@ oxe-ov | 2 | -- | -- |
| 3 | 31853 | 1 | 31853@ 172.27.143.186 | 2 | 186 | No |
| 14 | 31854 | 0 | 31854@ oxe-ov | 3 | -- | -- |
...
- sipdict -v is used to list the sip users by using the idx2.

o sipdict -n directory number of the SIP user is used to display the url associated.
(101)cpub_ov> sipdict -n 31027
Thu May 31 09:26:14 CEST 2012
URL = 31027@oxe-ov
Ed. 12 72 TG0069
OmniPCX Enterprise
o sipdict -u url of the SIP user is used to display the mcdu associated.
(101)cpub_ov> sipdict -u 31027 oxe-ov
Thu May 31 09:28:39 CEST 2012
31027@oxe-ov :
31027
Enter the url without the @ but just a space.
12.5.10 sipauth
o sipauth -l is used to list the sip users.
SIP AUTHENTIFICATION, dim = 128, nb records = 13
+----------+------------------------------------------------------------+------+
| mcdu | authentification | idx1 |
+----------+------------------------------------------------------------+------+
| 31020 | 31020 @ 0000 | 2 |
| 31021 | 31021 @ 0000 | 12 |
| 31853 | 31853 @ 0000 | 1 |
| 31022 | 31022 @ 0000 | 3 |
| 31026 | 31026 @ 0000 | 9 |
+----------+------------------------------------------------------------+------+
- the mcdu correponds to the directory number of the SIP user.

- the authentication corresponds to the user login and user pass for the
authentication, to managed on the SIP equipment if needed.
- the idx1 is assigned to the SIP users during creation and used internaly, same
than the one given by the sipdict command.
o sipauth -i is used to list the sip users by using the idx1.

SIP AUTHENTIFICATION, dim = 128, nb records = 13
+------+----------+------------------------------------------------------------+
| pos | mcdu | authentification |
+------+----------+------------------------------------------------------------+
| 2 | 31020 | 31020 @ 0000 |
| 12 | 31021 | 31021 @ 0000 |
| 1 | 31853 | 31853 @ 0000 |
| 3 | 31022 | 31022 @ 0000 |
| 9 | 31026 | 31026 @ 0000 |
+------+----------+------------------------------------------------------------+
o sipauth -n directory number of the SIP user is used to display the user login and user pass.
(101)cpub_ov> sipauth -n 31027
Thu May 31 09:36:56 CEST 2012
LOGIN = 31027@0000
12.5.11 sipregister
Ed. 12 73 TG0069
OmniPCX Enterprise
o sipregister, without option, display all the SIP and SIPS users registered on registrar.
sipregister h To get help menu.
*************************************************
Dump local registrar base
-------------------------------------------------
contact : sip:[email protected]:27836, udp, 502 s
-------------------------------------------------
contact : sip:[email protected], udp, 2867 s
-------------------------------------------------
contact : sip:[email protected], UDP, 319998256 s
-------------------------------------------------
-------------------------------------------------
*************************************************
******
For registred
each address user number
of record,the next: information
5 are present and given by the remote SIP equipment during
*************************************************
registration:
- the contact corresponds to the SIP address of the SIP equipment with the IP
address to locate it.
- the upd corresponds to the transport type, tcp can be shown if it is used.
- The xx s corresponds to the registration time left.
- If no port number, the OXE will use the port 5060
o sipregister l provides all the SIP users registered on the registrar (option c is used for SIPS
users)
sipregister h To get help menu.

*************************************************
Dump local registrar base
-------------------------------------------------
-------------------------------------------------
-------------------------------------------------
contact : sip:[email protected], UDP, 319998256 s
-------------------------------------------------
-------------------------------------------------
*************************************************
****** registred user number : 5
*************************************************
For each address of record,the next information are present and given by the remote SIP equipment during
registration:
Ed. 12 74 TG0069
OmniPCX Enterprise
12.5.12 csipsets
csipsets with no option provides all the SIP extension created on OXE.
+-----+--------+----------------+---------------+-----+
|Neqt |Number |Name |IP address |State|
+-----+--------+----------------+---------------+-----+
|02054|31020 |MyIc_touch 172.2| Unused| HS |
|02055|31027 |OT4135 | 172.27.143.184| ES |
|02058|31021 |RO31021 | Unused| HS |
|02059|31022 |31022 | 172.27.141.206| HS |
|02061|31026 |31026 | 172.27.141.210| ES |
|02064|31028 |MyIC_phone | Unused| HS |
|02066|31023 |31023 | Unused| HS |
|02068|31854 |31854 | Unused| ES |
+-----+--------+----------------+---------------+-----+
|Number of SIP extensions: 00008 |
+-----------------------------------------------------+
o the Neqt correponds to the equipment number of the SIP extension given during its
creation.
o the Number corresponds to the directory number of the SIP extension.
o the Name corresponds the name of the SIP extension.
o the IP address corresponds to the IP address of the SIP equipment associated to this SIP
extension, if Unused is shown, that means that no SIP equipment is registered for this
user.
o the State corresponds to the status of the SIP extension:
- HS means that the user is Out Of Service.
- ES means that the user is In Service.
The combination of the IP address and the State gives you more information:
o If the IP address is Unused and the State is ES:

- the user is created, but no SIP equipment has been registered for this user.
o If the IP address is Unused and the State is HS:
- the user has been already registered, but not anymore.
o If the IP address is full with an IP address and the State is HS:
- the user is registered, but the user is Out Of Service, this can be possible due to the
keep alive mechanism for SIP extension. After registartion, the SIP extension
doesnt send or answer to the OPTION messages.
o If the IP address is full with an IP address and the State is ES:
- the user is registrered and In Service.
csipsets d directory number returns the information only for this user.
(101)cpub_ov> csipsets d 31026
Mon Jun 4 14:08:56 CEST 2012

+-----+--------+----------------+---------------+-----+
+-----+--------+----------------+---------------+-----+
|02061|31026 |31026 | 172.27.141.210| ES |
+-----+--------+----------------+---------------+-----+
csipsets n neqt number returns the information only for this user.
(101)cpub_ov> csipsets n 2061
Mon Jun 4 14:09:54 CEST 2012

+-----+--------+----------------+---------------+-----+
+-----+--------+----------------+---------------+-----+
|02061|31026 |31026 | 172.27.141.210| ES |
+-----+--------+----------------+---------------+-----+
Ed. 12 75 TG0069
OmniPCX Enterprise
12.5.13 csipview com
Displays all the SIP extension calls.

No calls present, the display is:
(101)cpub_ov> csipview com
Mon Jun 4 14:10:28 CEST 2012

+-----+--------+----------------+---------------+--------+
|Neqt |Number |Name |IP address |Activity|
+-----+--------+----------------+---------------+--------+
+-----+--------+----------------+---------------+--------+
|Number of SIP extensions in communication: 00000 |
+--------------------------------------------------------+
Calls are present, the display is:
(101)cpub_ov> csipview com
Mon Jun 4 14:13:41 CEST 2012

+-----+--------+----------------+---------------+--------+
|Neqt |Number |Name |IP address |Activity|
+-----+--------+----------------+---------------+--------+
|02061|31026 |31026 | 172.27.141.210|CH-CC |
+-----+--------+----------------+---------------+--------+
|Number of SIP extensions in communication: 00001 |
+--------------------------------------------------------+

- the Neqt corresponds to the equipment number of the SIP extension given during
its creation.
- the Number corresponds to the directory number of the SIP extension.
- the Name corresponds the name of the SIP extension.
- the IP address corresponds to the IP address of the SIP equipment associated to
this SIP extension, if Unused is shown, that means that no SIP equipment is
registered for this user.
- the Activity corresponds to the presence of a Call Control Half Com. The Call
Control Half Comis in charge to interface the SIP world to the OXE world.
12.5.14 csiprestart
csiprestart d directory number restarts the SIP extension user:

(101)cpub_ov> csiprestart d 31026
Mon Jun 4 14:27:09 CEST 2012
csiprestart n neqt number restarts the SIP extension user:
(101)cpub_ov> csiprestart n 2061
Mon Jun 4 14:27:09 CEST 2012
The option -f exist to force the restart if needed
Ed. 12 76 TG0069
OmniPCX Enterprise
12.5.15 sipextusers
sipextusers without option returns the list of the SIP users associated to an Open Touch:
+---------+----------------------+------+----------+
| Number |Name |Ext GW|Registered|
+---------+----------------------+------+----------+
| 60999 | OXE_ADV_PROF|000001| Yes|
| 60001 | Dujardin Loulou|000001| No|
| 60002 | Lamy Chouchou|000001| No|
| 60050 | Sy Omar|000001| No|
+---------+----------------------+------+----------+
|Number of SIP USERS: 00004 |
+--------------------------------+
sipextusers -d directory number of the SIP device user:

+---------+----------------------+------+----------+
| Number |Name |Ext GW|Registered|
+---------+----------------------+------+----------+
| 60001 | Dujardin Loulou|000001| No|
+---------+----------------------+------+----------+
o the Number corresponds to the directory number of the SIP extension.

o the Name corresponds the name of the SIP extension.
o the Ext GW corresponds to the associated external SIP gateway linked to this SIP Device.
o the Registered gives the information to know if the SIP device is registered on OXE side.
12.6 Link between SIPMOTOR traces and Call Handling traces
12.6.1 Call Handling / SIPMOTOR links implementation
CALL HANDLING
Local SIP External SIP CSIP (Call Control Half

gateway gateway Com)
SIPMOTOR
The local SIP gateway link is used for the local SIP elements
- The SIP devices
- The external SIP Voice Mail
The external SIP gateways link are used for the connection between an external SIP equipment to the
OXE
- SIP carriers
Ed. 12 77 TG0069
OmniPCX Enterprise
- SIP applications (IVR, call center, etc...)
The Call Control Half Com link is used for the SIP extension users (SEPLOS), it corresponds to the CSIP
function.
According to the declaration type of the SIP equipment on the OXE, the behavior will be different on the
SIPMOTOR side, and also on the Call Handling side.
The exchanges between the SIPMOTOR and the Call Handling are different according to this declaration.
12.6.2 General view
When an issue appears in case of SIP equipment involved on the communication, it is important to check if
the problem is from the SIPMOTOR or from the Call Handling.
It is important to make the 2 traces simultaneously in case of problem.
When a call is done, we can see on the motortrace the exchange between the SIPMOTOR to the Call
handling.
Exchange from Call Handling to SIPMOTOR in SIPMOTOR traces:
[display_ipc_in] ------------ Begin ---------------

.
.
.
[display_ipc_in] ------------- End ----------------
Exchange from SIPMOTOR to Call Handling in SIPMOTOR traces:
[display_ipc_out] ------------ Begin ---------------

.
.
.
[display_ipc_out] ------------- End ----------------
Exchange from Call Handling to SIPMOTOR in Call Handling traces:

+------------------------------------------------------------+
| Message sent UA (neqt : XXXX-0) ----> SIP
Exchange from SIPMOTOR to Call Handling in Call Handling traces:
+------------------------------------------------------------+
| Message received SIP ----> UA (neqt : XXXX)
12.6.3 neqt link between SIPMOTOR and Call Handling traces
When traces are done on OXE to find the cause of the issue, it is important to link the call in the SIPMOTOR
traces and the Call Hanling traces. To do this check the neqt number (the neqt is 2250 in the following
examples)
In SIPMOTOR traces:
o For incoming call, the neqt is seen before the display_ipc_out message:
Mon May 28 14:22:38 2012 [CMotorCallManager::insertCallwithEqt] CMotorCall 2250 inserted.

Mon May 28 14:22:38 2012 11f7[sendLgEvtSipCreate] Event sent on eqt : 2250
Mon May 28 14:22:38 2012 [display_ipc_out] ------------ Begin ---------------
Mon May 28 14:22:38 2012 Id : -1
Mon May 28 14:22:38 2012 INVITE
Ed. 12 78 TG0069
OmniPCX Enterprise
- For outgoing call, the neqt is given on the display_ipc_in message from the Call
handling
Mon May 28 14:27:48 2012 [display_ipc_in] ------------ Begin ---------------

Mon May 28 14:27:48 2012 neqt : 2250 Id : -1
Mon May 28 14:27:48 2012 INVITE
In Call Handling traces:
- For incoming call, the neqt is seen with this message:
(215701:000005) SIP : message INVITE arrive sur le neqt : 2250.

(215701:000006) init_data_network
(215701:000007) init_data_network FIN
(215701:000008) SIP : ctrl_sip evt : 10752.
(215701:000009) +------------------------------------------------------------+
(215701:000010) | Message received SIP ----> UA (neqt : 2250)
- For outgoing call, the neqt is seen with this message:

(222651:000188) SIP : [send_to_motor] ipcSend resultat : 0 sur eqt : 2250
(222651:000189) SIP : [ipc_send] envoi du message : 10752.
(222651:000190) +------------------------------------------------------------+
(222651:000191) | Message sent UA (neqt : 2250-0) ----> SIP
For traces analysis, follow all the exhanges using this neqt. It is not possible to get more than one active call
using this neqt. When the call is released, this neqt is freed for another call.
The neqt number can correspond to:

o A SIP extension, the same everytime.
o A time slot of the SIP Trunk Group used on the local SIP gateway for SIP device user,
different according to which time slot is used.
o A time slot of the SIP Trunk Group used on the local SIP gateway for SIP external Voice
Mail, different according to which time slot is used.
o A time slot of the SIP Trunk Group used for the external SIP gateway, different according to
which time slot is used.
12.7 Information in the SIPMOTOR traces

In the SIPMOTOR traces, information are between [...]. These information are important to understand the
information after it and to troubleshoot the issue.
Examples:
- [CCall::receiveRequest] INVITE: The SIPMOTOR has received a SIP request and
the request is an INVITE.
- [CTransaction::changeState]: The SIPMOTOR has changed the state of a
transaction.
- [getFromHeader]: the SIPMOTOR gets the information from the FROM header in
case of SIP incoming call.
- [isDomainFromGwExt]: the SIPMOTOR checks if the information from the domain
part of the FROM corresponds to an external SIP gateway.
The information event and message are in relation with the direction of the call and the SIP message:
- event is for the Call Handling.
- message is for the SIPMOTOR.
Ed. 12 79 TG0069
OmniPCX Enterprise
The information between the [...] can more or less be understood. They can help to find the root cause of the
issue.
12.8 Follow a call on the SIPMOTOR trace

For SIP point of view, the call can be followed by the Call-ID, but in the SIPMOTOR, there are information
for calls distinctions
The neqt number is used to link the SIPMOTOR and Call Handling traces
The Session reference is used to follow the call.
o In this example, the Session reference is 1173
Mon May 28 15:21:04 2012 1173[CMotorCall::sipUriType] sip Uri.

...
Mon May 28 15:21:04 2012 1173[CMotorCall::getUserType] seplos station crypto=0.
...
Mon May 28 15:21:04 2012 1173[CMotorCall::emitInviteMessage] To: "Xlite PC" sip:31023@oxe-
ov.alcatel.fr;user=phone
...
Mon May 28 15:21:04 2012 1173[CMotorCall::inviteBuildContact] Contact: sip:31004@oxe-
ov.alcatel.fr
...
Mon May 28 15:21:04 2012
o To find this 1173 [CCall::makeGenericRequest] INVITE
Session reference for an outgoing call, search for [CMotorCall::sipUriType]
sip Uri. before the INVITE sent to the remote SIP equipment.
o To find this Session reference for an incoming call, search for [CCall::receiveRequest]
INVITE after the INVITE received from the remote SIP equipment.
The transation reference, this value can be used to follow the transaction status evolution and to get
information about this transaction
o In this example, the transaction reference is 21be
Mon May 28 15:21:04 2012 21be [CTransaction::changeState] STATE CHANGED TO INITIAL

...
Mon May 28 15:21:04 2012 21be [CTransaction::changeState] STATE CHANGED TO CALLING
...
Mon May 28 15:21:04 2012 21be [CTransaction::startTimer] Timer A is started (delay = 500 ms)
Mon May 28 15:21:04 2012 21be [CTransaction::startTimer] Timer B is started (delay = 4000 ms)
...
Mon May 28 15:21:04 2012 21be [CTransaction::changeState] STATE CHANGED TO PROCEEDING
...
Mon May 28 15:21:08 2012 21be [CTransaction::changeState] STATE CHANGED TO TERMINATED
o To find this transaction reference for an outgoing call, search for STATE CHANGED TO
INITIAL before the INVITE sent to the remote SIP equipment.
o To find this transaction reference for an incoming call, search for STATE CHANGED TO
INITIAL after the INVITE received from the remote SIP equipment.
o For one transaction, there is a pair of references. A clone reference is associated to the
main one: if the main one is 21be, the second reference is 21bf associated with the 200ok
receive or sent. This reference is seen with this message after the 200ok.
Mon May 28 15:21:08 2012 21bf [CTransaction::CTransaction] Transaction is cloned in 4 state
Ed. 12 80 TG0069
OmniPCX Enterprise
The dialog reference, this value can be used to follow the dialog evolution and to get information
about this dialog
- On this example, the dialog reference is 158a
Mon May 28 15:21:04 2012 158a [CDialog::createRequest]

Mon May 28 15:21:04 2012 158a [CDialog::buildServicesForAllRequest]
Mon May 28 15:21:04 2012 158a [CDialog::createInviteRequest]
...
Mon May 28 15:21:04 2012 158a [CDialog::onTransactionState(pTrans = 21be, previousState =
Terminated, currentState = Initial, reason = None]
...
Mon May 28 15:21:08 2012 158a [CDialog::receiveResponse]
Mon May 28 15:21:08 2012 158a [CDialog::receiveResponse] create a CONFIRMED dialog
- To find this dialog reference for an outgoing call, search for
CDialog::createRequest before the INVITE sent to the remote SIP equipment.
- To find this dialog reference for an incoming call, search for

CDialog::receiveRequest after the INVITE received from the remote SIP
equipment.
- For one dialog, there is a pair of reference, a clone reference associated to the
main one, if the main one is 158a, the second reference is 158b associated with the
200ok receive or sent. This reference is seen with this message after the 200ok.
Mon May 28 15:21:08 2012 158b [CDialog::CDialog] look for the transaction #0, transaction key
= z9hG4bKca60f1097ab026913ca3bf56995162be
This Information links the transaction to the dialog.

Mon May 28 15:21:04 2012 158a [CDialog::onTransactionState(pTrans = 21be, previousState =
- For the dialog, the transaction reference is linked. The dialog 158a is linked to the
transaction 21be.
- There is the same link for the clone references.
Mon May 28 15:21:08 2012 158b [CDialog::onTransactionState(pTrans = 21bf, previousState =
Proceeding, currentState = Completed, reason = Final resp reception]
The SIPMOTOR is using references for INVITE treatment:
The Session reference, this one is unique for the complete call (from INVITE to the 200ok of the
BYE)
The Dialog references, 2 references are used:

o The main one is created when the INVITE is sent or received
o The clone one, used to change the dialog state according to the transactions used for a new
event on the call (put on hold, transfer, etc...)
The Transaction references, the number of references depends of the call events (put on hold,
transfer, etc...)
o The main one is created when the INVITE is sent or received
o The other ones are created if an event is coming for the dialog associated (ACK, BYE,
REINVITE, REFER, etc...)
Ed. 12 81 TG0069
OmniPCX Enterprise
A permanent link is done between the Dialog (main and clone) and the Transactions (main and clones). Here
is an example for an incoming call with 2 REINVITEs and a BYE at the end:
UAC . . . . . UAS
(1) Assignation a reference to the session, dialog and transaction
(SIP set) (Proxy)
| | (4) Creation of the clone dialog and the first clone transaction,
|(1) INVITE | associated to the clone dialog
|-------------------->|
|(2) 100 Trying | (5) First clone transaction terminated
|<--------------------|
|(3) 180 Ringing |
|<--------------------| (6) Creation of the second clone transaction for the first REINVITE,
|(4) 200 OK | associated to the clone dialog
|<--------------------|
|(5) ACK | (8) Second clone transaction terminated
|-------------------->|
|(6) INVITE | (9) Creation of the third clone transaction for the second
|-------------------->| REINIVTE, associated to the clone dialog
|(7) 200 OK |
|<--------------------|
|(8) ACK |
(11) Third clone transaction terminated
|-------------------->| (12) Creation of a non-INVITE transaction (BYE) for the clone dialog
|(9) INVITE |
|-------------------->| (13) BYE transaction terminated, main transaction terminated,
|(10) 200 OK | session terminated and dialogs terminated
|<--------------------|
|(11) ACK |
|-------------------->|
|(12) BYE |
|-------------------->|
|(13) 200 OK |
|<--------------------|
12.9 Traces analyses
12.9.1 Incoming SIP call using a SIP Trunk Group: SIPMOTOR point of view
Here is an example of incoming call from a SIP device to an IPtouch.
Mon May 28 16:41:57 2012 RECEIVE MESSAGE FROM NETWORK (135.118.226.39:25648 [UDP])
----------------------utf8-----------------------
Via: SIP/2.0/UDP 135.118.226.39:25648;branch=z9hG4bK-d87543-46534e582323f252-1--d87543-;rport
Max-Forwards: 70
From: "PC_sip_device"<sip:[email protected]>;tag=f6448c0c
Call-ID: ZWEwMGI4YjUxNjMyOWRlZmEyNWEzYThmNzI4NDUzMGM.
CSeq: 1 INVITE
User-Agent: Sip Phone
Content-Length: 315
v=0
o=- 3 2 IN IP4 135.118.226.39
s=Sip_Phone
c=IN IP4 135.118.226.39
t=0 0
m=audio 7888 RTP/AVP 8 18 101
a=fmtp:18 annexb=no
a=fmtp:101 0-15
a=sendrecv
a=x-rtp-session-id:A56A9738C0BC4CEF8087E10840231621
-------------------------------------------------
Ed. 12 82 TG0069
OmniPCX Enterprise
The information RECEIVE MESSAGE FROM NETWORK (135.118.226.39:25648 [UDP]) is important to

know that the call is an incoming one from the SIP equipment 135.118.226.39 in UDP.
The SIPMOTOR checks the Call-Id to know if this INVITE is an INVITE or a REINVITE.
Mon May 28 16:41:57 2012 1153 [CCall::getDialog] Confirmed Dialog is not found (ID =
;f6448c0c)
Mon May 28 16:41:57 2012 1153 [CCall::getDialog] Initial Dialog Server not found
Here, it is an INVITE, because the dialog is not found.

The transaction and the dialog are put in place.
Mon May 28 16:41:57 2012 21a5 [CTransaction::changeState] STATE CHANGED TO INITIAL
...
Mon May 28 16:41:57 2012 156c [CDialog::onTransactionState(pTrans = 21a5, previousState =
Terminated,
Here currentState
the transaction reference is 21a5reason
= Initial, None] reference is 156c.
= dialog
and the
The transaction status is changed, because the dialog is initiated.

Mon May 28 16:41:57 2012 21a5 [CTransaction::changeState] STATE CHANGED TO PROCEEDING
Mon May 28 16:41:57 2012 21a5 [CTransaction::changeState] notifying the parent dialog
When a transaction is linked to a dialog, the transaction changed from INITIAL to PROCEEDING.
The SIPMOTOR generates the 100 Trying.

Mon May 28 16:41:57 2012 SEND MESSAGE TO NETWORK (135.118.226.39:25648 [UDP]) (BUFF LEN =
346)
----------------------utf8-----------------------
SIP/2.0 100 Trying
From: "PC_sip_device" <sip:[email protected]>;tag=f6448c0c
CSeq: 1 INVITE
Via: SIP/2.0/UDP 135.118.226.39:25648;received=135.118.226.39;branch=z9hG4bK-d87543-
46534e582323f252-1--d87543-;rport=25648
Content-Length: 0
The SIPMOTOR checks the Session Timer for the call.
-------------------------------------------------
Mon May 28 16:41:57 2012 [CSessionTimerContext::CSessionTimerContext] New

CSessionTimerContext from request (Server, UA)
Mon May 28 16:41:57 2012 [CSessionTimerContext::updateAfterRefreshReception] Update
CSessionTimerContext (refresh reception)
Mon May 28 16:41:57 2012 [CSessionTimerContext::updateSessionExpires] Session-Expires updated
: 0
Mon May 28 16:41:57 2012 [CSessionTimerContext::setRefreshMethod] Allow refreshMethod=INVITE
In this case, the SIP equipment doesnt send Session timer information because the value is 0 (updated :
0).
The SIPMOTOR makes the link between the dialog, transaction, the branch and the Cseq number.
Mon May 28 16:41:57 2012 156c [CDialog::addTransaction] added transaction 21a5 with branch
z9hG4bK-d87543-46534e582323f252-1--d87543-, with CSeq 1
The branch is a parameter added to the via to identify it. Regarding rfc3261, all the branch values must
start by z9hG4bK.
The CSeq is used to identify and to order a transaction, it consists of a sequence number and a method.
Ed. 12 83 TG0069
OmniPCX Enterprise
The SIPMOTOR checks for which OXE equipment the call is from.
Mon May 28 16:41:57 2012 [isDomainFromGwExt] Host from request is : 172.27.142.53.
Mon May 28 16:41:57 2012 [isDomainFromGwExt] User from request is : 31024
Mon May 28 16:41:57 2012 [domain not from an External Gateway.
Mon May 28 16:41:57 2012 1153[CMotorCall::setFilterUsedMode] To be traced = 0
Mon May 28 16:41:57 2012 1153[CMotorCall::initOfUserType] values are reseted
Mon May 28 16:41:57 2012 [getFromHeader] displayName="PC_sip_device".
Mon May 28 16:41:57 2012 [getFromHeader] [email protected].
Mon May 28 16:41:57 2012 [getFromHeader] clirPresent=0.
Mon May 28 16:41:57 2012 [isAddrInDico] user=31024 host=oxe-ov.alcatel.fr
Mon May 28 16:41:57 2012 [isUserInDico] [email protected]
Mon May 28 16:41:57 2012 [isUserInDico] found in the dictionnary.
Mon May 28 16:41:57 2012 [isAddrInDico] sip device station OK
-The SIPMOTOR checks first if the domain part from the PAI, and of the FROM if no PAI,
to see if the call is for an external SIP gateway.
- Here, we can see that the call is from a SIP Device.
The SIPMOTOR checks for whom the call is done .
Mon May 28 16:41:57 2012 [isAddrInDico] user=31004 host=oxe-ov.alcatel.fr
Mon May 28 16:41:57 2012 [isUserInDico] [email protected]
Mon May 28 16:41:57 2012 isUserInDico] NOT found in the dictionnary.
Mon May 28 16:41:57 2012 [isAddrInDico] other sip user
Here the call is for an other sip user, that means the call is for a non SIP user, corresponding to a legacy
set (IPtouch).
The SIPMOTOR checks the number of licenses available.
Mon May 28 16:41:57 2012 1153[CMotorCall::methodInviteReceived] nb available licenses=25
Here the number of licenses is 25, that means, 25 calls are possible on SIP using a SIP Trunk Group or
SEPLOS users.
The SIPMOTOR checks if the IP address received is managed on an IP domain.
Mon May 28 16:41:57 2012 The recevied host 135.118.226.39

Mon May 28 16:41:57 2012 Trying to find the ip address in domain list
Mon May 28 16:41:57 2012 The entry dom : 141 add_type=1
Mon May 28 16:41:57 2012 The entry dom ip low :172.27.141.165
Mon May 28 16:41:57 2012 The entry ipaddress from low :135.118.226.39
Mon May 28 16:41:57 2012 The entry compare :1
Mon May 28 16:41:57 2012 The entry compare 2 :0
Mon May 28 16:41:57 2012 iplink_is_good_range_for_reg
...
Mon May 28 16:41:57 2012 The user domain is 142
Here, the IP address of the SIP equipment corresponds to the IP domain 142.
If the IP address doesnt match an IP domain, the SIPMOTOR returns:
Mon May 28 16:41:57 2012 The user is ipadd not in any Domain range return state as -1
Ed. 12 84 TG0069
OmniPCX Enterprise
The SIPMOTOR checks the SDP received on the INVITE.

Mon May 28 16:41:57 2012 [checkSdpValidity] Media 0 type 1 contains 3 formats.
Mon May 28 16:41:57 2012 [checkSdpValidity] Format : 8.
Mon May 28 16:41:57 2012 1153[CMotorCall::isCryptoAuthorized] user crypto=0.
Mon May 28 16:41:57 2012 [convertSdpIntoTsdp] No Direction in the session part.
Mon May 28 16:41:57 2012 [convertSdpIntoTsdp] Check the direction in Session part - result:0.
Mon May 28 16:41:57 2012 [convertSdpIntoTsdp] media AUDIO detected (previous crypto=0).
Mon May 28 16:41:57 2012 [convertAudioMedia] The audio media contains 3 format(s).
Mon May 28 16:41:57 2012 [convertAudioMedia] Format 0 is 8.
Mon May 28 16:41:57 2012 [convertAudioMedia] 101.
Mon May 28 16:41:57 2012 [convertAudioMedia] Format is DTMF:101.
Mon May 28 16:41:57 2012 [convertAudioMedia] Direction is sendrecv.
Mon May 28 16:41:57 2012 [convertAudioMedia] Connection address retrieved in sdp:
135.118.226.39.
Mon May 28 16:41:57 2012 [convertIPStrIntoTuipv] 135.118.226.39 => 135.118.226.39
Mon May 28 16:41:57 2012 [display_sdp] address =135.118.226.39
Mon May 28 16:41:57 2012 [display_sdp] direction=0.
Mon May
The SDP28 16:41:57
contains 2012SDP
in this [convertSdpIntoTsdp] only (8,
three formats of medias one18
media takenthe
and 101), into account
direction is sendrecv
xxx meaning
crypto_index=0 clear media=1
in both direction and the IP address of connection is 135.118.226.39.
Mon May 28 16:41:57 2012 [convertSdpIntoTsdp] crypto_index=0 clear media=1.
The message to Call Handling is prepared and sent to it.
Mon May 28 16:41:57 2012 1153[sendLgEvtSipCreate] Event sent on eqt : 2250

Mon May 28 16:41:57 2012 Id : -1
Mon May 28 16:41:57 2012 INVITE
Mon May 28 16:41:57 2012 REQUEST URI : <> [email protected]:5060 ; user=name
Mon May 28 16:41:57 2012 FROM : <PC_sip_device> [email protected]:5060 ; user=name
Mon May 28 16:41:57 2012 TO : <"31004"> [email protected]:5060 ; user=name
Mon May 28 16:41:57 2012 CAC : 0
Mon May 28 16:41:57 2012 CAC ADDRESS :
Mon May 28 16:41:57 2012 CAC-CSBU info : UNKNOWN
Mon May 28 16:41:57 2012 CLIR : 0
Mon May 28 16:41:57 2012 Prack Required : 0
Mon May 28 16:41:57 2012 Allow Update : 0
Mon May 28 16:41:57 2012 SDP :
Mon May 28 16:41:57 2012 ADDRESS : 135.118.226.39 :7888
Mon May 28 16:41:57 2012 ALGOS :
Mon May 28 16:41:57 2012 PCMA
Mon May 28 16:41:57 2012 G729
Mon May 28 16:41:57 2012 101
Mon May 28 16:41:57 2012 DIRECTION : SEND & RECEIVE
Mon May 28 16:41:57 2012 crypto index : 0
Mon May 28 16:41:57 2012 N_GW_EXT : -1
Mon May 28 16:41:57 2012 [display_ipc_out] ------------- End ----------------
The call is sent to the Call handling on neqt 2250, regarding the type of SIP equipment detected by the
SIPMOTOR, some information are added or not on this message.
All the information about this call are sent to the Stand-By CPU.
Mon May 28 16:41:57 2012 SendToSipgwCpuSec: Message sent to the STAND-BY CPU
Mon May 28 16:41:57 2012 [receiveInviteMessage] send RemoteSdp to the StandBy.
Mon May 28 16:41:57 2012 SendToSipgwCpuSec: Message sent to the STAND-BY CPU
The information are sent to the Stand-By, like this, in case of bascul the SIP call will not be lost and known
on the new main CPU
The Call handling sends back an answer for this INVITE.

Mon May 28 16:41:57 2012 neqt : 2250 Id : -1
Mon May 28 16:41:57 2012 INFORMATIONAL
Mon May 28 16:41:57 2012 xx : 80
Mon May 28 16:41:57 2012 RELATIVE REQUEST : INVITE
Mon May 28 16:41:57 2012 [display_ipc_in] ------------- End ----------------
Ed. 12 85 TG0069
OmniPCX Enterprise
A 180 Ringing is sent to the SIPMOTOR without SDP
547)
----------------------utf8-----------------------
SIP/2.0 180 Ringing
To: "31004" <sip:[email protected]>;tag=15654dedb5658c165fbba7b0026e6ae9
CSeq: 1 INVITE
46534e582323f252-1--d87543-;rport=25648
Content-Length: 0
A 180 Ringing is sent to the SIPMOTOR without SDP
-------------------------------------------------
For each SIP call event, a message is send to the Stand-By CPU.
Mon May 28 16:41:57 2012 [receiveInformationalEvent] UpdateContext send on the StandBy.
The Call handling sends a new answer for this INVITE.

Mon May 28 16:41:58 2012 neqt : 2250 Id : -1
Mon May 28 16:41:58 2012 SUCCESSFUL
Mon May 28 16:41:58 2012 xx : 0
Mon May 28 16:41:58 2012 RELATIVE REQUEST : INVITE
Mon May 28 16:41:58 2012 CLIR : 0
Mon May 28 16:41:58 2012 COLP : 1
Mon May 28 16:41:58 2012 SDP :
Mon May 28 16:41:58 2012 ADDRESS : 172.27.142.64 :32514
Mon May 28 16:41:58 2012 ALGOS :
Mon May 28 16:41:58 2012 G729
Mon May 28 16:41:58 2012 101
Mon May 28 16:41:58 2012 DIRECTION : SEND & RECEIVE
Mon May 28 16:41:58 2012 crypto index : 0
A 200 ok is sent to the SIPMOTOR with SDP
The SIPMOTOR checks if the SDP given is compatible with the SDP received in the INVITE.
Mon May 28 16:41:58 2012 1153[CMotorCall::makeResponseSdp] Audio media.

Mon May 28 16:41:58 2012 1153[CMotorCall::appendAudioAttributToMedia] Direction: 0.
Mon May 28 16:41:58 2012 1153[CMotorCall::appendAudioAttributToMedia] format 101
Mon May 28 16:41:58 2012 1153[CMotorCall::makeResponseSdp] fromSdp.getMediaDesciprionCount :1
Mon May 28 16:41:58 2012 [sameCodec] accepted Format : 18.
Mon May 28 16:41:58 2012 [sameCodec] requested Format : 8.
Mon May 28 16:41:58 2012 [sameCodec] requested Format : 18.
Mon May 28 16:41:58 2012 [sameCodec] same Format.
Mon May 28 16:41:58 2012 1153[CMotorCall::mediaAccepted] Media accepted: m=audio 32514
RTP/AVP 18 101
a=sendrecv
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=ptime:20
a=maxptime:40
.
The codecs from the INVITE were 8 and 18, on the answer we have 18, in that case the call is accepted by
SIPMOTOR for SDP point of view.
The SIPMOTOR is changing the status of the dialog.
Ed. 12 86 TG0069
OmniPCX Enterprise
Mon May 28 16:41:58 2012 156c [CDialog::createResponse] create a CONFIRMED dialog
Due to this, the dialog reference and transaction reference are changed (internal SIPMOTOR functionning).
Mon May 28 16:41:58 2012 156d [CDialog::CDialog] look for the transaction #0, transaction key
= z9hG4bK-d87543-46534e582323f252-1--d87543-
Mon May 28 16:41:58 2012 156d [CDialog::CDialog] copy the transaction #0, transaction key =
z9hG4bK-d87543-46534e582323f252-1--d87543-
Mon May 28 16:41:58 2012 21a6 [CTransaction::CTransaction] Transaction is cloned in 4 state
The dialog reference is changed form 156c to 156d.

The transaction reference is changed from 21a5 to 21a6.
The SIPMOTOR is changing the status of the dialog.
1338216118 -> Mon May 28 16:41:58 2012 SEND MESSAGE TO NETWORK (135.118.226.39:25648 [UDP])
(BUFF LEN = 974)
----------------------utf8-----------------------
SIP/2.0 200 OK
P-Asserted-Identity: "IPtouch 172.27.1" <sip:[email protected];user=phone>
To: "31004" <sip:[email protected]>;tag=15654dedb5658c165fbba7b0026e6ae9
CSeq: 1 INVITE
46534e582323f252-1--d87543-;rport=25648
Content-Length: 241
v=0
o=OXE 1338216117 1338216117 IN IP4 172.27.142.53
s=abs
c=IN IP4 172.27.142.64
t=0 0
a=sendrecv
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=ptime:20
a=maxptime:40
-------------------------------------------------
The 200ok sent to the remote SIP equipment is generated with information from the INVITE received and
from the 200ok answer from the Call Handling.
The SIPMOTOR changes the status of the transaction.
Mon May 28 16:41:58 2012 21a6 [CTransaction::changeState] STATE CHANGED TO COMPLETED
The retransmission timers are started.
Mon May 28 16:41:58 2012 21a6 [CTransaction::startTimer] Timer G is started (delay = 500 ms)
Mon May 28 16:41:58 2012 21a6 [CTransaction::startTimer] Timer H is started (delay = 32000
ms)
Ed. 12 87 TG0069
OmniPCX Enterprise
The SIPMOTOR receives a ACK for the 200ok.
----------------------utf8-----------------------
Via: SIP/2.0/UDP 135.118.226.39:25648;branch=z9hG4bK-d87543-b00f692e5d3a246e-1--d87543-;rport
Max-Forwards: 70
To: "31004"<sip:[email protected]>;tag=15654dedb5658c165fbba7b0026e6ae9
From: "PC_sip_device"<sip:[email protected]>;tag=f6448c0c
CSeq: 1 ACK
Content-Length: 0
-------------------------------------------------
Mon May 28 16:41:59 2012 21a6 [CTransaction::changeState] STATE CHANGED TO TERMINATED
The retransmission timers are freed.

Mon May 28 16:41:59 2012 21a6 [CTransaction::freeTimerToken] Timer G is freed
Mon May 28 16:41:59 2012 21a6 [CTransaction::freeTimerToken] Timer H is freed
The SIPMOTOR changes the status of the dialog.

Mon May 28 16:41:59 2012 156d [CDialog::receiveAckRequest] the INVITE request is terminated
The ACK is sent to the Call Handling.

Mon May 28 16:41:59 2012 Id : -1
Mon May 28 16:41:59 2012 ACK
After call establishment, the call can be released by the OXE or by the remote SIP equipment.
Call released by the Call Handling:
- The BYE is sent from the Call Handling.

Mon May 28 16:42:00 2012 neqt : 2250 Id : -1
Mon May 28 16:42:00 2012 BYE
- Creation of a new transaction for the BYE.

The BYE is a new transaction for a SIP call, in that case, the transaction reference it is 21a7, and the status
is INITIAL.
- The BYE is sent to the remote SIP equipment.

454)
----------------------utf8-----------------------
BYE sip:[email protected]:25648 SIP/2.0
To: sip:[email protected];tag=f6448c0c
From: "31004" <sip:[email protected]>;tag=15654dedb5658c165fbba7b0026e6ae9
CSeq: 1948273321 BYE
Via: SIP/2.0/UDP 172.27.142.53;branch=z9hG4bK9f0b6b39121b23d361a5f6a8101aaa90
Max-Forwards: 70
Content-Length: 0
-------------------------------------------------
Ed. 12 88 TG0069
OmniPCX Enterprise
- The SIPMOTOR changes the transaction state.

Mon May 28 16:42:00 2012 21a7 [CTransaction::changeState] STATE CHANGED TO TRYING
- The retransmission timers are started.
Mon May 28 16:42:00 2012 21a7 [CTransaction::startTimer] Timer E is started (delay = 500 ms)
Mon May 28 16:42:00 2012 21a7 [CTransaction::startTimer] Timer F is started (delay = 16000
ms)
- The 200ok of the BYE request is received from the remote SIP equipment.
- The SIPMOTOR changes this transaction state.

- The retransmission timers are freed.
Mon May 28 16:42:00 2012 21a7 [CTransaction::freeTimerToken] Timer E is freed

Mon May 28 16:42:00 2012 21a7 [CTransaction::freeTimerToken] Timer F is freed
- The 200ok of the BYE request is sent to the Call Handling.

Mon May 28 16:42:00 2012 Id : -1
Mon May 28 16:42:00 2012 xx : 0
Mon May 28 16:42:00 2012 RELATIVE REQUEST : BYE
Mon May 28 16:42:00 2012 CLIR : 0
Mon May 28 16:42:00 2012 COLP : 0
- The Call Handling sends a message to the SIPMOTOR to release the neqt associated to
this SIP call
Mon May 28 16:42:00 2012 neqt : 2250 Id : -1
Mon May 28 16:42:00 2012 SIP EQT RELEASED
- The SIPMOTOR acknowledges the release of the neqt

Mon May 28 16:42:00 2012 Id : -1
Mon May 28 16:42:00 2012 SIP_EQT_RELEASE_ACK
- The SIPMOTOR kills the SIP call
Mon May 28 16:42:00 2012 [CMotorCallManager::onIncomingEvent] killSession.

Mon May 28 16:42:00 2012 1153 [CCall::killSession]
- The SIPMOTOR changes the state of the transactions

...
Call released by the remote SIP equipment:
- The BYE is received from the remote SIP equipment.
Ed. 12 89 TG0069
OmniPCX Enterprise
----------------------utf8-----------------------
BYE sip:oxe-ov.alcatel.fr SIP/2.0
Via: SIP/2.0/UDP 135.118.226.39:25648;branch=z9hG4bK-d87543-cf501c2f3311d050-1--d87543-;rport
Max-Forwards: 70
To: "31004"<sip:[email protected]>;tag=ba904e80f620e0f32593273ec97e818d
From: "PC_sip_device"<sip:[email protected]>;tag=b05ced13
Call-ID: NTEwZjI0M2VjZGY1YzExZTMzZWVjOGY2YzM0MmI5ODU.
CSeq: 2 BYE
Content-Length: 0
-------------------------------------------------
- The SIPMOTOR checks if the dialog is already exist.
Mon May 28 16:42:00 2012 1153 [CCall::getDialog] Confirmed Dialog found
Creation of a new transaction for the BYE.

The BYE is a new transaction for a SIP call. In that case, the transaction reference it is 21a7, and the status
is INITIAL.
Mon May 28 16:42:00 2012 21a7 [CTransaction::changeState] STATE CHANGED TO TRYING
- The BYE is sent to the Call handling.

Mon May 28 16:42:00 2012 Id : -1
Mon May 28 16:42:00 2012 BYE
- The Call Handling answers to the SIPMOTOR.

Mon May 28 16:42:00 2012 neqt : 2250 Id : -1
Mon May 28 16:42:00 2012 xx : 0
Mon May 28 16:42:00 2012 RELATIVE REQUEST : BYE
Mon May 28 16:42:00 2012 CLIR : 0
Mon May 28 16:42:00 2012 COLP : 0
Mon May 28 16:42:00 2012 [display_ipc_in] ------------- End ---------------
- The SIPMOTOR sends the 200 ok of the BYE to the remote SIP equipment.
Tue May 29 14:21:53 2012 SEND MESSAGE TO NETWORK (135.118.226.39:25648 [UDP]) (BUFF LEN =
546)
----------------------utf8-----------------------
SIP/2.0 200 OK
To: "31004" <sip:[email protected]>;tag=ba904e80f620e0f32593273ec97e818d
From: "PC_sip_device" <sip:[email protected]>;tag=b05ced13
Call-ID: NTEwZjI0M2VjZGY1YzExZTMzZWVjOGY2YzM0MmI5ODU.
CSeq: 2 BYE
cf501c2f3311d050-1--d87543-;rport=25648
Content-Length: 0
-------------------------------------------------
this SIP call
Ed. 12 90 TG0069
OmniPCX Enterprise

Mon May 28 16:42:00 2012 neqt : 2250 Id : -1
Mon May 28 16:42:00 2012 SIP EQT RELEASED

Mon May 28 16:42:00 2012 Id : -1
Mon May 28 16:42:00 2012 SIP_EQT_RELEASE_ACK
Mon May 28 16:42:00 2012 [CMotorCallManager::onIncomingEvent] killSession.

Mon May 28 16:42:00 2012 1153 [CCall::killSession]

...
12.9.2 Incoming SIP call using a SIP Trunk Group: Call Handling point of view
Here is an example of incoming call from a SIP device to an IPtouch.
Traces option used :

>tuner km
>tuner clear-traces
>trc i
>actdbg all=off
>tuner +cpu +cpl +at hybrid=on
>actdbg sip=on abcf=on isdn=on voip=on
>mtracer -a
The call arrives on the SIPMOTOR, and sent to the Call Handling
(292779:000028) +------------------------------------------------------------+
(292779:000030) | INVITE : [email protected]:5060 ; user=name
(292779:000031) | From : <PC_sip_device> [email protected]:5060 ; user=name
(292779:000032) | To : <"31004"> [email protected]:5060 ; user=name
(292779:000033) +------------------------------------------------------------+
(292779:000034) | SDP :
(292779:000035) | @IP:port = 135.118.226.39:7888
(292779:000036) | ALGOS :
(292779:000037) | PCMA
(292779:000038) | G729
(292779:000039) | DTMF : 101
(292779:000040) | DIRECTION : SEND & RECEIVE
(292779:000041) | cac : false
(292779:000042) | Prack_Required: 0
(292779:000043) | Allow_UPDATE: 0
(292779:000044) | autoAnswer : false
(292779:000045) +------------------------------------------------------------+
All the information received on the Call handling are given by the SIPMOTOR, the SIPMOTOR has already
done an analysis and a treatment of these information.
We can see the neqt used to make the link between the SIPMOTOR trace and Call Handling trace (here
2250)
Ed. 12 91 TG0069
OmniPCX Enterprise
The Call Handling checks the received payload.
(292779:000046) ctrl_payloads_on_reception_sdp payloads_recu[0]=0

(292779:000047) ctrl_payloads_on_reception_sdp payloads_recu[1]=17
(292779:000048) ctrl_payloads_on_reception_sdp dtmf_payload 101
When a call uses a SIP Trunk Group, the call is treated throught this SIP Trunk Group like a call on a
legacy T2 Trunk Group.
The Call Handling generates a SETUP message with the information given in the INVITE. The SETUP differs
if the Trunk Group is ISDN or ABCF.
___________________________________________________________________________
| (292779:000128) Concatenated-Physical-Event :
| long: 177 desti: 0 source: 0 cryst: 19 cpl: 0 us: 0 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 00 15
| SENDING COMPLETE
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=2) a0 90 -> T2 : No B channel
| IE:[1c] FACILITY (l=84)
| [91] Discriminator of supplementary service applications
| [aa] NFE (l=6):
| [80] Source Entity (l=1) End_PTNX
| [82] Destination Entity (l=1) End_PTNX
| [8b] Interpretation APDU (l=1): DISCARD (0)
| [a1] INVOKE (l=25):
| Invoke Ident. : 2ee0 (12000)
| OP: ECMA RO_CALLING_NAME (0)
| [80] Name presentation allowed (l=13) 'PC_sip_device'
| [a1] INVOKE (l=43):
| Invoke Ident. : 0001 (1)
| OP: ALCATEL RO_CLASSMARKS (1)
| [30] Sequence (l=30)
| [80] Feature identifier (l=5) 06 04 70 1f 20
| [82] Cug (l=1) 00
| [ab] Sequence of Project data (l=18)
| OP :RO_CLASSMARKS_SUPPLEMENTARY_INFO_1 (134623475)
| [80] Trunk group feature (l=5) 06 00 00 20 04
| [83] Current entity (l=1) 01
| IE:[6c] CALLING_NUMBER (l=7) -> 09 81 Num : 31024
| IE:[70] CALLED_NUMBER (l=6) -> 80 Num : 31004
| IE:[7d] HLC (l=2) 91 81
| [95] Locking shift. codeset : 5
| IE:[32] EI_PARTY_CATEGORY (l=1) -> EXTENSION (1)
| [9f] Non-locking shift. codeset : 7
| IE:[06] EI_IP_PAYLOADS (l=2) : (COMP/ECE/VAD) -> G711a/0/0 G729/0/0
| IE:[0a] EI_RTP_INFO (l=30)
| -> stop_packet=0 stop_rtp=0 h323=0 wc=1 rf=0 udp=1 rqm=0
| -> Transm_Bande=1 detection_Q23=1 dtmf_payload=101
| -> Port RTP = 7888, IPv4 : 135. 118. 226. 39.
| -> Port RTCP SR = 7889, IPv4 : 135. 118. 226. 39.
| -> Port RTCP RR = 7889, IPv4 : 135. 118. 226. 39.
| -> Port Fax = 0, IPv4 : 0. 0. 0. 0.
|______________________________________________________________________________
When the SIP message is from the SIPMOTOR to the Call Handling, the direction is message sent.
On this setup all the information are present:
Ed. 12 92 TG0069
OmniPCX Enterprise
- The calling and called number

- The codecs
- The RTP connection information
- ...
The Call Ref is identical for outgoing and incoming messages (here Call ref : 00 15).
The CALL PROC is present.

______________________________________________________________________________
| tei: 0 >>>> message received : CALL PROC (02) Call ref : 00 15
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=2) a0 90 -> T2 : No B channel
|______________________________________________________________________________
The ALERT is generated for this call.
______________________________________________________________________________
| tei: 0 >>>> message received : ALERT (01) Call ref : 00 15
|______________________________________________________________________________
|
.|| IE:[1c] FACILITY (l=64)
[91] Discriminator of supplementary service applications
| [aa] NFE (l=6):
| [a1] INVOKE (l=28):
| OP: ECMA RO_CALLED_NAME (1)
| [80] Name presentation allowed (l=16) 'IPtouch 172.27.1'
| [a1] INVOKE (l=20):
| [80] Feature identifier (l=5) 06 44 7e 1f 04
| IE:[1e] PROGRESS_ID (l=2) 80 88
| IE:[06] EI_IP_PAYLOADS (l=1) -> G729 Ece 1 Vad 0
|
The -> Transm_Bande=1
ALERT detection_Q23=1
has no RTP information, dtmf_payload=101
because the SDP on 18x is not set to true.
|______________________________________________________________________________
The ALERT is transformed on a SIP message to the SIPMOTOR, but first the Call Handling select
the good neqt to send the message to the SIPMOTOR.

...
(292779:000323) +------------------------------------------------------------+
(292779:000325) | Informational 180
(292779:000326) | RELATIVE REQUEST : INVITE
(292779:000327) | No SDP
(292779:000328) +------------------------------------------------------------+
The CONNECT is generated for this call.
Ed. 12 93 TG0069
OmniPCX Enterprise
_____________________________________________________________________________
| tei: 0 >>>> message received : CONNECT (07) Call ref : 00 15
|______________________________________________________________________________
|
| IE:[1c] FACILITY (l=64)
| [91] Discriminator of supplementary service applications
| [aa] NFE (l=6):
| [a1] INVOKE (l=28):
| OP: ECMA RO_CONNECTED_NAME (2)
| [80] Name presentation allowed (l=16) 'IPtouch 172.27.1'
| [a1] INVOKE (l=20):
| [80] Feature identifier (l=5) 06 44 7e 1f 04
| IE:[4c] CONNECTED_NUMBER (l=7) -> 00 81 Num : 31004
| IE:[06] EI_IP_PAYLOADS (l=1) -> G729 Ece 1 Vad 0
| -> Transm_Bande=1 detection_Q23=1 dtmf_payload=101
| -> Port RTP = 32514, IPv4 : 172. 27. 142. 64.
| -> Port RTCP SR = 32515, IPv4 : 172. 27. 142. 64.
| -> Port RTCP RR = 32515, IPv4 : 172. 27. 142. 64.
| -> Port Fax = 0, IPv4 : 0. 0. 0. 0.
|______________________________________________________________________________
The CONNECT has RTP information. These RTP information are used to create the SDP.
The CONNECT is transformed to a SIP message towards the SIPMOTOR, but first the Call
Handling selects the good neqt to send the message to the SIPMOTOR.

...
(292789:000554) +------------------------------------------------------------+
(292789:000556) | Successful 200
(292789:000558) +------------------------------------------------------------+
(292789:000559) | SDP :
(292789:000560) | @IP:port = 172.27.142.64:32514
(292789:000561) | ALGOS :
(292789:000562) | G729
(292789:000563) | DTMF : 101
(292789:000565) | AssertedAddress : <IPtouch 172.27.1> [email protected]:5060
(292789:000566) | COLP
(292789:000567) +------------------------------------------------------------+
The SIPMOTOR receives the ACK from the remote SIP equipment, and this message.
(292794:000580) +------------------------------------------------------------+
(292794:000582) | ACK
(292794:000583) +------------------------------------------------------------+
Ed. 12 94 TG0069
OmniPCX Enterprise
The ACK is transformed to a CONNECT ACK
________________________________________________________________________
| tei: 0 <<<< message sent : CONNECT ACK (0f) Call ref : 00 15
|______________________________________________________________________________
Call released by the Call Handling:
- The DISCONNECT is generated on the call.
______________________________________________________________________________
| tei: 0 >>>> message received : DISCONNECT [45] Call ref : 00 15
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 80 90 80 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________
- The DISCONNECT is transformed to a SIP message towards the SIPMOTOR, but first
the Call Handling selects the good neqt to send the message to the SIPMOTOR.
...
(292810:000684) +------------------------------------------------------------+
(292810:000686) | BYE
(292810:000687) +------------------------------------------------------------+
- Answer of the BYE received by the SIPMOTOR and transmited to the Call Handling.
(292811:000692) +------------------------------------------------------------+
(292811:000694) | Successful 200
(292811:000695) | RELATIVE REQUEST : BYE
(292811:000696) | No SDP
(292811:000697) +------------------------------------------------------------+
- Answer of the BYE is transformed to a Call Handling message for a RELEASE.

______________________________________________________________________________
| tei: 0 <<<< message sent : RELEASE [4d] Call ref : 00 15
|______________________________________________________________________________
|
|______________________________________________________________________________
- Acknowledge of the RELEASE by a REL COMP.

______________________________________________________________________________
| tei: 0 >>>> message received : REL COMP [5a] Call ref : 00 15
|______________________________________________________________________________
|
|______________________________________________________________________________
- After the REL COMP, the call is completely ended on Call Handling side.
Ed. 12 95 TG0069
OmniPCX Enterprise
According to the problem, more options can be used on the Call Handling trace, so that more information are
displayed. In the previous example, the minimum of options were set to see the exchanges between the
SIPMOTOR and the Call Handling.
It is important to understand the link between SIPMOTOR traces and Call Handling traces to make a
minimum of analysis before opening a Service Request.
12.9.3 Incoming SIP call in case of SIP extension: SIPMOTOR point of view
Here is an example of incoming call from a SIP extension to an IPtouch.
Tue Jun 26 08:03:05 2012 RECEIVE MESSAGE FROM NETWORK (135.118.226.21:61618 [UDP])
----------------------utf8-----------------------
Via: SIP/2.0/UDP 135.118.226.21:61618;branch=z9hG4bK-d87543-9c72747c0d38bb69-1--d87543-;rport
Max-Forwards: 70
From: "PC_sip_extenstion"<sip:[email protected]>;tag=c850be7c
Call-ID: MzBlMzgzNjY5NDg2NmE0NTRiMGYyYjMyOThjZmY4MWU.
CSeq: 1 INVITE
Content-Length: 317
v=0
o=- 5 2 IN IP4 135.118.226.21
s=SIP Phone
c=IN IP4 135.118.226.21
t=0 0
m=audio 46194 RTP/AVP 8 18 101
a=fmtp:18 annexb=no
a=fmtp:101 0-15
a=sendrecv
The information RECEIVE MESSAGE FROM NETWORK
------------------------------------------------- (135.118.226.21:61618[UDP]) is important to
know that the call is an incoming one from the SIP equipment 135.118.226.21 in UDP.
The OXE checks the Call-Id to know if this INVITE is an INVITE or a REINVITE.
Tue Jun 26 08:03:05 2012 11ef [CCall::getDialog] Confirmed Dialog is not found (ID = ;c850be7c)
Tue Jun 26 08:03:05 2012 11ef [CCall::getDialog] Initial Dialog Server not found
Here it is an INVITE because the dialog is not found.
The transaction and the dialog are put in place.

Tue Jun 26 08:03:05 2012 210c [CTransaction::changeState] STATE CHANGED TO INITIAL
...
Tue Jun 26 08:03:05 2012 15fd [CDialog::onTransactionState(pTrans = 210c, previousState =
Here, the transaction reference is 210c and the dialog reference is 15fd.
The transaction status is changed, because the dialog is initiated.

Tue Jun 26 08:03:05 2012 210c [CTransaction::changeState] STATE CHANGED TO PROCEEDING
Tue Jun 26 08:03:05 2012 210c [CTransaction::changeState] notifying the parent dialog
Ed. 12 96 TG0069
OmniPCX Enterprise
When a transaction is linked to a dialog, the transaction changed from INITIAL to PROCEEDING.
The SIPMOTOR generates the 100 Trying.
Tue Jun 26 08:03:05 2012 SEND MESSAGE TO NETWORK (135.118.226.21:61618 [UDP]) (BUFF LEN =
350)
----------------------utf8-----------------------
SIP/2.0 100 Trying
From: "PC_sip_extenstion" <sip:[email protected]>;tag=c850be7c
CSeq: 1 INVITE
9c72747c0d38bb69-1--d87543-;rport=61618
Content-Length: 0
-------------------------------------------------
The 100 Trying is generated by the SIPMOTOR.
The SIPMOTOR checks the Session Timer for the call.
Tue Jun 26 08:03:05 2012 [CSessionTimerContext::CSessionTimerContext] New

CSessionTimerContext from request (Server, UA)
Tue Jun 26 08:03:05 2012 [CSessionTimerContext::updateAfterRefreshReception] Update
CSessionTimerContext (refresh reception)
Tue Jun 26 08:03:05 2012 [CSessionTimerContext::updateSessionExpires] Session-Expires updated
: 0
Tue Jun 26 08:03:05 2012 [CSessionTimerContext::setRefreshMethod] Allow refreshMethod=INVITE
In this case, the SIP equipment doesnt send Session timer information because the value is 0 (updated :
0).
The SIPMOTOR makes the link between the transaction, the branch and the Cseq number.
Tue Jun 26 08:03:05 2012 15fd [CDialog::addTransaction] added transaction 210c with branch
z9hG4bK-d87543-9c72747c0d38bb69-1--d87543-, with CSeq 1
The branch is a parameter added to the via to identify it. Regarding rfc3261, all the branch values must
start with z9hG4bK.
The CSeq is used to identify and to order a transaction. It consists of a sequence number and a method.
The SIPMOTOR checks from which OXE equipment the call is.
Tue Jun 26 08:03:05 2012 [isDomainFromGwExt] Host from request is : 172.27.141.151.

Tue Jun 26 08:03:05 2012 [isDomainFromGwExt] User from request is : 31023
Tue Jun 26 08:03:05 2012 [domain not from an External Gateway.
Tue Jun 26 08:03:05 2012 11ef[CMotorCall::setFilterUsedMode] To be traced = 0
Tue Jun 26 08:03:05 2012 11ef[CMotorCall::initOfUserType] values are reseted
Tue Jun 26 08:03:05 2012 [getFromHeader] displayName="PC_sip_extenstion".
Tue Jun 26 08:03:05 2012 [getFromHeader] [email protected].
Tue Jun 26 08:03:05 2012 [getFromHeader] clirPresent=0.
Tue Jun 26 08:03:05 2012 [isAddrInDico] user=31023 host=oxe-ov.alcatel.fr
Tue Jun 26 08:03:05 2012 [isUserInDico] [email protected]
Tue Jun 26 08:03:05 2012 [isUserInDico] found in the dictionnary.
Tue Jun 26 08:03:05 2012 [isAddrInDico] seplos station OK
Here, we can see that the call is from a SEPLOS station.
The SIPMOTOR checks the number of available licenses.
Tue Jun 26 08:03:05 2012 11ef[CMotorCall::methodInviteReceived] nb available licenses=25
Ed. 12 97 TG0069
OmniPCX Enterprise
Here the number of licenses is 25, that means, 25 calls are possible on SIP using a SIP Trunk Group or
SEPLOS users
The SIPMOTOR checks if the received IP address is managed on an IP domain.
Tue Jun 26 08:03:05 2012 The recevied host 135.118.226.21

Tue Jun 26 08:03:05 2012 Trying to find the ip address in domain list
Tue Jun 26 08:03:05 2012 The entry dom : 142 add_type=1
Tue Jun 26 08:03:05 2012 The entry dom ip low :172.27.141.165
Tue Jun 26 08:03:05 2012 The entry ipaddress from low :135.118.226.21
Tue Jun 26 08:03:05 2012 The entry compare :1
Tue Jun 26 08:03:05 2012 The entry compare 2 :0
Tue Jun 26 08:03:05 2012 iplink_is_good_range_for_reg
...
Tue Jun 26 08:03:05 2012 The user domain is 142
Here, the IP address of the SIP equipment corresponds to the IP domain 142.
If the IP address doesnt match an IP domain, the SIPMOTOR returns:

Tue Jun 26 08:03:05 2012 The user is ipadd not in any Domain range return state as -1
The SIPMOTOR checks the SDP received in the INVITE.
Tue Jun 26 08:03:05 2012 [checkSdpValidity] Media 0 type 1 contains 3 formats.

Tue Jun 26 08:03:05 2012 [checkSdpValidity] Format : 8.
Tue Jun 26 08:03:05 2012 11ef[CMotorCall::isCryptoAuthorized] user crypto=0.
Tue Jun 26 08:03:05 2012 [convertSdpIntoTsdp] No Direction in the session part.
Tue Jun 26 08:03:05 2012 [convertSdpIntoTsdp] Check the direction in Session part - result:0.
Tue Jun 26 08:03:05 2012 [convertSdpIntoTsdp] media AUDIO detected (previous crypto=0).
Tue Jun 26 08:03:05 2012 [convertAudioMedia] The audio media contains 3 format(s).
Tue Jun 26 08:03:05 2012 [convertAudioMedia] Format 0 is 8.
Tue Jun 26 08:03:05 2012 [convertAudioMedia] 101.
Tue Jun 26 08:03:05 2012 [convertAudioMedia] Format is DTMF:101.
Tue Jun 26 08:03:05 2012 [convertAudioMedia] Direction is sendrecv.
Tue Jun 26 08:03:05 2012 [convertAudioMedia] Connection address retrieved in sdp:
135.118.226.21.
Tue Jun 26 08:03:05 2012 [convertIPStrIntoTuipv] 135.118.226.21 => 135.118.226.21
Tue Jun 26 08:03:05 2012 [display_sdp] address =135.118.226.21
Tue Jun 26 08:03:05 2012 [display_sdp] direction=0.
Tue Jun 26 08:03:05 2012 [convertSdpIntoTsdp] only one media taken into account xxx
The SDP contains
crypto_index=0 in this
clear SDP three formats of medias (8, 18 and 101), the direction is sendrecv meaning
media=1
in
Tueboth
Jundirection and the
26 08:03:05 2012IP [convertSdpIntoTsdp]
address of connection crypto_index=0
is 135.118.226.21.
clear media=1
The message to Call Handling is prepared and sent.

Tue Jun 26 08:03:05 2012 11ef[CMotorCall::sendLgEvtSipCreate] Event sent on eqt : 2066
Tue Jun 26 08:03:05 2012 ** SEPLOS **
Tue Jun 26 08:03:05 2012 [display_ipc_out] ------------ Begin ---------------
Tue Jun 26 08:03:05 2012 Id : -1
Tue Jun 26 08:03:05 2012 INVITE
Tue Jun 26 08:03:05 2012 REQUEST URI : <> [email protected]:5060 ; user=name
Tue Jun 26 08:03:05 2012 FROM : <PC_sip_extenstion> [email protected]:5060 ; user=name
Tue Jun 26 08:03:05 2012 TO : <"31004"> [email protected]:5060 ; user=name
Tue Jun 26 08:03:05 2012 CAC : 0
Tue Jun 26 08:03:05 2012 CAC ADDRESS :
Tue Jun 26 08:03:05 2012 CAC-CSBU info : UNKNOWN
Tue Jun 26 08:03:05 2012 CLIR : 0
Tue Jun 26 08:03:05 2012 Prack Required : 0
Tue Jun 26 08:03:05 2012 Allow Update : 0
Tue Jun 26 08:03:05 2012 SDP :
Tue Jun 26 08:03:05 2012 ADDRESS : 135.118.226.21 :46194
Tue Jun 26 08:03:05 2012 ALGOS :
Tue Jun 26 08:03:05 2012 PCMA
Tue Jun 26 08:03:05 2012 G729
Tue Jun 26 08:03:05 2012 101
Tue Jun 26 08:03:05 2012 DIRECTION : SEND & RECEIVE
Tue Jun 26 08:03:05 2012 crypto index : 0
Tue Jun 26 08:03:05 2012 N_GW_EXT : -1
Tue Jun 26 08:03:05 2012 [display_ipc_out] ------------- End ----------------
Ed. 12 98 TG0069
OmniPCX Enterprise
The call is sent to the Call handling on neqt 2066, regarding the type of SIP equipment detected by the
SIPMOTOR, some information are added or not on this message.
All the information about this call are sent to the Stand-By CPU.
Tue Jun 26 08:03:05 2012 SendToSipgwCpuSec: Message sent to the STAND-BY CPU
Tue Jun 26 08:03:05 2012 [receiveInviteMessage] send RemoteSdp to the StandBy.
Tue Jun 26 08:03:05 2012 SendToSipgwCpuSec: Message sent to the STAND-BY CPU
The information are sent to the Stand-By so that in case of bascul the SIP call will not be lost on the new
main CPU
The Call handling sends an answer back for this INVITE.
Tue Jun 26 08:03:05 2012 [display_ipc_in] ------------ Begin ---------------

Tue Jun 26 08:03:05 2012 neqt : 2066 Id : 1
Tue Jun 26 08:03:05 2012 INFORMATIONAL
Tue Jun 26 08:03:05 2012 xx : 0
Tue Jun 26 08:03:05 2012 RELATIVE REQUEST : INVITE
Tue Jun 26 08:03:05 2012 [display_ipc_in] ------------- End ----------------
A 100 Trying is sent by the Call Handling , but ignored by the SIPMOTOR.
Tue Jun 26 08:03:05 2012 [onIncomingEvent] INFORMATIONAL arrived.

Tue Jun 26 08:03:05 2012 [onIncomingEvent] 100 TRYING ignored.
This 100 Trying generated by the Call Handling is used to assign a session number for this call on the Call
Handling side, but not used by the SIPMOTOR
The Call handling sends an answer back for this INVITE.

Tue Jun 26 08:03:05 2012 neqt : 2066 Id : 1
Tue Jun 26 08:03:05 2012 INFORMATIONAL
Tue Jun 26 08:03:05 2012 xx : 80
Tue Jun 26 08:03:05 2012 SDP :
Tue Jun 26 08:03:05 2012 ADDRESS : 172.27.143.131 :32584
Tue Jun 26 08:03:05 2012 ALGOS :
Tue Jun 26 08:03:05 2012 G729
Tue Jun 26 08:03:05 2012 101
A 180 Ringing is sent by the Call Handling with SDP, for the moment, on a 18X message, the Call Handling
will put everytime a SDP, no possibility to disable it.
1340690585 -> Tue Jun 26 08:03:05 2012 11ef[CMotorCall::makeResponseSdp] Audio media.
Tue Jun 26 08:03:05 2012 11ef[CMotorCall::appendAudioAttributToMedia] Direction: 0.
Tue Jun 26 08:03:05 2012 11ef[CMotorCall::appendAudioAttributToMedia] format 101
Tue Jun 26 08:03:05 2012 11ef[CMotorCall::makeResponseSdp] fromSdp.getMediaDesciprionCount :1
Tue Jun 26 08:03:05 2012 [sameCodec] accepted Format : 18.
Tue Jun 26 08:03:05 2012 [sameCodec] requested Format : 8.
Tue Jun 26 08:03:05 2012 [sameCodec] same Format.
Tue Jun 26 08:03:05 2012 11ef[CMotorCall::mediaAccepted] Media accepted: m=audio 32584
RTP/AVP 18 101
a=sendrecv
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
Ed. 12 99 TG0069
OmniPCX Enterprise
The codecs from the INVITE were 8 and 18 and the answer contains 18. In that case the call is accepted by

1340690585 -> Tue Jun 26 08:03:05 2012 SEND MESSAGE TO NETWORK (135.118.226.21:61618 [UDP])
(BUFF LEN = 827)
----------------------utf8-----------------------
SIP/2.0 180 Ringing
To: "31004" <sip:[email protected]>;tag=05b5888d18d4e78f3554a55dadeefb08
CSeq: 1 INVITE
9c72747c0d38bb69-1--d87543-;rport=61618
Content-Length: 243
v=0
o=OXE 1340690585 1340690585 IN IP4 172.27.141.151
s=abs
c=IN IP4 172.27.143.131
t=0 0
a=sendrecv
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=ptime:20
a=maxptime:40
For each
SIP call event, a message is sent to the Stand-By CPU.
-------------------------------------------------
Tue Jun 26 08:03:05 2012 [receiveInformationalEvent] UpdateContext send on the StandBy.
The Call handling sends a new answer for this INVITE.

Tue Jun 26 08:03:08 2012 neqt : 2066 Id : 1
Tue Jun 26 08:03:08 2012 SUCCESSFUL
Tue Jun 26 08:03:08 2012 xx : 0
Tue Jun 26 08:03:08 2012 CLIR : 0
Tue Jun 26 08:03:08 2012 COLP : 1
Tue Jun 26 08:03:08 2012 SDP :
Tue Jun 26 08:03:08 2012 ADDRESS : 172.27.142.64 :32514
Tue Jun 26 08:03:08 2012 ALGOS :
Tue Jun 26 08:03:08 2012 G729
Tue Jun 26 08:03:08 2012 101
A 200 ok is sent to the SIPMOTOR with SDP
1340690588 -> Tue Jun 26 08:03:08 2012 11ef[CMotorCall::makeResponseSdp] Audio media.

Tue Jun 26 08:03:08 2012 11ef[CMotorCall::appendAudioAttributToMedia] Direction: 0.
Tue Jun 26 08:03:08 2012 11ef[CMotorCall::appendAudioAttributToMedia] format 101
Tue Jun 26 08:03:08 2012 11ef[CMotorCall::makeResponseSdp] fromSdp.getMediaDesciprionCount :1
Tue Jun 26 08:03:08 2012 [sameCodec] accepted Format : 18.
Tue Jun 26 08:03:08 2012 [sameCodec] same Format.
Tue Jun 26 08:03:08 2012 11ef[CMotorCall::mediaAccepted] Media accepted: m=audio 32514 RTP/AVP 18
Ed. 12 100 TG0069

OmniPCX Enterprise
The codecs from the INVITE were 8 and 18. The answer contains 18. In that case the call is accepted by

Tue Jun 26 08:03:08 2012 15fd [CDialog::createResponse] create a CONFIRMED dialog
Due to this, the dialog reference and transaction reference are changed (internal SIPMOTOR functionning).
Tue Jun 26 08:03:08 2012 15fe [CDialog::CDialog] look for the transaction #0, transaction key = z9hG4bK-
d87543-9c72747c0d38bb69-1--d87543-
Tue Jun 26 08:03:08 2012 15fe [CDialog::CDialog] copy the transaction #0, transaction key = z9hG4bK-
d87543-9c72747c0d38bb69-1--d87543-
Tue Jun 26 08:03:08 2012 210d [CTransaction::CTransaction] Transaction is cloned in 4 state
The dialog reference is changed form 15fd to 15fe.

The transaction reference is changed from 210c to 210d.
Tue Jun 26 08:03:08 2012 SEND MESSAGE TO NETWORK (135.118.226.21:61618 [UDP]) (BUFF LEN = 984)
----------------------utf8-----------------------
SIP/2.0 200 OK
To: "31004" <sip:[email protected]>;tag=05b5888d18d4e78f3554a55dadeefb08
CSeq: 1 INVITE
9c72747c0d38bb69-1--d87543-;rport=61618
Content-Length: 242
v=0
o=OXE 1340690585 1340690586 IN IP4 172.27.141.151
s=abs
c=IN IP4 172.27.142.64
t=0 0
a=sendrecv
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=ptime:20
a=maxptime:40
-------------------------------------------------
The 200ok sent to the remote SIP equipment is generated with information from the INVITE received and
from the 200ok answer from the Call Handling.
Tue Jun 26 08:03:08 2012 210d [CTransProceedingState::createResponse] Final : Transaction changes to

Completed state
The retransmission timers are started.
Tue Jun 26 08:03:08 2012 210d [CTransaction::startTimer] Timer G is started (delay = 500 ms)
Tue Jun 26 08:03:08 2012 210d [CTransaction::startTimer] Timer H is started (delay = 32000 ms)
The SIPMOTOR receives a ACK for the 200ok.
Ed. 12 101 TG0069

OmniPCX Enterprise
----------------------utf8-----------------------
Via: SIP/2.0/UDP 135.118.226.21:61618;branch=z9hG4bK-d87543-cc14ac1776189458-1--d87543-;rport
Max-Forwards: 70
To: "31004"<sip:[email protected]>;tag=05b5888d18d4e78f3554a55dadeefb08
From: "PC_sip_extenstion"<sip:[email protected]>;tag=c850be7c
CSeq: 1 ACK
Content-Length: 0
-------------------------------------------------

Tue Jun 26 08:03:08 2012 210d [CTransaction::changeState] STATE CHANGED TO TERMINATED
The retransmission timers are freed.
Tue Jun 26 08:03:08 2012 210d [CTransaction::freeTimerToken] Timer G is freed

Tue Jun 26 08:03:08 2012 210d [CTransaction::freeTimerToken] Timer H is freed
Tue Jun 26 08:03:08 2012 15fe [CDialog::receiveAckRequest] the INVITE request is terminated
The ACK is sent to the Call Handling.

Tue Jun 26 08:03:08 2012 Id : 1
Tue Jun 26 08:03:08 2012 ACK
Call released by the OXE:
- The BYE is sent from the Call Handling.

Tue Jun 26 08:03:10 2012 neqt : 2066 Id : 1
Tue Jun 26 08:03:10 2012 BYE

Tue Jun 26 08:03:10 2012 2110 [CTransaction::changeState] STATE CHANGED TO INITIAL
The BYE is a new transaction for a SIP call, in that case, the transaction reference it is 2110, and the status
is INITIAL.
- The BYE is sent to the remote SIP equipment.

Tue Jun 26 08:03:10 2012 2110 [CTransaction::changeState] STATE CHANGED TO TRYING
Ed. 12 102 TG0069

OmniPCX Enterprise
- The retransmission timers are started.
Tue Jun 26 08:03:10 2012 2110 [CTransaction::startTimer] Timer E is started (delay = 500 ms)
Tue Jun 26 08:03:10 2012 2110 [CTransaction::startTimer] Timer F is started (delay = 16000 ms)
- The 200ok of the BYE request is received from the remote SIP equipment.
----------------------utf8-----------------------
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.27.141.151;branch=z9hG4bK2385fb34fcefc38c24fa6848df37e986
To: <sip:[email protected]>;tag=c850be7c
From: "31004"<sip:[email protected]>;tag=05b5888d18d4e78f3554a55dadeefb08
CSeq: 716266225 BYE
Content-Length: 0
-------------------------------------------------
- The SIPMOTOR changes this transaction state.
Tue Jun 26 08:03:10 2012 2110 [CTransaction::changeState] STATE CHANGED TO COMPLETED
- The retransmission timers are freed.
Tue Jun 26 08:03:10 2012 2110 [CTransaction::freeTimerToken] Timer E is freed

Tue Jun 26 08:03:10 2012 2110 [CTransaction::freeTimerToken] Timer F is freed
- The 200ok of the BYE request is sent to the Call Handling.
Tue Jun 26 08:03:10 2012 ** SEPLOS **

Tue Jun 26 08:03:10 2012 [sendLgEvtSip] Event sent on eqt : 2066 Id :1
Tue Jun 26 08:03:10 2012 Id : 1
Tue Jun 26 08:03:10 2012 xx : 0
Tue Jun 26 08:03:10 2012 RELATIVE REQUEST : BYE
Tue Jun 26 08:03:10 2012 CLIR : 0
Tue Jun 26 08:03:10 2012 COLP : 0
- The Call Handling sent a message to the SIPMOTOR to release the neqt associated to
this SIP call
Tue Jun 26 08:03:10 2012 neqt : 2066 Id : 1
Tue Jun 26 08:03:10 2012 SIP EQT RELEASED

Tue Jun 26 08:03:10 2012 [CMotorCallManager::onIncomingEvent] The call with eqt: 2066 has released its
equipment.
Tue Jun 26 08:03:10 2012 [CMotorCallManager::onIncomingEvent] state = TERMINATED_STATE.
Tue Jun 26 08:03:10 2012 11ef[CMotorCall::unRegister] Remove eqt : 2066 diag : 1 from the map.
Tue Jun 26 08:03:10 2012 [CMotorCallManager::eraseCallwithEqt] erase 2066 1.
Tue Jun 26 08:03:10 2012 [CMotorCallManager::onIncomingEvent] killSession.

Tue Jun 26 08:03:10 2012 11ef [CCall::killSession]
Ed. 12 103 TG0069

OmniPCX Enterprise

Tue Jun 26 08:03:10 2012 210c [CTransaction::changeState] STATE CHANGED TO TERMINATED
...
Tue Jun 26 08:03:10 2012 2110 [CTransaction::changeState] STATE CHANGED TO TERMINATED
Call released by the remote SIP equipment:
- The BYE is received from the remote SIP equipment.

----------------------utf8-----------------------
BYE sip:oxe-ov.alcatel.fr SIP/2.0
Via: SIP/2.0/UDP 135.118.226.21:61618;branch=z9hG4bK-d87543-c47926131a084707-1--d87543-;rport
Max-Forwards: 70
To: "31004"<sip:[email protected]>;tag=efa4b05316a486724541975cb22707d1
From: "PC_sip_extenstion"<sip:[email protected]>;tag=c55fb830
Call-ID: MzIwMmRjNGI3YTE3ZjkwZTE0ODE4Y2IzZGU1ZTdjZDM.
CSeq: 2 BYE
Content-Length: 0
-------------------------------------------------
- The SIPMOTOR checks if the dialog already exists.
Tue Jun 26 08:03:10 2012 11ef [CCall::getDialog] Confirmed Dialog found

Tue Jun 26 08:03:10 2012 2110 [CTransaction::changeState] STATE CHANGED TO INITIAL
The BYE is a new transaction for a SIP call, in that case, the transaction reference it is 21a7, and the status
is INITIAL.
Tue Jun 26 08:03:10 2012 2110 [CTransaction::changeState] STATE CHANGED TO TRYING
- The BYE is sent to the Call handling.

Tue Jun 26 08:03:10 2012 Id : -1
Tue Jun 26 08:03:10 2012 BYE
- The Call Handling answers to the SIPMOTOR.

Tue Jun 26 08:03:10 2012 neqt : 2266 Id : -1
Tue Jun 26 08:03:10 2012 xx : 0
Tue Jun 26 08:03:10 2012 RELATIVE REQUEST : BYE
Tue Jun 26 08:03:10 2012 CLIR : 0
Tue Jun 26 08:03:10 2012 COLP : 0
Tue Jun 26 08:03:10 2012 [display_ipc_in] ------------- End ---------------
Ed. 12 104 TG0069

OmniPCX Enterprise
- The SIPMOTOR sends the 200 ok of the BYE to the remote SIP equipment.
Tue Jun 26 08:03:10 2012 SEND MESSAGE TO NETWORK (135.118.226.39:25648 [UDP]) (BUFF LEN =
546)
----------------------utf8-----------------------
SIP/2.0 200 OK
To: "31004"<sip:[email protected]>;tag=efa4b05316a486724541975cb22707d1
From: "PC_sip_extenstion"<sip:[email protected]>;tag=c55fb830
Call-ID: MzIwMmRjNGI3YTE3ZjkwZTE0ODE4Y2IzZGU1ZTdjZDM.
CSeq: 2 BYE
cf501c2f3311d050-1--d87543-;rport=25648
Content-Length: 0
-------------------------------------------------
Tue Jun 26 08:03:10 2012 2110 [CTransaction::changeState] STATE CHANGED TO COMPLETED
this SIP call
Tue Jun 26 08:03:10 2012 neqt : 2266 Id : -1
Tue Jun 26 08:03:10 2012 SIP EQT RELEASED

Tue Jun 26 08:03:10 2012 [CMotorCallManager::onIncomingEvent] The call with eqt: 2066 has released its
equipment.
Tue Jun 26 08:03:48 2012 [CMotorCallManager::onIncomingEvent] state = TERMINATED_STATE.
Tue Jun 26 08:03:48 2012 11fc[CMotorCall::unRegister] Remove eqt : 2066 diag : 1 from the map.
Tue Jun 26 08:03:48 2012 [CMotorCallManager::eraseCallwithEqt] erase 2066 1
Tue Jun 26 08:03:10 2012 [CMotorCallManager::onIncomingEvent] killSession.

Tue Jun 26 08:03:10 2012 11ef [CCall::killSession]

Tue Jun 26 08:03:10 2012 210c [CTransaction::changeState] STATE CHANGED TO TERMINATED
...
Tue Jun 26 08:03:10 2012 2110 [CTransaction::changeState] STATE CHANGED TO TERMINATED
Ed. 12 105 TG0069

OmniPCX Enterprise
12.9.4 Incoming SIP call in case of SIP extension: Call Handling point of view
Here an example of incoming call from a SIP extension to an IPtouch.
Traces option used :

>tuner km
>tuner clear-traces
>trc i
>actdbg all=off
>tuner +cpu +cpl +at hybrid=on
>actdbg sip=on csip=on
>mtracer -a
The call arrives on the SIPMOTOR, and sending to the Call Handling
(600095:000062) CSIP @@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 02066 activated @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
(600095:000063) CSIP_receiveSipMsg
(600095:000064) +------------------------------------------------------------+
(600095:000067) | From : <PC_sip_extenstion> [email protected]:5060 ; user=name
(600095:000068) | To : <"31004"> [email protected]:5060 ; user=name
(600096:000069) +------------------------------------------------------------+
(600096:000070) | SDP :
(600096:000071) | @IP:port = 135.118.226.21:46194
(600096:000072) | ALGOS :
(600096:000073) | PCMA
(600096:000074) | G729
(600096:000075) | DTMF : 101
(600096:000077) | cac : false
(600096:000078) | Prack_Required: 0
(600096:000079) | Allow_UPDATE: 0
(600096:000081) +------------------------------------------------------------+
(600096:000082) ..activeChId 0 featureList START_CALL
...
In case of SIP Extension, the call Handling treatment for the call starts by the message CSIP, for SIP
extension point of view.
In the first line, the information 02066 activated is used to inform that the Call Handling starts the treatment
of the SIP extension with the neqt 2066.
The Call Handling checks if a session is already opened for this SIP extension user.
(600096:000087) ..CSIPMsgSipInvite::getSession
(600096:000088) ....CSIP_getSessionFromRequestURI
(600096:000089) ......Didn't retrieve session for requestUri 31004
(600096:000090) ....CSIP_getFreeSession
(600096:000091) ......Got free session 1 for ChId 80 CSIP_INVITE_WAIT_STATUS_CH_ID
In that case, no session opened, the Call Handling assigns to this call the session number 1, for a second
call (if the first call is still up) the session will be 2, etc...
The Call Handling generates a 100 Trying for this session
(600096:000094) ......CSIPSession#1ChId#80::sendSipInformational
(600096:000095) ........CSIPSession#1ChId#80::emitMsgToSIPMotor
(600096:000096) ..........SIP_INFORMATIONAL sent
(600096:000097) +------------------------------------------------------------+
(600096:000099) | Informational 100
(600096:000101) | No SDP
(600096:000102) +------------------------------------------------------------+
Ed. 12 106 TG0069

OmniPCX Enterprise
This 100 Trying will not be taken in account by the SIPMOTOR, it is only used to start the session on the Call
handling side.
Getting the SDP information received
(600096:000121) CSIP_tradKey chId=128 CSIP_START_CALL

(600096:000122) CSIP_analyzeSdp 135.118.226.21:46194 DTMF=101 SIP_SENDRECV
(600096:000123) G_711_A/G_729_A -> G_711_A/G_729_A
(600096:000124) CSIP_tradKey -> cnx_create_tab(0, -1, 135.118.226.21:46194)
(600096:000125) CSIP_tradKey kindofkey=VSYST (6) cokey=17
(600096:000126) CSIP_sendInfoCs : No call server informations authorization.
This 100 Trying will not be taken in account by the SIPMOTOR, it is used only to start the session on the Call
handling side.
Analysis of the SDP information
(600096:000136) put_rtp_info end 2066 local.wc=0 distant.wc=0

(600096:000137) sip_ems_with_rfc2833-->disa_for_remote_ext=0
(600096:000138) sip_ems_with_rfc2833-->Result=0
(600096:000139) Exist_RCL_link-->Result=0,dtmf_direction=1
(600096:000141) SIP: mise a jour VPN
(600096:000142) dtmf_to_vpn_from_abc : dtmf_payload(2066)=101
(600096:000143) dtmf_to_vpn_from_abc : !LIEN_VPN
(600096:000144) Marhaban bikom dans le monde SIP : dtmf_payload(2066)= 101
(600096:000145) CSIP_isNwkCallWithSeplos neqt 2066 abc -1 vpn -1 result 0
(600096:000146) is_ems_ext_gw-->neqt=2066,Result=0
(600096:000147) send_cpl_connect_rtp_direct-->dtmf_direction=1
(600096:000152) CSIP_sendUpdateMsgFromCh call_id=0->1 neqt=-1->2066 state=NO_SCREEN-
>SCREEN_DIAL_0_DIGIT
(600096:000153) CSIP_sendUpdateMsgFromCh -> cnx_create_tab(1, 2066)
(600096:000154) CSIP_constructDistantField UTF-8 SCREEN_DIAL_0_DIGIT key=1
(600096:000155) ""
(600096:000156) CSIP_constructOtherField UTF-8 SCREEN_DIAL_0_DIGIT key=1
(600096:000157) "PC" 31023
(600096:000158) CSIP_constructSdp Default case
(600096:000159) 172.27.143.131:32584 G_729_A DTMF=101 SIP_SENDRECV
(600096:000160) CSIP_constructOtherInfo clir=0 forward=0 autoAnswer=0
(600096:000161) ..CSIPMsgInFactory::makeMsgInCh
(600096:000162) ..new CSIPMsgChDial0Digit at 0x54038ce8 - counter 1
(600096:000163) CSIP_sendUpdateMsgFromCh -> call CSIP_setFeatureList
(600096:000164) nulog_final: 0 typconv : 0 ptdemi->forwarded_neqph:-1
(600096:000165) CSIP_setFeatureList
(600096:000168) CSIP_sendInfoCs : No call server informations authorization..
The Call handling gets the SDP infomation of the equipment for the RBT to generate the SDP of the
180
(600096:000198) chgt_local_rtp_info ptdemi->info.hinfo=0 ptdemi->neqt=2066
(600096:000199) chgt_local_rtp_info local.wc=0 distant.wc=0 before update
(600096:000200) chgt_local_rtp_info end local.wc=0 distant.wc=0
(600096:000203) CSIP_sendUpdateMsgFromCh call_id=1->1 neqt=2066->2066
state=SCREEN_DIAL_0_DIGIT->SCREEN_DIAL_DIGIT
(600096:000204) CSIP_constructDistantField UTF-8 SCREEN_DIAL_DIGIT key=1
(600096:000205) ""
(600096:000206) CSIP_constructOtherField UTF-8 SCREEN_DIAL_DIGIT key=1
(600096:000207) " PC" 31023
(600096:000212) ..new CSIPMsgChDialDigit at 0x54038ce8 - counter 1
(600096:000215) CSIP_setFeatureList
Ed. 12 107 TG0069

OmniPCX Enterprise
Here, the IP address for the RBT is 172.27.143.131, and the port used is 32584 and the codec used is G729
(this information appears few times in the trace)
The 180 is generated by the Call Handling and sent to the SIPMOTOR.
(600096:000400) CSIP_receiveComAction
(600096:000401) ..activeChId 1 featureList --
(600096:000402) ..CSIP Queue CSIPMsgChCalledStatus
(600096:000403) ..CSIPMsgChCalledStatus::getSession
(600096:000404) ....CSIP_getSessionFromChId
(600096:000405) ......Retrieved session 1 for ChId 1
(600096:000406) ..CSIPMsgChCalledStatus::execute
(600096:000407) ....CSIPStateInviteWaitCalledStatus::doCSIPMsgChCalledStatus
(600096:000408) ......CSIP_findSessionInTransfer
(600096:000409) ........No session in transfer
(600096:000410) ......SUBSTATE_ACT_INFO1 0 (libre )
(600096:000411) ......CSIPSession#1ChId#1::setDistantSdp
(600096:000412) ........CSIPSession#1ChId#1::compareDistantSdp
(600096:000413) ..........Change 0.0.0.0:5060 DTMF=255 SIP_INACTIVE
(600096:000414) .......... -> 172.27.143.131:32584 G_729_A DTMF=101 SIP_SENDRECV
(600096:000415) ........CSIPSession#1ChId#1::resetIsSdpSentInInf
(600096:000416) ......CSIPSession#1ChId#1::sendSipInformational
(600096:000417) ........CSIPSession#1ChId#1::setIsSdpSentInInf
(600096:000419) ..........SIP_INFORMATIONAL sent
(600096:000420) +------------------------------------------------------------+
(600096:000422) | Informational 180
(600096:000424) +------------------------------------------------------------+
(600096:000425) | SDP :
(600096:000426) | @IP:port = 172.27.143.131:32584
(600096:000427) | ALGOS :
(600096:000428) | G729
(600096:000429) | DTMF : 101
(600096:000431) +------------------------------------------------------------+
(600096:000432) ......CSIPSession#1ChId#1::changeState
(600096:000433) ........CSIPStateInviteWaitCalledStatus -> CSIPStateInvite180WaitConversation
The state of the session, for Call Handling point of view, is changed to
CSIPStateInvite180WaitConversation
The Call handling gets the SDP infomation of the equipment for the 200ok
(600121:000486) SIP ipphone : interro statut 0 ptdemi->neqt(2049)

(600121:000487) SIP ipphone : GetneqtEnFace = -1 payload = 101 neqt =(2066)
(600121:000490) put_rtp_info end 2066 local.wc=0 distant.wc=0
(600121:000497) neqttouc neqt=2066 nekip=2049 toucacod=1
(600121:000498) neqttouc result=1000801 en Hexa !!!
(600121:000499) sip_behind_ice-->neqt=2066,Result=0
(600121:000503) numunpack_trace: 31004
(600121:000504) from_same_nb_in_mes : nulog=27,numero_lg=5
(600121:000505) CSIP_msg_notify_management : No MWI subscription.
(600121:000510) CSIP_sendUpdateMsgFromCh call_id=1->1 neqt=2049->2049 state=SCREEN_CALLED_STATUS-
>SCREEN_CONVERSATIO
(600121:000511) CSIP_constructDistantField UTF-8 SCREEN_CONVERSATION key=1
(600121:000512) "IPtouch 172.27.142.64" 31004
(600121:000513) CSIP_constructOtherField UTF-8 SCREEN_CONVERSATION key=1
(600121:000514) "PC" 31023
(600121:000519) ..new CSIPMsgChConversation at 0x54038ce8 - counter 1
(600121:000522) CSIP_setFeatureList START_CALL HOLD
Ed. 12 108 TG0069
OmniPCX Enterprise
Here, the IP address for the 200ok is 172.27.142.64, the used port is 32514 and the codec is G729. This
SDP corresponds to the IPtouch.
The 200ok is generated by the Call Handling and sent to the SIPMOTOR
(600121:000526) ..activeChId 1 featureList START_CALL HOLD
(600121:000527) ..CSIP Queue CSIPMsgChConversation
(600121:000528) ..CSIPMsgChConversation::getSession
(600121:000531) ..CSIPMsgChConversation::execute
(600121:000532) ....CSIPStateInvite180WaitConversation::doCSIPMsgChConversation
(600121:000533) ......CSIPSession#1ChId#1::setDistantSdp
(600121:000534) ........CSIPSession#1ChId#1::compareDistantSdp
(600121:000535) ..........Change 172.27.143.131:32584 G_729_A DTMF=101 SIP_SENDRECV
(600121:000536) .......... -> 172.27.142.64:32514 G_729_A DTMF=101 SIP_SENDRECV
(600121:000537) ........CSIPSession#1ChId#1::resetIsSdpSentInInf
(600121:000538) ......CSIPSession#1ChId#1::setDistantClir
(600121:000539) ......CSIPSession#1ChId#1::setDistantName
(600121:000540) ......CSIPSession#1ChId#1::setDistantNumber
(600121:000541) ......CSIPSession#1ChId#1::sendSipSuccessful
(600121:000543) ..........SIP_SUCCESSFUL sent
(600121:000544) +------------------------------------------------------------+
(600121:000546) | Successful 200
(600121:000548) +------------------------------------------------------------+
(600121:000549) | SDP :
(600121:000550) | @IP:port = 172.27.142.64:32514
(600121:000551) | ALGOS :
(600121:000552) | G729
(600121:000553) | DTMF : 101
(600121:000555) | AssertedAddress : <IPtouch 172.27.142.64> [email protected]:5060
(600121:000556) | COLP
(600121:000557) +------------------------------------------------------------+
(600121:000559) ........CSIPStateInvite180WaitConversation -> CSIPStateConnectedWaitAck
The state of the session, for Call Handling point of view, is changed to CSIPStateConnectedWaitAck.
The ACK is received from the SIPMOTOR

(600126:000642) +------------------------------------------------------------+
(600126:000643) | Message received SIP ----> UA (neqt : 2066-1)
(600126:000644) | ACK
(600126:000645) +------------------------------------------------------------+
(600126:000646) ..activeChId 1 featureList START_CALL HOLD
(600126:000647) ..CSIPMsgInFactory::makeMsgInSip
(600126:000648) ....SIP_ACK dialogId 1
(600126:000649) ....new CSIPMsgSipAck at 0x54038f90 - counter 2
(600126:000650) ..CSIP Queue CSIPMsgSipAck < CSIPMsgChUpdateRtp
(600126:000651) ..CSIPMsgSipAck::getSession
(600126:000652) ....CSIP_getSessionFromId
(600126:000653) ......Retrieved session 1 with ChId 1
(600126:000654) ..CSIPMsgSipAck::execute
(600126:000655) ....CSIPStateConnectedWaitAck::doCSIPMsgSipAck
(600126:000657) ........CSIPStateConnectedWaitAck -> CSIPStateConnected
Ed. 12 109 TG0069

OmniPCX Enterprise
The state of the session, for Call Handling point of view, is changed to CSIPStateConnected.
Call released by the OXE:
- The BYE is generated by the Call Handling and sent to the SIPMOTOR
(600143:000734) ..activeChId 1 featureList HOLD
(600143:000735) ..CSIP Queue CSIPMsgChOnHook
(600143:000736) ..CSIPMsgChOnHook::getSession
(600143:000739) ..CSIPMsgChOnHook::execute
(600143:000740) ....CSIPStateConnected::doCSIPMsgChOnHook
(600143:000741) ......CSIPSession#1ChId#1::sendMsgToCh
(600143:000742) ........CSIP_HANG_UP
(600143:000743) ......CSIPSession#1ChId#1::sendSipBye
(600143:000745) ..........SIP_BYE sent
(600143:000746) +------------------------------------------------------------+
(600143:000748) | BYE
(600143:000749) +------------------------------------------------------------+
(600143:000751) ........CSIPStateConnected -> CSIPStateByeWait200
The state of the session, for Call Handling point of view, is changed to CSIPStateByeWait200.
- The 200OK of the BYE is received on the Call Handling

(600144:000832) +------------------------------------------------------------+
(600144:000833) | Message received SIP ----> UA (neqt : 2066-1)
(600144:000834) | Successful 200
(600144:000835) | RELATIVE REQUEST : BYE
(600144:000836) | No SDP
(600144:000837) +------------------------------------------------------------+
(600144:000838) ..activeChId 0 featureList START_CALL
(600144:000839) ..CSIPMsgInFactory::makeMsgInSip
(600144:000840) ....SIP_SUCCESSFUL dialogId 1
(600144:000841) ....new CSIPMsgSip200ok at 0x54038ce8 - counter 1
(600144:000842) ..CSIP Queue CSIPMsgSip200ok
(600144:000843) ..CSIPMsgSip200ok::getSession
(600144:000844) ....CSIP_getSessionFromId
(600144:000845) ......Retrieved session 1 with ChId 81 CSIP_BYE_END_CH_ID
(600144:000846) ..CSIPMsgSip200ok::execute
(600144:000847) ....CSIPStateByeWait200::doCSIPMsgSip200ok
(600144:000849) ........CSIPStateByeWait200 -> CSIPStateIdle
(600144:000850) ........Stop timer TEMPO_CSIP_WAIT_200 (32.0 seconds) for session 1
(600144:000851) ........CSIPSession#1ChId#81::sendSipEqtReleased
(600144:000852) ..........CSIPSession#1ChId#81::emitMsgToSIPMotor
(600144:000853) ............SIP_EQT_RELEASED sent
(600144:000854) ........CSIPSession#1ChId#81::reinit
(600144:000855) ........CSIP_getSessionFromChId
(600144:000856) ..........No session for ChId 81 CSIP_BYE_END_CH_ID
(600144:000857) ........CSIP_inform_cpu_sec activeSession CSIP_UNDEF_SESSION_ID
(600144:000859) ..delete CSIPMsgSip200ok (0x54038ce8) - counter 0
(600144:000860) CSIP lib__demi() called for neqt 2066
The state of the session, for Call Handling point of view, change to CSIPStateIdle.
The neqt is released (SIP_EQT_RELEASED sent)

The half-com is released (CSIP lib__demi() called for neqt 2066)
On the Call Handling, the SIP extension calls have a session, this is the evolution of the session state from
the INVITE to the 200ok of the BYE:
Ed. 12 110 TG0069

OmniPCX Enterprise
- CSIPStateIdle -> CSIPStateInviteWaitDial0Digit

o Changing state from the INVITE to the 100 Trying
- CSIPStateInviteWaitDial0Digit -> CSIPStateInviteWaitCalledStatus

o Changing state from the 100 Trying to the 180 Ringing
- CSIPStateInviteWaitCalledStatus -> CSIPStateInvite180WaitConversation

o Changing state from the 180 Ringing to the 200 Ok
- CSIPStateInvite180WaitConversation -> CSIPStateConnectedWaitAck

o Changing state from the 200 Ok to the ACK
- CSIPStateConnectedWaitAck -> CSIPStateConnected

o Changing state from the ACK to the BYE
- CSIPStateConnected -> CSIPStateByeWait200

o Changing state from the BYE to the 200 Ok of the BYE
- CSIPStateByeWait200 -> CSIPStateIdle

o Changing state from the 200 Ok of the BYE to the next INVITE (next call)
Ed. 12 111 TG0069

OmniPCX Enterprise
12.10 Main call flows explanation
12.10.1 Forwards
The OXE is able to manage different types of forward. Then if an equipment performs a forward to a SIP
equipment, the SIP messages behavior will differ according to this forward type.
Topology for explanation:
Legacy phone B (31000)
SIP phone C
(31026)
OmniPCX Enterprise
Legacy phone A (31004)
12.10.1.1 Phone A calls B, and B is in direct foward to C.
In this type of call the OXE sends an INVITE to C (for all types of fowards) . Here are the different types of
INVITE sent according to the declaration of the SIP equipment on OXE:
- C is declared as SIP extension:
----------------------utf8-----------------------
INVITE sip:[email protected]:27836;rinstance=e26a48b411982396 SIP/2.0
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE, INFO
Supported: histinfo,replaces,timer,path
Session-Expires: 1800;refresher=uac
Min-SE: 900
To: "IPtouch 172.27.141" <sip:[email protected];user=phone>
From: "IPtouch 172.27.142.64" <sip:31004@oxe-
ov.alcatel.fr;user=phone>;tag=fc0ad7be3c9267a849d2
789c08cf26d3
Contact: <sip:[email protected];transport=UDP>
CSeq: 960429378 INVITE
Via: SIP/2.0/UDP 172.27.141.151;branch=z9hG4bKc2893fd8925d9aa6704859e3fb78877a
Max-Forwards: 70
Content-Length: 240
In that case, the important information is the TO field containing the directory number of the user forwarded
to the SIP extension (31000 in that case). Theres no more information to indicate that the call is forwarded.
Ed. 12 112 TG0069

OmniPCX Enterprise
- C is declared as SIP device or an external SIP gateway:

----------------------utf8-----------------------
INVITE sip:[email protected]:17680;rinstance=3e53f382fc6e4647 SIP/2.0
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE, INFO
Supported: histinfo,replaces,timer,path
Session-Expires: 1800;refresher=uac
Min-SE: 900
History-Info: <sip:31000@oxe-
ov.alcatel.fr?reason=SIP%3bcause%3d302%3btext%3d%22Moved%20Temporarily%22>;index=1,<sip:31026
@oxe-o
v>;index=1.1
To: <sip:[email protected];user=phone>
From: "IPtouch 172.27.1" <sip:31004@oxe-
ov.alcatel.fr;user=phone>;tag=4200fe39737a85684b86a11b9078a0c6
Via: SIP/2.0/UDP 172.27.141.151;branch=z9hG4bKcbbca67dd61c80b972173fb10c31900e
Max-Forwards: 70
InContent-Length:
that case, the important
240 information is the TO field containing the directory number of the user forwarded
to the SIP extension (31000 in that case), and the field History-Info. This information is present in case of
v=0
forward and if it is managed on the OXE side for the SIP Trunk Group associated to the SIP gateway.
The History-Info contains the directory number of the set forwarded, the reason of forward and the
destination of the forward.
The History-Info can be changed for Diversion for external SIP gateways by management.
The History-Info is not validated for SIP extension.
12.10.1.2 Phone A calls C, and C is forwarded to B.

----------------------utf8-----------------------
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/UDP 172.27.141.151;branch=z9hG4bK9e0dfb2b8f49bd46aaf944cee38cc455
Contact: <sip:[email protected]>
To: "SIP Phone"<sip:[email protected];user=phone>;tag=16325b19
From: "IPtouch 172.27.142.64"<sip:[email protected];user=phone>;tag=119145146a704a4541de9
Content-Length: 0
-------------------------------------------------
Most of the time the SIP equipment returns a 302 message to inform the proxy that the call is fowarded. This
message is immediate or after a delay according to the type of forward.
If the SIP equipment is a proxy, it is able to keep the call. In that case, 2 SIP legs are opened, one from the
OXE to the proxy, the second one from the proxy to the forwarded destination.
If the SIP equipment is declared as a SIP extension, the forwarding prefixes can be used on this equipment.
In that case no INVITE will be sent to the SIP equipment because the Call Handling knows that this user is
forwarded.
Ed. 12 113 TG0069

OmniPCX Enterprise
12.10.2 Transfer
To make a transfer, the OXE can use (receive and accept) different ways according to the call context:
- The REFER without Replaces

- The REFER with Replaces
- The REINVITE with Replaces

SIP phone C
(31026)
OmniPCX Enterprise
Legacy phone A (31004) SIP phone D

(31023)
12.10.2.1 Use of REFER without replaces.
C calls A and C makes a transfer to B
- C sends a REFER to the SIPMOTOR
----------------------utf8-----------------------
REFER sip:oxe-ov.alcatel.fr SIP/2.0
Via: SIP/2.0/UDP 172.27.141.210:63016;branch=z9hG4bK-d87543-5c3865307254f255-1--d87543-;rport
Max-Forwards: 70
To: "31004"<sip:[email protected]>;tag=171c87e6f9b80ed5f6819b411a72505c
From: "31026"<sip:[email protected]>;tag=15672359
Call-ID: ODFlNGNmY2JjNDgyOGEwNDRmYjhhY2NjODAxM2U2NWE.
CSeq: 3 REFER
Refer-To: <sip:[email protected]>
Referred-By: <sip:[email protected]:63016>
Content-Length: 0
-------------------------------------------------
On this REFER, the following information are present:
Refer-To contains the directory number of the transfer destination.
Referred-By contains the directory number of the user performing the transfer.
Ed. 12 114 TG0069

OmniPCX Enterprise
- The SIPMOTOR sends a 202 Accepted to C

Mon Jun 25 12:04:30 2012 SEND MESSAGE TO NETWORK (172.27.141.210:63016 [UDP]) (BUFF LEN =
665)
----------------------utf8-----------------------
SIP/2.0 202 Accepted
To: "31004" <sip:[email protected]>;tag=171c87e6f9b80ed5f6819b411a72505c
From: "31026" <sip:[email protected]>;tag=15672359
CSeq: 3 REFER
5c386530725
4f255-1--d87543-;rport=63016
The 202 Accepted0is send to accept the REFER, but the transfer is not yet done.
Content-Length:
-------------------------------------------------
- The SIPMOTOR sends a NOTIFY to C
----------------------utf8-----------------------
NOTIFY sip:[email protected]:63016 SIP/2.0
Content-Type: message/sipfrag
Event: refer
Subscription-State: terminated;reason=noresource
To: sip:[email protected];tag=15672359
From: "31004" <sip:[email protected]>;tag=171c87e6f9b80ed5f6819b411a72505c
CSeq: 1644340323 NOTIFY
Via: SIP/2.0/UDP 172.27.141.151;branch=z9hG4bK65961cae897ba970a6b559776cd2cf88
Content-Length: 16
SIP/2.0 200 OK
-------------------------------------------------
The NOTIFY corresponds to the final state of the transfer. Here the NOTIFY has 200 Ok at the end of the
message. In this example the transfer has be done by the OXE.
If the on NOTIFY, the information is 503 Unavailable, in that case, the transfer has failed. Some other
information can be present (488, 486, etc...) according to the failed cause.
- C replies to this NOTIFY

----------------------utf8-----------------------
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.27.141.151;branch=z9hG4bK65961cae897ba970a6b559776cd2cf88
To: <sip:[email protected]>;tag=15672359
From: "31004"<sip:[email protected]>;tag=171c87e6f9b80ed5f6819b411a72505c
CSeq: 1644340323 NOTIFY
Content-Length: 0
-------------------------------------------------
Ed. 12 115 TG0069

OmniPCX Enterprise
12.10.2.2 Use of REFER with replaces.
C calls A and C calls D and makes a transfer

- C sends a REFER to the SIPMOTOR to replace an existing dialog
----------------------utf8-----------------------
REFER sip:oxe-ov.alcatel.fr SIP/2.0
Via: SIP/2.0/UDP 172.27.141.210:63016;branch=z9hG4bK-d87543-d60505761b7d746d-1--d87543-;rport
Max-Forwards: 70
To: "31004"<sip:[email protected]>;tag=0219e846e66c868f72a9dbdfa8e58e2a
From: "31026"<sip:[email protected]>;tag=9c131c4f
Call-ID: ZTBjODRhNzFhYTY3ZGNiMjI4N2FjZDQzNTI2MjA2YjE.
CSeq: 7 REFER
Refer-To: "31023"<sip:31023@oxe-
ov.alcatel.fr?Replaces=YTI4MmJhZjcyMDAyYmYyODI2ZmU0NmE5MWVhMGU2MDc.%3Bto-
tag%3D053621a0570c23654c20fb10154dd7f5%3Bfrom-tag%3D7728f179>
Content-Length: 0
In-------------------------------------------------
this call flow there are three legs:
Leg1 corresponds to the call from C to A
Leg2 corresponds to the call from C to D for the direction C to SIPMOTOR
Leg3 corresponds to the call from C to D for the direction SIPMOTOR to D
In this REFER, the following information are present:

Refer-To contains the directory number of the transfer destination with a Replaces corresponding
to the leg to replace (leg2)
Referred-By contains the directory number of the user doing the transfer.
At the end of the transfer the leg1 is closed by C and leg2 is closed by the SIPMOTOR, only the leg3 from
the A to D remains.
12.10.2.3 Use of REINVITE with replaces.
C calls A and C calls D and C makes a transfer

- C sends a REINVITE to the SIPMOTOR to replace an existing dialog
----------------------utf8-----------------------
INVITE sip:oxe-ov.alcatel.fr SIP/2.0
Via: SIP/2.0/UDP 172.27.141.210:63016;branch=z9hG4bK-d87543-71672411fa2ca01c-1--d87543-;rport
Max-Forwards: 70
To: "31004"<sip:[email protected]>;tag=0219e846e66c868f72a9dbdfa8e58e2a
From: "31026"<sip:[email protected]>;tag=9c131c4f
Call-ID: ZTBjODRhNzFhYTY3ZGNiMjI4N2FjZDQzNTI2MjA2YjE.
CSeq: 6 INVITE
Replaces=YTI4MmJhZjcyMDAyYmYyODI2ZmU0NmE5MWVhMGU2MDc.%3Bto-
tag%3D053621a0570c23654c20fb10154dd7f5%3Bfrom-tag%3D7728f179>
Content-Length: 256
The principle is the same than a REFER with replaces, but it is a REINVITE message
On this REINVITE, the next information are present:

Referred-By contains the directory number of the user doing the transfer.
Replaces contains the the directory number of the transfer destination with a Replaces
corresponding to the leg to replace (leg2).
Ed. 12 116 TG0069

OmniPCX Enterprise
12.10.3 UPDATE on Early Media
In some calls scenarios, the OXE will send or receive an UPDATE on Early Media (before dialog opened) to
change the SDP.
SIP phone C
(31026)
OmniPCX Enterprise
Legacy phone A (31004)
Phone A calls B, B calls C and makes a blind transfer to C.
During the RINGING phase, the OXE will send an UPDATE (after sending the 180 RINGING) to C. The OXE
has to send a PRACK before sending the UPDATE, to make a Pre-Acknowledgment and receive a 200ok for
this PRACK.
After this, the OXE will be able to send the UPDATE.
- To send a PRACK the OXE needs a Require: 100rel on the 18X answer received:
----------------------utf8-----------------------
SIP/2.0 180 Ringing
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, SUBSCRIBE, OPTIONS, UPDATE
Contact: sip:172.27.143.186
Require: 100rel
To: <sip:[email protected];user=phone>;tag=d7758dbc7f49c9521d28e60ef312ab04
From: "IPtouch 172.27.1" <sip:31000@oxe-
ov.alcatel.fr;user=phone>;tag=0c835efa2e1bf86a90d0016a
Via: SIP/2.0/UDP 172.27.141.151;branch=z9hG4bK61c571ebc4b1f5e5ff9e122e7e8b4a06
RSeq: 1131790336
Content-Length: 0
- After receiving this Require: 100rel, the OXE generates the PRACK
-------------------------------------------------
----------------------utf8-----------------------
PRACK sip:172.27.143.186 SIP/2.0
Supported: replaces,timer,path
RAck: 1131790336 679245852 INVITE
From: <sip:[email protected];user=phone>;tag=0c835efa2e1bf86a90d0016a0389c18e
CSeq: 679245853 PRACK
Via: SIP/2.0/UDP 172.27.141.151;branch=z9hG4bK8b757b21da861556184ff74e5f5aaca7
Max-Forwards: 70
Content-Length: 0
-------------------------------------------------
Ed. 12 117 TG0069

OmniPCX Enterprise
- The OXE receives the 200ok of the PRACK

----------------------utf8-----------------------
SIP/2.0 200 OK
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, SUBSCRIBE, OPTIONS, UPDATE, INFO
Supported: timer,path,100rel
CSeq: 679245853 PRACK
-------------------------------------------------
- The OXE sends the UPDATE to change the SDP.

----------------------utf8-----------------------
UPDATE sip:172.27.143.186 SIP/2.0
Supported: replaces,timer,path
RAck: 1131790336 679245852 INVITE
CSeq: 679245852 UPDATE
Max-Forwards: 70
Content-Length: 291
v=0
o=OXE 1339422663 1339422663 IN IP4 172.27.141.151
s=abs
c=IN IP4 172.27.142.64
t=0 0
a=sendrecv
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=ptime:20
-------------------------------------------------
The UAS receiving this UPDATE is able to use the connection point for the RTP flow
Ed. 12 118 TG0069

OmniPCX Enterprise
12.11 Configuration issues

Most of the SIP issues are linked to a bad management.
When you connect a SIP equipment, it is mandatory to check if this equipment is tested and validated by
Alcatel-Lucent
- The SIP equipments like faxs, sets, etc are validated via the AAPP. The
Configuration procedures are available on BPWS.
- The SIP providers test the connection with OXE themselves. So if you want to
connect one SIP provider, check if this provider has done the interopability test. All
the configuration procedures are given by the providers and not by Alcatel-Lucent.
If a connected SIP equipment is not validated by Alcatel-Lucent, no support will be provided.
12.11.1 SIP configuration rule
General Parameters
- DPNSS prefix (necessary for optimisation on call forward).
- System codec (G729, G723).
- Support of multi-algo should be set to false.
Netadmin
- Use of specific characters (& _ $ ...) is not allowed for the nodename.
- Activate internal name resolver in spatial redundancy topologies.
Local SIP gateway

- The local SIP gateway is managed when the SIP Trunk group and the SIP Subnetwork are
managed (minimum of configuration to do).
Alcatel-Lucent recommends to use an ABCF SIP Trunk Group on the local SIP
gateway
The network number is a free one, must not used by another application (ABCF
network, Hybrid links, VPN hop, etc).
This network number is the same than the one managed on the SIP ABCF Trunk
Group linked to this local SIP gateway.
External SIP Gateway

- The external SIP gateway can use the same Trunk Group (TG) as the local SIP gateway.
- The external SIP gateway can use another Trunk Group.
If it is an ABCF TG, the network number set for this TG is different from the one
used on the TG used by the local SIP gateway.
If it is an ISDN TG, let the OXE manage the network number by itself. The
configuration is the same as a real ISDN T2/T1.
- If the external SIP gateway uses an ISDN SIP TG, only ARS must be used, no network or
routing numbers.
- If the external SIP gateway uses an ABCF SIP TG, network or routing numbers can be used
without restrictions. If the ARS is used, the OXE must not receive REFER (or REINVITE with
replaces) or 30X messages on this external SIP gateway (ARS limitation).
SIP Trunk group

- ABCF SIP TG: no restrictions about SIP messages.
- ISDN SIP TG: no REFER (or REINVITE with Replaces) or 30X messages will be sent and
received.
Ed. 12 119 TG0069

OmniPCX Enterprise
SIP Proxy
- By default, the SIP proxy is set with SIP Digest for the Minimal authentication method, but
there is no Realm managed, so it is necessary to disable the authentication (SIP None) or to
manage a Realm.
In case of SSH management, the SIP equiments must be managed as SIP gateway (choice 1).
12.11.2 SIP alarms generated on OXE
On the OXE SIP incidents are generated on Call Handling side, thes incidents are linked to a SIP alarm (files
under /tmpd), here an example of SIP alarm generated:
Alarm due to Subscriptions:
> 02/07/12 - 15:39:35 Warning alarm

37F6 [CResponse::checkResponseFields] unknown header is not applicable for
202/SUBSCRIBE responses
> 02/07/12 - 15:39:35 Minor alarm

[CSubscriptionState::receiveSubscribeMessage] Call: 28844ea68ff53075 eqt: -1
SUBSCRIPTION_STATE failed to emit a Successful message.
In that situation, the OXE receives a SUBSCRIBE message, but is not able to answer it, because the
purpose of this SUBSCRIBE message is unknown by the OXE.
When this types of alarm are present on the OXE, remove the Subscription on the remote SIP equipment to
avoid the Alarm.
When lots of alarms like these ones are generated on OXE, they can cause a crash of the SIPMOTOR.
Alarm due to bad SIP call context not copied on Stand-By CPU:
> 02/07/12 - 15:39:35 Warning alarm

37F6 [receiveInviteMessage] StandByCallCreation failed !.
On the traces, these information are present:
1309553189 -> [CDuplicateCall::create_duplication_data_struct] _ViaSet size 218.

1309553189 -> [CDuplicateCall::create_duplication_data_struct] Via is bigger than
uiCAlcStrStaticGrow:192 - RealSize:218.
1309553189 -> ALARM: [receiveInviteMessage] StandByCallCreation failed !.
In that situation, on the INVITE received, the VIA header is too long for the OXE and it is not able to send the
SIP context to the stand by CPU. The call is established, but in case of bascul, this will not be known by the
new main CPU.
Alarm to send an INVITE message:
> 02/07/12 - 15:39:35 Minor alarm

[receiveInviteEvent] Call: eqt: 30311 INITIAL_STATE failed to emit an Invite
message.
When the Information is receiveInviteEvent, the Call Handling sends an INVITE to the SIPMOTOR, but due
to a lack of ressources or licenses the INVITE cannot be sent by the SIPMOTOR.
Ed. 12 120 TG0069

OmniPCX Enterprise
> 02/07/12 - 15:39:35 Minor alarm

[receiveInviteMessage] failed to emit an Invite event.
When the Information is receiveInviteMessage, the SIPMOTOR has received an INVITE but due to a lack
of ressources (channels on SIP Trunk Group, CAC, compressors, ...) or licenses, the SIPMOTOR cannot
send the INVITE to the Call Handling.
Alarm due to a request not for the SIP proxy of the OXE:
> 06/05/12 - 21:56:44 Warning alarm

[CIOCom::receiveResponse] Received response is not for this entity
This alarm means that the SIPMOTOR receives a SIP request thats not for it, and is not able to route it to
another SIP equipment. Its necessary to make a SIPMOTOR traces to get the IP address of this SIP
equipment.
Alarm to send a SIP message MESSAGE:
> 06/05/12 - 22:14:46 Minor alarm

[receiveMessageEvent] Call: eqt: 2862 INITIAL_STATE failed to emit an instant
message.
The SIPMOTOR is not able to send a SIP message to a SIP extension. Remove the fact to send this
message on the SIP extension phone cos.
Alarm to emit a SIP message CANCEL:
> 03/08/12 - 09:31:11 Minor alarm

[receiveCancelEvent] Call: [email protected] eqt: 2175
COMPLETED_STATE failed to emit a Cancel message.
The SIPMOTOR generates this alarm because it is not able to send a CANCEL message, because the
dialog is already opened. The Call Handling asks the SIPMOTOR to send a CANCEL, but the 200ok for this
INVITE transaction is already arrived.
Alarm to emit a SIP message ACK:
> 02/24/12 - 16:31:42 Minor alarm

[receiveAckEvent] Call: [email protected] eqt: 2175
TERMINATED_STATE failed to emit an Ack message.
The SIPMOTOR generates this alarm because it is not able to ACK an INVITE transaction, because the
transaction is already terminated. Open a SR for analysis.
Ed. 12 121 TG0069

OmniPCX Enterprise
12.11.3 Common SIP issues
This part is used to explain the general possible issues on the OXE, not for a specific equipment
12.11.3.1 SIPMOTOR
Issue 1: No SIPMOTOR processes are running
- Symptom: With the ps -edf | grep sipmotor command, no processes are present
- Explanation: This is due to a bad configuration of the SIP on your OXE. For instance the SIP
Trunk group managed on the local SIP gateway is not a SIP Trunk Group.
- Solution: Manage the good configuration and a restart of the CPU is mandatory.
Issue 2: Only 2 SIPMOTOR processes are running
- Symptom: With the ps -edf | grep sipmotor command, only 2 SIPMOTOR processes are
present
- Explanation: When a modification is done on the SIP Trunk Group associated to the local
SIP gateway, for instance to replace Mini SIP Trunk group by a SIP Trunk group, the OXE
needs do resize the memory space due to this modification (often after the first management
of the local SIP gateway)
- Solution: A restart of the CPU is mandatory
Issue 3: SIPMOTOR in degraded mode
- Symptom: SIPMOTOR is rejecting all the call by a 503 message, and with the tool
sipdump, the status of the SIPMOTOR is in degraded mode
- Explanation: This a protection for the SIPMOTOR, when there are too many SIP instance
in the SIPMOTOR, the SIPMOTOR switches in degraded mode to protect itself. When it has
this status, all the incoming SIP requests are rejected by a 503. This mechanism avoids the
application from being overwhelmed by the traffic.
- Solution: nothing can be done, the SIPMOTOR will disable this mode automaticaly due to
some internal timers and thresholds. However, check that all Remote Domain and SIP
Outbound Proxy addresses are correctly added on Trusted IP Addresses.
Issue 4: Losing all the SIP call contexts
- Symptom: If a restart of the SIPMOTOR is performed, all the SIP call contexts are lost
- Explanation: The restart of the SIPMOTOR provides the loss of all the SIP contexts. If SIP
calls are established, the RTP flow is maintained. At the SIP point view the call is not
present anymore, which means that if the SIPMOTOR receives a BYE for a call, the BYE will
be answered by a 481 Call/Transaction Does Not Exist, but the call will be stopped. Also if
Ed. 12 122 TG0069

OmniPCX Enterprise
you use the session timer (time to check if the call is still up for the SIP point of view) the call
will be cut by the OXE because the context is unknown by the SIPMOTOR
- Solution: This is a normal behaviour if the restart is done manually. If the SIPMOTOR
automatically restarts a SR must be opened for analysis.
Issue 5: SIPMOTOR memory leak.
- Symptom: The SIPMOTOR is using more and more memory space.
- Explanation: When the SIP is managed on the OXE, the SIPMOTOR processes uses
memory space. When the traffic is going up, the used memory space is increasing. When
the traffic rate is going down, the memory space used is decreasing.
Now, if when the traffic rate is going down, the memory space used doesnt decrease
correctly, and if day after day, even if there is no traffic, the used memory is growing, the
SIPMOTOR will finally crash. In such case, the SIPMOTOR has problems to delete some
SIP contexts from its memory. After accumulation of the not deleted SIP contexts, the
SIPMOTOR cannot work properly and crashes.
- Action to do:
Check if the configuration of the OXE respects the Alcatel-Lucent

recommendations.
Check if the REGISTER messages received on SIPMOTOR are not too much,
the registration of a SIP equipments must not be used as a keep alive.
Check if the SIPMOTOR doesnt receive SIP messages not for it.
Check if the SIPMOTOR doesnt receive SUBSCRIBE messages not used by
OXE.
- Solution: A restart of the SIPMOTOR can be done and due to this, all the SIP contexts are
deleted. The problem will be solved but only for a time, if the root cause is not found, the
problem will be back again. Open a SR for analysis.
Ed. 12 123 TG0069

OmniPCX Enterprise
12.11.3.2 Call failure
Issue 1: Incoming SIP calls are cut by the OXE after 32 seconds:
- Symptom: Incoming SIP calls are cut by the OXE after ~3 seconds (or 32 seconds in case of
SIP extension) and the 200ok from OXE is never ACK by the external SIP equipment.
- Explanation: If the system is in spatial redundancy, check if the FQDN of the OXE is used by
the external SIP equipement. In fact on the Contact, the FQDN is added by the OXE. This
FQDN is unknown by the SIP equipment (because it uses the IP address), and it doesnt
answer to this 200ok. The OXE sends several times the 200ok and cuts the call because no
ACK is received for this call.
- Solution: The remote SIP equipment must use the FQDN of the OXE. Since the R10, a
parameter is present on the external SIP gateway only Contact with IP address used to put
the IP address of the main CPU instead of the FQDN in the Contact header.
Issue 2: Calls are not possible anymore from a SIP equipment:
- Symptom: The SIP calls are not possible thru an external SIP gateway in high traffic.
- Explanation: Check if the IP address managed on the external SIP gateway is put in
quarantine (in sipalarm files)
- Solution: Manage the IP address on the trusted SIP IP addresses. A restart of the
SIPMOTOR is mandatory after management.
Issue 3: SIP calls are rejected with a 502:
- Symptom: A SIP call, using an ABCF SIP Trunk Group, to an external number is not
possible (thru a carrier for instance) and rejected most of the time by a 502 Bad Gateway.
Internal calls are ok and incoming calls also ok for this SIP equipment.
- Explanation: When the message 502 is reponded to a SIP request, the problem is due to the
management, that means, the information on the SIP request are not good for the call in
progress. In that case, the call is done from an ABCF SIP Trunk Group to an external called
party, the call is rejected because the DID transcoding is set to True on the ABCF SIP
Trunk Group
- Solution: Set the DID transcoding of the SIP ABCF Trunk group to false (mandatory).
Issue 4: SIP calls are rejected with a 488 Not Acceptable here:
- Symptom: A SIP call is rejected by 488 SIP message,
- Explanation: When a SIP call arrives on the OXE, the Call Handling checks if the SDP
received is compatible for this call, if it is not the case, the Call Handling asks the
SIPMOTOR to send a response 488 for this request
- Solution: Manage the SDP of the SIP equipment to be compatible with the configuration of
the OXE or the opposite.
Ed. 12 124 TG0069

OmniPCX Enterprise
Issue 5: SIP calls are rejected with different reasons:
- Symptom: A SIP call is rejected by 488, 502, 404, etc...
- Explanation: When a SIP call arrives on the OXE, this call is automatically rejected by OXE,
but the reason can be different, even if the scenario of the call is the same. The SIP is linked
to the shelf 19 associated to the CPUs, so if the CPUs are not belonging to the IP domain 0,
the virtual INTIP boards of the shelf 19 doesnt belong to the IP domain 0, and the SIP is
affected by this configuration.
- Solution: Manage CPUs IP addresses on the IP domain 0, this mandatory in case of SIP.
Issue 6: SIP calls are rejected with 403 No license available:
- Symptom: A SIP call is rejected by 403 No license available.
- Explanation: When a SIP call is done, a license is used for this call. In case of incoming call,
if no more license is available, the OXE rejects the call by a 403 No licenses available. The
problem can be only the number bought by the customer. It is no enough according to the
number of simultaneous SIP calls, or some SIP call contexts are blocked on the
SIPMOTOR.
- Action to do:
When no more SIP calls, restart the SIPMOTOR.

Run the SIPMOTOR traces:
>motortrace 3 (or 6)
>traced -l /tmpd/traced -s 10000000 -f 50 -d &
Keep the trace running until the issue is present.
When the issue is present, run sipdump and make the choice 1 and 4 every
minutes during 5/10 minutes.
Stop the traces
When no more SIP calls are present on OXE, run the following traces (do not
restart the SIPMOTOR!!!):
>motortrace 3 (or 6)
>traced >/tmpd/trace_sip.log and make one call and stop it.
On the file trace_sip.log, search for nb available licenses=.
- Solution: If the number of licenses is the number of the licenses bought on OXE, there is no
issue, the solution is to buy more licenses. If the number is less than the number bought,
open a SR and provide the traces files and the Infocollect of the site.
Ed. 12 125 TG0069

OmniPCX Enterprise
12.11.4 SIP Device issues
An important thing to remember about SIP device is that all the calls are linked to the SIP Trunk Group
associated to the local SIP Gateway. So if you manage a SIP ABCF Trunk Group or an ISDN SIP Trunk
Group, the behaviour will be different.
Issue 1: Forward on no reply doesnt work when the destination is a SIP device:
- Symptom: It is not possible to make a forward on no reply (on an IPtouch for instance) when
the destination is a SIP device, ok for immediat forward.
- Explanation: The SIP device behavior is linked to the SIP Trunk group associated to the
local SIP gateway, if you use an ISDN SIP TG, or an ABCF SIP TG, the behaviour will be
different. The SIP Trunk Group used on the local SIP gateway is a SIP ISDN TG.
- Solution: Change the SIP Trung Group managed on the local SIP gateway from SIP ISDN
TG to SIP ABCF TG. A restart of the SIPMOTOR is mandatory.
Issue 2: Afer a while, all SIP phones registrations and subscriptions are impossible
- Symptom: More than 1000 SIP Devices loose their registration. Only a double bascul of
PBX resolves this issue
- Explanation: As there are more than 1000 SIP devices which register/subscribe at the same
time, there is too much traffic to be managed by the PBX and resources on SIPMOTOR are
blocked. Around 45000 Subscription and Registration can be handled in 3 hours time. This
is really a big number. Oxe is dealing with. Solution should be to stop some of the unwanted
Subscribe messages, and increase the subscriptions and registration timers on SIP Devices.
Unwanted subscriptions meant here was even though voice mail was not configured for a
phone set, subscription value was configured, this should be 0.
Example of Registration too brief:

Sun Sep 30 06:53:09 2012 RECEIVE MESSAGE FROM NETWORK (172.30.125.75:5060 [UDP])
----------------------utf8-----------------------
REGISTER sip:172.30.127.2:5060 SIP/2.0
Expires: 60
1348980789 -> Sun Sep 30 06:53:09 2012 SEND MESSAGE TO NETWORK (172.30.125.75:5060 [UDP]) (BUFF LEN =
394)
----------------------utf8-----------------------
SIP/2.0 423 Registration Too Brief
Min-Expires: 1800
Example of sipalarm when subscription is impossible on /tmpd:

[CSubscriptionState::receiveSubscribeMessage] eqt: -1 SUBSCRIPTION_STATE failed to emit a Successful
message.
Example of DHCP buffer issue on /varlog/messages:
Nov 7 00:01:52 sr_cpub dhcpd: send_packet: No buffer space available

Nov 7 00:01:52 sr_cpub kernel: Neighbour table overflow.
Nov 7 00:01:52 sr_cpub kernel: Neighbour table overflow.
- Solutions:
1. Increase registration and susbcriptions timers on SIP Devices from 60 secondes to
1800.
Ed. 12 126 TG0069

OmniPCX Enterprise
2. Deactivate unnecessary subscriptions sent to PBX when no services are configured

on users management, example: if Voicemail is available via another application,
subscription must not be sent to PBX
3. Configure a dedicated VLAN for OXE (CS, GD) and one or more VLANs for SIP
Devices in order to decrease ARP requests on DHCP service
With the current Linux OS, OXE has a limitation in handling more than 1000 data equipment if it
is connected in the same sub-network. So we need to have a seperate VLAN in between to
handle this. OXE CS must be placed under separate subnet and the IP Phones distributed under
different other subnets
12.11.5 SIP extension issues
The SIP extension is not linked to a SIP Trunk Group, it can be created without SIP management
Issue 1: SIP fax equipment, declared as a SIP extension, doesnt work:
- Symptom: when a SIP fax equipment tries to make a call, the REINVITE for the T38
negociation is never seen
- Explanation: When a SIP fax call is done, the establishement of the call is done in two
phases, opening of RTP channel then opening of a T38 channel, in case of SIP extension,
the T38 is not implemented, so the second phase cannot be done, and the call is stopped
- Solution: Use of a SIP Device user instead of a SIP extension
Issue 2: SIP extension multiline, SIP phone monoline:
- Symptom: when a SIP extension is created, it is a multiline user, and if the SIP phone is
associated is monoline, the functioning of the SIP extension can cause issue
- Explanation: A SIP extension user, declared in business mode, is multiline, that means taht
teh SIP phone associated must be multiline as well, if it is not the case, the call to the
second line of the user is rejected by the SIP phone, and this can cause disturbances on the
SIP extension behaviour (call handling side) .
- Solution: A SIP phone associated to a SIP extension user must be multiline.
12.11.6 SIP External Gateway Issue
Issue 1: One way calls after remote SIP equipment put on hold and call is retrieved:
- Symptom: A SIP call is done between the OXE and a remote SIP gateway. This SIP
equipment puts the call on hold, the OXE equipment can hear the MOH, and when the SIP
equipment retrieves it, the one way call is present.
- Explanation: When the SIP external gateway puts on hold, it sends a REINVITE with a
Black Hole (c=0.0.0.0 on SDP) or an INACTIVE to stop the RTP flow, before sending a
new REINVITE with a SDP for MOH. When a new REINVITE is sent to get back the
converstaion, the OXE is not able to connect the RTP flow to the SDP given on this
REINVITE.
Ed. 12 127 TG0069

OmniPCX Enterprise
- Solution: On the external SIP gateway, set the parameter Ignore inactive/black hole to
TRUE. In that case, the OXE will not take into account the Black Hole or the INACTIVE.
Issue 2: One way call in case of incoming/outgoing calls:
- Symptom: An incoming or an outgoing calls are well established, but no speech sent by
OXE
- Explanation: The problem has been seen after an upgrade from a version lower to I160516c
to a R10. On the traces taken, the OXE is not getting SDP or, INVITE or 200ok. The problem
was about the parameter Routing Application, this parameter is used for the feature
Force_on_NET. In case of incoming call to the OXE, this call is not for an equipment
connected to the OXE, but for an external user (mobile phone for instance), so for such call,
the OXE doesnt need to reserve ressources on its side. This parameter has been designed
for that.
- Solution: Set the parameter to False if it set to True.
Issue 3: No SDP in the outgoing INVITE

- Symptom: No SDP in the outgoing INVITE
- Solution: Set the parameter to False if it set to True.
11.13 Summary for SIP issue analyse

The purpose of this chapter is to give a way to analyse a SIP issue.
In case of SIP issue, a minimum of traces must be done, the motortrace trace is the minimum. The
Infocollect must always be done in case of SIP issue to get all the information needed to troubleshoot.
Here are the different steps to start the analyse:
- Check if the SIP equipment is validated by Alcatel-Lucent.

- Check if the OXE configuration and SIP equipments respect the rules given on this
document.
- Check if the CPUs belong to the IP domain 0.
- Check the Network management.
- Check the local SIP configuration (motortrace c).
- Check the incvisu file, and if SIP incidents, check the sipalarm files to find the causes of
them.
- Check if an incident or a backtrace is generated when the issue is present.
- Check if the problem is from the SIPMOTOR or the Call Handling
If a SR will be opened:
- Provide a minimum of traces.

- Provide the call scenario (Caller, Called Party, IP addresses, etc...), provide all the
information you can.
- Provide the Infocollect.
- Provide your analysis of the issue, it is mandatory for you to make an analysis before
opening a SR.
Provide a remote connection to the site (RMA, VPN, etc...)
Ed. 12 128 TG0069

OmniPCX Enterprise
13. SYMPTOMS, DIAGNOSIS AND SOLUTIONS

13.1.1 Outgoing Call Cancel sent by OXE after 180 w SDP
Symptom: SIP ISDN Outgoing call are cancelled by OXE after 180 Ringing SDP (G711) reception.
Diagnosis: - Check if CSs IP Address is configured on IP Domain 0.

- Check extra domain codec where caller is located
Solution: As only G711 codec is available for Outgoing calls ( IP Compression Type + G711 on TG) and
caller is located in a restricted domain (Extra Domain Coding Algorithm + With Compression on IP
Domain), OXE cannot sends/receives media stream. Call is cancelled.
13.1.2 Telephone-event are not provided on SDP offer
Symptom: Re-INVITE sent by OXE to SIP Provider doesnt contain telephone event media on SDP offer
Solution: On SIP > SIP External Gateway, set parameter To EMS to False.
13.1.3 Loss of communication with SIP External Voicemail
Symptom: Frequent loss of communication between external voicemail and OXE connected via SP trunk
Diagnosis: Check if congestion occurs with incident 5816 when you try to access to the voice mail.
Check if Voicemail IP Address is present on Trusted IP Addresses
Solution: Voicemail was put in quarantine and during one half hour all calls in direction of Voicemail were
blocked
13.1.4 Impossible to let a message when routing via SIP Automated Attendant
Symptom: It is not possible to let a message on the voicemail of the called number in case of an automated
attendant SIP and when the Phone Feature COS Voicemail forwarding is set at Ring called set mail
Solution: On System > Other System Param. > Spec. Customer Features Parameters > Voice Mail
forwarding SIP auto att, set this parameter to true
13.1.5 When call is transfer from a Third Party Server, after few seconds, a Re-Invite is
sent by OXE to reroute RTP to a GD card
Symptom: When call is established, after few seconds, OXE sends a reinvite request to redirect RTP to a GD
card.
Solution: DPNSS is used on this scenario. On System > Other System Param. > External Signalling
Parameters > DeActivate Path Replacement, set this parameter to true
13.1.6 Incoming call from a SIP Third Party Server is rejected by OXE with a SIP Error 488
Not Acceptable Here
Symptom: Incoming call is rejected by a SIP Error 488 Not acceptable Here
Ed. 12 129 TG0069

OmniPCX Enterprise
Diagnosis: Check Extra Domain Coding Algorithm concordance

Check Public Access Category
Solution:
On IP > IP Domain > Extra Domain Coding Algorithm must be the same as third party offer
On Categories > Access Category > Go down hierarchy > Public Access Category > Select COS 31
and give correct rights
13.1.7 Incoming call is not recognized as INTERNATIONAL
Symptom: Incoming call received on set phone indicates local call instead of international call.
Diagnosis: - Country code is not separated of received number by PBX so canonical form is not correctly
set up. Canonical form is + country code *(number). So, number should be +4971182137777 in order
to detect that is an international incoming call.
Solution: Add the country code 49 on External Country Code section Translator > External Numbering Plan >
Country Codes:
Country code prefix : 49
Country Value + Germany
13.1.8 When we attempt to register on SIP External Gateway, OXE answers by a SIP error
482 Loop Detected
Symptom: For each register sent to OXE, we have a SIP error 482 Loop Detected, as below REGISTER
request:
1352974529 -> Thu Nov 15 11:15:28 2012 SEND MESSAGE TO NETWORK (172.27.139.90:5060 [UDP]) (BUFF LEN
= 478)
----------------------utf8-----------------------
REGISTER sip:hq2cs.labjtr.fr SIP/2.0
Supported: 100rel,path
User-Agent: OmniPCX Enterprise R10.1 j2.501.16.c
To: sip:[email protected]
From: sip:[email protected];tag=a9ca34e0b0534fb9d4e0823b7b5d4eaa
Contact: <sip:[email protected];transport=UDP>;expires=1800
And error received:

Thu Nov 15 11:15:28 2012 RECEIVE MESSAGE FROM NETWORK (172.27.139.90:5060 [UDP])
----------------------utf8-----------------------
SIP/2.0 482 Loop Detected
From: sip:[email protected];tag=a9ca34e0b0534fb9d4e0823b7b5d4eaa
CSeq: 1821162596 REGISTER
Via: SIP/2.0/UDP 172.27.145.122;branch=z9hG4bK47b7d67d20268bb0c40d57c60e4c1cb9
Content-Length: 0
Diagnosis: Registration is done by Domain Name resolution so the sip Request-URI sip:hq2cs.labjtr.fr must
be matched with machin name filled on SIP Gateway. The SIP URL of REGISTER contains the SRV/A
domain name. Proxy loops that call back to itself because it does not know about itself as the SRV/A domain.
Solution: Modify the SIP Gateway in order to have the same Machin Name as SIP URL contained on
REGISTER, use the command netadmin to do it:
Trunk Group : 35
IP Address : 172.27.139.90
Machin name : hq2cs.labjtr.fr
Proxy Port Number : 5060
DNS local domain name : labjtr.fr
DNS type + DNS A
First DNS IP Address : 172.27.139.88
Ed. 12 130 TG0069

OmniPCX Enterprise
13.1.9 When we attempt to register our SIP External Gateway with an external SIP Proxy,
SIP Proxy answers by a SIP error 416 Unsupported URI Scheme
Symptom: For each register sent to external SIP Proxy, we have a SIP error 416 Unsupported URI
Scheme, as below REGISTER request:
1352975879 -> Thu Nov 15 11:37:56 2012 RECEIVE MESSAGE FROM NETWORK (172.27.145.122:5060 [UDP])
----------------------utf8-----------------------
REGISTER sip:hq2.labjtr.fr SIP/2.0
To: sip:hq2.labjtr.fr
From: sip:hq2.labjtr.fr;tag=56b8ce5bd76524902b5c171f39c9bbdf
Contact: <sip:172.27.145.122;transport=UDP>;expires=1800
Via: SIP/2.0/UDP 172.27.145.122;branch=z9hG4bKdc224f76827da20ba9390b081ef8aed0
Max-Forwards: 70
Content-Length: 0
And error received:

Thu Nov 15 11:37:56 2012 SEND MESSAGE TO NETWORK (172.27.145.122:5060 [UDP]) (BUFF LEN = 344)
----------------------utf8-----------------------
SIP/2.0 416 Unsupported URI Scheme
To: sip:hq2.labjtr.fr;tag=75e766ee37e6bf967b4c84db521f8406
From: sip:hq2.labjtr.fr;tag=56b8ce5bd76524902b5c171f39c9bbdf
Via: SIP/2.0/UDP 172.27.145.122;branch=z9hG4bKdc224f76827da20ba9390b081ef8aed0
Content-Length: 0
Diagnosis: Registration ID is not present on REGISTER request so SIP Proxy cannot authenticate the OXE.
Configure the parameter Registration Id on SIP External Gateway
Solution: Configure the parameter Registration Id on SIP External Gateway, as well

1352976351 -> Thu Nov 15 11:45:50 2012 RECEIVE MESSAGE FROM NETWORK (172.27.145.122:5060 [UDP])
----------------------utf8-----------------------
REGISTER sip:hq2.labjtr.fr SIP/2.0
From: sip:[email protected];tag=bfc35e619db3ff4f042097e7b390c30a
Via: SIP/2.0/UDP 172.27.145.122;branch=z9hG4bK8d42eea8f1c72df626c86ea191f7ff76
Max-Forwards: 70
Content-Length: 0
Thu Nov 15 11:45:50 2012 SEND MESSAGE TO NETWORK (172.27.145.122:5060 [UDP]) (BUFF LEN = 396)
----------------------utf8-----------------------
SIP/2.0 200 OK
To: sip:[email protected];tag=2810b4ed27aa41ba89b99ef3631a8c0d
From: sip:[email protected];tag=bfc35e619db3ff4f042097e7b390c30a
Via: SIP/2.0/UDP 172.27.145.122;branch=z9hG4bK8d42eea8f1c72df626c86ea191f7ff76
Content-Length: 0
Ed. 12 131 TG0069

OmniPCX Enterprise
13.1.10 Incoming call doesnt transit via Trunk Group configured on SIP Ext Gw
Symptom: When we make a trkvisu of SIP Trunk Group used by SIP External Gateway during an incoming
call, we observed that no SIP Access is used.
Diagnosis: - by checking INVITE request received from Network, we can see that domain contained on
FROM header is not recognized by SIP External Gateway, so call transits through Main SIP Gateway.
1332292333 -> Wed Mar 21 02:12:13 2012 RECEIVE MESSAGE FROM NETWORK (172.27.138.36:5060 [UDP])
----------------------utf8-----------------------
Via: SIP/2.0/UDP 172.27.138.36:5060;branch=z9hG4bK15ac35dc;rport
Max-Forwards: 70
From: "Boss Hoggs" <sip:[email protected]>;tag=as5ff02451
Wed Mar 21 02:12:13 2012 [isDomainFromGwExt] Host from request is : 172.27.144.20.

Wed Mar 21 02:12:13 2012 [isDomainFromGwExt] User from request is : 0033XXXXXXXXX
Wed Mar 21 02:12:13 2012 [domain not from an External Gateway.
Wed Mar 21 02:12:13 2012 11cd[CMotorCall::onReceiveRequest] system option=0 extGw=-1.

Wed Mar 21 02:12:13 2012 11cd[CMotorCall::toGatewayOrProxy] request for proxydomain=172.27.144.20.
Solution: Modify FROM header sent by external application in order to match with remote domain configured
on SIP External Gateway
13.1.11 Wrong caller number sent in case of forward
Symptom: Wrong caller number on OpenTouch anymobile device when using multi device feature.
Example: External user 0980406562 (phone A)
OT MIC SIP directory number 7905 (358306667908) (phone B)
OT anymobile number +358 (0) 505307949 (phone C)
Phone A calls phone B with a redirection to phone C. During phone C ringing phase, Calling Number
of phone B is displayed instead of Calling number of phone A
Diagnosis: - Check if history-info/diversion header is present on requests received from OpenTouch with
related forward informations
- Check External Signalling Parameters (Calling Name Presentation, NPD for external forward
Solution: NPD for external forward is configured at -1 so OXE sends redirecting number in case of forward.
When parameters is configured with NPD used by SIP Trunk Group, initial Calling Number is sent.
Before NPD modification:

P-Asserted-Identity: "0501636" <sip:[email protected];user=phone>
From: "0501636" <sip:[email protected];user=phone>;tag=77b6c1402197fc477d9268f1a0563007
After NPD modification:

P-Asserted-Identity: "0501636" <sip:[email protected];user=phone>
From: "0501636" <sip:[email protected];user=phone>;tag=10067c3f78682c28d55da5b1cc350f86
13.1.12 Diversion/History-Info header is not present
Symptom: User A (+33298285305) calls user B (1481001) located on PBX. User B is on immediate forward
to User C (+33675445566). Second leg transits via the Trunk Group 16 (SIP ISDN All Countries) and SIP
External Gw 2 (Remote domain: 172.44.266.44). Diversion header is not added by OXE.
Ed. 12 132 TG0069

OmniPCX Enterprise
Diagnosis: - Check External Signalling Parameters, Trunk Group and SIP External Gateway configuration
Solution: Configure following parameters:

System > Other System Param > External Signalling Parameters
NPD for external forward: 10 (NPD used by SIP ISDN Trunk Group)
Trunk Groups > Trunk Group
IE External Forward: Diverting leg information
SIP > SIP Ext GW
Diversion Info to provide via: Diversion
(013064:000323) | Diversion :
(013064:000324) | Url : <> [email protected]
(013064:000325) | Reason : UNCONDITIONAL
13.1.13 SIP-Trunking Name is displayed on calling phone set when call is established
Symptom: SIP Trunking Name is displayed on calling phone set when call is established with an external
user through SIP Externl Gateway. SIP Trunk type is ISDN ALL COUNTRIES. Example: A is an internal
phone set and dials external number +33014596222, when call is established, phone set doesnt display
called number
Diagnosis: Check if SIP Carrier sends a P-Asserted-Identity header on SIP 200 OK Response when call is
established.
Solution: If no Called information is present on connection message (SIP 200 OK), OXE by default displays
the trunk group name.
13.1.14 From header doesnt have the national format

Symptom: Bad tagging of the calling from a SIP ISDN gateway
Diagnosis: When value on From header is not canonical, OXE tags the calling number like ISDN unknown
Solution: Modify the from received on OXE by adding canonical form and manage the country code like this
the calling number will be tagged as national
13.1.15 Incoming and outgoing fax communications impossible through SIP Gw

Symptom: Re-INVITE with T38 on SDP is not sent by FAX Server, voice communication is cut before T38
ngotiation
Diagnosis: As PBX is configured in spatial redundancy, FQDN is used. In this case, FQDN corresponds to
the nodename concatenate with the DNS local domain name managed on SIP Gw. When OXE makes a fax
call to Fax Server, FQDN is used on CONTACT header and as Fax Server cannot resolve it, call is cut.
Solution: Use an external DNS server for FQDN resolution or check at false the Contact with IP Address
parameter on SIP Ext Gw.
13.1.16 No Re-Invite with T38 offer sent by OXE

Symptom: No T38 bascul during fax communication between PBX and FAX Gw
Diagnosis: On INVITE sent by the FAX Gw, FROM header contains the IP Address of PBX instead of IP
Address of FAX Gw. So, when a Fax call arrives, this is the internal Sip Gw on PBX that is used and SIP-
ABCF trunk group associated. RE-INVITE(T38) is only available on trunk group SIP ISDN.
Solution: Modify the IP Address on From Header sent by Fax Gw
Ed. 12 133 TG0069

OmniPCX Enterprise
13.1.17 External call with secret identity over SIP Provider fails
Symptom: Impossible to receive incoming calls with the secret ID
Diagnosis: When a call is received with the secret ID, the call is rejected by OXE with a 480 (not able to
reach the third party)
Solution: The OXE is using the FROM field for the SIP gateway selection, in case of secret id, the FROM
field contains this: [email protected], so an external SIP gateway should correspond to the
domain part of the URI, in that case anonymous.invalid (SIP Remote domain), this external SIP gateway has
the same configuration than the one used to reach the SIP provider.
13.1.18 On SIP outgoing call, dynamic ports are used instead of port 5060
Symptom: why the OXE uses one of the dynamic ports for a SIP call instead of the port 5060?
Diagnosis: When a SIP trace is done with wireshark, the source port, when the OXE is the initiator of the
call, can be different from 5060 (SIP port managed on the database)
Solution: Regarding the RFC3581, the initiator of the SIP call can choose a port number different from the
default SIP port (5060) for its source port. So in that case the OXE is able to choose one port from the
range of dynamic ports.
The important impacts about this behavior is the management of the size of dynamic ports range and also to
take into accounts the configuration of the firewalls from the customers network, to authorize them to use the
dynamic ports for SIP communication.
13.1.19 A "+" character is added on calling number when ISDN call is routed to SIP
Diagnosis: Addition of "+" is normal, because incoming call from ISDN is tagged with 21 81 which
corresponds to a National Call and according to the RFC, a + must be added before the Calling Number
______________________________________________________________________________
| tei: 0 >>>> message received : SETUP [05] Call ref : 00 37
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 8c -> T2 : B channel 12 exclusive
| IE:[6c] CALLING_NUMBER (l=6) -> 21 81 Num : 2000
| IE:[7d] HLC (l=2) 91 81
|______________________________________________________________________________
Solution: The "+" is added because the calling party is tagged "national" on the ISDN call, so the OXE ia
added the "+". None configuration must be done on OXE side.
13.1.20 Diversion Field doesnt have the canonical form
Symptom: User A (+33298285305) calls user B (1481001) located on PBX. User B is on immediate forward
to User C (+33675445566). Second leg transits via the Trunk Group 16 (SIP ISDN All Countries) and SIP
External Gw 2 (Remote domain: 172.44.266.44). Diversion field has not the canonical form: 1481001
Diagnosis: Check NPD configuration, Diversion filed should be as follow: +331481001(canonical format)
corresponds to +33 (France Country Code) 1481001 (Forwarded device number)
Solution: Configure a NPD for normal calls and a NPD for forward as below:
Ed. 12 134 TG0069

OmniPCX Enterprise
Here is NPD for normal calls:

Consult/Modify: Numbering Plan Description (NPD)

Node Number (reserved) : 1
Instance (reserved) : 1
Description identifier : 100

Name : SIP
Calling Numbering plan ident. + NPI/TON Isdn National
Called numbering plan ident. + NPI/TON : Isdn Unknown
Authorize personal calling num use + True
Install. number source + NPD source
Default number source + None used
Called DID identifier : 10
Calling/Connected DID identifier : -1
Installation number : 9839

And this is NPD for fwd calls:

Consult/Modify: Numbering Plan Description (NPD)

Node Number (reserved) : 1
Description identifier : 69

Name : FWD
Calling Numbering plan ident. + Unknown
Called numbering plan ident. + Unknown
Authorize personal calling num use + False
Install. number source + None used
Default number source + None used
Called DID identifier : 10
Calling/Connected DID identifier : 10

13.1.21 Leg1 and leg2 are external set, when OXE user performs a blind transfer, it doesnt
work
Symptom: External UserA calls OXE user B thru public SIP Trunk(OXE user DDI: 210457060).
User B calls C (mobile phone) through public SIP trunk
B transfers the call to A before C answers
C answers the call but is not able to talk to external user, transfer is not complete by OXE
Diagnosis: Parameter Support Re-Invite without SDP is checked at TRUE on SIP External Gateway.
Consequence is OXE doesnt perform transfer due to a R&D restriction on support of PRACK by remote
according to this OXE configuration.
Solution: When PRACK is supported by SIP Provider, the parameter Support Re-Invite without SDP must
be checked at false on SIP External Gateway.
13.1.22 SingleStep Transfer with REFER, no referred-by in the following INVITE

Symptom: OXE user A makes a call to an external SIP Server user B through SIP ABC-F Trunk. SIP Server
user B makes a single step transfer to SIP Server user C with REFER method. In the following INVITE sent
by OXE, the header referred-by is missing (see RFC 3892)
Solution: Since 10.1 (J2.501.21 release), a new parameter is available on System > Other System Param >
SIP Parameters > Transfer : Refer using single step. This paramter is set by default at True and to obtain
Referred-by in such case, it must be checked at False.
Ed. 12 135 TG0069

OmniPCX Enterprise
13.1.23 Major alarm szSdpMessage > 1000 is present on sipalarm.log

Symptom: On SIPAlarm.log we can see many Major Sip Alarms [CDuplicateCall::sendRemoteSdp]
szSdpMessage > 1000 !!!!!!!!!
Diagnosis: The following issue is not a problem and is a generic restriction. When SDP received by OXE
exceeds the limit of 1000, INVITE is not duplicate on CPU standby. This allows to avoid problems on
duplication link.
Solution: Change on external application the SDP offer to get only the codec available on the OXE
13.1.24 SIP-Trunking Bad routing and bad display from time to time trough SIP trunk
Symptom: Customer complains of a bad routing of incoming calls from time to time. Also getting strange info
on screen as for example : customer receives " Unavailable " that is displayed on agent desktop and calls
are routed to bad RSI and Agent Group
Diagnosis: SIPMOTOR receives a call with following FROM header: [email protected] and TO
header 3256391522. As the FROM is wrong formatted, SIPMOTOR cannot find the SIP External Gateway
associated and the SIP Trunk Group.
Nevertheless, the INVITE transits via the Main Gateway (SIP > SIP Gateway) corresponds to virtual entity
1000 on Call Handling:
032042:033267) +------------------------------------------------------------+
(032042:033269) | INVITE : [email protected]:5060 ; user=phone
(032042:033270) | From : <> [email protected]:5060 ; user=phone
(032042:033271) | To : <"3256391522 3256391522"> [email protected]:5060 ; user=phone
(032042:033272) +------------------------------------------------------------+
(032042:033273) | SDP :
(032042:033274) | @IP:port = 81.247.255.128:14670
(032042:033275) | ALGOS :
(032042:033276) | PCMA
(032042:033277) | G729
(032042:033278) | DTMF : 101
(032042:033280) | cac : false
(032042:033281) | Prack_Required: 0
(032042:033282) | Allow_UPDATE: 0
(032042:033284) +------------------------------------------------------------+
(032042:033313) SIP sui_arr_sip :called_entity=1000
(032042:033319) SIP_remp_callin...
When incoming call doesn't match with a SIP External Gateway, default behavior is to send the call on Main
SIP Gateway, Trunk Group used is 59 where no DDI translation is activated so Call Handling take the Called
Number and find on the numbering plan the prefix 3 which corresponds to 2963.. and make the following
SETUP:
CALLING_NUMBER:
CALLED_NUMBER: 296322 => RSI monitored by Call Center
So call is routed to RSI 296322 and calling number cannot be displayed on agent desktop
Solution: Request SIP Provider to resolve the wrong FROM header [email protected]
13.1.25 SIPMOTOR goes to "Degraded mode enabled" state

Symptom: All register and call are not generated by Call Handling.
SIPMOTOR was in degraded mode the January 9th 2013 at 06:27:49. There was no traffic at this time.
Ed. 12 136 TG0069

OmniPCX Enterprise
A dhs3_init -R SIPMOTOR had to be used to restart the process
The installation consists of 20 external gateways. During the issue, no incidents or backtraces detected but
only incident 5816 Minor failure in SIP component. No major failure incidents to report.
Wed Jan 9 06:27:53 2013 11d1-----------------------------------------------------------------
Wed Jan 9 06:27:53 2013 11d1[CMotorCall::onTimersFires] Call (eqt=-1 diag=-1) timer fired type 5.
1357709273 -> Wed Jan 9 06:27:53 2013 11d1---------------------------------------------------------
--------
Wed Jan 9 06:27:53 2013 11d1[CMotorCall::onErrorOnSendRequest] stack::SRM_REGISTER
Wed Jan 9 06:27:53 2013 ALARM: [registerError] failed to emit a Register message.
Wed Jan 9 06:27:49 2013 ALARM: [CCall::CCall] Degraded mode enabled

Wed Jan 9 06:27:49 2013 ALARM: CPU main
Wed Jan 9 06:27:49 2013 [CMotorCall :: CMotorCall()] Oxe_Version_Name = OmniPCX Enterprise R10.0
j1.410.53
Diagnosis: We see on provided traces that the ip address 182.16.101.2 is quarantined continuously (4 times
in 2 hrs).
Hence the REGISTER message sent that ip addr. is failed and too many alarms triggerred. Thatswhy motor
goes to degraded mode. This is the main reason for the degraded mode. I checked the infocollect as well as
i loaded the customer database and found that there is no entry in trusted ip:
From infocollect, we can see that there is no ip in trusted ip list.

+-----------------------------------------------------------------------+
| Trusted IP Address List |
+-----------------------------------------------------------------------+
+-----------------------------------------------------------------------+
| Quaranted IP Address List |
+-----------------------------------------------------------------------+
If we include the ip addresses managed in external gateway in trusted ip then those ips will not be
quarantined. and no REGISTER message will be blocked.
Once you do this, there wont be much of alarm triggerred and Motor won't go to degraded mode.
Solution: Manage on Trusted IP Addresses all Remote Domain and SIP Outbound Proxiess IP addresses
used on SIP External Gateway
13.1.26 A Diversion header is added in case of single step transfer after a consultation call
Symptom:
OXE linked to SBC Acme via SIP TG ISDN
OXE linked to SIP Server via SIP TG ABC-F
1) Incoming call through SIP Trunking (ISDN) to a RSI point, strategy route the call to an Agent1.
2) Agent1 makes a consultation call (two step transfer) to the initial RSI point and is in communication with
Agent2.
3) Agent1 or Agent2 releases the call and Agent1 is reconnected to external caller.
4) Agent1 makes a singlesteptransfer to a RSI point which distributes the call to a RoutingPoint monitored by
an external SIP Server.
5) An INVITE is generated by SIPMOTOR to SIPServer and contains an unnecessary history-info header
which contains the RSI used when consultation call.
Diagnosis: According to RFC 5806 Diversion Indication in SIP, this extension provides the ability for the
called SIP user agent to identify from whom the call was diverted and why the call was diverted.
When a diversion occurs, a Diversion header SHOULD be added to the forwarded request or forwarded 3xx
response. The Diversion header MUST contain the Request-URI of the request prior to the diversion.
The Diversion header SHOULD contain a reason that the diversion occurred.
Ed. 12 137 TG0069

OmniPCX Enterprise
When CSTA function Diverted is called by Call Handling, RSI is routing the call to External Routing Point.
Its a kind of diversion (as following figure). Hence, SETUP message will contain
RO_DIVERTING_LEG_INFORMATION2, which will add Diversion Header in Invite.
Singlestep Immediate Forward

Transfer
Set A -------------> Set B------------------->Set C-----------------------> Set D
SIP ISDN SIP ABCF
Solution: Call is diverted by the RSI to an External Routing Point so generated INVITE contains diversion
header. Adding Diversion Header in this scenario is a normal behavior
13.1.27 Incoming calls from SIP Provider are rejected by SIPMOTOR after upgrade from
R9.0 to R10.1
Symptom:
Scenario is the following:
An incoming call from a SIP Provider is handled by OXE Sipmotor and rejected with an error 488 Not
Acceptable Here
Tue Mar 12 09:49:49 2013 RECEIVE MESSAGE FROM NETWORK (194.179.10.3:5060 [UDP])
----------------------utf8-----------------------
INVITE sip:[email protected];user=phone SIP/2.0
Via: SIP/2.0/UDP 194.xxx.10.3:5060;branch=z9hG4bKq5f96100fgbgrtgo72s1.1
To: "xxx163324" <sip:[email protected];user=phone>
From: "Bella Ciao"
<sip:[email protected];user=phone>;tag=a1649ecd827305b375fa94a302192f35
Call-ID: ERICSSONBTK_ORIG_10212e20b3bba6afbb51f46cb4bf9515@192.168.195.252
Max-Forwards: 28
Content-Length: 392
Contact: <sip:[email protected]:5060;transport=udp>
Allow: INVITE, ACK, CANCEL, BYE, PRACK, OPTIONS
Supported: timer, 100rel
P-Asserted-Identity: "Bella Ciao" <sip:[email protected];user=phone>
User-Agent: OmniPCX Enterprise R10.1
Min-SE: 180
P-Charging-Vector: icid-value=2257dea5034f1a4d0aa6a336403f0a6;orig-ioi=bifonica.net
Route: <sip:[email protected]:5060;user=phone;lr>
Tue Mar 12 09:49:49 2013 114e[CMotorCall::ctrlRouteHeader] call server is in route. ===> the OXE IP
Address is present on Route Header (10.81.32.xxx)
Tue Mar 12 09:49:49 2013 isDomainFromGwExt SCSWorking: NO
Tue Mar 12 09:49:49 2013 [isDomainFromGwExt] Host from request is : bstk.bifonica.net.
Tue Mar 12 09:49:49 2013 [isDomainFromGwExt] User from request is : +34xxx163301
Tue Mar 12 09:49:49 2013 isDomainFromGwExt--> For Non-PCS case GwExt=5
Tue Mar 12 09:49:49 2013 [isValidGwExt] ext gw 5 is valid ===> SIPMOTOR has found the SIP Ext Gw and
Remote Domain matches with the From header [bstk.telefonica.net]
Tue Mar 12 09:49:49 2013 114e[CMotorCall::onReceiveRequest] release the call 488. ==> call is
rejected by SIPMOTOR
Tue Mar 12 09:49:49 2013 SEND MESSAGE TO NETWORK (194.xxx.10.3:5060 [UDP]) (BUFF LEN = 562)
----------------------utf8-----------------------
SIP/2.0 488 Not Acceptable Here
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, SUBSCRIBE, OPTIONS, UPDATE
To: "xxx163324" <sip:[email protected];user=phone>;tag=a87ceaccaf57393baca277c6893d0636
From: "Bella Ciao"
<sip:[email protected];user=phone>;tag=a1649ecd827305b375fa94a302192f35
Call-ID: ERICSSONBTK_ORIG_10212e20b3bba6afbb51f46cb4bf9515@192.168.195.252
Ed. 12 138 TG0069

OmniPCX Enterprise
Via: SIP/2.0/UDP 194.xxx.10.3:5060;branch=z9hG4bKq5f96100fgbgrtgo72s1.1

Content-Length: 0
Diagnosis: Since the release 10.1, a new Boolean has been added on System parameters
Two use cases are taken into account
Use case 1
INVITE sip:+33155669001@RemoteDomain SIP/2.0
To : <sip:+33155669001@BelongingDomain>
From : <sip:+33147858000@RemoteDomain>
Route : <sip:RegID@OXE_Address> ===> our use case
Although the domain part of the ReqURI doesnt indicate the OXE, the content of the Route header leads the
OXE to accept the call, thanks to the loose route mechanism defined in RFC 3261.
In another hand, the following INVITE is re-routed to the RemoteDomain destination:

Use case 2
INVITE sip:+33155669001@RemoteDomain SIP/2.0
To : <sip:+33155669001@BelongingDomain>
From : <sip:+33147858000@RemoteDomain>
Route : <sip : OXE_Address>
The following system parameter is introduced :

Loose Route with RegID : Yes / No - Default : Yes
If it is set to Yes, such INVITE is re-routed to the RemoteDomain destination.
If it is set to No, such INVITE is accepted.
Following configuration must be done on OXE to accept this incoming call:

On SIP > SIP External Gateway > Registration ID: xxx163324
On System > Others System Params > SIP Parameters > Loose Route with RegID: False
13.1.28 Remote extension issue in ringing phase

Symptom: An incoming call thru SIP Trunking to a OXE user with a associated Remote Extension number
reachable thru SIP-Trunking. When REX device ringing, OXE user device ringing is stopped
Diagnosis: For call using SIP trunking and other issues, please check that System>Other Parameters :
DTMF on Alert is set to NO.
The default value for "DTMF on Alert" in system parameter is false. For countries, Italy and New Zealand,
this boolean will be set to true defaultly.
Solution: Set the system parameter DTMF on Alert to False
13.1.29 Overflow on Remote Extension impossible when SIP Extension seen Out of Service
Symptom: SIP Extension with a Remote Extension tandem (external number thru SIP-Trunking or ISDN)
SIP Extension device is deregistered, out of service on csipsets
When a 4059IP Operatore tries to reach the SIP Extension, overflow to Remote Extension is not happening
Solution: Configure the Overflow as below:

System > Other System Param > System Parameter > Overflow on OoS Extension : TRUE
Categories > Phone Facilities Categories > Forward if MIPT/IP/SIP sets OOS : 1
13.1.30 Country Code is not added on Calling Number when call is performed since a GSM
Symptom:
On Italy the National Numbering Plan is the following:
- National number: 0xx
- GSM number: 3xx
Ed. 12 139 TG0069

OmniPCX Enterprise
- Emergency call: 1xx

- Green number: 8xx
Country Code managed on OXE is 39
Topology is the following:

- leg1 ISDN T2 OXE (Calling Number, NPD: TON National)
- leg2 OXE SIP ISDN Call Center (Calling Number, NPD: Unknown)
The behavior of the incoming call to user agent is the following:

1. Incoming call from National number:
The external user 0267766460 dials 0396053373, the call arrives on SIP client as +39267766460. Country
Code +39 is added
2. Incoming call from GSM number:
The GSM user 3358316655 dials 0396053373, the call arrives on SIP client as 3358316655. Country Code
is not added
Diagnosis:
As below SETUPs received from ISDN T2
______________________________________________________________________________
| tei: 0 >>>> message received : SETUP [05] Call ref : 47 43
| SENDING COMPLETE
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 81 -> T2 : B channel 1 exclusive
| IE:[6c] CALLING_NUMBER (l=12) -> 00 80 Num : 3358318655 ===> Unknown (doesn't match with country
code, nothing is added) FROM : <Isdn_IT> [email protected]:5060 ; user=phone
______________________________________________________________________________
| tei: 0 >>>> message received : SETUP [05] Call ref : 47 3e
| SENDING COMPLETE
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 81 -> T2 : B channel 1 exclusive
| IE:[6c] CALLING_NUMBER (l=11) -> 21 80 Num : 117775510 ====> TON National (+39 is added) FROM :
<Isdn_IT> [email protected]:5060 ; user=phone
Solution: There is no canonical form in transit when the calling number is Unknown (information received
from Provider for when call is performed from a GSM)
OXE creates a canonical form in transit only with a calling number national or international .
Callin Number Unknown = no modification
Calling Number National = add +xx (xx =country code)
Request provider to send the SETUP with TON National
13.1.31 Call Back issue on Open Touch

Symptom:
Call Back feature doesn't work on 40x8 and MyIC Devices
On 8082 device, feature works fine
Issue observed:
User 40x8 or MyIC Desktop makes a Call Back
Invite received by OXE Call Handling is formatted as below:
(076026:000022) | From : <HQ148ID4 user> [email protected]:5060 ; user=name
(076026:000023) | To : <> [email protected]:5060 ; user=name
Ed. 12 140 TG0069

OmniPCX Enterprise
First 0 is used by Call Handling for ARS prefix so INVITE generated to provider is formatted like as
298285305 and not routable
Whereas with 8082 device:

(075607:000012) +------------------------------------------------------------+
(075607:000015) | From : <HQ148ID3 user> [email protected]:5060 ; user=name
(075607:000016) | CLIR
(075607:000017) | To : <> [email protected]:5060 ; user=name
We have 00 with first 0 for the ARS Prefix, number sent to SIP Provider is 0298285305
External Call Back

Basic Number: DEF
Number Digits to be removed: 0
Digits to Add: 00
Diagnosis:
Initial INVITE received by OXE is the following:
Tue Mar 19 14:14:53 2013 [display_ipc_out] ------------ Begin ---------------
Tue Mar 19 14:14:53 2013 Id : -1
Tue Mar 19 14:14:53 2013 INVITE
Tue Mar 19 14:14:53 2013 REQUEST URI : <> [email protected]:5060 ; user=phone
Tue Mar 19 14:14:53 2013 FROM : <> [email protected]:5060 ; user=phone
Tue Mar 19 14:14:53 2013 TO : <"Tango Charlie"> [email protected]:5060 ; user=phone
Country Code +33 is received on FROM. Then NPD/External Call Back transforms the number to
00298285305
And relayed as below to Open Touch:

Tue Mar 19 14:14:53 2013 [display_ipc_in] ------------ Begin ---------------
Tue Mar 19 14:14:53 2013 neqt : 480 Id : -1
Tue Mar 19 14:14:53 2013 INVITE
Tue Mar 19 14:14:53 2013 REQUEST URI : <> [email protected]:5260 ; user=phone
Tue Mar 19 14:14:53 2013 FROM : <298285305> [email protected]:5060 ; user=phone
Tue Mar 19 14:14:53 2013 TO : <> [email protected]:5260 ; user=phone
For Call Back, FROM should be sent to OpenTouch as this: FROM : <0298285305> [email protected]:5060 ;
user=phone
Solution: Solution available in J2.603.22
13.1.32 only 62 simultaneous calls are sent out of the OXE, all other calls are
released
rd th
Symptom: only 62 simultaneous calls can go out of the OXE, 63 64 ... calls seems to be stuck in the OXE
despite the SIP trunk group shows numerous channels as FREE
Diagnosis: a pair of SIP virtual access is 62 channels. Each time a SIP virtual access is added to a SIP
Trunk group, the Call Server must be rebooted, because these newly created channels will show as FREE
but cant be used by the Call Handling until a reboot.
Solution: reboot the Call Server
Ed. 12 141 TG0069

OmniPCX Enterprise
BEFORE CALLING ALCATEL-LUCENTS SUPPORT CENTER
Before calling Alcatels Business Partner Support Centre (ABPSC), make sure that you have read
through:
The Release Notes which lists features available, restrictions etc.
This chapter and completed the actions suggested for your systems problem.
Additionally, do the following and document the results so that the Alcatel Technical Support can
better assist you:
Have any information that you gathered while troubleshooting the issue to this point available to
provide to the TAC engineer (such as traces).
[Have a network diagram ready in case of ABC-F Networking problem].
[Have a data network diagram ready in case of VoIP problems. Make sure that relevant information
is listed such as bandwidth of the links, equipments like firewalls, etc.].
[Have a VoIP Audit report available in case of VoIP problems].
Note
Dial-in access is also mandatory to help with effective problem resolution.
Comments
Adapt the paragraph if specific or additional information or actions are required depending on the
subject.
Ed. 12 142 TG0069

OmniPCX Enterprise
14. ANNEXE: REGISTER / INVITE WITH OR WITHOUT AUTHENTICATION
14.1 Register of set
14.1.1 Classical management of SIP on the OXE
Before the register, make the management of the SIP Gateway & the ABC-F SIP Trunk Group for the
installation of the SIP Processes.
Go under /SIP/SIP Getaway
Consult/modify your SIP Trunk GroupGroup :
The network used in the SIP TG MUST be different from the one used for the node, the VPN, the TG.
Ed. 12 143 TG0069

OmniPCX Enterprise
14.1.2 Register of set without authentication

There are two types of SIP sets: the SIP Extension set and the SIP Device set. Under SIP/ SIP Proxy, the
minimal authentication method must be SIP None
14.1.3 Register of set with authentication

The authentication is managed in the proxy, Minimal authentication method + Digest
Remark:When Digest is enabled, authentication is requested for registration and incoming/outgoing calls
For each SIP Device or SIP Extension, the authentication username and password must be the same in the
OXE management side and SIP set management side
You can check this on OXE via SIP/Authentication:
See below the REGISTER frames:
11041 . . . . . OXE
SIP set) (Registrar)
IP=172.27.138.39 FQDN=N11.alcatel.com
| |
|(1) REGISTER |
|-------------------->|
|(2) 401 Unauthorized |
|<--------------------|
|(3) REGISTER |
|-------------------->|
|(4) 200 OK |
|<--------------------|
Challenge explanations :
o The Authentification scheme field corresponds to the OXE information about authentication.
The information Digest corresponds to the challenge type
o The information qop corresponds to the "quality of protection" values supported by the server.
The value "auth" indicates authentication.
Ed. 12 144 TG0069

OmniPCX Enterprise
o The information nonce corresponds to control the integrity of the authentication information
received by the SIP equipment
o The information realm corresponds to the SIP authentication domain, only one can be
managed on the OXE => managed in proxy
The realm is managed in the SIP proxy section, parameter is Authentication realm
14.2 INVITE of set
14.2.1 INVITE of set without authentication

UAC UAS
11041 OXE 11001
| | |
| INVITE | |
|-------------------->| |
| 100 Trying | |
|<--------------------| |
| |<------------------------------->|
| 180 Ringing | |
|<--------------------| |
| 200 OK | |
|<--------------------| |
| ACK | |
|-------------------->| |
| Media Session |
|<=====================================================>|
| BYE | |
|-------------------->| |
| 200 OK | |
|<--------------------| |
Remark : For a simple call, the ABC-F SIP TG is not used
14.2.2 INVITE of set with authentication

The authentication is managed in the proxy, Minimal authentication method + Digest
UAC UAS
11041 OXE 11001
| | |
| INVITE | |
|-------------------->| |
| 100 Trying | |
|<--------------------| |
|407 Proxy Auth Required| |
|<--------------------| |
| ACK | |
|-------------------->| |
| | |
|INVITE with challenge| |
|-------------------->| |
| 100 Trying | |
|<--------------------| |
Ed. 12 145 TG0069

OmniPCX Enterprise
| |<------------------------------->|
| 180 Ringing | |
|<--------------------| |
| 200 OK | |
|<--------------------| |
| ACK | |
|-------------------->| |
| Media Session |
|<=====================================================>|
| BYE | |
|-------------------->| |
| 200 OK | |
|<--------------------| |
14.3 Register of an external gateway
14.3.1 Register of an external gateway without authentication
Remarks :
The management of the SIP routing on OXE node with ARS & Numbering command table is a
prerequisite and is not included in this documentation
The network used in the ISDN SIP TG MUST be different than the network used for the installation,
the VPN, the ABC SIP TG, the TG.
If a FQDN is used for OXE, you have to do a new netadmin to update correctly the SIP Gateway.
As below configuration of the SIP External Gateway:
Ed. 12 146 TG0069

OmniPCX Enterprise
One registration Id is mandatory and the registration timer must be different than 0.
Configuration of SIP Proxy stays with default values:
Same scenario with the use of FQDN. As below when FQDN is used for outgoing:
Ed. 12 147 TG0069

OmniPCX Enterprise
When FQDN is used for incoming, belonging domain parameter must be configured, ex: n12.alcatel.com
Ed. 12 148 TG0069

OmniPCX Enterprise
14.3.2 Register of an external gateway with authentication
In order to REGISTER the external gateway, we need an authentication password managed on OXE.
For that, a creation of a SIP device/SIP Extension user with authentication password is requested. This
step will add the URL and associated password on SIP Dictionnary/SIP Authentication tables used when
a register with challenge is received by sipmotor
All the management is the following :
Configure the SIP gateway as previously and Configure the SIP proxy :
For the REGISTER, the

proxy MUST be configured
with DIGEST
IT IS NECESSARY TO CREATE A USER WITH SIP DEVICE TYPE IN ORDER TO HAVE

PASSWORD FOR THE REGISTRATION
Ed. 12 149 TG0069

OmniPCX Enterprise
Authentication
password
We can retrieve the authentication password of this user under : / SIP / Authentication :
** In N11 : Configure the SIP external gateway :
This parameter is used for the

authentication in the INVITE ,
not for the REGISTER. So this
parameter stays by default.
Ed. 12 150 TG0069

OmniPCX Enterprise
When the REGISTER is done, we can see in OXE in user / IP SIP Extension
IP @ of remote
domain
In order to REGISTER the external gateway with the use of a realm, this is exacly the same princip.
We need an authentication password in OXE. For that, a creation of a SIP device user with
authentication password is requested.
Configure the SIP gateway as previously and Configure the SIP proxy :
For the REGISTER, the proxy

MUST be configured with
DIGEST and with authentication
realm
Ed. 12 151 TG0069

OmniPCX Enterprise
14.4 INVITE of an external gateway with authentication

Simple call between 12004 (IP Phone) in N12 to 11006 (IP Phone) in N11
UAC UAS
12004 N12 N11
11006
(caller). . . . . . .. . . . . . . . . (proxy). . . . . . . . . . .
.(callee)
IP=172.27.144.26 IP=172.27.144.20
Following is the management of authentication on incoming/outgoing calls between two OXE nodes
with the use of FQDN
Note that Proxy menu is by default (Minimal authentication method = None)
The external gateway on both nodes:
Ed. 12 152 TG0069

OmniPCX Enterprise
Same scenario with the use of realm:
Ed. 12 153 TG0069

OmniPCX Enterprise
** The external gateway in N11 & N12:
Ed. 12 154 TG0069

OmniPCX Enterprise
End of document
Ed. 12 155 TG0069

TG0069 Sip PDF

Uploaded by

Copyright:

Available Formats

TG0069 Sip PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TG0069 Sip PDF

Uploaded by

Copyright:

Available Formats

TROUBLESHOOTING GUIDE TG0069 Ed.

OmniPCX Enterprise Nb of pages :152 Date : 23rd April 2014

SUBJECT : Session Initiation Protocol (SIP)

2. DOCUMENT HISTORY ................................................................. 7

4. ABBREVIATIONS AND NOTATIONS............................................. 7

6. SIP LICENSING ......................................................................... 12

7. INTERWORKING WITH OXE ...................................................... 13

8. SIP OXE IMPLEMENTATION ...................................................... 13

9. IP DOMAINS, CODECS AND PCS ............................................... 37

10. CONTENTS OF A SIP MESSAGES (GENERAL VIEW) .................. 41

11. EXAMPLES OF COMMON SIP FLOWS ....................................... 44

12. TROUBLESHOOTING ................................................................ 51

13. SYMPTOMS, DIAGNOSIS AND SOLUTIONS ............................. 129

BEFORE CALLING ALCATEL-LUCENTS SUPPORT CENTER ............... 142

NOTE ........................................................................................... 142

14. ANNEXE: REGISTER / INVITE WITH OR WITHOUT

4. ABBREVIATIONS AND NOTATIONS

OXE : OmniPCX Enterprise

SIP : Session Initiation Protocol

URI : Uniform Resource Identifier

5.1 SIP Overview

Transport Layer TCP UDP

5.2 SIP Terminology

User Agent (UA)

o User Agent Client (UAC): Initiator of the SIP requests

5.3 SIP structure

Application Session, dialog

Transaction Treatment, retransmission of messages

Transport Emission, reception of the messages

Syntax/Encoding Analyse of the messages (Parsing)

UDP TCP Transport protocol

5.4 SIP Messages

1xx: informational (transaction in progress).

5.5 SIP Transaction, Dialog & Session

The transactions have to separated:

The Non-INVITE transaction

5.6 SIP Addressing

Examples for SIP URIs:

For OXE uses on the username part numbers and no names.

177 M SIP users = 13/ 25

7. INTERWORKING WITH OXE

8. SIP OXE IMPLEMENTATION

8.1 RFCs implemented on OXE

8.1.2 RTP, T38 & DTMF (used for SIP)

RFC 2617: HTTP Authentication : Basic and Digest Access Authentication

8.2 SIPMOTOR processes

All processes can be forced to reset with the command:

They will be automatically relaunched after a few seconds.

The following commands can be used as well:

8.3 OXE duplication

8.4 The OXE contains the following compoments:

INIVTE with leg1 INVITE with leg1

INVITE with leg1 INVITE with leg2

Two different INVITEs on each proxy sides.

8.4.5 SIP users

On the OXE , there are two types of SIP users:

SIP Extension(or SEPLOS)

It is very important to remember this behaviour.

8.4.6 SIP External Voice Mail