Requires Sonus SBC2000/1000 Version 2.2 or later
Normally, the SBC automatically maps History-Info into Redirecting Number; however, the automated mapping function works for specific reasons encoded in the History-Info header. In some cases, like Lync's forwarding feature, a reason is not present.
SMM may be used to map the History-Info to the FROM (or Redirecting) as detailed in this document.
The process entails:
INVITE sip:3539@10.1.1.74 SIP/2.0
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, REFER, NOTIFY, REGISTER
Via: SIP/2.0/UDP 10.1.1.91
To: <sip:3539@10.1.1.74>
From: <sip:13790060529@10.1.1.74>;tag=254b0000
Call-ID: 4-1f0@10.1.1.91
CSeq: 552136960 INVITE
Contact: sip:test@10.1.1.91
HISTORY-INFO: <sip:+39975379@bcc-lyncFE-01.com;user=phone>;index=1;ms-retarget-reason=forwarding , <sip:+13790060529@bcc-lyncFE-01.com;user=phone>;index=1.2
Cisco-Guid: 4170650438-384321033-2730718288-2880066070
Content-Type: application/sdp
Content-Length: 250
Create a SIP Message Rule Table.
Add a SIP Message Rule to capture the first ordinarl of the History-infoheader using the Add Header selection.
Add a calling number transformation to move the number from SV User Value 1 to Calling Number
INVITE sip:+13539@lyncserver.sbc.net:5068 SIP/2.0
Allow: INVITE, ACK, CANCEL, BYE, UPDATE, NOTIFY, OPTIONS, REFER, REGISTER
Call-ID: call-63002900-0000-0010-0C13-12@10.1.1.74
Contact: <sip:+39975379@10.1.1.74:5066;transport=TCP>
Content-Length: 231
Content-Type: application/sdp
CSeq: 2 INVITE
From: <sip:+39975379@sbc2000.sbc.net>;tag=a01014a-2977
Max-Forwards: 70
Supported: replaces,update,100rel
To: <sip:+13539@lyncserver.sbc.net:5068>
User-Agent: SONUS SBC1000/2000 3.0.0v222 UX
Via: SIP/2.0/TCP 10.1.1.74:5066;branch=z9hG4bK-UX-0a01-014a-3821