Page History

...

The SBC does not natively transport the received Reason header, so, using the configuration below, the SBC can pass-through the Reason header to other call legs.

...

1. Create two new SIP Message Rule Tables. The first will be used to capture the SIP Reason header from SIP CANCEL messages delivered by LYNC. The second will be used to add the Reason header to CANCEL messages being sent by the SBC.

   Panel
   borderStyle none
   Caption 0 Figure 1 Create SIP Message Rule Table Image Modified

   Panel
   borderStyle none
   Caption 0 Figure 1 Collect Reason Image Modified

   Panel
   borderStyle none
   Caption 0 Figure 1 Send Reason Image Modified

2. Add a SIP Message Rule to capture the Reason header using the Add Header selection.

   Panel
   borderStyle none
   Caption 0 Figure 1 Add SIP Message Rule Image Modified

   Tip
   The Header Name Reason isn't included in the token drop-down list. It must be typed in by hand!

   Panel

   CANCEL sip:+15103644064@ux.vx.net;user=phone SIP/2.0
   FROM: <sip:+14083489775@vx.net;user=phone>;tag=6186a5308f;epid=03FE79405B
   TO: <sip:+15103644064@ux.vx.net;user=phone>
   CSEQ: 34 CANCEL
   CALL-ID: e2cb98ce-038e-442b-be0c-f82c1265e0d3
   MAX-FORWARDS: 70
   VIA: SIP/2.0/TLS 10.1.1.73:49399;branch=z9hG4bKbbacc69a
   CONTACT: <sip:SBA1.vx.net:5067;transport=Tls>
   CONTENT-LENGTH: 0
   USER-AGENT: RTCC/4.0.0.0 MediationServer
   Reason: SIP;cause=200;text="Call completed elsewhere";ms-acceptedby="sip:jdoe@vx.net"(reason header from LYNC)

   Panel

3. In a separate SIP Message Table, add a SIP Message Rule to add the Reason header to the outgoing SIP CANCEL message. Again, use the Add Header selection.

   Panel
   borderStyle none
   Caption 0 Figure 1 Add Reason Header Image Modified

   Panel

   CANCEL sip:15103644064@vxgw2.vx.net:5060;user=phone SIP/2.0
   reason: SIP;cause=200;text="Call completed elsewhere";ms-acceptedby="sip:jdoe@vx.net" (SBC-added reason header)
   Allow: INVITE, ACK, CANCEL, BYE, UPDATE, NOTIFY, OPTIONS, REFER, REGISTER
   Call-ID: call-F96B1300-0000-0010-0C13-8@10.1.1.74
   Content-Length: 0
   CSeq: 1 CANCEL
   From: <sip:+14083489775@10.1.1.74:5060;user=phone>;tag=a01014a-d
   Max-Forwards: 70
   To: <sip:15103644064@vxgw2.vx.net:5060;user=phone>
   User-Agent: NET UX 2.2.1v999 UX
   Via: SIP/2.0/TCP 10.1.1.74:5060;branch=z9hG4bK-UX-0a01-014a-0038

   Panel

4. On the LYNC or SBA Signaling Group, add the capture SIP Message Rule to the Inbound Message Manipulation.

   Panel
   borderStyle none
   Caption 0 Figure 1 Add Capture SIP Message Rule Image Modified

5. On any Signaling Group which would send a forked call, add the sending SIP Message Rule to the Outbound Message Manipulation.

   Panel
   borderStyle none
   Caption 0 Figure 1 Add Sending SIP Message Rule Image Modified

Debugging Output

...