Inbound call routing

[Константин Носов]

Hallo!

I wan't to handle inbound calls via Kazoo.

I created gateway config in

/etc/freeswitch/gateways

gateway.xml

I check that it's connected via sofia status

I added number, that's assosiated with my account to Numbers in Gui

I created callflow for that number.

I've added carrier ip to ACL

http://take.ms/ZMv8f

and finally, when I call to my number,,, I got it rejected. Why?

Here is fs-cli output http://pastebin.com/M70xU0DA

"

1. 2014-08-21 01:54:51.923395 [DEBUG] sofia.c:8702 IP 195.128.182.62 Rejected by acl "authoritative". Falling back to Digest auth.

"

but why?I have already added it to acl, accept?

[James Aimonetti]

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

The issue appears to be that you added your carrier to the
"authoritative" list, which is the wrong ACL list.

Please use the SUP utility to manipulate the ACLs:

https://2600hz.atlassian.net/wiki/display/Dedicated/How+to+use+the+SUP+command#HowtousetheSUPcommand-ManipulatetheACLs


"authoritative" == SBC, "trusted" == carrier/devices

On 2014-08-20 15:04, Константин Носов wrote:
> Hallo!
> I wan't to handle inbound calls via Kazoo.
>
> I created gateway config in
> /etc/freeswitch/gateways
> gateway.xml
>
> I check that it's connected via sofia status
>
> I added number, that's assosiated with my account to Numbers in Gui
> I created callflow for that number.
>
> I've added carrier ip to ACL
> http://take.ms/ZMv8f
>
> and finally, when I call to my number,,, I got it rejected. Why?
> Here is fs-cli output http://pastebin.com/M70xU0DA
> "
>

> 1. 2014-08-21 01:54:51.923395 [DEBUG] sofia.c:8702 IP 195.128.182.62

> Rejected by acl "authoritative". Falling back to Digest auth.
>
> "
> but why?I have already added it to acl, accept?
>

- --
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/

iQEcBAEBAgAGBQJT9hcyAAoJENTKa+JPXCVgfSsH/01ivAShXBjxX/2lxK/v3Qi0
dd4t5BoUny7eCDmuG5zDWd42iBgkhtJuReeYumo0hsR+N5+UAPGb4z/X875XtVl4
tCXCIl9JUKzXonyFsVq9veUzLV9kgttv5AAoc5RB6FD8WihQW7u2BiOPR996YBUa
yQq4CUJNZXdUmgMY4dSeeWMfwppKuOmQhHF04KUxBqebpwiJEYUFFz6uht2Z0nun
H/Y5AAPGRfGseefDHE/hPSeStM7DSDXbdNTu4u/mBglupyAl7CNUnOJ1A8ivrM9z
y5PzkLgONtvz6G2U2gluLTbEkjMfc/cqSxf6X9Z/qNSKX+EGjGv3QlQZjwlaEI8=
=r86M
-----END PGP SIGNATURE-----

[Константин Носов]

I changed  "network-list-name" to "trusted",
and now It seems to be working.

IP 195.128.182.62 Approved by acl "trusted[]". Access Granted.

Super!

But now I have

Standard REPORTING, cause: NO_ROUTE_DESTINATION

I don't understand why. I've created callfrom from that number to mailbox, but Kazoo write me that there is no route. What could be a reason for that?

sip:...@2600hz.com

[hding]

Hi,

Is your problem solved?

I am facing the same problem. I make inbound call from carrier, I got SIP/2.0 604 Nope Nope Nope in freeswitch.

From kazoo log:

ecallmgr_fs_route:142 (<0.1139.0>) processing dialplan fetch request e31c1d2a-8f06-11e5-a404-759b71aeabf1 (call XbciUVupBY) from frees...@example.com

ts_route_req:24 (<0.15447.18>) received a request asking if trunkstore can route this call

stepswitch_inbound:39 (<0.15446.18>) unable to determine account for +1DID#: not_found

ecallmgr_fs_route:308 (<0.980.5>) received affirmative route response for request e31c1d2a-8f06-11e5-a404-759b71aeabf1

ecallmgr_fs_route:314 (<0.980.5>) node frees...@example.com accepted dialplan route response for request e31c1d2a-8f06-11e5-a404-759b71aeabf1

I did not see any Kamailio logs when inbound from Carrier call to Kazoo. Is it normal?

I had +1DID# callflow created, and Carrier ACL "trusted" in the system_config.

Please let me know what else need to be done?

Thanks,
Hao