AudioCodes Mediant 800B MSBR User Manual page 536

Mediant 800B MSBR
due to, for example, the device's topology hiding (e.g., IP address) of its LAN elements.
The device resolves this by replacing the call identifiers received from the application
server with the correct call identifiers (e.g., user A and user B). Thus, users subscribed to
the service can receive relevant NOTIFY messages from the device and use the service.
Figure 34-2: Interworking NOTIFY XML Body for Application Server
To enable this feature, set the 'SBC Dialog-Info Interworking'
(EnableSBCDialogInfoInterworking) parameter to Enable. When this feature is disabled,
the device forwards the NOTIFY message as is, without modifying its XML body.
Below is an example of an XML body where the call-id, tags, and URIs have been
replaced by the device:
<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
version="10" state="partial"
entity="sip:alice@example.com">
<dialog id="zxcvbnm3" call-id="67402270@10.132.10.150"
local-tag="1c137249965"
remote-tag="CCDORRTDRKIKWFVBRWYM" direction="initiator">
<state event="replaced">terminated</state>
</dialog>
<dialog id="sfhjsjk12" call-id="67402270@10.132.10.150"
local-tag="1c137249965"
remote-tag="CCDORRTDRKIKWFVBRWYM" direction="receiver">
<state reason="replaced">confirmed</state>
<replaces
call-id="67402270@10.132.10.150"
local-tag="1c137249965"
remote-tag="CCDORRTDRKIKWFVBRWYM"/>
<referred-by>
sip:bob-is-not-here@vm.example.net
</referred-by>
<local>
<identity display="Jason Forster">
sip:jforsters@home.net
</identity>
<target uri="sip:alice@pc33.example.com">
<param pname="+sip.rendering" pval="yes"/>
</target>
</local>
<remote>
<identity display="Cathy Jones">
sip:cjones@example.net
</identity>
User's Manual 536 Document #: LTRT-12813