01:35:27 <mentax> Hi all
01:36:27 <mentax> mc_: question - when I receive a System Alert email it said: Sent from eSr6THy7... what does it mean and how to find the host which send it?
01:38:24 <mentax> Trying to figure out what cause the error: System Alert: recovery_on_timer_expire 2001 to betty.customer1 (outbound) on db96a95350e6e....
08:04:02 <alane> mentax: "Sent from" is encoded by default via system.encoded_node in the template, if you want to reveal the actual node name you can change the template to system.node, the encoding is a base64 of the md5 of the node so it is a one way hash.
11:15:02 <mentax> alane: I just need to know which server has this md5 if it is permanent
12:14:32 <alane> mentax: I've written a quick escript so you can get the hash of a node. If you put this file https://gist.github.com/kageds/df2b9d35cf3b75988a2e67ad0319d061 in /opt/kazoo/ and then run /opt/kazoo/bin/kazoo escript calc_hash.escript kazoo_apps@`hostname` it should output node "kazoo_apps@kz01.??????.com" = 40AB0CGsTZKnlVDv94uVIQ
12:15:46 <mentax> alane Wow! Thank you!
12:32:49 <alane> no problem, hope it helps
14:18:29 <mentax_> How can I set that kazoo will add local area code automatically? customer need to dial 321 123 1234 and they need to be able to dial 123 1234 and 321 will add 
15:10:25 <mentax_> There is another major issue, when customer call outside, kazoo did not allow to leave voicemail to remote phone
15:25:16 <mc_> mentax_: dialplans for the account can auto-correct it
15:25:44 <mc_> and did the terminating leg answer the call for voicemail?
16:38:57 <mentax_> sooooo wired... Lot of calls dropping in the middle off call
16:39:07 <mentax_> something is not right....
17:09:22 <hmmhesays> freeswitch logs will tell you why.
17:15:15 <mentax_> sup -necallmgr ecallmgr_maintenance list_fs_nodes and sup ecallmgr_maintenance list_fs_nodes should return the same value?
17:17:46 <mc_> mentax_: only if ecallmgr is running on both the `ecallmgr@hostname` and `kazoo_apps@hostname`
17:18:10 <mc_> otherwise -necallmgr is needed to talk to the ecallmgr@hostname VM
17:18:28 <mc_> with no -n{NAME} sup defaults to `kazoo_apps`
17:19:30 <mentax_> how can I find out? kazoo-ecallmgr running from startup script i.e systemctl start kazoo-ecallmgr
17:21:02 <mc_> kazoo-applications status
17:21:05 <mc_> will list all running nodes
17:21:24 <mc_> and list nodes running ecallmgr
17:23:36 <mentax_> so, I can see ecallmgr⊙sdc and kazoo_apps⊙sdc
17:25:15 <mentax_> sup ecallmgr_maintenance list_fs_nodes
17:25:15 <mentax_> Command failed: {'EXIT',{noproc,{gen_server,call,[ecallmgr_fs_nodes,{connected_nodes,false}]}}}
17:26:53 <mc_> yup, expected if ecallmgr isn't running
17:28:42 <mentax_> mc_: how them it should be running? kazoo-ecallmgr status return data
17:31:40 <mentax_> https://docs.2600hz.com/sysadmin/doc/kazoo/cluster-guide/#assign-freeswitch-to-ecallmgr-zones
17:32:18 <mentax_> Verify on Kazoo in each zone that only FreeSWITCH for that zone is listed sup -necallmgr ecallmgr_maintenance list_fs_nodes
17:32:18 <mentax_> If ecallmgr is started separately, with systemd or init, the command would be: sup -necallmgr ecallmgr_maintenance list_fs_nodes
17:32:42 <mentax_> is it correct statement? So confusing 
17:34:57 <hmmhesays> you have to specify sup connected to the ecallmgr node  sup -necallmgr ecallmgr_maintenance etc
17:40:11 <mentax_> hmmhesays on my old cluster both commands return fsnodes
17:52:21 <mentax_> sup kapps_controller start_app ecallmgr
17:52:44 <mentax_> can both of the be running on the same time?
17:56:03 <mentax_> I believe that how I fix it before in old cluster if I'm not mistaken 
17:57:09 <mentax_> mc_: Any idea? ^^
17:58:23 <mc_> what are trying to fix?
17:58:38 <mc_> don't run list_fs_nodes on the node not running ecallmgr
17:59:16 <mentax_> I have all in one server with external DBs cluster
17:59:59 <mentax_> I have lots of issue with System "Alert: unallocated_number" and "recovery_on_timer_expire"
18:00:12 <mentax_> and calls are dropping
18:05:05 <mc_> timer expire tends to suggest firewall on client side
18:05:22 <mc_> unallocated number suggests you haven't mapped the number to an account (or the number doesn't exist)
18:07:59 <mentax_> it is registered in the system =(
18:09:03 <hmmhesays> registration doesn't mean the rest of the signaling is going to work
18:09:14 <hmmhesays> if you're using UDP it's a crap shoot
18:10:02 <mentax_> hmmhesays: Do you think if I will switch my phones to TCP it will be better?
18:50:40 <mentax_> very very strange... It seems like "kapps_controller start_app ecallmgr" did something and now I'm no longer see "Alert: unallocated_number" and "recovery_on_timer_expire"
19:30:53 <hmmhesays> I'm totally blanking on the API to transfer a call