Comfort Noise (RFC 3389) is the noise played in an RTP stream to prevent a user form hearing total silence on the connection. Not all telephony systems have the ability to play music while a party is on hold.  Without Comfort Noise (CN) the party on hold may think the connection dropped.

Starting with ECZ740 the Acme Packet SBC has the ability to inject Comfort Noise into an RTP stream by analyzing the SDP Offer and SDP Answer from both SIP endpoints. CN interworking is triggered on a per realm basis.

In the example below the calling party (Skype for Business) SDP Offer contains CN and is traversing a realm called core which has CN interworking enabled. The SBC forwards SDP to the called party. If the called party SDP Answer contains CN the SBC does not do anything because both endpoints support Comfort Noise. If CN is not present in the PSTN’s SDP Answer the SBC adds CN to the egress SDP Answer (towards Skype for Business) and will take responsibility for injecting CN into the RTP stream.

Example SBC configuration

Example call flow where SBC inserts comfort noise when Skype for Business sends CN during an active call

Comfort Noise state is exchanged with Active-Standby units high availability SBC pair. If there is a mid call failover and the standby becomes active, it will honor the CN message exchange between the called and calling party and generate Comfort Noise.

Additional document may be found in the ECZ740 Configuration Guide which is publicly accessible here.

 

  1. Bob Nielsen says:

    Mark,

    Do you have any documents on the data that is stored in the ACME on cdr records? on how to retrieve the cdr information?

  2. Mark says:

    There is an Accounting Guide with CDR VSA info, how to configure the SBC, etc.. The SBC sends CDR’s via Radius, FTP, or SFTP. Another cool thing is you can use HMR’s to populate custom VSA info.

    http://docs.oracle.com/en/industries/communications/session-border-controller/index.html