Hi Aravind, Thank you for your question.
To understand why the I-CSCF processing does not happen on an All-in-one Clearwater deployment it would help to think about what the role of the I-CSCF is. The I-CSCF is responsible for finding which S-SCSF is serving the requested subscriber. A real World IMS deployment may contain multiple S-SCSCFs, only one S-CSCF gets assigned to each registered subscriber and it is the I-CSCF's responsibility to find out which S-CSCF that is and to route messages on to it. On a Clearwater All-in-one node we know that there is only one single S-CSCF, and that all subscribers must be served by this S-CSCF. This means there is no use in having any I-CSCF processing, all messages can simply be routed to the one single S-CSCF. This is why you are not seeing any I-CSCF processing in the sprout log you have provided. This does not however explain why you are receiving a 404 error. A 404 error typically means the subscriber which you are attempting to register has not been provisioned in the HSS. Can you log onto Ellis by going to http://<aio-identity> and verify the subscriber you are attempting to register does exist. If everything does look okay and registers are still failing can you please provide the full sprout log for the time that the register was attempted. Thanks, Andrew From: Clearwater [mailto:[email protected]] On Behalf Of Shirabur, Aravind Ashok (CMS) Sent: Tuesday, April 25, 2017 8:36 AM To: [email protected] Subject: [Project Clearwater] All-in-one Images setup supports I-CSCF functionality ? Hi, All-in-one Images setup supports I-CSCF functionality ? Trying to REGISTER the X-Lite UE to clearwater (clearwater-infrastructure 1.0-160518.173307) IMS network, registration fails with error response -404. After analyzing the sprout logs I-CSCF is not involved in the REGISTER path, instead the REGISTER message delivered directly to S-CSCF. How to configure the I-CSCF ? attaching the 'shared_config' file "All-in-one Images" setup is trying to integrate with HPE-HSS 24-04-2017 11:41:57.508 UTC Debug basicproxy.cpp:92: Process REGISTER request 24-04-2017 11:41:57.508 UTC Verbose sproutletproxy.cpp:503: Sproutlet Proxy transaction (0x26ca080) created 24-04-2017 11:41:57.508 UTC Debug basicproxy.cpp:1271: Report SAS start marker - trail (c) 24-04-2017 11:41:57.508 UTC Debug pjutils.cpp:674: Cloned Request msg REGISTER/cseq=1 (rdata0x7f662408b3f8) to tdta0x26ca490 24-04-2017 11:41:57.508 UTC Debug pjsip: tsx0x26cc918 Transaction created for Request msg REGISTER/cseq=1 (rdata0x7f662408b3f8) 24-04-2017 11:41:57.508 UTC Debug pjsip: tsx0x26cc918 Incoming Request msg REGISTER/cseq=1 (rdata0x7f662408b3f8) in state Null 24-04-2017 11:41:57.508 UTC Debug pjsip: tsx0x26cc918 State changed from Null to Trying, event=RX_MSG 24-04-2017 11:41:57.508 UTC Debug basicproxy.cpp:213: tsx0x26cc918 - tu_on_tsx_state UAS, TSX_STATE RX_MSG state=Trying 24-04-2017 11:41:57.508 UTC Debug pjsip: endpoint Response msg 408/REGISTER/cseq=1 (tdta0x26cd080) created 24-04-2017 11:41:57.508 UTC Debug sproutletproxy.cpp:124: Find target Sproutlet for request 24-04-2017 11:41:57.508 UTC Debug sproutletproxy.cpp:163: Found next routable URI: sip:scscf.cwaio:5052;transport=TCP;lr;orig 24-04-2017 11:41:57.508 UTC Debug sproutletproxy.cpp:334: Possible service name - scscf 24-04-2017 11:41:57.508 UTC Debug sproutletproxy.cpp:340: Hostname - cwaio 24-04-2017 11:41:57.508 UTC Debug scscfsproutlet.cpp:381: S-CSCF Transaction (0x26ce1c0) created 24-04-2017 11:41:57.508 UTC Verbose sproutletproxy.cpp:1159: Created Sproutlet scscf-0x26ce1c0 for Request msg REGISTER/cseq=1 (tdta0x26ca490) 24-04-2017 11:41:57.508 UTC Verbose sproutletproxy.cpp:2067: Routing Request msg REGISTER/cseq=1 (tdta0x26ca490) (866 bytes) to downstream sproutlet scscf: --start msg-- REGISTER sip:cmshpe.com SIP/2.0^M Via: SIP/2.0/TCP 192.168.1.176:55337;rport=55337;received=192.168.1.176;branch=z9hG4bKPjOv5TCMYJtX7PPAJ9XwpHOz1vjbLgNO8N^M Path: <sip:[email protected]:5058;transport=TCP;lr;ob>^M Via: SIP/2.0/TCP 192.168.1.14:9000;rport=65430;received=192.168.1.14;branch=z9hG4bK-524287-1---d346e05081a6b464^M Max-Forwards: 70^M Contact: <sip:[email protected]:9000;transport=tcp;rinstance=bbeada83830e3779>^M To: "Aravind" <sip:[email protected]>^M From: "Aravind" <sip:[email protected]>;tag=64cd157d^M Call-ID: 84253MzY0OGViMzc4YWMxYmU4NGM1YThjYTk4N2RjOWZiNWI^M CSeq: 1 REGISTER^M Expires: 3600^M Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, OPTIONS, MESSAGE^M User-Agent: X-Lite release 4.9.8 stamp 84253^M P-Visited-Network-ID: cmshpe.com^M Route: <sip:scscf.cwaio:5052;transport=TCP;lr;orig>^M Content-Length: 0^M Thanks Aravind
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
