Jake,
There's quite a lot of configurability involved here, as to which registration
types it should trigger on (initial registration, reregistration or
deregistration) and whether the S-CSCF should include the request/response in
the body.
Here's an example which provides extensive behaviour, for an AS which is
contacted on TCP, using SRV records, with a domain name of "sample-as.test",
sending on all registration types, and including as much information as
possible.
<InitialFilterCriteria>
<Priority>0</Priority>
<TriggerPoint>
<ConditionTypeCNF>0</ConditionTypeCNF>
<SPT>
<ConditionNegated>0</ConditionNegated>
<Group>0</Group>
<Method>REGISTER</Method>
<Extension>
<RegistrationType>0</RegistrationType>
<RegistrationType>1</RegistrationType>
<RegistrationType>2</RegistrationType>
</Extension>
</SPT>
</TriggerPoint>
<ApplicationServer>
<ServerName>
sip:sample-as.test;transport=TCP
</ServerName>
<DefaultHandling>0</DefaultHandling>
<Extension>
<IncludeRegisterRequest/>
<IncludeRegisterResponse/>
</Extension>
</ApplicationServer>
</InitialFilterCriteria>
Richard
From: Clearwater [mailto:[email protected]] On
Behalf Of Jake Brown
Sent: 02 March 2017 04:08
To: [email protected]
Subject: [Project Clearwater] Sprout and third-party registrations
I am looking for a IFC example that would induce the behavior described in the
manual where the S-CSCF would pass a third party registration onto an AS:
>From the online manual:
AS invocation also occurs on REGISTER - this is called third-party registration
(3GPP TS 24.229 s5.4.1.7 and 7A):
* When a UE registers with Sprout, if the iFCs require it, it passes a
third-party registration onto an AS.
* Message body handling for third-party registration, per 3GPP TS 24.229
s5.4.1.7A: including optionally service info, a copy of the registration, and a
copy of the response.
* Network-initiated deregister. If the third-party registration fails and
the iFC requests it, we must deregister the UE.
Thank You
Jake
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
