Hi Steve,

Sprout does support this use case. To get Sprout to add a P-Asserted-Identity 
for the tel URI you will need to set up the tel URI as an alias of the SIP URI.

The spec (TS 24.229, rel 10, 5.4.3.2) says about adding a P-Asserted-Identity

                If there was no original dialog identifier present in the 
topmost Route header field of the incoming request and if the served user is 
not considered a priviledged sender then:

a)            if the P-Asserted-Identity header field contains only a SIP URI 
and if the S-CSCF has knowledge that the SIP URI contained in the received 
P-Asserted-Identity header field is an alias SIP URI for a tel URI, add a 
second P-Asserted-Identity header field containing this tel-URI, including the 
display name associated with the tel URI, if available;

Sprout finds out what the aliases are for a public identity by getting the 
registration state from Homestead/HSS. The aliases for the requested public 
identity are all the public identities in the same Service Profile as the 
requested public identity.

In the Sprout logs, the HSS lookup shows a only single public identity in the 
Service Profile, e.g
                <ServiceProfile>
                                                <PublicIdentity>
                                                                
<Identity>sip:[email protected]</Identity>
                                                                <Extension>
                                                                                
<IdentityType>0</IdentityType>
                                                                </Extension>
                                                </PublicIdentity>
                                                <InitialFilterCriteria> ….

Can you add the tel URI then as an alias to the SIP URI (by adding a 
PublicIdentity block to the RegistrationState XML)?

Ellie


From: Clearwater [mailto:[email protected]] On 
Behalf Of Steve Yeoman
Sent: 03 November 2015 22:38
To: [email protected]
Subject: [Clearwater] IPSMGW support

Hi,

We're testing an IPSMGW solution, as per 3GPP 24.341, signalling flows in 
section B.5

In the attached log, sprout is not applying the Tel URI to the 
P-Asserted-Identity header in the SIP MESSAGE as per section B-5.3 (page 35).

Can you confirm if Sprout supports this use-case? and if so how can I configure 
it to apply both the SIP and Tel URI values for the P-Asserted-Identity in the 
sip MESSAGE sent to the IP-SM-GW.

thanks
Steve Yeoman



------------------------------------------------------------------------------------------
Steve Yeoman, Software Engineer, 
http://www.opencloud.com<http://www.opencloud.com/>

_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Reply via email to