Hi Eleanor, Indeed, if the + is added to the SIP URI identity, then both P-Asserted-Identities are included in the message to the IPSMGW.
Is there a reason for imposing that match restriction? logically you can alias any SIP URI identity to a Tel URI identity. e.g. in the spec, it has a different value for each of the identities: P-Asserted-Identity: "John Doe" <sip:[email protected]> P-Asserted-Identity: tel:+12125551111 cheers Steve ------------------------------------------------------------------------------------------ Steve Yeoman, Software Engineer, http://www.opencloud.com Tel: +1 647 342 6183, Mobile: +1 416 662 4490 On 18 November 2015 at 08:46, Eleanor Merry <[email protected]> wrote: > Hi Steve, > > > > Actually, one of my colleagues has pointed out that the SIP URI and the > Tel URI don’t quite match. The Tel URI has a +, the SIP URI does not, so > they’re not exact aliases. Can you please fix this up and try the call > again? > > > > Ellie > > > > *From:* Clearwater [mailto:[email protected]] > *On Behalf Of *Eleanor Merry > *Sent:* 16 November 2015 19:05 > *To:* Steve Yeoman; [email protected] > *Subject:* Re: [Clearwater] IPSMGW support > > > > Hi Steve, > > > > Thanks for sending the logs across. I agree that the IFCs now look correct > – I’m currently investigating why the P-Asserted-Identity header isn’t > being added. > > > > Ellie > > > > *From:* Clearwater [mailto:[email protected] > <[email protected]>] *On Behalf Of *Steve > Yeoman > *Sent:* 15 November 2015 22:09 > *To:* [email protected] > *Subject:* Re: [Clearwater] IPSMGW support > > > > Hi, > > > > Thanks for that. To effect the aliasing of the Tel URI, I associated a > second IMPU to the IMPI in HSS. Now Sprout is retrieving the registration > details like this: > > > > 08-11-2015 17:09:26.352 UTC Debug httpconnection.cpp:610: Received HTTP > response: status=200, doc=<ClearwaterRegData> > > <RegistrationState>REGISTERED</RegistrationState> > > <IMSSubscription> > > <PrivateID>[email protected]</PrivateID> > > <ServiceProfile> > > <PublicIdentity> > > <Identity>sip:[email protected] > </Identity> > > <Extension> > > <IdentityType>0</IdentityType> > > </Extension> > > </PublicIdentity> > > <PublicIdentity> > > <Identity>tel:+6505550202</Identity > <+6505550202%3c/Identity>> > > <Extension> > > <IdentityType>0</IdentityType> > > <Extension> > > > <DisplayName>6505550202</DisplayName> > > </Extension> > > </Extension> > > </PublicIdentity> > > > > I repeated the test, log attached. I'm still not seeing the second > P-Asserted-Identity header in the MESSGE to the IPSMGW. Did I miss > something? > > > > > > > > > > ------------------------------------------------------------------------------------------ > > Steve Yeoman, Software Engineer, http://www.opencloud.com > > Tel: +1 647 342 6183, Mobile: +1 416 662 4490 > > > > > > On 6 November 2015 at 09:40, Eleanor Merry <[email protected]> > wrote: > > 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 > > > > >
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
