Hi Ellie,
I am unable to establish diameter link with Open HSS. Please find below logs
(homestead) and configuration .
12-10-2016 12:00:03.815 UTC Debug diameterresolver.cpp:91:
DiameterResolver::resolve for realm , host 10.112.87.132, family 2
12-10-2016 12:00:03.821 UTC Debug baseresolver.cpp:523: Attempt to parse
10.112.87.132 as IP address
12-10-2016 12:00:03.821 UTC Debug diameterresolver.cpp:175: Target is an IP
address - default port/transport
12-10-2016 12:00:03.821 UTC Debug realmmanager.cpp:381: Adding peer:
10.112.87.132
12-10-2016 12:00:03.821 UTC Debug freeDiameter: Diameter peer 10.112.87.132
added
12-10-2016 12:00:03.821 UTC Debug freeDiameter: New global list of peers:
{peer}(@0x7f2acc016070): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc010f80): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc0124b0): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc010a40): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc0104c0): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc0113d0): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc011f80): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc011c60): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc0131b0): 10.112.87.132 [STATE_NEW, cnt:0sr,0pa]
12-10-2016 12:00:03.821 UTC Warning diameterstack.cpp:858: No connected
Diameter peers have been found
12-10-2016 12:00:03.821 UTC Debug freeDiameter: Peer timeout reset to 0 seconds
(+/- 2)
12-10-2016 12:00:03.821 UTC Debug freeDiameter: '10.112.87.132' in state
'STATE_CLOSED' waiting for next event.
12-10-2016 12:00:04.792 UTC Debug freeDiameter: 'STATE_CLOSED' <--
'FDEVP_PSM_TIMEOUT' ((nil),0) '10.112.87.132'
12-10-2016 12:00:04.792 UTC Debug freeDiameter: 10.112.87.132: Connecting...
12-10-2016 12:00:04.792 UTC Debug freeDiameter: 'STATE_CLOSED' ->
'STATE_WAITCNXACK' '10.112.87.132'
12-10-2016 12:00:04.792 UTC Debug freeDiameter: Peer timeout reset to 10 seconds
12-10-2016 12:00:04.792 UTC Debug freeDiameter: '10.112.87.132' in state
'STATE_WAITCNXACK' waiting for next event.
12-10-2016 12:00:04.792 UTC Debug freeDiameter: Prepared 1 sets of connection
parameters to peer 10.112.87.132
12-10-2016 12:00:04.793 UTC Debug freeDiameter: Connecting to TCP
10.112.87.132(3868)...
12-10-2016 12:00:04.793 UTC Debug freeDiameter: TCP connection to
10.112.87.132(3868) failed: Connection refused
12-10-2016 12:00:04.793 UTC Debug diameterstack.cpp:371: Callback (type 11)
from freeDiameter: 10.112.87.132
12-10-2016 12:00:04.793 UTC Error realmmanager.cpp:142: Failed to connect to
10.112.87.132
12-10-2016 12:00:04.793 UTC Debug baseresolver.cpp:498: Add 10.112.87.132:3868
transport 132 to blacklist for 30 seconds, graylist for 0 seconds
12-10-2016 12:00:04.793 UTC Debug diameterresolver.cpp:91:
DiameterResolver::resolve for realm , host 10.112.87.132, family 2
12-10-2016 12:00:04.793 UTC Debug baseresolver.cpp:523: Attempt to parse
10.112.87.132 as IP address
12-10-2016 12:00:04.793 UTC Debug diameterresolver.cpp:175: Target is an IP
address - default port/transport
12-10-2016 12:00:04.793 UTC Debug realmmanager.cpp:381: Adding peer:
10.112.87.132
12-10-2016 12:00:04.793 UTC Info diameterstack.cpp:833: Peer already exists
12-10-2016 12:00:04.793 UTC Debug realmmanager.cpp:389: Peer already exists:
10.112.87.132
12-10-2016 12:00:04.793 UTC Warning diameterstack.cpp:858: No connected
Diameter peers have been found
12-10-2016 12:00:04.793 UTC Debug freeDiameter: 'STATE_WAITCNXACK' <--
'FDEVP_CNX_FAILED' ((nil),0) '10.112.87.132'
12-10-2016 12:00:04.793 UTC Debug freeDiameter: Peer timeout reset to 30
seconds (+/- 2)
12-10-2016 12:00:04.793 UTC Debug freeDiameter: 'STATE_WAITCNXACK' ->
'STATE_CLOSED' '10.112.87.132'
12-10-2016 12:00:04.793 UTC Debug freeDiameter: '10.112.87.132' in state
'STATE_CLOSED' waiting for next event.
12-10-2016 12:00:04.793 UTC Debug freeDiameter: 'STATE_CLOSED' <--
'FDEVP_TERMINATE' ((nil),0) '10.112.87.132'
12-10-2016 12:00:04.793 UTC Status freeDiameter: 10.112.87.132: Going to ZOMBIE
state (no more activity)
12-10-2016 12:00:04.793 UTC Status freeDiameter: 'STATE_CLOSED' -> STATE_ZOMBIE
(terminated) '10.112.87.132'
12-10-2016 12:00:04.964 UTC Verbose httpstack.cpp:293: Process request for URL
/ping, args (null)
12-10-2016 12:00:04.964 UTC Verbose httpstack.cpp:69: Sending response 200 to
request for URL /ping, args (null)
12-10-2016 12:00:05.228 UTC Debug alarm.cpp:253: Reraising all alarms with a
known state
12-10-2016 12:00:09.793 UTC Debug diameterresolver.cpp:91:
DiameterResolver::resolve for realm , host 10.112.87.132, family 2
12-10-2016 12:00:09.793 UTC Debug baseresolver.cpp:523: Attempt to parse
10.112.87.132 as IP address
12-10-2016 12:00:09.793 UTC Debug diameterresolver.cpp:175: Target is an IP
address - default port/transport
12-10-2016 12:00:09.793 UTC Debug realmmanager.cpp:381: Adding peer:
10.112.87.132
12-10-2016 12:00:09.793 UTC Debug freeDiameter: Diameter peer 10.112.87.132
added
12-10-2016 12:00:09.793 UTC Debug freeDiameter: New global list of peers:
{peer}(@0x7f2acc016070): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc010f80): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc0124b0): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc010a40): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc0104c0): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc0113d0): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc011f80): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc011c60): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc0131b0): 10.112.87.132 [STATE_ZOMBIE, cnt:0sr,0pa]
{peer}(@0x7f2acc013860): 10.112.87.132 [STATE_NEW, cnt:0sr,0pa]
-------------------------------------------------------Shared_config-----------------------------------------
# Deployment definitions
home_domain=open-ims.test
sprout_hostname=cw-aio
hs_hostname=10.112.87.250:8888
hs_provisioning_hostname=10.112.87.250:8889
xdms_hostname=10.112.87.250:7888
ralf_hostname=
# Email server configuration
smtp_smarthost=127.0.0.1
smtp_username=username
smtp_password=password
[email protected]
# I-CSCF/S-CSCF configuration
upstream_hostname=scscf.cw-aio
# Keys
signup_key=secret
turn_workaround=secret
ellis_api_key=secret
ellis_cookie_key=secret
reduce_cassandra_mem_usage=Y
# HSS configuration
hss_hostname=10.112.87.132
hss_port=3868
enum_file=enum.json
--------------------------------------DaimeterPeerHSS.xml------------------------------
<?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="10.112.87.132" />
<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>
Message: 1
Date: Wed, 5 Oct 2016 16:03:13 +0000
From: "Eleanor Merry (projectclearwater.org)"
<[email protected]>
To: "[email protected]"
<[email protected]>
Subject: Re: [Project Clearwater] Integration of Open HSS_All-in-one
Message-ID:
<by2pr02mb208601e0be02e519e388be8a9b...@by2pr02mb2086.namprd02.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Hi Surender,
To use an external HSS you'll need to set the following settings in
/etc/clearwater/shared_config
hss_hostname=<address of your HSS>
hss_realm=<realm your HSS is located in> hss_port=<port of your HSS's Cx
interface>
Both hss_hostname and hss_realm are optional. If a realm is configured,
homestead will try NAPTR/SRV resolution on the realm to find and connect to (2
by default) diameter peers in the realm.
If a hostname is also configured, this will be used in the Destination-Host
field on the diameter messages, so that the messages will be routed to that
host.
If just a hostname is configured, homestead will just attempt to create and
maintain a single connection to that host.
You can find more information on this at
http://clearwater.readthedocs.io/en/latest/External_HSS_Integration.html, and
you may also find
http://clearwater.readthedocs.io/en/latest/OpenIMSCore_HSS_Integration.html
useful.
For your other queries:
1. You can configure subscribers to use an application server that provides
these functions by setting their IFCs in the HSS. You can use the MMTel
application server built into Clearwater for this - see the details at
http://clearwater.readthedocs.io/en/latest/OpenIMSCore_HSS_Integration.html#adding-the-mmtel-application-server
for more information.
2. The key restrictions of the all-in-one solutions are:
* hard-coded realm - the all-in-one image uses a hard-coded realm of
example.com so your SIP URI might be sip:[email protected] - by default,
SIP uses this realm for routing but example.com won't resolve to your host so
you need to configure an outbound proxy on all your SIP clients
* performance - since all software runs on a single virtual machine,
performance is significantly lower than even the smallest scale deployment
* scalability - there is no option to scale up and add more virtual machines to
boost capacity - for this, you must create a normal deployment
* fault-tolerance - since everything runs on a single virtual machine, if that
virtual machine fails, the service as a whole fails.
3. I didn't understand this question. What's the 'other DNS'?
Ellie
From: Clearwater [mailto:[email protected]] On
Behalf Of Surender Singh
Sent: 03 October 2016 07:11
To: [email protected]
Subject: [Project Clearwater] Integration of Open HSS_All-in-one
Hello,
I deployed the All in one solution in VMware machine .My IN-OUT calls are
working to other network using BGCF/IBCF feature .
Now i want Integrate the Open HSS with Homestead node .Can you suggest me where
I need to make the entry in aio solution .
I having some below query..
1) Can we provision the basic supplementary service (CF Service, Three
Party, Call-Transfer , Call park etc .) in open HSS.
2) Any other drawbacks of the all-in-one solution apart from Performance
/Production.
3) Can i integrate the other DNS for DNS query .
Regards
Surender Singh
::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information
could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
may contain viruses in transmission. The e mail and its contents (with or
without referred errors) shall therefore not attach any liability on the
originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the
author and may not necessarily reflect the views or opinions of HCL or its
affiliates. Any form of reproduction, dissemination, copying, disclosure,
modification, distribution and / or publication of this message without the
prior written consent of authorized representative of HCL is strictly
prohibited. If you have received this email in error please delete it and
notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and
other defects.
----------------------------------------------------------------------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.projectclearwater.org/pipermail/clearwater_lists.projectclearwater.org/attachments/20161005/2ddbd5cf/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
------------------------------
End of Clearwater Digest, Vol 42, Issue 4
*****************************************
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
