NSE: Difference between revisions

Latest revision as of 13:41, 28 March 2018

NSE (Named Signaling Events) is a proprietary protocol to switch from voice to passthrough for fax/modem communication without involving SIP. It uses a proprietary event, based on NTE (Named Telephone Events). NTE is not proprietary, but NSE is.

TelcoBridges and NSE

We currently support NSE events:

192 (switch to passthru)
193 (disable echo)
194 (switch back to voice)

This adds a new SIP SDP entry that looks like this for initial negotiation:

a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194

The system does not send a SIP re-invite, but instead will send this NSE event 192.

Call Flow

Configuration

Toolpack v2.7: NSE configuration

References

@@ Line 1: / Line 1: @@
-NSE (Named Signaling Events) is a proprietary protocol to switch from voice to Passthru, without involving SIP. It uses a proprietary event, based on NTE (see 3.5 Payload Format). So NTE is not proprietary, but NSE is.
+NSE (Named Signaling Events) is a proprietary protocol to switch from voice to passthrough for fax/modem communication without involving SIP. It uses a proprietary event, based on NTE (Named Telephone Events). NTE is not proprietary, but NSE is.
 == TelcoBridges and NSE ==
-Our implementation only support NSE events:
+We currently support NSE events:
 <pre>
 (switch to passthru)
@@ Line 8: / Line 8: @@
 (switch back to voice)
 </pre>
+This adds a new SIP SDP entry that looks like this for initial negotiation:
+<pre>
+a=rtpmap:100 X-NSE/8000
+a=fmtp:100 192-194
+</pre>
+The system does not send a SIP re-invite, but instead will send this NSE event 192.
+===Call Flow===
+[[Image:NSE_call_flow.png| ]]
+== Configuration ==
+*[[Toolpack v2.7: NSE configuration]]
 == References ==
 *[http://tools.ietf.org/html/rfc2833 RFC 2833]
 *[https://supportforums.cisco.com/docs/DOC-1381 list of NSE events]
 [[category:Glossary]]