Still struggling with easiest setup / v4

388 views
Skip to first unread message

Christian Lox

unread,
Nov 6, 2016, 9:22:48 AM11/6/16
to 2600hz-users
Hi all,

Really desperate, cannot get kazoo to work.
Any help highly appreciated. I am quite sure this might answer some future questions for new kazoo beginners.

What I want to achieve for now:

- Connect kazoo to our sip provider (sipgate trunking).
- be able to call into kazoo on one of the numbers associated with our trunk
- in step2 call out using the above trunk and maybe additional ones
   and be able to receive faxes


What I did:

- installed the needed components (rabbitmq,couchdb,freeswitch,kamailio….) and configured them according to the kazoo.configs repo.
- downloaded the 4.0.3 release and unpacked into /opt/kazoo; did a „make“, „make build-release“ and „make sup_completion“ there.
  Symlinked sup to /usr/bin and changed DEFAULT_ROOT to /opt/kazoo/_rel/kazoo
- changed Erlang cookie in configs and rel/_rel directories
- started two screen sessions: one running ./scripts/dev-start-apss.sh and the other ./scripts/dev-start-ecallmgr.sh
- added free switch node and admin account, imported prompts.
- downloaded monster-ui and additional apps, run „gulp build-prod“ and pointed apache to the „dist“ dir as webroot for monster-ui
- activated the apps like "number manager" and „callflow"
- checked for system_config/number_manager document in couchdb. Not yet there.
- added a number via number_manager like this: +49202123456789 where +49 is the international prefix for Germany, 202 is the area code and 123456789 is the phone number => no error in UI, number appears in number manager as spare number.
- BUT in callflow app I CANNOT select the number; it does not appear there
- Now also the system_config/number_manager document is there.
  If I change the reconcile_regex there the UI does not let me add any further number, no error, just nothing happens when clicking  „begin import“.
  The java script console tells me "monster.js?bust=1478438383106:311 Uncaught TypeError: Cannot use 'in' operator to search for 'message' in 404
    at Function.m.each.m.forEach 
- after having changed the reconcile_regex I ran „sup kapps_config flush“ and „sup kapps_config flush number_manager“

My reconcile rege looks like this:
"^((\\+49)?[2-9]{2,5}[1-9][0-9]{5,10})$“ which should match the German area codes and numbers. I guess.:)

Or is the problem in the reconcile_regex?

I am really willing to help with documentation issues but need help in getting things up and running before….

Thanks,
Christian

Darren Schreiber

unread,
Nov 6, 2016, 10:01:09 AM11/6/16
to 2600hz...@googlegroups.com

It sounds like you’ve take most of the correct steps. You are saying the number DOES show in number manager but DOES NOT show in callflows? The number shows in “Spare Numbers” in Number Manager? What happens when you click the Sync button?

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

Christian Lox

