Hi, When Ellis creates a subscriber it gives them the default iFCs; these specify that the built-in MMTEL application server should be used for all originating and terminating calls.
All subscribers created through Ellis will have this iFC set – but you can later modify the subscriber to remove the iFC (or create a new subscriber entirely) through the Homestead-prov API (see https://github.com/Metaswitch/crest/blob/dev/docs/homestead_prov_api.md for details of the API). For the iFC log, can you please send the whole section of the Sprout log dealing with the iFC, and let me know what the subscriber is doing (e.g. registering, making a call, …)? Ellie From: [email protected] [mailto:[email protected]] On Behalf Of atva angel Sent: 07 July 2015 18:57 To: Clearwater Mail Subject: [Clearwater] Regarding to IFCs Configuration Hi community, I have a configuration file available for my Application server at /usr/share/clearwater/ellis/web-content/js/app-servers.json. At current, I don't assign the AS server for any userid on Ellis webgui. However, when my user does register via X-lite, the ifc is always included. In the debug log on Sprout: 07-07-2015 17:01:02.977 UTC Debug httpconnection.cpp:629: Received HTTP response: status=200, doc=<ClearwaterRegData> <RegistrationState>REGISTERED</RegistrationState> <IMSSubscription xsi="http://www.w3.org/2001/XMLSchema-instance"; noNamespaceSchemaLocation="CxDataType.xsd"> <PrivateID>Unspecified</PrivateID> <ServiceProfile> <InitialFilterCriteria> <TriggerPoint> <ConditionTypeCNF>0</ConditionTypeCNF> <SPT> <ConditionNegated>0</ConditionNegated> <Group>0</Group> <Method>INVITE</Method> <Extension/> </SPT> </TriggerPoint> <ApplicationServer> <ServerName>sip:mmtel.example.com</ServerName<sip:mmtel.example.com%3c/ServerName>> <DefaultHandling>0</DefaultHandling> </ApplicationServer> </InitialFilterCriteria> <InitialFilterCriteria> <Priority>0</Priority> <TriggerPoint> <ConditionTypeCNF/> <SPT> <ConditionNegated>0</ConditionNegated> <Group>0</Group> <Method>REGISTER</Method> <Extension/> </SPT> </TriggerPoint> <ApplicationServer> <ServerName>sip:example.com:5060;maddr=192.168.1.2</ServerName<sip:example.com:5060;maddr=192.168.1.2%3c/ServerName>> <DefaultHandling>session_continued</DefaultHandling> </ApplicationServer> </InitialFilterCriteria> <InitialFilterCriteria> <Priority>0</Priority> <TriggerPoint> <ConditionTypeCNF>0</ConditionTypeCNF> <SPT> <ConditionNegated>0</ConditionNegated> <Group>0</Group> <Method>INVITE</Method> <Extension/> </SPT> </TriggerPoint> <ApplicationServer> <ServerName>sip:example.com:5060;maddr=192.168.1.2</ServerName<sip:example.com:5060;maddr=192.168.1.2%3c/ServerName>> <DefaultHandling>0</DefaultHandling> </ApplicationServer> </InitialFilterCriteria> <PublicIdentity> <Identity>sip:[email protected]</Identity<sip:[email protected]%3c/Identity>> </PublicIdentity> </ServiceProfile> </IMSSubscription> </ClearwaterRegData> My questions: 1. Why is the ifc included when the user does register although I don't assign the AS for user on ellis? 2. Is there any way to exclude the rfc of mmtel or my AS during my user does register? 3. Why does it return false value as below? 07-07-2015 17:01:02.981 UTC Debug ifchandler.cpp:540: Add to group 0 val false 07-07-2015 17:01:02.981 UTC Debug ifchandler.cpp:558: Result group 0 val false 07-07-2015 17:01:02.981 UTC Debug ifchandler.cpp:571: iFC does not match Thanks, Tam Vo
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
