...
Panel |
---|
...
borderColor | green |
---|---|
bgColor | transparent |
borderWidth | 2 |
...
...
In this section:
|
...
Info |
---|
...
|
...
|
...
The SIP
...
Dual-Tone Multi-Frequency (DTMF) trigger detection and notification functionality enables the
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
The
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
honorSdpClockRate
is enabled (...
Note |
---|
DSP resources are used when interworking between different codecs. When using in-band to out-of-band or in-band to DTMF digit (RFC 2833) interworking (both directions), DSP resources are required. |
Note |
---|
Pass-through calls are supported when receiving digits through RFC 2833 or out-of-band (SIP INFO). |
The
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
The
Spacevars | ||
---|---|---|
|
To enable this feature, configure and enable the
Spacevars | ||
---|---|---|
|
To configure via CLI, use following syntax:
Code Block |
---|
% set profiles dtmfTrigger <egress | ingress> interdigitTimeout <timeout_value> longdigitDuration <longdigitDuration> pattern <trigger_pattern> state <enabled | disabled> |
Below is a CLI example of enabling DTMF interworking for PSP "profile1" with transcoding.
Code Block | ||
---|---|---|
|
...
set profiles media packetServiceProfile pprfile1 packetToPacketControl conditionsInAdditionToNoCommonCodec differentDtmfRelay |
...
enable
commit |
...
Refer to DTMF Trigger - CLI, Packet Service Profile - CLI or Dtmf Trigger Profile - Dtmf Trigger, Packet Service Profile - Flags, Packet To Packet Control - Condition In Addition To No Common Codec (EMA) for configuration details.
The
Spacevars | ||
---|---|---|
|
Code Block | ||
---|---|---|
| ||
% set profiles media packetServiceProfile profile1 flags digitDetectSendEnabled enable
% set profiles media packetServiceProfile profile1 flags interworkDtmfWithoutTranscoding enable |
Note |
---|
To use DTMF interworking without DSP resources, the Packet Service Profile flag |
...
Refer to Packet Service Profile - CLI or Packet Service Profile - Flags (EMA) for configuration details.
To preserve the privacy and security model for media flows as well, the SBC implements an RTP Relay. In RTP Relay, the call endpoints send media packets to an address/port on the SBC. As the media packets flow through the SBC, the source and destination addresses are changed such that the SBC is itself always one of the endpoints in each call leg. Thus, the carrier's internal addresses are not exposed to the peering partner, and inbound media flows are directed only to a limited set of well-defined SBC addresses for security filtering purposes.
Figure
...
SIP IP Pipe Example Using SBC 5000 Series below depicts the two SIP IP "pipes" used by the
Spacevars | ||
---|---|---|
|
Caption | ||||||
---|---|---|---|---|---|---|
| ||||||
The SIP Application Server manages the SIP MS/IAD/phone through the IP cloud, shown by the dotted line in Figure 1 . This interaction is logically removed from the SIP SBC software and hence is not annotated in the following examples.
Audio call data may be encoded according to any of the algorithms below for delivery through the IP Media Stream:
The IP Media Stream uses the Realtime Transport Protocol (RTP) to deliver call data for all audio compression algorithms.
Caption | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
The Key Press Markup Language (KPML) functionality enables the
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
There are two types of subscriptions that the KPML recognizes:
Spacevars | ||
---|---|---|
|
Note |
---|
Note: The stream reversal is not supported for H.323-SIP calls. |
Caption | ||||
---|---|---|---|---|
| ||||
Where: F1: KPML Subscribe Message from Application Server to SIPSG. F2: 200 OK message from SIPSG to Application Server. F3: Digit Detect message from SIPSG to NRMA. F5: Digit Detect notify message (pending) from NRMA to SIPSG. F6: Notify message from SIPSG to Application Server. F7: 200 OK message from Application Server to SIPSG. F8: Mid call Digit Detect Notify message from NRMA to SIPSG. F9: Notify message from SIPSG to Application Server. F10: Notify OK message from Application Server to SIPSG. |
Caption | ||||
---|---|---|---|---|
| ||||
Where: F1: KPML Subscribe Message from Application Server to SIPSG. F2: 200 OK message from SIPSG to Application Server. F3: Digit Detect message from SIPSG to NRMA. F5: Digit Detect notify message (pending) from NRMA to SIPSG. F6: Notify message from SIPSG to Application Server. F7: 200 OK message from Application Server to SIPSG. F8: Digit Detect Notify message (if match found) from NRMA to SIPSG. F9: Notify message from SIPSG to Application Server. F10: Digit Detect Notify message (if match found) from NRMA to SIPSG. F11: 200 OK Notify message from Application Server to SIPSG. F12: Notify message from SIPSG to Application Server. F13: Notify message from Application Server to SIPSG. |
Caption | ||||
---|---|---|---|---|
| ||||
Caption | ||||
---|---|---|---|---|
| ||||
Caption | ||||
---|---|---|---|---|
| ||||
When a KPML subscription is received with "stream=reverse" attribute, the
Spacevars | ||
---|---|---|
|
Note |
---|
The KPML supports GW-GW calls. However, KPML does not support GW-GW for Reverse Stream calls. |
Caption | ||||
---|---|---|---|---|
| ||||
The
Spacevars | ||
---|---|---|
|
Pagebreak |
---|