• IP address and port number for the OPS bearer resource
• A description of the requested session.
2. The SIP PH strips the SCTP and IP headers and compacts the
message to the internal SIP format. The SIP PH then selects a
switching module for the SIP terminal process and forwards the
message.
3. The SIP system process receives the INVITE. It detects no ISUP
MIME and checks to determine whether SFID 769 (SIP without
Encapsulated ISUP) is
on. If the SFID is active, as in this
example, the SIP system process sets a flag to indicate
subsequent ISUP messages should not be encapsulated,
processing continues and the INVITE is sent to the SIP terminal
process.
4. The SIP terminal process sees that ISUP encapsulation is not
allowed and will default the mandatory parameters of the IAM. It
also performs digit analysis to determine whether the call should
be routed to a line or a trunk. In this example, it is determined
that the call should be routed to an ISUP trunk. Additionally, the
SIP terminal process determines that the call from the OPS must
arrive at a bearer resource so it requests that the CMP select a
bearer resource for the call.
5. The CMP:
• determines that the call arrives at a SIP packet group,
• selects a switching module for the bearer terminal process.
The determined information as well as the IP address and port
number of the OPS bearer resource are then forwarded to the
selected IP bearer switching module.
SIP without Encapsulated ISUP - Detailed
Call Scenario
Call Flow
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
3-57
To Next Page
Loading...
Need help?
General
