Adding and Removing Freeswitch Nodes Using ecallmgr

[jon2718]

Hi,

I am putting together a Kazoo cluster. I attempted to add one of my two Freeswitch nodes like so:

/opt/kazoo/utils/sup/sup -n ecallmgr ecallmgr_maintenance add_fs_node freeswitch@sc-kazoo-freeswitch1 

This failed with the message: {error,no_connection}

I then can see the Freeswitch node I attempted to add via: 

/opt/kazoo/utils/sup/sup -n ecallmgr ecallmgr_config get fs_nodes

[<<"freeswitch@sc-kazoo-freeswitch1">>]

I then attempt to remove the Freeswitch node using:

/opt/kazoo/utils/sup/sup -n ecallmgr ecallmgr_maintenance remove_fs_node freeswitch@sc-kazoo-freeswitch1

removing freeswitch@sc-kazoo-freeswitch1 from ecallmgr system config

However, when I do another get_s_nodes, the FS node is still there.  Is there some issue with the remove functionality?

I am following the instructions for Kazoo install from this page: https://2600hz.atlassian.net/wiki/display/Dedicated/via+RPM

My other question is whether I need to pass the freeswitch username as shown in the example when I add the FS node.  I am not fully clear how ecallmgr talks to Freeswitch and why this is failing.  There should not be a firewall issue as this is all over a LAN.

Thanks in advance for your help.

-Jon

[Darren Schreiber]

I’ve seen this remove issue before. If the node never got connected, I think it fails to remove it.

Please file this as a bug on tickets.2600hz.com

--
You received this message because you are subscribed to the Google Groups "2600hz-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-users...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[James Aimonetti]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

When adding FreeSWITCH nodes, you need to use the full user@hostname
that mod_kazoo reports. From the fs_cli, issuing an 'erlang status'
will show you a line like:

Registered as Erlang node frees...@hostname.com, visible as freeswitch

You must use 'frees...@hostname.com' to add the node, and you must
make sure your ecallmgr box can resolve 'hostname.com' to the correct IP.

- --
James Aimonetti
Lead Systems Architect / Impressionable Scallywag
"I thought I fixed that"

2600Hz | http://2600hz.com
sip:ja...@2600hz.com
tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJUyF7CAAoJENTKa+JPXCVgwb4IALO02xNHy2yfsG30+cgHCjT2
XOoKquVB1BkYuIzAK18x/r3em9JBpl0UQFba9If0ecT2dkyjoxbityo+b5d6COJ7
AfSc6BcxSBfWUiwqR2+slrq8bhY7vW7SRG8blpRxDgroPkIfDgHaIoGlqyjpijpc
1ppkd+LEtYmjRR54srZjVWG4j77/NS7fKSsd1QMfEU3t1ATFTxCTZVfnSFErOPOS
1Xg8YbW5w4rMhReFOLCD6q0l+kJYSK1FHpJUSBHuY2FC8ivyJR2b/4q/+CxItQIa
/DvLGMTkHrJ0auqmuZKE2Z0VcwyrQyqv0plI6S1H5fUs/CZ64WpXTqtExkmyJEI=
=h4uw
-----END PGP SIGNATURE-----

[jon2718]

Thanks.

1) I am sure the hostname is resolving to the right IP.  The node still won't register and I see no activity in the fs_cli.  Is it possible because I added the node and it initially failed, something is awry with the configuration.  How do I completely remove the node and add it again, given the bug when trying to remove a node that initially fails.  What other things should I look at that would cause adding a FS node to fail.  It's not a firewall issue as I am on a LAN with all ports open.  Also, BTW, I am running on Google Cloud. 

2) I tried to add a bug report, but I keep getting the message that a reporter is required and I don't have sign-in access to your Jira site.

sip:...@2600hz.com

[Siuleinad]

I have seen the error before make sure using the following commands return the FQDN and the IP of your server

hostname

hostname -f

hostname -i 

The clue there is using fs_cli -x "erlang status" you should see freeswitch@FQDN where FQDN your server name, if not there is an error on the way you are declaring your hostname.

if hostname does not give you the FQDN try adding it manual with "hostname FQDN" (replace FQDN with your server, if you are using CentOS, change file /etc/sysconfig/network and use FQDN in the HOSTNAME variable as well) then restart kz-apps and see the status of the erlang on freeswitch (fs_cli -x "erlang status"). if not connected try adding the freeswitch to kazoo back again, it should connect.