VoIP Enhancements

FR1041 - IP Network Interface Series 2 Card: Ethernet Link Status, Duplex Type and Speed

This feature allows the host to query the following on the IP Network Interface Series 2 card at any time:

the Ethernet Link status

speed and duplex type of the NET1, NET2 and NET3 ports located on the Multi-Function Media I/O card

When restarting the host application or initiating a new host application, the Ethernet port status needs to be known. Based on that status, appropriate actions could be taken like taking all the channels OOS in that card. whenever the Ethernet link goes down, an Alarm message is sent to the host. When the Ethernet link comes back up, an Alarm Clear message is sent.

This feature will add a functionality to query the individual Ethernet link status, speed and duplex type for the IPN Series 2 card using the Card Query message (0x0083). These shall be reported in the Card Query response. They will also be reported in the Card status report (0x00A6) whenever the card comes in service after a reset.

The Card Status Query message response is obtained from the switch when the host sends a Card Status Query message.

The Card Status Query message is obtained when the IPN Series 2 card comes into service after reset.

FR1023 - IP Network
Series 2 NLP Control Support

The IP Network Series 2 card NLP Control Support feature allows the enabling or disabling of the Non-Linear Processor (NLP) sub-component within the IP Network Series 2 card Echo Cancellation control. This feature is supported by adding new bitmap values to the RTP Echo Cancellation (0x0103) TLV. This TLV remains backward compatible to allow enabling and disabling of the existing echo cancellation function.

This feature is not supported by the VDAC-ONE card.

FR895 - Report and Control of P-Asserted and
P-Access Network Info Headers

The CSP SIP stack can report the "Remote-Party-ID" and the "RPID Privacy" headers if present in the SIP INVITE message.

Now with this feature, the SIP stack can read and write the "Privacy" header as follows:

Privacy (Defined in RFC 3323)

and the following private headers (P-Headers):

P-Asserted-Identity (Defined in RFC 3325)

P-Preferred-Identity (Defined in RFC 3325)

P-Access-Network-Info (Defined in RFC 3455)

By default, the SIP stack does not report these P-headers. You have to enable this functionality. The SIP stack does not modify any other SIP headers for privacy related to this feature.

FR893 - Send and Receive SIP Signals Using the Same Port

Prior to this feature, the CSP received inbound SIP signals on a specific User Datagram Protocol (UDP) port - by default it was port 5060. The receiving port could be changed at run time.

All outbound SIP signals were sent out on a UDP port allocated by the CSP when you configured SIP. This port number could be any valid (and unused) port number above 1023. The port used for outbound SIP signaling from the CSP remained constant until SIP was deconfigured.

FR330 - SIP Support for MIME

Prior to this feature, the CSP Session Initiation Protocol (SIP) did not support Multipurpose Internet Mail Extensions (MIME) in outgoing messages. This feature allows a user to send proprietary MIME or standard MIME such as ISUP in outgoing messages. MIME data in incoming messages will be reported to the host.

FR882 - SIP Notify Subscription State

This features adds support for Subscription-State headers in REFER-NOTIFY requests in Call Agent Mode (CAM) and non-CAM configurations.

The benefits of this feature include:

Host control on REFER-NOTIFY Subscription-State header.

Host control on the duration of REFER-NOTIFY subscription ("expires" parameter).

Host control on the retry-after time interval, which would be used to inform the remote UA when the REFER request could be retried in case the previous REFER failed.

Customizable reason code in the Subscription-State header of REFER-NOTIFY that terminates the subscription.

FR883 - SIP Notifications of Options

The SIP stack can now report the receipt of SIP OPTIONS to the host.

The SIP method, OPTIONS, allows a User Agent (UA) to query another UA or a proxy regarding its capabilities. This feature allows a client to discover information about the supported methods, extension content types with or without a dialog being established.

When the CSP receives an OPTIONS message, it is reported to the host as a PPL Event Indication including the Request URI in the message.

FR884 - SIP Referred By Mechanism

