Larry, It's good to hear from you. Thanks for your comments on installation and configuration and it's great that you've successfully got Clearwater integrated with your HSS and 3rd-party registration working to your RCS AS.
You're right that there's a bug in our OPTIONS handling - good spot! I've raised https://github.com/Metaswitch/sprout/issues/253 to cover this and hope to code a fix in the next couple of days. Thanks, Matt On Tue, Oct 15, 2013 at 18:42:47, Larry O'Shea wrote: > To: [email protected] > Subject: [Clearwater] RCS question > > Hi, > > I've installed the clearwater software on a single Amazon instance. > > I was really impressed by the packaging .. the install and config > couldn't have been easier. > Also installing on a single small instance .. I wasn't sure it would > work on such a low spec box but working fine for me. > > I got as far as Registering my RCS client with clearwater, and getting > the SIP Third party Register in to my RCS AS. > That meant that the interface from clearwater to my HSS is working > fine, the IFCs were downloaded from the HSS and worked fine. > > The problem I have now is: > - routing SIP OPTIONS - OPTIONs is being sent by client to clearwater > - and we expect it to be routed to our AS but it is just being Acked. > In RCS the OPTIONS are used to determine capabilities for contacts, so > we need this to work so that the A client can see that the B client is > RCS capable. > > We can get traces for this if let us know what to get > > Thanks, > Larry > > <http://openmindnetworks.com> > > > Follow us on LinkedIn > <http://www.linkedin.com/company/76647?trk=co_fol-start> > > > openmindnetworks.com _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
