Hi Paul, You are correct, the SUBSCRIBE does trigger a LIR.
The lookup for the originating subscriber doesn't trigger an LIR - the S-CSCF is known from the Service-Route on a previous register. The lookup for the terminating subscribee does trigger an LIR though - the S-CSCF for this subscriber is not yet known. Hope this helps, Ellie From: Paul Sun [mailto:[email protected]] Sent: 02 December 2014 01:43 To: Eleanor Merry; [email protected] Subject: RE: [Clearwater] 489 Event Package Not supported Hi Ellie I double checked through the packet trace captured on homestead, and I found that SPROUT sends http://<hss-mirror>:8888/impu/sip%3A123456789%40domain1.com/location<http://%3chss-mirror%3e:8888/impu/sip%3A123456789%40domain1.com/location> to request the name of the server currently serving the specified user. It maps to a Location-Info-Request to the HSS. So, I would like to make a clear understanding why sprout still sends the HTTP request to homestead even those the event package is not supported. Thanks - paul From: Paul Sun Sent: Monday, December 01, 2014 4:34 PM To: 'Eleanor Merry'; [email protected]<mailto:[email protected]> Subject: RE: [Clearwater] 489 Event Package Not supported Hi Ellie That's strange, I actually observe there is a LIR generated from homestead when a SUBSCRIBE message arrived in S-CSCF. Any idea? - PS -----Original Message----- From: Eleanor Merry [mailto:[email protected]] Sent: Saturday, November 29, 2014 3:50 AM To: Paul Sun; [email protected]<mailto:[email protected]> Subject: RE: [Clearwater] 489 Event Package Not supported Hi Paul, A SIP SUBSCRIBE will not trigger a LIR. A client has to be registered to send a SUSCRIBE (otherwise the P-CSCF will reject the SUBSCRIBE as untrusted). When the client successfully registers, the 200 OK they receive from the P-CSCF will include a Service-Route header, which is set to the subscriber's S-CSCF. When the client then makes a new request, they are meant to include this value as a route header (and if they don't, the P-CSCF will add it). As the subscriber's S-CSCF is known, there is no need to do an LIR. Ellie -----Original Message----- From: Paul Sun [mailto:[email protected]] Sent: 28 November 2014 03:45 To: Eleanor Merry; [email protected]<mailto:[email protected]> Subject: RE: [Clearwater] 489 Event Package Not supported Hi Ellie Will a SIP SUBSCRIBE message trigger a LIR between homestead and HSS? - PS -----Original Message----- From: Eleanor Merry [mailto:[email protected]] Sent: Friday, November 28, 2014 3:07 AM To: Paul Sun; [email protected]<mailto:[email protected]> Subject: RE: [Clearwater] 489 Event Package Not supported Hi, Clearwater only supports processing and creating a subscription for a SUBSCRIBE that has the Event type 'reg'. If Clearwater receives a SUBSCRIBE with any other Event type (or a SUBSCRIBE that isn't targeted at the home domain/the local node, or a SUBSCRIBE that doesn't accept 'application/reginfo+xml') then it will simply proxy it on - I presume that in this case it's back to the XLite client which then rejects it with a 489. If it's Clearwater generating the 489 (rather than the subscribee), then can you please send me the Sprout debug logs for this? Thanks, Ellie -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Paul Sun Sent: 27 November 2014 10:34 To: [email protected]<mailto:[email protected]> Subject: [Clearwater] 489 Event Package Not supported Hi While testing with X-lite on Clearwater, I noticed that when client send SIP SUBSCRIBE, a 489 Event Package Not supported is returned, is it normal? - PS _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
