When one user dials *97{mailbox number} to a mailbox that doesn't belong to them, a recording plays that says you're not allowed to access this mailbox.

I'm not sure if it has to do with a setting on the callflow or a system-wide setting or what.

I'm trying to setup grandstream with KAZOO, but when making outbound call, in debug log I see: received route request with no account-id

and phone return error 604 nope nope nope

looks like when I enable options: "Add Auth Header on Re-register" & Enable 100rel it start working... Strange

could someone confirm that this options should be enabled?

does not work =(

event 'channel_create' had no account id

When I restart the phone, I was able to call, but 2 minutes later it did not allow me to call anymore...

Anyone?

do I need to add freeswitch servers to the ecallmgr document ACLs? I have all in one installation with freeswitch and kamailio in one box

mentax: according to the documentation, you need to do so docs.2600hz.com/sysadmin/doc/instal…ll_via_centos7/#setting-up-ecallmgr

As possible as you can, do not modify database documents directly, always check for sup commands first.

BadRequest: sup -necallmgr ecallmgr_maintenance allow_carrier FREESWITCHFQDN FREESWITCHIP

do I need to use it?

couse I see totally opposite things about it

somebody says it need to be done, somebody says it will brake the system

mentax: I don't know about that, I have never used it myself.

BadRequest if you run "sup -necallmgr ecallmgr_maintenance carrier_acls" do you have your freeswitch ip over there?

BadRequest: Do you know where in database I can find this carrier_acls?

mentax: I am running a AIO server, so the own server's IP address is being listed there, but apparently only Kamailio is being listed there, I can tell that because of the `{IP_ADDRESS}:5060` (note the port number) output.

mentax: I guess carriers document is within `system_config/ecallmgr`

Carriers configuration*