Hi James You are correct, I noticed that the value is set to 2, and the auto assignment on S-CSCF is failed. I changed it to “1” and now is working….
Appreciated your help. - PS From: James Coleman [mailto:[email protected]] Sent: Friday, May 23, 2014 6:49 PM To: Paul Sun Cc: Eleanor Merry; [email protected] Subject: Re: [Clearwater] CLearwater with OpenIMSCore HSS I also see in webconsole there is no way to set s-cscf (probably indication it is better to allow HSS to control that value). I never had to set value for s-cscf in HSS. Initially the value was populated and user_state set to 1. When I had problem I saw user_state became 1 (or sometimes 2 un-registered) and s-cscf name (and diametername) was cleared. To recover from that I set the user_state back to 0 (and removed homestead_cache entry). After that REGISTER (MAR/MAA and SAR/SAA and user_state=1 and values were populated for s-cscf name. James. On 23 May 2014 11:39, Paul Sun <[email protected]<mailto:[email protected]>> wrote: From the HSS webconsole, the function to configure the S-CSCF is disabled. When MAR is received in HSS, HSS failed the request, so no SAR is generated from Clearwater. I checked on the imsu table under above situatiin, both scscf and diameter fields are null. PS -------- Original message -------- From: James Coleman Date:2014/05/23 18:32 (GMT+08:00) To: Paul Sun Cc: Eleanor Merry ,[email protected]<mailto:[email protected]> Subject: Re: [Clearwater] CLearwater with OpenIMSCore HSS sip uri and port is in scscf_name in hss . . what is in your imsu table on hss? e.g. scscf_name and diameter_name for me: | sip:10.99.99.99:5054<http://10.99.99.99:5054> | ec2-54-99-99-99.compute-1.amazonaws.com<http://ec2-54-99-99-99.compute-1.amazonaws.com> | Better to leave HSS populate those values I think if possible . . . :-7 s-cscf assignment? Sorry I'm not sure. There is a SAR/SAA done some time after the MAR/MAA. I think in the SAR the scscf name is sent to HSS. James. . . SAR/SAA: No. Time Source Destination Protocol Length Info 834 14:42:02.998612 10.124.51.133 54.216.183.64 DIAMETER 468 cmd=Server-AssignmentRequest(301) flags=RP-- appl=3GPP Cx(16777216) h2h=1966d462 e2e=7cbc85a5 Frame 834: 468 bytes on wire (3744 bits), 468 bytes captured (3744 bits) Linux cooked capture Internet Protocol Version 4, Src: 10.124.51.133 (10.124.51.133), Dst: 54.216.183.64 (54.216.183.64) Transmission Control Protocol, Src Port: 59354 (59354), Dst Port: diameter (3868), Seq: 2005, Ack: 1605, Len: 400 Diameter Protocol Version: 0x01 Length: 400 Flags: 0xc0 Command Code: 301 Server-Assignment ApplicationId: 3GPP Cx (16777216) Hop-by-Hop Identifier: 0x1966d462 End-to-End Identifier: 0x7cbc85a5 [Answer In: 841] AVP: Session-Id(263) l=66 f=-M- val=ec2-54-198-205-191.compute-1.amazonaws.com<http://ec2-54-198-205-191.compute-1.amazonaws.com>;1400162251;4976 AVP: Vendor-Specific-Application-Id(260) l=32 f=-M- AVP: Auth-Session-State(277) l=12 f=-M- val=NO_STATE_MAINTAINED (1) AVP: Origin-Host(264) l=50 f=-M- val=ec2-54-198-205-191.compute-1.amazonaws.com<http://ec2-54-198-205-191.compute-1.amazonaws.com> AVP: Origin-Realm(296) l=21 f=-M- val=10.124.51.133 AVP: Destination-Host(293) l=24 f=-M- val=hss.openims.test AVP: Destination-Realm(283) l=20 f=-M- val=openims.test AVP: User-Name(1) l=34 f=-M- val=+353894468340<tel:%2B353894468340>@openims.test AVP: Public-Identity(601) l=42 f=VM- vnd=TGPP val=sip:+353894468340<tel:%2B353894468340>@openims.test AVP: Server-Name(602) l=34 f=VM- vnd=TGPP val=sip:10.124.51.133:5054<http://10.124.51.133:5054> AVP: Server-Assignment-Type(614) l=16 f=VM- vnd=TGPP val=RE_REGISTRATION (2) AVP: User-Data-Already-Available(624) l=16 f=VM- vnd=TGPP val=USER_DATA_NOT_AVAILABLE (0) No. Time Source Destination Protocol Length Info 841 14:42:03.123082 54.216.183.64 10.124.51.133 DIAMETER/XML 1120 cmd=Server-AssignmentAnswer(301) flags=-P-- appl=3GPP Cx(16777216) h2h=1966d462 e2e=7cbc85a5 Frame 841: 1120 bytes on wire (8960 bits), 1120 bytes captured (8960 bits) Linux cooked capture Internet Protocol Version 4, Src: 54.216.183.64 (54.216.183.64), Dst: 10.124.51.133 (10.124.51.133) Transmission Control Protocol, Src Port: diameter (3868), Dst Port: 59354 (59354), Seq: 5949, Ack: 2405, Len: 1052 [4 Reassembled TCP Segments (5396 bytes): #836(1448), #837(1448), #840(1448), #841(1052)] Diameter Protocol Version: 0x01 Length: 5396 Flags: 0x40 Command Code: 301 Server-Assignment ApplicationId: 3GPP Cx (16777216) Hop-by-Hop Identifier: 0x1966d462 End-to-End Identifier: 0x7cbc85a5 [Request In: 834] [Response Time: 0.124470000 seconds] AVP: Session-Id(263) l=66 f=-M- val=ec2-54-198-205-191.compute-1.amazonaws.com<http://ec2-54-198-205-191.compute-1.amazonaws.com>;1400162251;4976 AVP: Origin-Host(264) l=24 f=-M- val=hss.openims.test AVP: Origin-Realm(296) l=20 f=-M- val=openims.test AVP: Auth-Session-State(277) l=12 f=-M- val=NO_STATE_MAINTAINED (1) AVP: Vendor-Specific-Application-Id(260) l=32 f=-M- AVP: User-Name(1) l=34 f=-M- val=+353894468340<tel:%2B353894468340>@openims.test AVP: User-Data(606) l=5132 f=VM- vnd=TGPP val=3c3f786d6c2076657273696f6e3d22312e302220656e636f... AVP: Charging-Information(618) l=40 f=VM- vnd=TGPP AVP: Result-Code(268) l=12 f=-M- val=DIAMETER_SUCCESS (2001) On 23 May 2014 11:07, Paul Sun <[email protected]<mailto:[email protected]>> wrote: I did a try to update the imsu table in HSS, and hardcoded the SIP URI on scsf_name, and the user can now be registered. But still do not know the reason why it cannot be registered even the preferred S-CSCF is configured. Also, pls correct my understanding. When homestead sends MAR to HSS, HSS will response MAA with the S-CSCF assignment, rite? - PS From: James Coleman [mailto:[email protected]<mailto:[email protected]>] Sent: Friday, May 23, 2014 6:01 PM To: Paul Sun Cc: Eleanor Merry; [email protected]<mailto:[email protected]> Subject: Re: [Clearwater] CLearwater with OpenIMSCore HSS I'm just guessing here but the error you show makes me think of something I see. "User is registered but has no S-CSCF name stored - HSS database consistency error" What does your IMSU and IMPUs show for that user in HSS? User state and scscf? I see that sometimes (sometimes after a session is interrupted on server side): in HSS IMPU shows REGISTERED but in IMSU no s-cscf name (or diameter name) is set. REGISTERs don't work if this happens. To clear that inconsistency I set user_state back to 0 in HSS. mysql -u hss -p hss_db, then do select * from impu; and update impu set userstate=0 where id=<the_id_of_user_from_impu_table>; And in cassandra on clearwater also remove the entry from user cqlsh; use homestead_cache; select * from impu; delete from impu where ....; And (probably out of superstition more than necessity) I restart hss. Might not be your issue though :-7 James. A working MAR/MAA for your reference: . . . No. Time Source Destination Protocol Length Info 799 14:42:02.438537 10.124.51.133 54.216.183.64 DIAMETER 484 cmd=Multimedia-AuthRequest(303) flags=RP-- appl=3GPP Cx(16777216) h2h=1966d461 e2e=7cbc85a4 Frame 799: 484 bytes on wire (3872 bits), 484 bytes captured (3872 bits) Linux cooked capture Internet Protocol Version 4, Src: 10.124.51.133 (10.124.51.133), Dst: 54.216.183.64 (54.216.183.64) Transmission Control Protocol, Src Port: 59354 (59354), Dst Port: diameter (3868), Seq: 1589, Ack: 1197, Len: 416 Diameter Protocol Version: 0x01 Length: 416 Flags: 0xc0 Command Code: 303 Multimedia-Auth ApplicationId: 3GPP Cx (16777216) Hop-by-Hop Identifier: 0x1966d461 End-to-End Identifier: 0x7cbc85a4 [Answer In: 800] AVP: Session-Id(263) l=66 f=-M- val=ec2-54-198-205-191.compute-1.amazonaws.com<http://ec2-54-198-205-191.compute-1.amazonaws.com>;1400162251;4975 AVP: Vendor-Specific-Application-Id(260) l=32 f=-M- AVP: Auth-Session-State(277) l=12 f=-M- val=NO_STATE_MAINTAINED (1) AVP: Destination-Realm(283) l=20 f=-M- val=openims.test AVP: Destination-Host(293) l=24 f=-M- val=hss.openims.test AVP: Origin-Host(264) l=50 f=-M- val=ec2-54-198-205-191.compute-1.amazonaws.com<http://ec2-54-198-205-191.compute-1.amazonaws.com> AVP: Origin-Realm(296) l=21 f=-M- val=10.124.51.133 AVP: User-Name(1) l=34 f=-M- [email protected]<mailto:[email protected]> AVP: Public-Identity(601) l=42 f=VM- vnd=TGPP val=sip:+353894468340<tel:%2B353894468340>@openims.test AVP: SIP-Auth-Data-Item(612) l=32 f=VM- vnd=TGPP AVP: SIP-Number-Auth-Items(607) l=16 f=VM- vnd=TGPP val=1 AVP: Server-Name(602) l=34 f=VM- vnd=TGPP val=sip:10.124.51.133:5054<http://10.124.51.133:5054> No. Time Source Destination Protocol Length Info 800 14:42:02.532474 54.216.183.64 10.124.51.133 DIAMETER 476 cmd=Multimedia-AuthAnswer(303) flags=-P-- appl=3GPP Cx(16777216) h2h=1966d461 e2e=7cbc85a4 Frame 800: 476 bytes on wire (3808 bits), 476 bytes captured (3808 bits) Linux cooked capture Internet Protocol Version 4, Src: 54.216.183.64 (54.216.183.64), Dst: 10.124.51.133 (10.124.51.133) Transmission Control Protocol, Src Port: diameter (3868), Dst Port: 59354 (59354), Seq: 1197, Ack: 2005, Len: 408 Diameter Protocol Version: 0x01 Length: 408 Flags: 0x40 Command Code: 303 Multimedia-Auth ApplicationId: 3GPP Cx (16777216) Hop-by-Hop Identifier: 0x1966d461 End-to-End Identifier: 0x7cbc85a4 [Request In: 799] [Response Time: 0.093937000 seconds] AVP: Session-Id(263) l=66 f=-M- val=ec2-54-198-205-191.compute-1.amazonaws.com<http://ec2-54-198-205-191.compute-1.amazonaws.com>;1400162251;4975 AVP: Origin-Host(264) l=24 f=-M- val=hss.openims.test AVP: Origin-Realm(296) l=20 f=-M- val=openims.test AVP: Auth-Session-State(277) l=12 f=-M- val=NO_STATE_MAINTAINED (1) AVP: Vendor-Specific-Application-Id(260) l=32 f=-M- AVP: Public-Identity(601) l=42 f=VM- vnd=TGPP val=sip:+353894468340<tel:%2B353894468340>@openims.test AVP: User-Name(1) l=34 f=-M- [email protected]<mailto:[email protected]> AVP: SIP-Number-Auth-Items(607) l=16 f=VM- vnd=TGPP val=1 AVP: SIP-Auth-Data-Item(612) l=124 f=VM- vnd=TGPP AVP: Result-Code(268) l=12 f=-M- val=DIAMETER_SUCCESS (2001) On 23 May 2014 08:50, Paul Sun <[email protected]<mailto:[email protected]>> wrote: Below is the MAR and MAA No. Time Source Sport Destination Dport RawProto Protocol Length VlanId Dscp Info 91 2014-05-23 15:08:10.487038 192.168.0.144 34924 192.168.0.134 3868 TCP DIAMETER 416 0 cmd=Multimedia-AuthRequest(303) flags=RP-- appl=3GPP Cx(16777216) h2h=737ffa6 e2e=58a3be69 Frame 91: 416 bytes on wire (3328 bits), 416 bytes captured (3328 bits) Linux cooked capture Internet Protocol Version 4, Src: 192.168.0.144 (192.168.0.144), Dst: 192.168.0.134 (192.168.0.134) Transmission Control Protocol, Src Port: 34924 (34924), Dst Port: diameter (3868), Seq: 2761, Ack: 1993, Len: 348 Diameter Protocol Version: 0x01 Length: 348 Flags: 0xc0 Command Code: 303 Multimedia-Auth ApplicationId: 3GPP Cx (16777216) Hop-by-Hop Identifier: 0x0737ffa6 End-to-End Identifier: 0x58a3be69 [Answer In: 93] AVP: Session-Id(263) l=35 f=-M- val=192.168.0.144;1400817034;31 AVP: Vendor-Specific-Application-Id(260) l=32 f=-M- AVP: Auth-Session-State(277) l=12 f=-M- val=NO_STATE_MAINTAINED (1) AVP: Destination-Realm(283) l=19 f=-M- val=example.com<http://example.com> AVP: Destination-Host(293) l=21 f=-M- val=192.168.0.134 AVP: Origin-Host(264) l=21 f=-M- val=192.168.0.144 AVP: Origin-Realm(296) l=21 f=-M- val=192.168.0.144 AVP: User-Name(1) l=30 f=-M- [email protected]<mailto:[email protected]> AVP: Public-Identity(601) l=38 f=VM- vnd=TGPP val=sip:[email protected]<mailto:sip%[email protected]> AVP: SIP-Auth-Data-Item(612) l=32 f=VM- vnd=TGPP AVP: SIP-Number-Auth-Items(607) l=16 f=VM- vnd=TGPP val=1 AVP: Server-Name(602) l=34 f=VM- vnd=TGPP val=sip:192.168.0.144:5054<http://192.168.0.144:5054> No. Time Source Sport Destination Dport RawProto Protocol Length VlanId Dscp Info 93 2014-05-23 15:08:10.496040 192.168.0.134 3868 192.168.0.144 34924 TCP DIAMETER 224 0 cmd=Multimedia-AuthAnswer(303) flags=-P-- appl=3GPP Cx(16777216) h2h=737ffa6 e2e=58a3be69 Frame 93: 224 bytes on wire (1792 bits), 224 bytes captured (1792 bits) Linux cooked capture Internet Protocol Version 4, Src: 192.168.0.134 (192.168.0.134), Dst: 192.168.0.144 (192.168.0.144) Transmission Control Protocol, Src Port: diameter (3868), Dst Port: 34924 (34924), Seq: 1993, Ack: 3109, Len: 156 Diameter Protocol Version: 0x01 Length: 156 Flags: 0x40 Command Code: 303 Multimedia-Auth ApplicationId: 3GPP Cx (16777216) Hop-by-Hop Identifier: 0x0737ffa6 End-to-End Identifier: 0x58a3be69 [Request In: 91] [Response Time: 0.009002000 seconds] AVP: Session-Id(263) l=35 f=-M- val=192.168.0.144;1400817034;31 AVP: Origin-Host(264) l=21 f=-M- val=192.168.0.134 AVP: Origin-Realm(296) l=19 f=-M- val=example.com<http://example.com> AVP: Auth-Session-State(277) l=12 f=-M- val=NO_STATE_MAINTAINED (1) AVP: Vendor-Specific-Application-Id(260) l=32 f=-M- AVP: Result-Code(268) l=12 f=-M- val=DIAMETER_UNABLE_TO_COMPLY (5012) -----Original Message----- From: PS Sent: Friday, May 23, 2014 1:17 PM To: 'Eleanor Merry'; '[email protected]<mailto:[email protected]>' Subject: RE: CLearwater with OpenIMSCore HSS 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: PS Sent: Friday, May 23, 2014 10:32 AM To: 'Eleanor Merry'; [email protected]<mailto:[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]<mailto:[email protected]>] Sent: Thursday, May 22, 2014 7:55 PM To: PS; [email protected]<mailto:[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<http://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<http://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]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of PS Sent: 22 May 2014 10:43 To: PS; DURECU, OLIVIER (OLIVIER); [email protected]<mailto:[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]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of PS Sent: Thursday, May 22, 2014 5:30 PM To: DURECU, OLIVIER (OLIVIER); [email protected]<mailto:[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]<mailto:[email protected]>] Sent: Thursday, May 22, 2014 5:18 PM To: PS; [email protected]<mailto:[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<tel:%2B33%280%29%20160402759> GSM: +33(0) 683776482<tel:%2B33%280%29%20683776482> -----Message d'origine----- De : [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] De la part de PS Envoyé : jeudi 22 mai 2014 11:13 À : [email protected]<mailto:[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]<mailto:[email protected]> http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/listinfo/clearwater [https://lh6.googleusercontent.com/-hOsXXSXoa0Y/UX-28huVdeI/AAAAAAAAAII/pF1UxAvxLgE/w600-h161-no/rcs-email-sig.jpg] [https://lh5.googleusercontent.com/-pP2K9aC_OqY/UoKWY19BjcI/AAAAAAAAAeg/Xw1NHN5wLDk/w158-h27-no/image001.png]<http://www.linkedin.com/company/76647?trk=fc_badge> openmindnetworks.com<http://openmindnetworks.com> [https://lh6.googleusercontent.com/-hOsXXSXoa0Y/UX-28huVdeI/AAAAAAAAAII/pF1UxAvxLgE/w600-h161-no/rcs-email-sig.jpg] [https://lh5.googleusercontent.com/-pP2K9aC_OqY/UoKWY19BjcI/AAAAAAAAAeg/Xw1NHN5wLDk/w158-h27-no/image001.png]<http://www.linkedin.com/company/76647?trk=fc_badge> openmindnetworks.com<http://openmindnetworks.com> [https://lh6.googleusercontent.com/-hOsXXSXoa0Y/UX-28huVdeI/AAAAAAAAAII/pF1UxAvxLgE/w600-h161-no/rcs-email-sig.jpg] [https://lh5.googleusercontent.com/-pP2K9aC_OqY/UoKWY19BjcI/AAAAAAAAAeg/Xw1NHN5wLDk/w158-h27-no/image001.png]<http://www.linkedin.com/company/76647?trk=fc_badge> openmindnetworks.com<http://openmindnetworks.com> _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
