Hi Ellie Great news is the connection between Clearwate-Homestead and OpenIMSCore-HSS is now ready, I can see CER/CEA/DWR/DWA.
Now, I am hitting another problem, the user can be registered in HSS, but when process the MAR, it failed. Below is the error in HSS, any idea? Type "exit" to stop FHoSS! 2014-05-23 13:14:41,635 [Thread-12] DEBUG de.fhg.fokus.hss.main.Task - Processing MAR! 2014-05-23 13:14:41,643 [Thread-12] ERROR de.fhg.fokus.hss.cx.op.MAR - User is registered but has no S-CSCF name stored - HSS database consistency error -PS -----Original Message----- From: Paul Sun Sent: Friday, May 23, 2014 10:32 AM To: 'Eleanor Merry'; [email protected] Subject: RE: CLearwater with OpenIMSCore HSS Hi Ellie Thank for the reply. I am a bit confused. Should I change the realm in Clearwater? Or should I change in OpenIMSCore FHoSS? Can u advice? Also, where should I change in the Clearwater if it is required? - PS -----Original Message----- From: Eleanor Merry [mailto:[email protected]] Sent: Thursday, May 22, 2014 7:55 PM To: Paul Sun; [email protected] Subject: RE: CLearwater with OpenIMSCore HSS Hi Paul, The realm in the HSS configuration file should match the home domain of your deployment. By default on an all-in-one install this is example.com - have you changed it to open-ims.test? If this does match, then can you get a network capture between the Clearwater deployment and the HSS during a register? Can you also share your /etc/clearwater/config, and look in the homestead logs (in /var/log/homestead) for errors? To answer your previous questions as well: 1. I am able to build the All-in-one-images in UBUNTU, and now I tried to configure the X-LITE to make test call, however, I am failed. I double check the configuration, and I am abit confused what should I fill in "Server:" in STUN configurations. Anyone can help? You should use the aio-identity - the value of this depends on how you installed the all-in-one image. If you installed an All-in-One node from an Amazon AMI, then the aio-identity is the public DNS name that EC2 has assigned to your node. This will look something like ec2-12-34-56-78.compute-1.amazonaws.com and can be found on the EC2 Dashboard on the "instances" panel. If you installed an All-in-One node from an OVF image in VMPlayer or VMWare, the aio-identity is the IP address that was assigned to the node via DHCP. You can find this out by logging into the node's console and typing hostname -I. If you installed an All-in-One node from an OVF in VirtualBox, the aio-identity is 'localhost'. 2. It seems that I should follow the manual build on All-in-one-Images section, however, I need to know what exactly need to do on step 2: "find the preseed/late_command entry in the all-in-one image's install script - as of writing this is as follows, but please check the linked file for the latest version". Can anyone help to explain what is required to do? This process takes the standard Ubuntu installation ISO and patches the install process (the "preseed" file) to automatically install Clearwater. Ellie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Paul Sun Sent: 22 May 2014 10:43 To: Paul Sun; DURECU, OLIVIER (OLIVIER); [email protected] Subject: Re: [Clearwater] CLearwater with OpenIMSCore HSS The DiameterPeerHSS.xml is like below. When the SIP client trying to register on Clearwater, I can see CER/CEA between Clearwater and OpenIMSCore_HSS, but below error is presented on the term of OpenIMSCore_hss. 2014-05-22 17:41:00,830 INFO de.fhg.fokus.hss.main.HSSContainer - waitForExit Type "exit" to stop FHoSS! java.lang.Exception: Read failed at de.fhg.fokus.diameter.DiameterPeer.transport.Communicator.run(Communicator.java:187) java.lang.Exception: Read failed at de.fhg.fokus.diameter.DiameterPeer.transport.Communicator.run(Communicator.java:187) Alos, the SIP REGISTER request is rejected by 403 Forbidden., any idea? <?xml version="1.0" encoding="UTF-8"?> <!-- HSS Server config --> <DiameterPeer FQDN="hss.open-ims.test" Realm="open-ims.test" Vendor_Id="10415" Product_Name="JavaDiameterPeer" AcceptUnknownPeers="1" DropUnknownOnDisconnect="1" Tc="30" Workers="4" QueueLength="32" > <Acceptor port="3868" bind="192.168.0.134" /> <Auth id="16777216" vendor="10415"/><!-- 3GPP Cx --> <Auth id="16777216" vendor="4491"/><!-- CableLabs Cx --> <Auth id="16777216" vendor="13019"/><!-- ETSI/TISPAN Cx --> <Auth id="16777216" vendor="0"/><!-- ETSI/TISPAN Cx --> <Auth id="16777217" vendor="10415"/><!-- 3GPP Sh --> <Auth id="16777221" vendor="10415"/> </DiameterPeer> -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Paul Sun Sent: Thursday, May 22, 2014 5:30 PM To: DURECU, OLIVIER (OLIVIER); [email protected] Subject: Re: [Clearwater] CLearwater with OpenIMSCore HSS HI I am using the SVN source, so I believed it is config problem. Is it possible to share the correct configurations? - PS -----Original Message----- From: DURECU, OLIVIER (OLIVIER) [mailto:[email protected]] Sent: Thursday, May 22, 2014 5:18 PM To: PS; [email protected] Subject: RE: CLearwater with OpenIMSCore HSS Hi A frequent error is to use the OpenIMS HSS archive found on their web site, which is outdated You have to check out the most recent from their SVN repo, build it and everything should be fine Olivier DURECU Bell Labs / IP Platform Research Villarceaux Center Tel: +33(0) 160402759 GSM: +33(0) 683776482 -----Message d'origine----- De : [email protected] [mailto:[email protected]] De la part de Paul Sun Envoyé : jeudi 22 mai 2014 11:13 À : [email protected] Objet : [Clearwater] CLearwater with OpenIMSCore HSS Hi I am able to make test call using the All-In-One-Images, and now I would like to extend my test on integrating the Clearwater with OpenIMSCore HSS. I followed the instructions in the wiki, but not able to get successes, is there anyone can provide guideline? Thanks PS _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
