SIP History-Info Field Usage

[malte]

i am trying to get our IP-Office as compliant as possible to "Deutsche Telekom CompanyFlex Complete" as described in 1TR119.

To forward calls with the "original caller"-CLIP, our customers had to book the option CLIP-NO-SCREENING due to the missing History-Info Field. Since there is currently a lot of controversy in Germany about the manipulation of CLIP, there will soon be potential legal problems here.

How can I submit the History Info header? Is there an option in the config, that may be missed? Or is that a sales argument for SBCE ?

13.4 Call Forwarding by Deflection (302)
A SIP-PBX may initiate network-based Call Forwarding by responding to a SIP INVITE with a 302 SIP response
which contains the new target in the Contact-header. The SIP-PBX shall add a SIP History-Info header field.
The SIP-PBX shall not insert the transport parameter in the Contact header of the 302 SIP response.
The NGN will forward the INVITE to the new target and send a 181 SIP response to the caller.
13.5 Call Forwarding by New INVITE
To forward with a new INVITE (on or out of dialog), the SIP-PBX must follow the procedures in SIPCONNECT
2.0 [22] Chapter 11.1 with the following clarifications:
• The request-URI identifying the forwarded-to target destination.
• A History-Info header field containing the Enterprise Public Identity of the forwarding user
• A P-Asserted-Identity header field or P-Preferred-Identity header field containing a valid identity of the
forwarding user.
• In order to enable the NGN to supervise the status of the call setup towards a SIP-PBX in case of call
forwarding, the SIP-PBX shall generate a 18x response message (181 (Call is Being Forwarded) or 183
(Session Progress) without SDP) and send it to the originating user as soon as the call forwarding has been
applied.
• In case a 181 response is sent to the originating user with information about the diverted-to identity, the
SIP-PBX shall include a SIP URI of the diverted-to user into a History-Info header field in a 181 (Call Is
Being Forwarded) response message and send it to the originating user. As it is not known what the
diverted-to user's TIR settings are, a Privacy header field with a priv-value set to "history" needs to be
included in escaped form in the hi-entry representing the diverted-to user.
• In case a 180 (Ringing) has been received from the diverted-to user, a 180 response (with or without SDP)
shall be sent to the originating user.
Please note that in case of Call Forwarding without proper History-Info header field, the identity in FROM-header
field will be screened by the network. In case the original caller identity shall be transported transparently, then
either History-Info header field or CLIP No Screening is necessary.

Certifications: ACIS and ACSS
Location: Leipzig, Germany

 

[derfloh]

I always just use PAI for that.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN