Once the header manipulation has been configured, the “FROM” header will get modified from the content that present in “Diversion” header.ġ3:37:42.094 : 172.22.10.10 : NOTICE : INVITE SIP/2.0 Go in to SBC Configuration and in “Msg policy & Manipulations”, create a Message Manipulation rule as below Now the user DID number is appearing in Diversion SIP header, a message manipulation rule can be configured and assigned to SIP trunks IP Group against “Outbound Message Manipulation Set” The Diversion header will contain the DID of the user that forwarding the call.ĭiversion: reason=unconditional counter=1 Once enabled, run a logging on SBC and see if the “Diversion” header appears. In the Skype for Business\Lync control panel, “Trunk Configuration”, enable “Enable forward call history” and save. Before doing that, there is a small configuration change need to be done on Skype for Business\Lync server voice routing.
With Audiocodes, a SIP header manipulation rule can be configured to cater this requirement. Some organizations accept this as it is but in my experience, most prefer to have the user DID be sent as the calling ID.
The downside of this method is that, when ever a call forward configured on Skype for Business\Lync client, the call will get forwarded to the configured destination with the number presentation of pre-configured number and not the original DID of the user. This issue an be overcome by employing IP-to-IP Outbound number manipulation to manipulate the calling number and replace it with any number that belongs to the SIP Trunk. Basically, the calling number presentation must have a number that belongs to the SIP trunk. In an ISDN, this will be fine as PSTN provider will mask the calling number with the pilot number of the ISDN.īut, in a PSTN SIP Trunk scenario, this will be problematic as SIP Trunk provider will refuse to send any numbers that are unknown to the trunk. As you all know, in a PSTN call forwarding scenario, Skype for Business\Lync server always forward the original caller ID to PSTN.
0 kommentar(er)