unread,
Nov 6, 2016, 10:14:03 AM11/6/16
to 2600hz...@googlegroups.com
Yes, exactly.
Numbers are in number manager, shown in „spare numbers“.
In call flows though it says when trying to add a number: no phone numbers (with "spare numbers“ selected).
When syncing in number manager I get a notification that it has succeeded. And the kazoo console also confirms:

(kazoo...@connect.domain.com)1> ########## fixing [account%2F02%2F5f%2F93bae5f121212121112] ##########
[account%2F02%2F5f%2F93bae5f121212121112] getting numbers from account db
[account%2F02%2F5f%2F93bae5f121212121112] getting numbers from callflow
[account%2F02%2F5f%2F93bae5f121212121112] getting numbers from trunkstore
[account%2F02%2F5f%2F93bae5f121212121112] getting numbers from numbers%2F%2B4920
[account%2F02%2F5f%2F93bae5f121212121112] start fixing numbers%2F%2B4920
[account%2F02%2F5f%2F93bae5f121212121112] done fixing numbers%2F%2B4920
########## done fixing [account%2F02%2F5f%2F93bae5f121212121112] ##########

But still no numbers in callflows.
sup crossbar_maintenance find_account_by_number
Lists the account, btw.

When trying to delete one of the number in numbermanager I get the error, number is not reconcilable?! Same error when trying to add a further number via curl!

So, after having changed the reconcile_regex I cannot add/delete any number and no number is selectable in call flows.

Darren Schreiber

unread,
Nov 6, 2016, 10:17:16 AM11/6/16
to 2600hz...@googlegroups.com

Using http://regexr.com/ I see that your RegEx does not, in fact, match your number.

 

You wrote: ^((\+49)?[2-9]{2,5}[1-9][0-9]{5,10})$

 

This means the number:

·         Starts with +49 (optional)

·         Followed by between two and five digits of 2-9

·         Followed by the digit 1-9

·         Followed by between five and ten digits

 

However, in your example number 49202123456789, the fourth digit is a 0, which is a violation of your RegEx. To test if this is really the problem, try adding 49222123456789 (note I’ve changed the fourth digit) and see if things work. If they do, the problem is your RegEx and you need to revise it to accurately portray the number scheme you are utilizing.

Christian Lox

unread,
Nov 6, 2016, 10:25:05 AM11/6/16
to 2600hz-users
Thanks for spotting this!
I can add the number you suggested via Number Manager! This is a small success! :)
BUT:
Still does not show up in Callflows. :( 
(I did sync in Number Manager after adding.)

To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-users+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.


 

-- 


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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.

Darren Schreiber

unread,
Nov 6, 2016, 10:25:53 AM11/6/16
to 2600hz...@googlegroups.com

Would you mind running:

 

sup kapps_maintenance migrate

 

I’m curious if you have a view or something missing.

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.

 

-- 


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.

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

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

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

Christian Lox

unread,
Nov 6, 2016, 10:35:20 AM11/6/16
to 2600hz-users

Ran the migrate command but still no number in callflows. 


root@connect /home/lox # sup kapps_maintenance migrate

updating dbs...

refreshing database (28/28) 'system_data'

refreshing database (27/28) 'system_config'

archiving to /tmp/system_config.json

    archived 86 docs

refreshing database (26/28) 'system_schemas'

refreshing database (25/28) 'system_auth'

refreshing database (24/28) 'system_media'

refreshing database (23/28) 'sip_auth'

refreshing database (22/28) 'accounts'

refreshing database (21/28) 'ratedeck'

refreshing database (20/28) 'global_provisioner'

refreshing database (19/28) 'faxes'

refreshing database (18/28) 'services'

refreshing database (17/28) 'offnet'

refreshing database (16/28) 'anonymous_cdrs'

refreshing database (15/28) 'port_requests'

refreshing database (14/28) 'dedicated_ips'

refreshing database (13/28) 'acdc'

refreshing database (12/28) 'oauth'

refreshing database (11/28) 'webhooks'

refreshing database (10/28) 'token_auth'

refreshing database (9/28) 'alerts'

refreshing database (8/28) 'tasks'

refreshing database (7/28) '_global_changes'

refreshing database (6/28) '_replicator'

refreshing database (5/28) '_users'

refreshing database (4/28) 'account/02/5f/93bae5f121212121112'

updated descendant count for 025f93bae5f121212121112

refreshing database (3/28) 'account/02/5f/93bae5f121212121112-201611'

refreshing database (2/28) 'numbers/+4920'

refreshing database (1/28) 'numbers/+4922'

removing depreciated databases...

no fax docs in db for fax migration account%2F02%2F5f%2F93bae5f121212121112

running media migrations...

migrating relevant settings from system_config/callflow to system_config/media

migrating relevant settings from system_config/media_mgr to system_config/media



To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-users+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

 

-- 


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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.

Darren Schreiber

unread,
Nov 6, 2016, 10:36:12 AM11/6/16
to 2600hz...@googlegroups.com

At this point I’d probably want to log into the box and take a look, as I’m not sure where to guide you further or if it’s a bug. Is that possible? If so I’ll be on IRC in a few hours if you want to ask me live there.

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.

 

-- 


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.

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

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

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

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

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

Christian Lox

unread,
Nov 6, 2016, 10:40:45 AM11/6/16
to 2600hz-users
sure would that be possible. Every help highly appreciated!
I'll check IRC then; Could you please send me your ssh public key?

To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-users+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

 

-- 


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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.

Darren Schreiber

unread,
Nov 6, 2016, 11:02:31 AM11/6/16
to 2600hz...@googlegroups.com

The issue is that the number is listed as available. It’s not actually assigned to the account.

 

  "pvt_state": "available",

  "pvt_module_name": "knm_local",

 

That should be in_service

 

How did you add the number exactly in the first place?

 

Also, you appear to be running CouchDB 2.0 which we’re not quite ready to support yet formally, I would caution the use of that. You may hit undocumented bugs that we aren’t going to fix quite yet. It is fine to do it as long as you understand the risk.

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.

 

-- 


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.

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

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

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

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

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

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

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

Christian Lox

unread,
Nov 6, 2016, 11:07:03 AM11/6/16
to 2600hz-users
ok, will use couchdb 1.6

I added via Number Manager. Just entered in the box and clicked "begin import" or similar.
Do i need to follow different steps?
And can i update the db document or how to get it "in_service"?
Maybe via curl /phone_numers/1223/activate IIRC?

THANKS!

To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-users+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

 

-- 


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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.

Darren Schreiber

unread,
Nov 6, 2016, 11:08:28 AM11/6/16
to 2600hz...@googlegroups.com

This is somewhat beyond my knowledge as I’ve actually never played directly with the phonenumbers APIs, but I do think this is a bug. I would have assumed the numbers were assigned already. I could be wrong. I don’t think this has to do with Couch (to be clear, formal supported verison of couch is Cloudant’s BigCouch)

 

Anyway... This issue isn’t about Couch, it’s about it not saying in_service

 

You can try the activate API. If it doesn’t work, you can manually change it in the database and then clear the cache on the local system.

 

If you can’t figure it out, please do file a bug at tickets.2600hz.com so we can correct this.

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.

 

-- 


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.

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

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

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

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

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

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

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

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

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

Christian Lox

unread,
Nov 6, 2016, 11:17:16 AM11/6/16
to 2600hz-users
ok, will try with a fresh 1.6 couchdb instance. BigCouch was not an option when i first tried it out, because it was nearly impossible installing it on a recent ubuntu (which is what we use) system.

Are you still looking or can i drop the db?

Will report back if i get it fixed via the api.


To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-users+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

 

-- 


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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.

Mike Montgomery

unread,
Nov 6, 2016, 11:17:17 AM11/6/16
to 2600hz...@googlegroups.com
In 3.22 you can use a sup command to add and activate numbers to accounts. I would expect 4.0 is similar.

From Stormqloud’s big book of sup commands….. (https://github.com/stormqloud/kazoo-tgbbok/blob/master/sup_commands)

sup whistle_number_manager_maintenance activate_phone_number Number
sup whistle_number_manager_maintenance activate_phone_number Number AccountId
sup whistle_number_manager_maintenance cleanup_phone_numbers
sup whistle_number_manager_maintenance cleanup_phone_numbers Account
sup whistle_number_manager_maintenance create_and_activate_phone_number Number AccountId
sup whistle_number_manager_maintenance create_phone_number Number
sup whistle_number_manager_maintenance create_phone_number Number AccountId



Best Regards,

Mike Montgomery
919 539 6133
>>>>>> - added a number via number_manager like this: +49202123456789where +49 is the international prefix for Germany, 202 is the area code and 123456789 is the phone number => no error in UI, number appears in number manager as spare number.
>>>> To unsubscribe from this group and stop receiving emails from it, send an email to2600hz-user...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>> --
>>>> 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 to2600hz-user...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>>> 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 to2600hz-user...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>>> 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 to2600hz-user...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> 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 to2600hz-user...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> 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 to2600hz-user...@googlegroups.com.

Darren Schreiber

unread,
Nov 6, 2016, 11:17:47 AM11/6/16
to 2600hz...@googlegroups.com

Well leave it on 2.0 then I’d say J

 

I am not looking, but why drop the DB? Just try changing the number state in the DB and see if it fixes the issue.

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.

 

-- 


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.

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

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

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

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

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

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

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

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

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

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

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

Darren Schreiber

unread,
Nov 6, 2016, 11:18:12 AM11/6/16
to 2600hz...@googlegroups.com
I *think* this is the same creation process he’s already invoked via the API. It’s setting the number state to available though.

Christian Lox

unread,
Nov 6, 2016, 11:53:54 AM11/6/16
to 2600hz-users
ok, changing the state to "in_service" in ocuchdb makes the numbers available in callflows. Yeah! One step further! :)

But still no phone is ringing:

I am trying to call the added (and of course callflow'ed) number from my mobile (0174...):

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:177 (<0.2973.0>) received fetch request for undefined (3ae71b43-313e-45e4-b78f-0217c7408c9f) user creds from freeswitch@connect.

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:270 (<0.2973.0>) looking up credentials of 0174...@sipconnect.sipgate.de for a password

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:563 (<0.865.0>) published request with msg id 3ae71b43-313e-45e4-b78f-0217c7408c9f for <0.2973.0>

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:40 (<0.4905.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:215 (<0.4905.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:244 (<0.4905.0>) 0174.....@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:45 (<0.4905.0>) auth failure for 0174.....@sipconnect.sipgate.de: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:90 (<0.4905.0>) sending SIP authentication error

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.4905.0>) published to targeted(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:482 (<0.865.0>) failed to find key 'Auth-Method' on API message

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:330 (<0.865.0>) failing API JSON: {"Node":"kazoo_apps@connect","Defer-Response":"true","Msg-ID":"3ae71b43-313e-45e4-b78f-0217c7408c9f","Event-Name":"authn_err","Event-Category":"directory","App-Version":"4.0.0","App-Name":"registrar"}

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:733 (<0.865.0>) ignoring invalid resp as it was deferred

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:861 (<0.865.0>) request timeout exceeded for msg id: 3ae71b43-313e-45e4-b78f-0217c7408c9f and client: <0.2973.0>

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:254 (<0.2973.0>) authn request lookup failed: timeout

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:207 (<0.2973.0>) sending authn XML to 'freeswitch@connect.': <document type="freeswitch/xml"><section name="result" description="Route Not Found"><result status="not found"/></section></document>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:177 (<0.2978.0>) received fetch request for undefined (6c8d28e3-80af-45e0-ac39-c27e66a74b15) user creds from freeswitch@connect.

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:270 (<0.2978.0>) looking up credentials of 0174.......@sipconnect.sipgate.de for a password

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_worker:563 (<0.865.0>) published request with msg id 6c8d28e3-80af-45e0-ac39-c27e66a74b15 for <0.2978.0>

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:40 (<0.4917.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:215 (<0.4917.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:244 (<0.4917.0>) 01745...@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:45 (<0.4917.0>) auth failure for 0174......@sipconnect.sipgate.de: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:90 (<0.4917.0>) sending SIP authentication error

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.4917.0>) published to targeted(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_api:482 (<0.865.0>) failed to find key 'Auth-Method' on API message

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_api:330 (<0.865.0>) failing API JSON: {"Node":"kazoo_apps@connect....","Defer-Response":"true","Msg-ID":"6c8d28e3-80af-45e0-ac39-c27e66a74b15","Event-Name":"authn_err","Event-Category":"directory","App-Version":"4.0.0","App-Name":"registrar"}

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_worker:733 (<0.865.0>) ignoring invalid resp as it was deferred

Nov  6 16:40:54 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_worker:861 (<0.865.0>) request timeout exceeded for msg id: 6c8d28e3-80af-45e0-ac39-c27e66a74b15 and client: <0.2978.0>

Nov  6 16:40:54 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:254 (<0.2978.0>) authn request lookup failed: timeout

Nov  6 16:40:54 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:207 (<0.2978.0>) sending authn XML to 'freeswitch@connect.': <document type="freeswitch/xml"><section name="result" description="Route Not Found"><result status="not found"/></section></document> 


The trunk was added via /etc/freeswitch/gateways/sipgate.xml (I know, not the preferred way of doing but obviously the only one possible with this provider).

freeswitch@connect.> sofia status

                     Name   Type                                       Data State

=================================================================================================

           sipinterface_1 profile           sip:mod_...@1.2.3.4:11000 RUNNING (0)

  sipinterface_1::sipgate gateway       sip:US...@sipconnect.sipgate.de REGED

=================================================================================================

1 profile 0 aliases


    >>>>>> To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-users+unsubscribe@googlegroups.com.

    >>>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>>>
    >>>>>>
    >>>>>> --
    >>>>>> 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+unsubscribe@googlegroups.com.

    >>>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>>
    >>>>> --
    >>>>> 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+unsubscribe@googlegroups.com.

    >>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>>
    >>>>> --
    >>>>> 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+unsubscribe@googlegroups.com.

    >>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>
    >>>> --
    >>>> 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 to2600hz-users+unsubscribe@googlegroups.com.

    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>>
    >>>> --
    >>>> 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 to2600hz-users+unsubscribe@googlegroups.com.

    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-users+unsubscribe@googlegroups.com.

    >>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-users+unsubscribe@googlegroups.com.

    >>> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-users+unsubscribe@googlegroups.com.

    >> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-users+unsubscribe@googlegroups.com.

    >> For more options, visit https://groups.google.com/d/optout.
    >
    > --
    > 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+unsubscribe@googlegroups.com.

    > For more options, visit https://groups.google.com/d/optout.
    >
    >
    > --
    > 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+unsubscribe@googlegroups.com.

    > For more options, visit https://groups.google.com/d/optout.

    --
    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+unsubscribe@googlegroups.com.

    For more options, visit https://groups.google.com/d/optout.


--
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+unsubscribe@googlegroups.com.

Darren Schreiber

unread,
Nov 6, 2016, 12:18:20 PM11/6/16
to 2600hz...@googlegroups.com

Why is the IP address of your provider not in the ACLs? It looks like it’s challenging the call?

    >>>>>> 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.
    >>>>>>
    >>>>>>
    >>>>>> --
    >>>>>> 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.
    >>>>>
    >>>>> --
    >>>>> 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.
    >>>>>
    >>>>> --
    >>>>> 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.
    >>>>
    >>>> --
    >>>> 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 to2600hz-user...@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>>
    >>>> --
    >>>> 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 to2600hz-user...@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-user...@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-user...@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-user...@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-user...@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >
    > --
    > 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.
    >
    >
    > --
    > 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.

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


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

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

Christian Lox

unread,
Nov 6, 2016, 12:22:10 PM11/6/16
to 2600hz-users
I followed https://2600hz.atlassian.net/wiki/display/docs/Connecting+via+SIP+Trunks
The "unofficial" way.
Do i need to add the acl though?
We need to configure user/pass for the trunk; thats what i meant with "not the preferred way".

2016-11-06 18:18 GMT+01:00 Darren Schreiber <dschr...@2600hz.com>:

Why is the IP address of your provider not in the ACLs? It looks like it’s challenging the call?

 

From: <2600hz...@googlegroups.com> on behalf of Christian Lox <torc...@gmail.com>
Reply-To: "2600hz...@googlegroups.com" <2600hz...@googlegroups.com>
Date: Sunday, November 6, 2016 at 8:52 AM


To: 2600hz-users <2600hz...@googlegroups.com>
Subject: Re: Still struggling with easiest setup / v4

ok, changing the state to "in_service" in ocuchdb makes the numbers available in callflows. Yeah! One step further! :)

But still no phone is ringing:

I am trying to call the added (and of course callflow'ed) number from my mobile (0174...):

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:177 (<0.2973.0>) received fetch request for undefined (3ae71b43-313e-45e4-b78f-0217c7408c9f) user creds from freeswitch@connect.

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:270 (<0.2973.0>) looking up credentials of 0174...@sipconnect.sipgate.de for a password

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:guest@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:563 (<0.865.0>) published request with msg id 3ae71b43-313e-45e4-b78f-0217c7408c9f for <0.2973.0>

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:40 (<0.4905.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:215 (<0.4905.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:244 (<0.4905.0>) 0174.....@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:45 (<0.4905.0>) auth failure for 0174.....@sipconnect.sipgate.de: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:90 (<0.4905.0>) sending SIP authentication error

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.4905.0>) published to targeted(amqp://guest:guest@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:482 (<0.865.0>) failed to find key 'Auth-Method' on API message

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:330 (<0.865.0>) failing API JSON: {"Node":"kazoo_apps@connect","Defer-Response":"true","Msg-ID":"3ae71b43-313e-45e4-b78f-0217c7408c9f","Event-Name":"authn_err","Event-Category":"directory","App-Version":"4.0.0","App-Name":"registrar"}

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:733 (<0.865.0>) ignoring invalid resp as it was deferred

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:861 (<0.865.0>) request timeout exceeded for msg id: 3ae71b43-313e-45e4-b78f-0217c7408c9f and client: <0.2973.0>

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:254 (<0.2973.0>) authn request lookup failed: timeout

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:207 (<0.2973.0>) sending authn XML to 'freeswitch@connect.': <document type="freeswitch/xml"><section name="result" description="Route Not Found"><result status="not found"/></section></document>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:177 (<0.2978.0>) received fetch request for undefined (6c8d28e3-80af-45e0-ac39-c27e66a74b15) user creds from freeswitch@connect.

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:270 (<0.2978.0>) looking up credentials of 0174.......@sipconnect.sipgate.de for a password

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:guest@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_worker:563 (<0.865.0>) published request with msg id 6c8d28e3-80af-45e0-ac39-c27e66a74b15 for <0.2978.0>

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:40 (<0.4917.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:215 (<0.4917.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:244 (<0.4917.0>) 01745121880@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:45 (<0.4917.0>) auth failure for 0174......@sipconnect.sipgate.de: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:90 (<0.4917.0>) sending SIP authentication error

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.4917.0>) published to targeted(amqp://guest:guest@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

    >>>>>> To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-users+unsubscribe@googlegroups.com.


    >>>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>>>
    >>>>>>
    >>>>>> --
    >>>>>> 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+unsubscribe@googlegroups.com.


    >>>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>>
    >>>>> --
    >>>>> 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+unsubscribe@googlegroups.com.


    >>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>>
    >>>>> --
    >>>>> 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+unsubscribe@googlegroups.com.


    >>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>
    >>>> --
    >>>> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>>
    >>>> --
    >>>> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >
    > --
    > 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+unsubscribe@googlegroups.com.


    > For more options, visit https://groups.google.com/d/optout.
    >
    >
    > --
    > 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+unsubscribe@googlegroups.com.


    > For more options, visit https://groups.google.com/d/optout.

    --
    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+unsubscribe@googlegroups.com.


    For more options, visit https://groups.google.com/d/optout.


--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.

Darren Schreiber

unread,
Nov 6, 2016, 12:22:49 PM11/6/16
to 2600hz...@googlegroups.com

Yes. You still need to add the ACLs for inbound to actually work. All that document does (aside from cause problems) is allow the remote party to know your IP address. It doesn’t actually authenticate them in the Kazoo system, that is still done by ACL.

 

 

From: <2600hz...@googlegroups.com> on behalf of Christian Lox <torc...@gmail.com>
Reply-To: "2600hz...@googlegroups.com" <2600hz...@googlegroups.com>
Date: Sunday, November 6, 2016 at 9:21 AM
To: 2600hz-users <2600hz...@googlegroups.com>
Subject: Re: Still struggling with easiest setup / v4

 

I followed https://2600hz.atlassian.net/wiki/display/docs/Connecting+via+SIP+Trunks
The "unofficial" way.
Do i need to add the acl though?
We need to configure user/pass for the trunk; thats what i meant with "not the preferred way".

2016-11-06 18:18 GMT+01:00 Darren Schreiber <dschr...@2600hz.com>:

Why is the IP address of your provider not in the ACLs? It looks like it’s challenging the call?

 

From: <2600hz...@googlegroups.com> on behalf of Christian Lox <torc...@gmail.com>
Reply-To: "2600hz...@googlegroups.com" <2600hz...@googlegroups.com>
Date: Sunday, November 6, 2016 at 8:52 AM


To: 2600hz-users <2600hz...@googlegroups.com>
Subject: Re: Still struggling with easiest setup / v4

ok, changing the state to "in_service" in ocuchdb makes the numbers available in callflows. Yeah! One step further! :)

But still no phone is ringing:

I am trying to call the added (and of course callflow'ed) number from my mobile (0174...):

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:177 (<0.2973.0>) received fetch request for undefined (3ae71b43-313e-45e4-b78f-0217c7408c9f) user creds from freeswitch@connect.

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:270 (<0.2973.0>) looking up credentials of 0174...@sipconnect.sipgate.de for a password

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:563 (<0.865.0>) published request with msg id 3ae71b43-313e-45e4-b78f-0217c7408c9f for <0.2973.0>

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:40 (<0.4905.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:215 (<0.4905.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:244 (<0.4905.0>) 0174.....@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:45 (<0.4905.0>) auth failure for 0174.....@sipconnect.sipgate.de: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:90 (<0.4905.0>) sending SIP authentication error

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.4905.0>) published to targeted(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:482 (<0.865.0>) failed to find key 'Auth-Method' on API message

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:330 (<0.865.0>) failing API JSON: {"Node":"kazoo_apps@connect","Defer-Response":"true","Msg-ID":"3ae71b43-313e-45e4-b78f-0217c7408c9f","Event-Name":"authn_err","Event-Category":"directory","App-Version":"4.0.0","App-Name":"registrar"}

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:733 (<0.865.0>) ignoring invalid resp as it was deferred

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:861 (<0.865.0>) request timeout exceeded for msg id: 3ae71b43-313e-45e4-b78f-0217c7408c9f and client: <0.2973.0>

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:254 (<0.2973.0>) authn request lookup failed: timeout

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:207 (<0.2973.0>) sending authn XML to 'freeswitch@connect.': <document type="freeswitch/xml"><section name="result" description="Route Not Found"><result status="not found"/></section></document>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:177 (<0.2978.0>) received fetch request for undefined (6c8d28e3-80af-45e0-ac39-c27e66a74b15) user creds from freeswitch@connect.

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:270 (<0.2978.0>) looking up credentials of 0174.......@sipconnect.sipgate.de for a password

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_worker:563 (<0.865.0>) published request with msg id 6c8d28e3-80af-45e0-ac39-c27e66a74b15 for <0.2978.0>

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:40 (<0.4917.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:215 (<0.4917.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:244 (<0.4917.0>) 01745...@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:45 (<0.4917.0>) auth failure for 0174......@sipconnect.sipgate.de: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:90 (<0.4917.0>) sending SIP authentication error

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.4917.0>) published to targeted(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

    >>>>>> 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.
    >>>>>>
    >>>>>>
    >>>>>> --
    >>>>>> 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.
    >>>>>
    >>>>> --
    >>>>> 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.
    >>>>>
    >>>>> --
    >>>>> 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.
    >>>>
    >>>> --
    >>>> 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 to2600hz-user...@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>>
    >>>> --
    >>>> 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 to2600hz-user...@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-user...@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-user...@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-user...@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-user...@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >
    > --
    > 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.
    >
    >
    > --
    > 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.

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


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

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

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

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

Christian Lox

unread,
Nov 6, 2016, 4:22:03 PM11/6/16
to 2600hz-users
ok, ACLs updated, but still no phone ringing.... (see above)

sup -necallmgr ecallmgr_maintenance allow_carrier CarrierName CarrierIP
does not seem to work? At least there showed nothing up in acl_summary after having issued this and also an reloadacl in fs_cli did not show the CarrierIP.

After inserting the CarrierIP(s) as described in https://2600hz.atlassian.net/wiki/display/Dedicated/Inbound+Calls+Fail they showed up and call goes through.
Is this the correct method of inserting the ACL?

If I interpret the debug log correctly there is still an issue with the number:
Kazoo recognizes the account and the according callflow and tries to bridge the call but fails:

Nov  6 18:18:31  connect 2600hz[9660]: added leg c3fa5e7e-3b8b-43e1-95b8-42549f7b370f to call

Nov  6 18:18:31 connect 2600hz[9660]: |c3fa5e7e-3b8b-43e1-95b8-42549f7b370f|ecallmgr_fs_authz:34 (<0.1673.0>) channel is authorized

Nov  6 18:18:31 connect 2600hz[9660]:  published to callevt(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key call.LEG_CREATED.6c7f9011690e8718024a800f1d413e5d%40sipconnect%2Esipgate%2Ede) via <0.1037.0>

Nov  6 18:18:31 connect 2600hz[9660]: |00000000000|ecallmgr_fs_channels:448 (<0.1316.0>) removed 1 channel(s) with id c3fa5e7e-3b8b-43e1-95b8-42549f7b370f on freeswitch@connect..

Nov  6 18:18:31 connect 2600hz[9660]: |6c7f9011690e8718...@sipconnect.sipgate.de|ecallmgr_call_events:913 (<0.1640.0>) suppressing bridge execute complete in favour the kazoo masquerade of this event

Nov  6 18:18:31 connect 2600hz[9660]: |6c7f9011690e8718...@sipconnect.sipgate.de|ecallmgr_call_events:710 (<0.1640.0>) publishing call event channel_execute_complete 'bridge()' result: unallocated_number

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|kapps_call_command:2536 (<0.2605.0>) bridge channel execute completed with result UNALLOCATED_NUMBER(fail)

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|cf_util:513 (<0.2605.0>) attempting to find failure branch for sip:404:UNALLOCATED_NUMBER

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|cf_exe:350 (<0.2594.0>) attempted 'undefined' child UNALLOCATED_NUMBER

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|cf_exe:350 (<0.2594.0>) attempted 'undefined' child sip:404

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|cf_exe:400 (<0.2594.0>) continuing to child '_'

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|cf_exe:404 (<0.2594.0>) wildcard child does not exist, we are lost...hanging up



What might be causing this?


2016-11-06 18:22 GMT+01:00 Darren Schreiber <dschr...@2600hz.com>:

Yes. You still need to add the ACLs for inbound to actually work. All that document does (aside from cause problems) is allow the remote party to know your IP address. It doesn’t actually authenticate them in the Kazoo system, that is still done by ACL.

 

 

From: <2600hz...@googlegroups.com> on behalf of Christian Lox <torc...@gmail.com>
Reply-To: "2600hz...@googlegroups.com" <2600hz...@googlegroups.com>
Date: Sunday, November 6, 2016 at 9:21 AM
To: 2600hz-users <2600hz...@googlegroups.com>


Subject: Re: Still struggling with easiest setup / v4

 

I followed https://2600hz.atlassian.net/wiki/display/docs/Connecting+via+SIP+Trunks
The "unofficial" way.
Do i need to add the acl though?
We need to configure user/pass for the trunk; thats what i meant with "not the preferred way".

2016-11-06 18:18 GMT+01:00 Darren Schreiber <dschr...@2600hz.com>:

Why is the IP address of your provider not in the ACLs? It looks like it’s challenging the call?

 

From: <2600hz...@googlegroups.com> on behalf of Christian Lox <torc...@gmail.com>
Reply-To: "2600hz...@googlegroups.com" <2600hz...@googlegroups.com>
Date: Sunday, November 6, 2016 at 8:52 AM


To: 2600hz-users <2600hz...@googlegroups.com>
Subject: Re: Still struggling with easiest setup / v4

ok, changing the state to "in_service" in ocuchdb makes the numbers available in callflows. Yeah! One step further! :)

But still no phone is ringing:

I am trying to call the added (and of course callflow'ed) number from my mobile (0174...):

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:177 (<0.2973.0>) received fetch request for undefined (3ae71b43-313e-45e4-b78f-0217c7408c9f) user creds from freeswitch@connect.

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:270 (<0.2973.0>) looking up credentials of 0174...@sipconnect.sipgate.de for a password

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:guest@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:563 (<0.865.0>) published request with msg id 3ae71b43-313e-45e4-b78f-0217c7408c9f for <0.2973.0>

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:40 (<0.4905.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:215 (<0.4905.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:244 (<0.4905.0>) 0174.....@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:45 (<0.4905.0>) auth failure for 0174.....@sipconnect.sipgate.de: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:90 (<0.4905.0>) sending SIP authentication error

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.4905.0>) published to targeted(amqp://guest:guest@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:482 (<0.865.0>) failed to find key 'Auth-Method' on API message

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:330 (<0.865.0>) failing API JSON: {"Node":"kazoo_apps@connect","Defer-Response":"true","Msg-ID":"3ae71b43-313e-45e4-b78f-0217c7408c9f","Event-Name":"authn_err","Event-Category":"directory","App-Version":"4.0.0","App-Name":"registrar"}

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:733 (<0.865.0>) ignoring invalid resp as it was deferred

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:861 (<0.865.0>) request timeout exceeded for msg id: 3ae71b43-313e-45e4-b78f-0217c7408c9f and client: <0.2973.0>

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:254 (<0.2973.0>) authn request lookup failed: timeout

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:207 (<0.2973.0>) sending authn XML to 'freeswitch@connect.': <document type="freeswitch/xml"><section name="result" description="Route Not Found"><result status="not found"/></section></document>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:177 (<0.2978.0>) received fetch request for undefined (6c8d28e3-80af-45e0-ac39-c27e66a74b15) user creds from freeswitch@connect.

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:270 (<0.2978.0>) looking up credentials of 0174.......@sipconnect.sipgate.de for a password

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:guest@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_worker:563 (<0.865.0>) published request with msg id 6c8d28e3-80af-45e0-ac39-c27e66a74b15 for <0.2978.0>

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:40 (<0.4917.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:215 (<0.4917.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:244 (<0.4917.0>) 01745121880@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:45 (<0.4917.0>) auth failure for 0174......@sipconnect.sipgate.de: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:90 (<0.4917.0>) sending SIP authentication error

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.4917.0>) published to targeted(amqp://guest:guest@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

    >>>>>> To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-users+unsubscribe@googlegroups.com.


    >>>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>>>
    >>>>>>
    >>>>>> --
    >>>>>> 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+unsubscribe@googlegroups.com.


    >>>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>>
    >>>>> --
    >>>>> 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+unsubscribe@googlegroups.com.


    >>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>>
    >>>>> --
    >>>>> 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+unsubscribe@googlegroups.com.


    >>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>
    >>>> --
    >>>> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>>
    >>>> --
    >>>> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >
    > --
    > 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+unsubscribe@googlegroups.com.


    > For more options, visit https://groups.google.com/d/optout.
    >
    >
    > --
    > 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+unsubscribe@googlegroups.com.


    > For more options, visit https://groups.google.com/d/optout.

    --
    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+unsubscribe@googlegroups.com.


    For more options, visit https://groups.google.com/d/optout.


--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.

Darren Schreiber

unread,
Nov 6, 2016, 5:00:51 PM11/6/16
to 2600hz...@googlegroups.com

The ACL thing is annoying and maybe broken? That’s an age-old issue we simply haven’t had time to fix yet. I think it updates the DB but then doesn’t flush the cache so still shows the old list. Honestly it’s buggy as hell and I don’t trust it anymore – use the DB like you said.

 

As for why your call is now failing, I think your ACL is right now (you have “channel is authorized”, yaaay)

 

However the second part which is now erroring out does not appear to be the same issue. Your inbound call is working. It seems you’re forwarding the call outbound (to a mobile phone? Or…) The log snippet isn’t the full log and/or not in debug mode, so I can’t tell. But basically this line:

 

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|kapps_call_command:2536 (<0.2605.0>) bridge channel execute completed with result UNALLOCATED_NUMBER(fail)

 

Means now FreeSWITCH received the call, got instructions on how to bridge it to the next destination successfully, but failed to do so because whoever it bridged to responded with a “404” or similar error. Thus, the number being dialed wasn’t understood. You’d want to go grab the FreeSWITCH logs now to see what happened next.

 

You’re close.

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:563 (<0.865.0>) published request with msg id 3ae71b43-313e-45e4-b78f-0217c7408c9f for <0.2973.0>

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:40 (<0.4905.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:215 (<0.4905.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:244 (<0.4905.0>) 0174.....@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:45 (<0.4905.0>) auth failure for 0174.....@sipconnect.sipgate.de: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:90 (<0.4905.0>) sending SIP authentication error

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.4905.0>) published to targeted(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:482 (<0.865.0>) failed to find key 'Auth-Method' on API message

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:330 (<0.865.0>) failing API JSON: {"Node":"kazoo_apps@connect","Defer-Response":"true","Msg-ID":"3ae71b43-313e-45e4-b78f-0217c7408c9f","Event-Name":"authn_err","Event-Category":"directory","App-Version":"4.0.0","App-Name":"registrar"}

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:733 (<0.865.0>) ignoring invalid resp as it was deferred

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:861 (<0.865.0>) request timeout exceeded for msg id: 3ae71b43-313e-45e4-b78f-0217c7408c9f and client: <0.2973.0>

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:254 (<0.2973.0>) authn request lookup failed: timeout

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:207 (<0.2973.0>) sending authn XML to 'freeswitch@connect.': <document type="freeswitch/xml"><section name="result" description="Route Not Found"><result status="not found"/></section></document>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:177 (<0.2978.0>) received fetch request for undefined (6c8d28e3-80af-45e0-ac39-c27e66a74b15) user creds from freeswitch@connect.

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:270 (<0.2978.0>) looking up credentials of 0174.......@sipconnect.sipgate.de for a password

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_worker:563 (<0.865.0>) published request with msg id 6c8d28e3-80af-45e0-ac39-c27e66a74b15 for <0.2978.0>

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:40 (<0.4917.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:215 (<0.4917.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:244 (<0.4917.0>) 01745...@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:45 (<0.4917.0>) auth failure for 0174......@sipconnect.sipgate.de: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:90 (<0.4917.0>) sending SIP authentication error

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.4917.0>) published to targeted(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

    >>>>>> 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.
    >>>>>>
    >>>>>>
    >>>>>> --
    >>>>>> 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.
    >>>>>
    >>>>> --
    >>>>> 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.
    >>>>>
    >>>>> --
    >>>>> 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.
    >>>>
    >>>> --
    >>>> 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 to2600hz-user...@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>>
    >>>> --
    >>>> 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 to2600hz-user...@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-user...@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-user...@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-user...@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-user...@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >
    > --
    > 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.
    >
    >
    > --
    > 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.

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


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

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

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

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

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

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

Christian Lox

unread,
Nov 7, 2016, 11:30:52 AM11/7/16
to 2600hz-users
I found out that the sip phone (a very old snom 360) sends the 404 back when the option "support broken registrar" is not active.
When active the phone rings! :)
I cannot see any difference in the INVITE message though; not sure if it fixes this  kind of message anyway.

Can I ignore this and be happy it works now?
Or should I change something on kazoo side instead of using "support broken registrart"? 

2016-11-06 23:00 GMT+01:00 Darren Schreiber <dschr...@2600hz.com>:

The ACL thing is annoying and maybe broken? That’s an age-old issue we simply haven’t had time to fix yet. I think it updates the DB but then doesn’t flush the cache so still shows the old list. Honestly it’s buggy as hell and I don’t trust it anymore – use the DB like you said.

 

As for why your call is now failing, I think your ACL is right now (you have “channel is authorized”, yaaay)

 

However the second part which is now erroring out does not appear to be the same issue. Your inbound call is working. It seems you’re forwarding the call outbound (to a mobile phone? Or…) The log snippet isn’t the full log and/or not in debug mode, so I can’t tell. But basically this line:

 

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718024a800f1d413e...@sipconnect.sipgate.de|kapps_call_command:2536 (<0.2605.0>) bridge channel execute completed with result UNALLOCATED_NUMBER(fail)

 

Means now FreeSWITCH received the call, got instructions on how to bridge it to the next destination successfully, but failed to do so because whoever it bridged to responded with a “404” or similar error. Thus, the number being dialed wasn’t understood. You’d want to go grab the FreeSWITCH logs now to see what happened next.

 

You’re close.

 

 

 

From: <2600hz...@googlegroups.com> on behalf of Christian Lox <torc...@gmail.com>
Reply-To: "2600hz...@googlegroups.com" <2600hz...@googlegroups.com>
Date: Sunday, November 6, 2016 at 1:21 PM


To: 2600hz-users <2600hz...@googlegroups.com>
Subject: Re: Still struggling with easiest setup / v4

ok, ACLs updated, but still no phone ringing.... (see above)

 

sup -necallmgr ecallmgr_maintenance allow_carrier CarrierName CarrierIP

does not seem to work? At least there showed nothing up in acl_summary after having issued this and also an reloadacl in fs_cli did not show the CarrierIP.

After inserting the CarrierIP(s) as described in https://2600hz.atlassian.net/wiki/display/Dedicated/Inbound+Calls+Fail they showed up and call goes through.
Is this the correct method of inserting the ACL?

If I interpret the debug log correctly there is still an issue with the number:

Kazoo recognizes the account and the according callflow and tries to bridge the call but fails:

Nov  6 18:18:31  connect 2600hz[9660]: added leg c3fa5e7e-3b8b-43e1-95b8-42549f7b370f to call

Nov  6 18:18:31 connect 2600hz[9660]: |c3fa5e7e-3b8b-43e1-95b8-42549f7b370f|ecallmgr_fs_authz:34 (<0.1673.0>) channel is authorized

Nov  6 18:18:31 connect 2600hz[9660]:  published to callevt(amqp://guest:guest@127.0.0.1:5672) exchange (routing key call.LEG_CREATED.6c7f9011690e8718024a800f1d413e5d%40sipconnect%2Esipgate%2Ede) via <0.1037.0>

Nov  6 18:18:31 connect 2600hz[9660]: |00000000000|ecallmgr_fs_channels:448 (<0.1316.0>) removed 1 channel(s) with id c3fa5e7e-3b8b-43e1-95b8-42549f7b370f on freeswitch@connect..

Nov  6 18:18:31 connect 2600hz[9660]: |6c7f9011690e8718024a800f1d413e...@sipconnect.sipgate.de|ecallmgr_call_events:913 (<0.1640.0>) suppressing bridge execute complete in favour the kazoo masquerade of this event

Nov  6 18:18:31 connect 2600hz[9660]: |6c7f9011690e8718024a800f1d413e...@sipconnect.sipgate.de|ecallmgr_call_events:710 (<0.1640.0>) publishing call event channel_execute_complete 'bridge()' result: unallocated_number

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718024a800f1d413e...@sipconnect.sipgate.de|kapps_call_command:2536 (<0.2605.0>) bridge channel execute completed with result UNALLOCATED_NUMBER(fail)

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718024a800f1d413e...@sipconnect.sipgate.de|cf_util:513 (<0.2605.0>) attempting to find failure branch for sip:404:UNALLOCATED_NUMBER

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718024a800f1d413e...@sipconnect.sipgate.de|cf_exe:350 (<0.2594.0>) attempted 'undefined' child UNALLOCATED_NUMBER

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718024a800f1d413e...@sipconnect.sipgate.de|cf_exe:350 (<0.2594.0>) attempted 'undefined' child sip:404

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718024a800f1d413e...@sipconnect.sipgate.de|cf_exe:400 (<0.2594.0>) continuing to child '_'

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718024a800f1d413e...@sipconnect.sipgate.de|cf_exe:404 (<0.2594.0>) wildcard child does not exist, we are lost...hanging up

 

 

What might be causing this?

2016-11-06 18:22 GMT+01:00 Darren Schreiber <dschr...@2600hz.com>:

Yes. You still need to add the ACLs for inbound to actually work. All that document does (aside from cause problems) is allow the remote party to know your IP address. It doesn’t actually authenticate them in the Kazoo system, that is still done by ACL.

 

 

From: <2600hz...@googlegroups.com> on behalf of Christian Lox <torc...@gmail.com>
Reply-To: "2600hz...@googlegroups.com" <2600hz...@googlegroups.com>
Date: Sunday, November 6, 2016 at 9:21 AM
To: 2600hz-users <2600hz...@googlegroups.com>


Subject: Re: Still struggling with easiest setup / v4

 

I followed https://2600hz.atlassian.net/wiki/display/docs/Connecting+via+SIP+Trunks
The "unofficial" way.
Do i need to add the acl though?
We need to configure user/pass for the trunk; thats what i meant with "not the preferred way".

2016-11-06 18:18 GMT+01:00 Darren Schreiber <dschr...@2600hz.com>:

Why is the IP address of your provider not in the ACLs? It looks like it’s challenging the call?

 

From: <2600hz...@googlegroups.com> on behalf of Christian Lox <torc...@gmail.com>
Reply-To: "2600hz...@googlegroups.com" <2600hz...@googlegroups.com>
Date: Sunday, November 6, 2016 at 8:52 AM


To: 2600hz-users <2600hz...@googlegroups.com>
Subject: Re: Still struggling with easiest setup / v4

ok, changing the state to "in_service" in ocuchdb makes the numbers available in callflows. Yeah! One step further! :)

But still no phone is ringing:

I am trying to call the added (and of course callflow'ed) number from my mobile (0174...):

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:177 (<0.2973.0>) received fetch request for undefined (3ae71b43-313e-45e4-b78f-0217c7408c9f) user creds from freeswitch@connect.

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:270 (<0.2973.0>) looking up credentials of 0174...@sipconnect.sipgate.de for a password

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:guest@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:563 (<0.865.0>) published request with msg id 3ae71b43-313e-45e4-b78f-0217c7408c9f for <0.2973.0>

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:40 (<0.4905.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:215 (<0.4905.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:244 (<0.4905.0>) 0174.....@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:45 (<0.4905.0>) auth failure for 0174.....@sipconnect.sipgate.de: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:90 (<0.4905.0>) sending SIP authentication error

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.4905.0>) published to targeted(amqp://guest:guest@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:482 (<0.865.0>) failed to find key 'Auth-Method' on API message

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:330 (<0.865.0>) failing API JSON: {"Node":"kazoo_apps@connect","Defer-Response":"true","Msg-ID":"3ae71b43-313e-45e4-b78f-0217c7408c9f","Event-Name":"authn_err","Event-Category":"directory","App-Version":"4.0.0","App-Name":"registrar"}

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:733 (<0.865.0>) ignoring invalid resp as it was deferred

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:861 (<0.865.0>) request timeout exceeded for msg id: 3ae71b43-313e-45e4-b78f-0217c7408c9f and client: <0.2973.0>

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:254 (<0.2973.0>) authn request lookup failed: timeout

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:207 (<0.2973.0>) sending authn XML to 'freeswitch@connect.': <document type="freeswitch/xml"><section name="result" description="Route Not Found"><result status="not found"/></section></document>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:177 (<0.2978.0>) received fetch request for undefined (6c8d28e3-80af-45e0-ac39-c27e66a74b15) user creds from freeswitch@connect.

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:270 (<0.2978.0>) looking up credentials of 0174.......@sipconnect.sipgate.de for a password

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:guest@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_worker:563 (<0.865.0>) published request with msg id 6c8d28e3-80af-45e0-ac39-c27e66a74b15 for <0.2978.0>

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:40 (<0.4917.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:215 (<0.4917.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:244 (<0.4917.0>) 01745121880@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:45 (<0.4917.0>) auth failure for 0174......@sipconnect.sipgate.de: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:90 (<0.4917.0>) sending SIP authentication error

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.4917.0>) published to targeted(amqp://guest:guest@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

    >>>>>> To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-users+unsubscribe@googlegroups.com.


    >>>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>>>
    >>>>>>
    >>>>>> --
    >>>>>> 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+unsubscribe@googlegroups.com.


    >>>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>>
    >>>>> --
    >>>>> 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+unsubscribe@googlegroups.com.


    >>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>>
    >>>>> --
    >>>>> 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+unsubscribe@googlegroups.com.


    >>>>> For more options, visit https://groups.google.com/d/optout.
    >>>>
    >>>> --
    >>>> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>>
    >>>> --
    >>>> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-users+unsubscribe@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >
    > --
    > 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+unsubscribe@googlegroups.com.


    > For more options, visit https://groups.google.com/d/optout.
    >
    >
    > --
    > 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+unsubscribe@googlegroups.com.


    > For more options, visit https://groups.google.com/d/optout.

    --
    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+unsubscribe@googlegroups.com.


    For more options, visit https://groups.google.com/d/optout.


--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.

Darren Schreiber

unread,
Nov 7, 2016, 11:31:34 AM11/7/16
to 2600hz...@googlegroups.com

Yes that’s the SNOM doesn’t like our contact string, known issue still.

 

You can ignore it. What you did is correct.

 

From: <2600hz...@googlegroups.com> on behalf of Christian Lox <torc...@gmail.com>
Reply-To: "2600hz...@googlegroups.com" <2600hz...@googlegroups.com>
Date: Monday, November 7, 2016 at 8:14 AM
To: 2600hz-users <2600hz...@googlegroups.com>
Subject: Re: Still struggling with easiest setup / v4

 

I found out that the sip phone (a very old snom 360) sends the 404 back when the option "support broken registrar" is not active.


When active the phone rings! :)
I cannot see any difference in the INVITE message though; not sure if it fixes this  kind of message anyway.


Can I ignore this and be happy it works now?
Or should I change something on kazoo side instead of using "support broken registrart"? 

2016-11-06 23:00 GMT+01:00 Darren Schreiber <dschr...@2600hz.com>:

The ACL thing is annoying and maybe broken? That’s an age-old issue we simply haven’t had time to fix yet. I think it updates the DB but then doesn’t flush the cache so still shows the old list. Honestly it’s buggy as hell and I don’t trust it anymore – use the DB like you said.

 

As for why your call is now failing, I think your ACL is right now (you have “channel is authorized”, yaaay)

 

However the second part which is now erroring out does not appear to be the same issue. Your inbound call is working. It seems you’re forwarding the call outbound (to a mobile phone? Or…) The log snippet isn’t the full log and/or not in debug mode, so I can’t tell. But basically this line:

 

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|kapps_call_command:2536 (<0.2605.0>) bridge channel execute completed with result UNALLOCATED_NUMBER(fail)

 

Means now FreeSWITCH received the call, got instructions on how to bridge it to the next destination successfully, but failed to do so because whoever it bridged to responded with a “404” or similar error. Thus, the number being dialed wasn’t understood. You’d want to go grab the FreeSWITCH logs now to see what happened next.

 

You’re close.

 

 

 

From: <2600hz...@googlegroups.com> on behalf of Christian Lox <torc...@gmail.com>
Reply-To: "2600hz...@googlegroups.com" <2600hz...@googlegroups.com>
Date: Sunday, November 6, 2016 at 1:21 PM


To: 2600hz-users <2600hz...@googlegroups.com>
Subject: Re: Still struggling with easiest setup / v4

ok, ACLs updated, but still no phone ringing.... (see above)

 

sup -necallmgr ecallmgr_maintenance allow_carrier CarrierName CarrierIP

does not seem to work? At least there showed nothing up in acl_summary after having issued this and also an reloadacl in fs_cli did not show the CarrierIP.

After inserting the CarrierIP(s) as described in https://2600hz.atlassian.net/wiki/display/Dedicated/Inbound+Calls+Fail they showed up and call goes through.
Is this the correct method of inserting the ACL?

If I interpret the debug log correctly there is still an issue with the number:

Kazoo recognizes the account and the according callflow and tries to bridge the call but fails:

Nov  6 18:18:31  connect 2600hz[9660]: added leg c3fa5e7e-3b8b-43e1-95b8-42549f7b370f to call

Nov  6 18:18:31 connect 2600hz[9660]: |c3fa5e7e-3b8b-43e1-95b8-42549f7b370f|ecallmgr_fs_authz:34 (<0.1673.0>) channel is authorized

Nov  6 18:18:31 connect 2600hz[9660]:  published to callevt(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key call.LEG_CREATED.6c7f9011690e8718024a800f1d413e5d%40sipconnect%2Esipgate%2Ede) via <0.1037.0>

Nov  6 18:18:31 connect 2600hz[9660]: |00000000000|ecallmgr_fs_channels:448 (<0.1316.0>) removed 1 channel(s) with id c3fa5e7e-3b8b-43e1-95b8-42549f7b370f on freeswitch@connect..

Nov  6 18:18:31 connect 2600hz[9660]: |6c7f9011690e8718...@sipconnect.sipgate.de|ecallmgr_call_events:913 (<0.1640.0>) suppressing bridge execute complete in favour the kazoo masquerade of this event

Nov  6 18:18:31 connect 2600hz[9660]: |6c7f9011690e8718...@sipconnect.sipgate.de|ecallmgr_call_events:710 (<0.1640.0>) publishing call event channel_execute_complete 'bridge()' result: unallocated_number

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|kapps_call_command:2536 (<0.2605.0>) bridge channel execute completed with result UNALLOCATED_NUMBER(fail)

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|cf_util:513 (<0.2605.0>) attempting to find failure branch for sip:404:UNALLOCATED_NUMBER

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|cf_exe:350 (<0.2594.0>) attempted 'undefined' child UNALLOCATED_NUMBER

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|cf_exe:350 (<0.2594.0>) attempted 'undefined' child sip:404

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|cf_exe:400 (<0.2594.0>) continuing to child '_'

Nov  6 18:18:31 connect 2600hz[9530]: |6c7f9011690e8718...@sipconnect.sipgate.de|cf_exe:404 (<0.2594.0>) wildcard child does not exist, we are lost...hanging up

 

 

What might be causing this?

2016-11-06 18:22 GMT+01:00 Darren Schreiber <dschr...@2600hz.com>:

Yes. You still need to add the ACLs for inbound to actually work. All that document does (aside from cause problems) is allow the remote party to know your IP address. It doesn’t actually authenticate them in the Kazoo system, that is still done by ACL.

 

 

From: <2600hz...@googlegroups.com> on behalf of Christian Lox <torc...@gmail.com>
Reply-To: "2600hz...@googlegroups.com" <2600hz...@googlegroups.com>
Date: Sunday, November 6, 2016 at 9:21 AM
To: 2600hz-users <2600hz...@googlegroups.com>


Subject: Re: Still struggling with easiest setup / v4

 

I followed https://2600hz.atlassian.net/wiki/display/docs/Connecting+via+SIP+Trunks
The "unofficial" way.
Do i need to add the acl though?
We need to configure user/pass for the trunk; thats what i meant with "not the preferred way".

2016-11-06 18:18 GMT+01:00 Darren Schreiber <dschr...@2600hz.com>:

Why is the IP address of your provider not in the ACLs? It looks like it’s challenging the call?

 

From: <2600hz...@googlegroups.com> on behalf of Christian Lox <torc...@gmail.com>
Reply-To: "2600hz...@googlegroups.com" <2600hz...@googlegroups.com>
Date: Sunday, November 6, 2016 at 8:52 AM


To: 2600hz-users <2600hz...@googlegroups.com>
Subject: Re: Still struggling with easiest setup / v4

ok, changing the state to "in_service" in ocuchdb makes the numbers available in callflows. Yeah! One step further! :)

But still no phone is ringing:

I am trying to call the added (and of course callflow'ed) number from my mobile (0174...):

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:177 (<0.2973.0>) received fetch request for undefined (3ae71b43-313e-45e4-b78f-0217c7408c9f) user creds from freeswitch@connect.

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:270 (<0.2973.0>) looking up credentials of 0174...@sipconnect.sipgate.de for a password

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:563 (<0.865.0>) published request with msg id 3ae71b43-313e-45e4-b78f-0217c7408c9f for <0.2973.0>

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:40 (<0.4905.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:215 (<0.4905.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:244 (<0.4905.0>) 0174.....@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:45 (<0.4905.0>) auth failure for 0174.....@sipconnect.sipgate.de: not_found

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|reg_authn_req:90 (<0.4905.0>) sending SIP authentication error

Nov  6 16:40:50 connect 2600hz[12933]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_channel:159 (<0.4905.0>) published to targeted(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:482 (<0.865.0>) failed to find key 'Auth-Method' on API message

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_api:330 (<0.865.0>) failing API JSON: {"Node":"kazoo_apps@connect","Defer-Response":"true","Msg-ID":"3ae71b43-313e-45e4-b78f-0217c7408c9f","Event-Name":"authn_err","Event-Category":"directory","App-Version":"4.0.0","App-Name":"registrar"}

Nov  6 16:40:50 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:733 (<0.865.0>) ignoring invalid resp as it was deferred

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|kz_amqp_worker:861 (<0.865.0>) request timeout exceeded for msg id: 3ae71b43-313e-45e4-b78f-0217c7408c9f and client: <0.2973.0>

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:254 (<0.2973.0>) authn request lookup failed: timeout

Nov  6 16:40:52 connect 2600hz[12999]: |3ae71b43-313e-45e4-b78f-0217c7408c9f|ecallmgr_fs_authn:207 (<0.2973.0>) sending authn XML to 'freeswitch@connect.': <document type="freeswitch/xml"><section name="result" description="Route Not Found"><result status="not found"/></section></document>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:177 (<0.2978.0>) received fetch request for undefined (6c8d28e3-80af-45e0-ac39-c27e66a74b15) user creds from freeswitch@connect.

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|ecallmgr_fs_authn:270 (<0.2978.0>) looking up credentials of 0174.......@sipconnect.sipgate.de for a password

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.865.0>) published to callmgr(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key authn.req.sipconnect%2Esipgate%2Ede) via <0.1014.0>

Nov  6 16:40:52 connect 2600hz[12999]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_worker:563 (<0.865.0>) published request with msg id 6c8d28e3-80af-45e0-ac39-c27e66a74b15 for <0.2978.0>

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:40 (<0.4917.0>) trying to authenticate 0174....@sipconnect.sipgate.de

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:215 (<0.4917.0>) failed to lookup realm sipconnect.sipgate.de in accounts: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:244 (<0.4917.0>) 01745...@sipconnect.sipgate.de not found in aggregate

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:45 (<0.4917.0>) auth failure for 0174......@sipconnect.sipgate.de: not_found

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|reg_authn_req:90 (<0.4917.0>) sending SIP authentication error

Nov  6 16:40:52 connect 2600hz[12933]: |6c8d28e3-80af-45e0-ac39-c27e66a74b15|kz_amqp_channel:159 (<0.4917.0>) published to targeted(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key ecal...@connect.fabbrica.one-<0.865.0>-1cc23b80) via <0.1602.0>

    >>>>>> 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.
    >>>>>>
    >>>>>>
    >>>>>> --
    >>>>>> 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.
    >>>>>
    >>>>> --
    >>>>> 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.
    >>>>>
    >>>>> --
    >>>>> 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.
    >>>>
    >>>> --
    >>>> 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 to2600hz-user...@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>>
    >>>> --
    >>>> 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 to2600hz-user...@googlegroups.com.


    >>>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-user...@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>>
    >>> --
    >>> 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 to2600hz-user...@googlegroups.com.


    >>> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-user...@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >>
    >> --
    >> 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 to2600hz-user...@googlegroups.com.


    >> For more options, visit https://groups.google.com/d/optout.
    >
    > --
    > 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.
    >
    >
    > --
    > 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.

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


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

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

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

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

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

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

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

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

Christian Lox

unread,
Nov 15, 2016, 8:50:31 AM11/15/16
to 2600hz-users
Hi all,

With the great help from Darren and others I managed to finish the configuration of inbound calls.
Setting up call flows (including receiving fax) works like a charm.

But still need some guidance on configuring outbound calls, no calls going through.

I set up a document in the offset DB, as described here:

But not sure If I understand things correctly:

- Offnet DB is used for outbound calls, correct?
- What exactly is „rules" (also called „routes“ in the above mentioned document) for? Is this the indicator to send calls to this carrier if number matches with rule?
- same question for „formatters“. It is mentioned this is for *inbound*?

Thanks!


After inserting the CarrierIP(s) as described in https://2600hz.atlassian.net/wiki/display/Dedicated/Inbound+Calls+Failthey showed up and call goes through.

Stanislav Filippov

unread,
Nov 17, 2016, 12:19:32 PM11/17/16
to 2600hz-users
Hi, Christian!

Do you use centos or debian? Which version?
Erlang installed with kerl or packages e.g. from erlang-solutions?
Which documentation did you use for install process?
Is it single server setup or multiple?

Thanks!
Stanislav

Gordon Sims

unread,
Dec 6, 2016, 7:28:31 AM12/6/16
to 2600hz-users
Mike,

Do you or maybe someone else has an updated list of sup commands that can be used.  I've tried replacing out whistle with kazoo in the command and even tried putting in kapps for craps and giggles, but always get 'Invalid command or wrong number of arguments, please try again".  I've checked stormqloud's link and it states that it only works on 3.21 and obviously 3.22 since its part of that version train.  It is nice having these simple one liners to add in phone numbers, especially when you have multiple systems (non Kazoo) that you need to migrate over.  Just looking to shave some time is all.

Thanks,

Gordon

fred

unread,
Dec 6, 2016, 10:12:03 AM12/6/16
to 2600hz-users
You can generate the sup commands list yourself.

/opt/kazoo/lib/sup*/priv/build-autocomplete.escript \ /etc/bash_completion.d/sup.bash /opt/kazoo > /usr/doc/sup_commands

Reply all
Reply to author
Forward
0 new messages