Lucent Technologies 5ESS - Page 87

- HOP COUNTER=ISUPMIME
- CARRIER SELECTION=ISUPMIME
Note: All SIP messages have the common SIP headers used to
identify and route SIP messages and associate them with
particular transactions within calls, e.g.: either Request URI or
response status line, To, From, Call-ID, CSeq, Via, Contact,
Length, Max-Forwards, etc. The following message flow
description does not explicitly list these. For more detailed
examples, refer to the Session Initiation Protocol (SIP) -
Interface Specification, 235-900-344, document.
This message flow starts with an ISUP Initial Address Message
(IAM) received at the OPS, which routes the call to a SIP packet
trunk and sends a SIP INVITE message to the TPS. The ISUP
Figure 3-6 5ESS
®
Switch OPS - 5ESS
®
Switch TPS Message
Flow
Lucent O Lucent O
5E-XC
TM
SIP
INVITE {SDP, ISUP IAM}
IAM
183 SESSION PROGRESS {SDP}
Audible Ringing Provided from Termination
200 OK (INVITE) {ISUP ANM}
ANM
ACK
REL
200 OK (BYE)
Call in Talking State
TPSOPS
UPDATE {SDP}
ACM
1
2
3
4
5
6
7
5E-XC
TM
Originating
PSTN
Switch
Terminating
PSTN
Switch
IAM
200 OK (UPDATE) {SDP}
8
180 RINGING {ISUP ACM}
ACM
ANM
Called Party
goes off-hook
Called Party
goes on-hook
SUS
INFO {ISUP SUS}
SUS
200 OK INFO
BYE {ISUP REL}
REL
RLC
RLC
COT
COT
Message Flows
Call Flow
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
3-17