This feature supports the insecure refer technique using the Referred-By mechanism. This mechanism supports Call Agent Mode (CAM) and non-CAM configurations. The Referred-By header is disabled by default.

There are applications of the REFER where it is desirable to provide the refer target with the information about the referrer. The refer target can use this information when deciding whether to admit the referenced request. This feature provides the refer target with the SIP URI of the referrer.

FR688 - Report REFER Request URI in PPL Event Indication

The REFER message implements a call transfer service.

A user agent (referrer) uses the REFER message to request another user agent (referee) that it is in session-establish state with, to contact a third user agent (refer target).

The Refer target is identified by a SIP URI in the Refer-To header field in the REFER message.

You can enable this feature to get the Request-URI, in the Request-Line of the REFER message, reported to the host.

Example: With a SIP-to-ISDN call, if any ISDN related information like UUI, UUI encoding, or presentation indicator is present as a parameter in the Request-URI, this feature allows the host to get this data.

FR674 - Connect One-Way for Music on Hold

The Connect One-Way for Music on Hold feature allows customers to connect to SIP channels in order to support listen-only music for calls put on hold. This feature supports backwards compatibility.

FR0088 - SIP Signaling Support for T.38 Fax Media Sessions
(for Non-Call Agent Mode)

The Session Initiation Protocol (SIP) is a signaling protocol used for establishing sessions in an IP network. A session can be a simple two-way telephone call or a collaborative multi-media conference session. SIP uses Session Description Protocol (SDP) to convey and negotiate media session information.

Prior to this feature, the CSP signaling stack establishes only audio media sessions. This feature enhances the SIP and SDP stacks to allow the existing CSP media resources to originate and terminate T.38 fax media sessions. The CSP can now:

Signal T.38 fax parameters using the network

Control of local DSP resources to start a T.38 fax session

The CSP SIP signaling state machine can initiate a switchover from audio to T.38 fax or Pass-Through image sessions.

A session starts with audio capabilities, and upon fax tone detection, the T.38 fax capabilities are negotiated.

Upon successful negotiation, the session continues with the fax capabilities. The media termination hosts exchange T.38 Internet fax packets.

FR1047 - Disabling the SIP Domain Name System (DNS) Server

Prior to this feature, you enabled and disabled the Domain Name System (DNS) Server at the card level. The DNS task and a UDP socket, used to contact the DNS Server, is created when the Matrix Controller card boots up. Disabling the DNS Server disables the DNS functionality in the Matrix Controller card.

Important! By default, the DNS Server is not configured (disabled).

Once the DNS Server is configured in the CSP SIP stack, there was no provision to disable the DNS Server lookup.

This feature allows the host application to disable the DNS Server lookup at any time. Disabling the DNS Server stops the CSP from sending outbound SIP calls requesting a DNS Server lookup.

 

FR1166 - SIP Remote Party ID and RPID Privacy for Outbound Calls

Important! This feature contains information for the SIP Remote Party ID and RPID Privacy for both inbound and outbound calls.

 

The SIP Remote Party ID and SIP RPID Privacy header fields allow certain telephony services as well as some regulatory and public safety requirements.

These services include the following:

calling identity delivery

calling identity delivery blocking

tracing originator of call

Baseline SIP supports each of these services independently, but cannot support all combinations. For example, a caller that wants to maintain privacy and consequently provides unintelligible information in the SIP From header field will not be identifiable by intermediaries. However, since SIP does not allow the contents of the From header field to be modified by intermediaries, the intermediaries that do not directly perform cannot perform certain services.

FR1188 - SIP Tunneling

SIP tunneling is a mechanism that transports any kind of data using SIP signaling messages.

The CSP SIP stack now supports tunneling with the host playing an important role.

The SIP stack acts as a "black box" and the host determines what data to tunnel and what format to transport.

FR1250 - SIP Access To Parameters in To Header

This feature gives the host read and write access to the parameter field of the "To" header of the initial INVITE request. The SIP stack reports to the host the parameters (if present) in the "To" header of the INVITE within the Request for Service with Data or PPL Event Indication for subsequent data. This reporting is disabled by default.