Hi all

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?

Trying to figure out what cause the error: System Alert: recovery_on_timer_expire 2001 to betty.customer1 (outbound) on db96a95350e6e....

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.

alane: I just need to know which server has this md5 if it is permanent

mentax: I've written a quick escript so you can get the hash of a node. If you put this file 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

alane Wow! Thank you!

no problem, hope it helps

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

There is another major issue, when customer call outside, kazoo did not allow to leave voicemail to remote phone

mentax_: dialplans for the account can auto-correct it

and did the terminating leg answer the call for voicemail?

sooooo wired... Lot of calls dropping in the middle off call

something is not right....

freeswitch logs will tell you why.

sup -necallmgr ecallmgr_maintenance list_fs_nodes and sup ecallmgr_maintenance list_fs_nodes should return the same value?

mentax_: only if ecallmgr is running on both the `ecallmgr@hostname` and `kazoo_apps@hostname`

otherwise -necallmgr is needed to talk to the ecallmgr@hostname VM

with no -n{NAME} sup defaults to `kazoo_apps`

how can I find out? kazoo-ecallmgr running from startup script i.e systemctl start kazoo-ecallmgr

kazoo-applications status

will list all running nodes

and list nodes running ecallmgr

so, I can see ecallmgr⊙sdc and kazoo_apps⊙sdc

sup ecallmgr_maintenance list_fs_nodes

Command failed: {'EXIT',{noproc,{gen_server,call,[ecallmgr_fs_nodes,{connected_nodes,false}]}}}

yup, expected if ecallmgr isn't running

mc_: how them it should be running? kazoo-ecallmgr status return data

Verify on Kazoo in each zone that only FreeSWITCH for that zone is listed sup -necallmgr ecallmgr_maintenance list_fs_nodes

If ecallmgr is started separately, with systemd or init, the command would be: sup -necallmgr ecallmgr_maintenance list_fs_nodes

is it correct statement? So confusing

you have to specify sup connected to the ecallmgr node sup -necallmgr ecallmgr_maintenance etc

hmmhesays on my old cluster both commands return fsnodes

sup kapps_controller start_app ecallmgr

can both of the be running on the same time?

I believe that how I fix it before in old cluster if I'm not mistaken

mc_: Any idea? ^^

what are trying to fix?

don't run list_fs_nodes on the node not running ecallmgr

I have all in one server with external DBs cluster

I have lots of issue with System "Alert: unallocated_number" and "recovery_on_timer_expire"

and calls are dropping

timer expire tends to suggest firewall on client side

unallocated number suggests you haven't mapped the number to an account (or the number doesn't exist)

it is registered in the system =(

registration doesn't mean the rest of the signaling is going to work

if you're using UDP it's a crap shoot

hmmhesays: Do you think if I will switch my phones to TCP it will be better?

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"

I'm totally blanking on the API to transfer a call