Page History
| Panel | ||||
|---|---|---|---|---|
In this section:
|
| Info | ||
|---|---|---|
| ||
Related articles: |
The following sections describe the LMSD inter-working without tones:
- Implementing LMSD When SBC Cannot Play Tones
- When SBC is Handling P-Com-DropEarlyMedia
- Calls Originating from MSC
- Ignoring ISUP MIME
| Anchor | ||||
|---|---|---|---|---|
|
When 180 ringing with SDP and valid Alert-Info header is received, but
...
the
| Spacevars | ||
|---|---|---|
|
...
the
| Spacevars | ||
|---|---|---|
|
...
| Spacevars | ||
|---|---|---|
|
- Accept Alert-Info is enabled on the leg which receives 180 ringing.
- 180 ringing is received with SDP answer.
- Alert-Info is received in LMSD format
...
<http:/LMSD/tone?sig-id=
...
x>,where x = (rt).Sends 180 ringing with Alert-Info header and without SDP when
...
the
cannot play the required LMSD specified tone or the tone and announcement profile is not configured on both legs of a call.Spacevars 0 product Info title
...
Note In LMSD inter-working state, if
...
the
receives 18x ringing without SDP, it relays 180 without SDP and remains in the same state. TheSpacevars 0 product
...
passes the Alert-Info transparently, regardless of the transparency setting of Alert-Info header.Spacevars 0 product
The
...
| Spacevars | ||
|---|---|---|
|
Egress leg IPSP flag Accept Alert-Info is enabled.
Initial INVITE received with SDP.
180 ringing is received from the MSC with SDP.
Alert-Info received in LMSD format
...
<http:/LMSD/tone?sig-id=
...
x>,where x = ct or bt.
...
Info title Note If the tone is not in ct, bt or rt format, SMM is used to convert that string to rt.
| Anchor | ||||
|---|---|---|---|---|
|
...
| Multiexcerpt | ||
|---|---|---|
| ||
The |
...
|
...
|
...
The
|
...
The
|
|
...
header in the initial INVITE in the format ̶ |
...
the
|
...
|
...
When |
...
interworking is carried out in |
...
the
|
...
the
|
...
final |
...
response. |
| Anchor | ||||
|---|---|---|---|---|
|
| Multiexcerpt | ||
|---|---|---|
| ||
For calls originating from the MSC server, a 180 ringing with SDP response triggers a flag in the MSC to play a |
...
ringback tone. This |
...
causes the need for the
|
...
<http:/ |
...
null> request to |
...
force the MSC to stop the |
...
ringback tone. |
...
To facilitate this, the
stopLmsdToneOnUpdate, to accomplish the following on the leg which received the update |
...
from the MSC:
|
...
|
...
|
...
|
...
|
...
|
...
|
| Info | ||
|---|---|---|
| ||
This flag is disabled by default. Refer to SIP Trunk Group - Stop LMSD Tone On Update - CLI for configuration details. |
| Anchor | ||||
|---|---|---|---|---|
|
...
| Multiexcerpt | ||||
|---|---|---|---|---|
| ||||
The
|
...
flag, |
...
then treat the call as a normal SIP call. |
...
If SIP-I is configured for incoming messages, |
...
the
|
...
to the outgoing messages. |
| Info | ||
|---|---|---|
| ||
This flag is disabled by default. Refer to SIP Trunk Group - Drop ISUP Mime Body - CLI for configuration details. |
| Pagebreak |
|---|
Overview
Content Tools