Adding Numbers to Kazoo

[Mark McDonald]

We've been experimenting with a new Kazoo installation and have everything working well with the exception of adding external numbers to an account.  Here's what we did so far:

1) Setup an account with 2600hz and purchased a couple of numbers.  

2) Created PBX on the 2600hz platform (specifying FreeSwitch as the platform type)

3) On our Kazoo Installation, we added a Carrier, specifying the same SIP Server/Realm and User/Pass as specified in 2600hz's platform.

After doing this, we can place calls out and they seem to work fine.  What we're trying to figure out is how to add numbers to our Kazoo installation so that the numbers can be assigned to an account.  I've googled everything I can think of and found some references to the Numbers document, however there's nothing I can find that specifies what needs to be in this document.

Are we going about this the wrong way?

-Mark

[Joshua Goldbard]

Mark,

To be clear, this is a private install, and you are not using our hosted cluster, correct?

Cheers,
Joshua

Sent from my iPad

[Mark McDonald]

Both, technically. It's a private install with the trunks/numbers coming from your hosted cluster.

-Mark

On Oct 27, 2012, at 11:22 AM, Joshua Goldbard <j...@2600hz.com>
wrote:

-

Mark McDonald
ma...@siteserver.com

Office: 805.578.2000
Mobile: 805.857.5614

[Darren Schreiber]

For your private install you must manually modify the the user document in
the database to grant permission to add numbers manually.

https://groups.google.com/forum/#!msg/2600hz-dev/wpHDH9I8WU0/6gzwP-waJjEJ
details how to do it (toward the bottom).



--
Darren Schreiber
CEO / Co-Founder

[Mark McDonald]

We've added the pvt_wnm_allow_additions to both the superduper account and the sub account (test customer), which in turn adds the "Add Number" field in the Number Manager, however when trying to add a number (+1805203xxxx), it returns:

There was an error when trying to acquire +1805203xxxx, would you like to retry? (xxxx is obviously the rest of the number)

We're unclear as to whether we should be/there is a way to add a number to the system globally and then under the sub account choose that number and assign it to a Call Flow, or if the number should be directly assigned to the customer account.

-Mark

On Oct 27, 2012, at 11:27 AM, Darren Schreiber <dar...@2600hz.com>

 wrote:

[Darren Schreiber]

That means the number is already in the system assigned to another account, or was at some point assigned to another account. It won't allow you to assign it again to a different account unless you clear it out.

Go into your database, port 5984, in the numbers/+1805 database. Find the +1805203xxxx doc. Delete it. Then try to add it again.

If you go on the wiki and search for "Number Lifecycle" you'll see what we're working to implement. It's not complete. It will allow master accounts to hold numbers and sub-accounts to be assigned said numbers, and prevent people from adding numbers who aren't authorized. All the back-end code is actually there but the front-end is not.

There is a separate wiki document for the API calls to do this yourself which I believe do work, in full, and allow the behavior you desire. But the documentation is currently lacking on that, so I'm going to call that incomplete for now as well (unless you can read the Erlang code and figure it out, in which case, feel free to contribute to the docs so that we can get this wrapped up)

--

Darren Schreiber

CEO / Co-Founder

 visit: www.2600hz.com

 sip:dar...@2600hz.com

 tel: 415-886-7901

[Mark McDonald]

There must be something as I can try to add anything (+18055551818, +18185551215, etc) and I get the same error (There was an error when trying to acquire +1xxxxxxxxxx, would you like to retry?)  I'm going to work with this a bit more and will post a more detailed response.  From what I'm able to find via Google Searches, we're also missing some offnet database updates that we need to get in place - right now we're defining a Carrier for each account which we don't want to do.

We're updating our internal wiki as we go through this process start to finish and I'll update the 2600hz wiki as soon as we're completed with the items we found to be lacking in the documentation.  There appear to be huge gaps in regards to the offnet and carrier documents (unless I'm missing something)...

-Mark

On Oct 27, 2012, at 12:04 PM, Darren Schreiber <dar...@2600hz.com>

 wrote:

That means the number is already in the system assigned to another account, or was at some point assigned to another account. It won't allow you to assign it again to a different account unless you clear it out.

Go into your database, port 5984, in the numbers/+1805 database. Find the +1805203xxxx doc. Delete it. Then try to add it again.

If you go on the wiki and search for "Number Lifecycle" you'll see what we're working to implement. It's not complete. It will allow master accounts to hold numbers and sub-accounts to be assigned said numbers, and prevent people from adding numbers who aren't authorized. All the back-end code is actually there but the front-end is not.

There is a separate wiki document for the API calls to do this yourself which I believe do work, in full, and allow the behavior you desire. But the documentation is currently lacking on that, so I'm going to call that incomplete for now as well (unless you can read the Erlang code and figure it out, in which case, feel free to contribute to the docs so that we can get this wrapped up)

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[17].png>

 tel: 415-886-7901

[Darren Schreiber]

Offnet IS the carrier documents, except that offnet is just a global document for all customers.

You can copy over a carrier doc from an individual account into the offnet database, they're the same thing basically. Just remove anything that's clearly account specific (like an account id).

--

 tel: 415-886-7901

[Darren Schreiber]

Oh, and to find the errors is simple – open the developer tools in your browser (like in Chrome) and look at the network requests. There will be a Request-ID header in the logs. You can grep that request-id in your server-side logs to find out what the error really was.

--

 tel: 415-886-7901

[Mark McDonald]

{"auth_token":"7a393d40195286551d5eadfccc015789","status":"error","message":"unauthorized","error":"500","data":{"unauthorized":"Not authorized to perform requested number operation"},"request_id":"7a96968333d3b10d127bad68d067f1a1"}

Here's the grep from the logs with the most relevant information I could see:

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|crossbar_bindings:489 (<0.15099.5>) routing v1_resource.execute.put.phone_numbers matches v1_resource.execute.put.phone_numbers

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:104 (<0.15099.5>) attempting to create number 8051231234 for account 96fa9c45a8a060f4b371274b1214b11f

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_util:82 (<0.15099.5>) number '8051231234' can be reconciled, proceeding

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_number:737 (<0.15099.5>) The number could not be found

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:121 (<0.15099.5>) account is not authorized to create a new number: false

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_number:707 (<0.15099.5>) Not authorized to perform requested number operation

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:134 (<0.15099.5>) create number prematurely ended: unauthorized

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|v1_util:834 (<0.15099.5>) halting execution here

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|v1_util:801 (<0.15099.5>) generating error 500 response, unauthorized

-Mark

On Oct 27, 2012, at 12:17 PM, Darren Schreiber <dar...@2600hz.com>

 wrote:

Oh, and to find the errors is simple – open the developer tools in your browser (like in Chrome) and look at the network requests. There will be a Request-ID header in the logs. You can grep that request-id in your server-side logs to find out what the error really was.

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[24].png>

 tel: 415-886-7901

[Darren Schreiber]

You have not properly added the flag to your account that allows you to add numbers.

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:121 (<0.15099.5>) account is not authorized to create a new number: false

Also don't post your auth-token in the future please :-)

--

 tel: 415-886-7901

[Mark McDonald]

:)  I didn't think you'd like that - this is fire walled off and will be rebuilt by the end of the day.

Here's our /accounts/superduperaccount Document:

{
   "_id": "96fa9c45a8a060f4b371274b1214b11f",
   "_rev": "5-36b669f20948d39edab8836cbe785639",
   "available_apps": [
       "voip",
       "pbxs",
       "numbers",
       "accounts",
       "developer"
   ],
   "pvt_superduper_admin": true,
   "name": "altered",
   "realm": "altered",
   "timezone": "America/Los_Angeles",
   "caller_id": {
   },
   "caller_id_options": {
   },
   "notifications": {
   },
   "media": {
       "bypass_media": "auto"
   },
   "music_on_hold": {
   },
   "pvt_type": "account",
   "pvt_api_key": "altered",
   "pvt_tree": [
   ],
   "pvt_wnm_numbers": [
   ],
   "pvt_vsn": "1",
   "pvt_created": 63518252856,
   "pvt_modified": 63518252856,
   "pvt_account_db": "altered",
   "pvt_account_id": "altered",
   "pvt_wnm_allow_additions": true
}

On Oct 27, 2012, at 1:05 PM, Darren Schreiber <dar...@2600hz.com>

 wrote:

You have not properly added the flag to your account that allows you to add numbers.

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:121 (<0.15099.5>) account is not authorized to create a new number: false

Also don't post your auth-token in the future please :-)

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[28].png>

 tel: 415-886-7901

[Darren Schreiber]

Can you try clearing your cache?

sup wh_cache flush


- Darren

[Jon Blanton]

pvt_wnm_allow_additions must be added to the account doc in the "accounts" db and in the account's database

-Jon

[Darren Schreiber]

agh yes thanks Jon.

Mark – all account docs must always be in sync between the account itself and the global accounts/ doc.

and those docs are cached so you should issue sup wh_cache flush after any changes.

--

Darren Schreiber

CEO / Co-Founder

 visit: www.2600hz.com

 sip:dar...@2600hz.com

 tel: 415-886-7901

[Mark McDonald]

account/96/fa/9c45a8a060f4b371274b1214b11f 96fa9c45a8a060f4b371274b1214b11f

So under that document as well?

-Mark

On Oct 27, 2012, at 1:57 PM, Jon Blanton <jbla...@2600hz.com>

 wrote:

[Mark McDonald]

Ok, that did it - now I can add numbers to the account, and in turn assign those numbers to a Call Flow.  Problem is, now that the Call Flow is built, I'm not seeing the call get to our system.  If my only reference to 2600hz is in the offnet database (not a specific carrier on any of the individual accounts) using SIP Auth (User/Pass), how does the system route that call to an account on our system?

-Mark

On Oct 27, 2012, at 2:07 PM, Mark McDonald <Ma...@siteserver.com>

 wrote:

[Yuriy Nasida]

Hello guys and thank you for perfect stuff !

I think that I have same issue. I can add DID manually (according your instructions below) and add them to callflow but ...  when I try to make inbound call to new DID,  I recieve '503' sip message. System ask login\password for inbound INVITE but it should not I think. Also I can add DID numbers of USA only. How can I add any DID of other country as well ?

Please advice.

Thanks.

---

From: Ma...@siteserver.com
To: 2600h...@googlegroups.com

Subject: Re: Adding Numbers to Kazoo

Date: Sat, 27 Oct 2012 21:20:09 +0000

[Mark McDonald]

Yuriy,

That's where I was a bit confused - Kazoo won't handle or configure the SIP registrations - you'll need to do this on each of your FreeSwitch servers.  You can do this by creating a /gateways directory in /etc/freeswitch and creating an XML file (2600.xml for example).  In there, put the following:

<include>

  <gateway>

    <param name="realm" value="yoursipealm.sip.2600hz.com"/>

    <param name="username" value="youruser"/>

    <param name="password" value="yourpass"/>

    <param name="register" value="true"/>

  </gateway>

</include>

Either restart Freeswitch, or login (cli) and reloadxml / reload mod_sofia.  Freeswitch will now maintain the connection to 2600's SIP servers and accept incoming INVITE's.  Not sure on what other country's are supported on 2600hz's platform - I'll leave that for someone else.

-Mark McDonald

ma...@siteserver.com

Office: 805.578.2000 x 231

Mobile: 805.857.5614

On Oct 29, 2012, at 6:01 PM, Yuriy Nasida <nas...@live.ru>

 wrote:

Hello guys and thank you for perfect stuff !

I think that I have same issue. I can add DID manually (according your instructions below) and add them to callflow but ...  when I try to make inbound call to new DID,  I recieve '503' sip message. System ask login\password for inbound INVITE but it should not I think. Also I can add DID numbers of USA only. How can I add any DID of other country as well ?

Please advice.

Thanks.

---

From: Ma...@siteserver.com
To: 2600hz-d...@googlegroups.com

[Kirill Sysoev]

Hi Yuri

To be able to add other than USA numbers you need to correct "reconcile_regex" field in number_manager document system_config database.

Just start with that and may be another questions will be solved automatically

Regards, 

2012/10/30 Yuriy Nasida <nas...@live.ru>

[Yuriy Nasida]

Mark, It is very strange but I really don't see how can I add  DID provider to my private installation of  kazoo . System really can not be registered anywhere by means of kazoo UI as far as I see. Sure we can add this on xml files of FS nodes but this looks not good. Also, as far as I understand we has to be able to assign DID numbers from main account to  account of more lower level as some 'resourse'.

Kirill, I have changed reconcile_regex but still can add DID of  USA  only. When I try to add DID like this +7-XXX-XXXXXXX and press 'OK' - nothing happens. I don't see any errors.

But ... It is not main issue. How can I set IP address of inbound carrier which give me this DID number? I don't want ask UN\pass for INVITES from this provider. Just IP.

Um... I can use some 'device' and set authorisation method - IP. This way I able to have inbound DID provider but it looks not good I think.

Also I have to do 'reloadacl' on FS node, otherwise such device on kazoo still ask UN\pass  for inbound INVITES.

Please advice.

Thanks.

---

Date: Tue, 30 Oct 2012 07:14:50 +0400

Subject: Re: Adding Numbers to Kazoo

From: kirill...@gmail.com
To: 2600h...@googlegroups.com

[Luis Azedo]

Hi,

to add non us numbers you need to change /var/www/html/whapps/numbers/numbers_manager/number_manager.js

search and replace regex expressions because these are not taken from kazoo db.

to add your did providers edit the /etc/freeswitch//etc/freeswitch/autoload_configs/acl.conf.xml

and add the IP addresses then on fs_cli do "reloadacl"

this is just a workaround, kazoo team is working on some of api to integrate did providers (search, provision, etc)

hope this helps

--

Luis Azedo

[Yuriy Nasida]

I see. Ok will look forward :)
Thanks!

---

Date: Wed, 31 Oct 2012 21:08:33 +0000

Subject: Re: Adding Numbers to Kazoo

From: luis....@factorlusitano.com
To: 2600h...@googlegroups.com

[Kirill Sysoev]

Hi Yuri, Luis

Seems I was also answering about acls but message disappeared in a strange way..

At the moment configuring acls is already proceeding through couchdb:
Overview -> system_config -> ecallmgr

Document looks like this:

{
   "_id": "ecallmgr",
   "_rev": "18-61b3b9070c4daba15abc98c057a120e3",
   "default": {
       "default": {
       },
       "fs_nodes": [
           "frees...@kz8.domain.tld",
           "frees...@kz9.domain.tld"
       ],
       "fs_cmds": [
           {
               "load": "mod_sofia",
               "reloadacl": ""
           }
       ],
       "node_down_grace_period": 10000,
       "acls": {
           "dialogic": {
               "type": "allow",
               "network-list-name": "authoritative",
               "cidr": "XX.XX.XX.XX/32"
           },
           "fs_radius": {
               "type": "allow",
               "network-list-name": "authoritative",
               "cidr": "XX.XX.XX.XX/32"
           }
       },
       "distribute_message_query": true,
       "distribute_presence": true,
       "authz_enabled": false,
       "default_ringback": "%(2000,4000,440,480)",
       "default_recording_extension": ".mp3",
       "recording_file_path": "/tmp/"
   }
}


Regarding adding numbers through UI.
Little hint to not to mess with kazoo_UI code changing:

just try to add it without 7 i.e. 4951234567
It will add the number and 7 will be prefixed automatically :))

Best,
Kirill

2012/11/1 Yuriy Nasida <nas...@live.ru>

[Kirill Sysoev]

Hi Darren!

Just trying to save you a bit of time for new features development :)))))

Making final preparation steps to start migration our customers to kazoo atm

Hope they will appreciate this move :)

Regards

четверг, 1 ноября 2012 г. пользователь Darren Schreiber писал:

Thanks for your continued help in posting Kirill!!! This is fantastic.

[Darren Schreiber]

We are about to come out with a new version of mod_erlang_event, I would actually suggest, if you haven't moved anyone yet, that you wait for that.

It's a SIGNIFICANT improvement. Could use your awesome testing skills :-)

I can't even begin to tell you how excited I am about this next release. When it comes to stability, this is a major improvement for high-volume call capacity centers.

--

Darren Schreiber

CEO / Co-Founder

 visit: www.2600hz.com

 sip:dar...@2600hz.com

 tel: 415-886-7901

[zhi sun]

i am also interested in what kinds of things are improved comparing to the old mod_erlang_event shipped with FS.

thanks,
-zhisun

2012/11/1 Darren Schreiber <dar...@2600hz.com>

[Kirill Sysoev]

Thank you for info Darren

Will wait a bit

On the other hand you guys producing improvements continuously: after mod_erlang_event, Kamailio could hit the street or whatever and so on .... :)))

[Darren Schreiber]

Fair point :-)

[in...@beltex.nl]

any news on did providers ?

I read that there are some libraries, are they available? 

Op donderdag 1 november 2012 06:16:24 UTC+1 schreef Darren Schreiber het volgende:

[Martin Splinter]

where should we do it in v3??

Op dinsdag 30 oktober 2012 02:07:22 UTC+1 schreef SupermanSC:

[Yuriy Nasida]

Martin,

You don't need to do this with v3. It's old tread :)

You can add DID via admin account (button 'Add number' in 'Number Manager' appl ).

Next, you will have to open inbound carrier IP in database manually. Plus don't forget to add IP adreess of kamailio as well

Look at this manual https://2600hz.atlassian.net/wiki/display/docs/Inbound+Calls+Fail

---

Date: Sun, 19 Jan 2014 15:43:45 -0800
From: in...@beltex.nl
To: 2600h...@googlegroups.com

--
You received this message because you are subscribed to the Google Groups "2600hz-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[BelTex ISP]

Hi and thanks

I have two trunks and one requires registration for inbound, outbound works great but inbound not as the trunk is not registered.

I have been trying to get the add number button visible for some time now ))))) No luck yet

So inbound routing is not yet working, but ill prop get it working soon

Yuriy Nasida schreef op 20-1-2014 16:55:

Martin,

You don't need to do this with v3. It's old tread :)

You can add DID via admin account (button 'Add number' in 'Number Manager' appl ).

Next, you will have to open inbound carrier IP in database manually. Plus don't forget to add IP adreess of kamailio as well

Look at this manual�https://2600hz.atlassian.net/wiki/display/docs/Inbound+Calls+Fail

---

Date: Sun, 19 Jan 2014 15:43:45 -0800
From: in...@beltex.nl
To: 2600h...@googlegroups.com
Subject: Re: Adding Numbers to Kazoo

where should we do it in v3??

Op dinsdag 30 oktober 2012 02:07:22 UTC+1 schreef SupermanSC:

Yuriy,

That's where I was a bit confused - Kazoo won't handle or configure the SIP registrations - you'll need to do this on each of your FreeSwitch servers. �You can do this by creating a /gateways directory in /etc/freeswitch and creating an XML file (2600.xml for example). �In there, put the following:

<include>

� <gateway>

� � <param name="realm" value="yoursipealm.sip.2600hz.com"/>

� � <param name="username" value="youruser"/>

� � <param name="password" value="yourpass"/>

� � <param name="register" value="true"/>

� </gateway>

</include>

Either restart Freeswitch, or login (cli) and reloadxml / reload mod_sofia. �Freeswitch will now maintain the connection to 2600's SIP servers and accept incoming INVITE's. �Not sure on what other country's are supported on 2600hz's platform - I'll leave that for someone else.

-Mark McDonald

ma...@siteserver.com

Office: 805.578.2000 x 231

Mobile: 805.857.5614

On Oct 29, 2012, at 6:01 PM, Yuriy Nasida <nas...@live.ru>

�wrote:

Hello guys and thank you for perfect stuff !

I think that I have same issue. I can add DID manually (according your instructions below) and add them to callflow but ... �when I try to make inbound call to new DID, �I recieve '503' sip message. System ask login\password for inbound INVITE but it should not I think. Also I can add DID numbers of USA only. How can I add any DID of other country as well ?

Please advice.

Thanks.

---

From:�Ma...@siteserver.com

To: 2600hz-d...@googlegroups.com
Subject: Re: Adding Numbers to Kazoo
Date: Sat, 27 Oct 2012 21:20:09 +0000

Ok, that did it - now I can add numbers to the account, and in turn assign those numbers to a Call Flow. �Problem is, now that the Call Flow is built, I'm not seeing the call get to our system. �If my only reference to 2600hz is in the offnet database (not a specific carrier on any of the individual accounts) using SIP Auth (User/Pass), how does the system route that call to an account on our system?

-Mark

On Oct 27, 2012, at 2:07 PM, Mark McDonald <Ma...@siteserver.com>

�wrote:

account/96/fa/9c45a8a060f4b371274b1214b11f�96fa9c45a8a060f4b371274b1214b11f

So under that document as well?

-Mark

On Oct 27, 2012, at 1:57 PM, Jon Blanton <jbla...@2600hz.com>

�wrote:

pvt_wnm_allow_additions must be added to the account doc in the "accounts" db and in the account's database

-Jon

Mark McDonald wrote:

:) �I didn't think you'd like that - this is fire walled off and will be rebuilt by the end of the day.

�wrote:

You have not properly added the flag to your account that allows you to add numbers.

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:121 (<0.15099.5>) account is not authorized to create a new number: false

Also don't post your auth-token in the future please :-)

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[28].png>

Darren Schreiber

CEO / Co-Founder

�visit:�www.2600hz.com

�sip:dar...@2600hz.com

�tel:�415-886-7901

From:�Mark McDonald <Ma...@siteserver.com>
Reply-To:�"2600h...@googlegroups.com" <2600h...@googlegroups.com>
Date:�Saturday, October 27, 2012 1:03 PM
To:�"<2600h...@googlegroups.com>" <2600h...@googlegroups.com>
Subject:�Re: Adding Numbers to Kazoo

{"auth_token":"7a393d40195286551d5eadfccc015789","status":"error","message":"unauthorized","error":"500","data":{"unauthorized":"Not authorized to perform requested number operation"},"request_id":"7a96968333d3b10d127bad68d067f1a1"}

Here's the grep from the logs with the most relevant information I could see:

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|crossbar_bindings:489 (<0.15099.5>) routing v1_resource.execute.put.phone_numbers matches v1_resource.execute.put.phone_numbers

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:104 (<0.15099.5>) attempting to create number 8051231234 for account 96fa9c45a8a060f4b371274b1214b11f

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_util:82 (<0.15099.5>) number '8051231234' can be reconciled, proceeding

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_number:737 (<0.15099.5>) The number could not be found

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:121 (<0.15099.5>) account is not authorized to create a new number: false

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_number:707 (<0.15099.5>) Not authorized to perform requested number operation

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:134 (<0.15099.5>) create number prematurely ended: unauthorized

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|v1_util:834 (<0.15099.5>) halting execution here

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|v1_util:801 (<0.15099.5>) generating error 500 response, unauthorized

-Mark

On Oct 27, 2012, at 12:17 PM, Darren Schreiber <dar...@2600hz.com>

�wrote:

Oh, and to find the errors is simple � open the developer tools in your browser (like in Chrome) and look at the network requests. There will be a Request-ID header in the logs. You can grep that request-id in your server-side logs to find out what the error really was.

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[24].png>

Darren Schreiber

CEO / Co-Founder

�visit:�www.2600hz.com

�sip:dar...@2600hz.com

�tel:�415-886-7901

From:�Mark McDonald <Ma...@siteserver.com>
Reply-To:�"2600h...@googlegroups.com" <2600h...@googlegroups.com>
Date:�Saturday, October 27, 2012 12:14 PM
To:�"<2600h...@googlegroups.com>" <2600h...@googlegroups.com>
Subject:�Re: Adding Numbers to Kazoo

There must be something as I can try to add anything (+18055551818, +18185551215, etc) and I get the same error (There was an error when trying to acquire +1xxxxxxxxxx, would you like to retry?) �I'm going to work with this a bit more and will post a more detailed response. �From what I'm able to find via Google Searches, we're also missing some offnet database updates that we need to get in place - right now we're defining a Carrier for each account which we don't want to do.

We're updating our internal wiki as we go through this process start to finish and I'll update the 2600hz wiki as soon as we're completed with the items we found to be lacking in the documentation. �There appear to be huge gaps in regards to the offnet and carrier documents (unless I'm missing something)...

-Mark

On Oct 27, 2012, at 12:04 PM, Darren Schreiber <dar...@2600hz.com>

�wrote:

That means the number is already in the system assigned to another account, or was at some point assigned to another account. It won't allow you to assign it again to a different account unless you clear it out.

Go into your database, port 5984, in the numbers/+1805 database. Find the +1805203xxxx doc. Delete it. Then try to add it again.

If you go on the wiki and search for "Number Lifecycle" you'll see what we're working to implement. It's not complete. It will allow master accounts to hold numbers and sub-accounts to be assigned said numbers, and prevent people from adding numbers who aren't authorized. All the back-end code is actually there but the front-end is not.

There is a separate wiki document for the API calls to do this yourself which I believe do work, in full, and allow the behavior you desire. But the documentation is currently lacking on that, so I'm going to call that incomplete for now as well (unless you can read the Erlang code and figure it out, in which case, feel free to contribute to the docs so that we can get this wrapped up)

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[17].png>

Darren Schreiber

CEO / Co-Founder

�visit:�www.2600hz.com

�sip:dar...@2600hz.com

�tel:�415-886-7901

From:�Mark McDonald <Ma...@siteserver.com>
Reply-To:�"2600h...@googlegroups.com" <2600h...@googlegroups.com>
Date:�Saturday, October 27, 2012 12:01 PM
To:�"<2600h...@googlegroups.com>" <2600h...@googlegroups.com>
Subject:�Re: Adding Numbers to Kazoo

We've added the�pvt_wnm_allow_additions to both the superduper account and the sub account (test customer), which in turn adds the "Add Number" field in the Number Manager, however when trying to add a number (+1805203xxxx), it returns:

There was an error when trying to acquire +1805203xxxx, would you like to retry? (xxxx is obviously the rest of the number)

We're unclear as to whether we should be/there is a way to add a number to the system globally and then under the sub account choose that number and assign it to a Call Flow, or if the number should be directly assigned to the customer account.

-Mark

On Oct 27, 2012, at 11:27 AM, Darren Schreiber <dar...@2600hz.com>

�wrote:

For your private install you must manually modify the the user document in
the database to grant permission to add numbers manually.

https://groups.google.com/forum/#!msg/2600hz-dev/wpHDH9I8WU0/6gzwP-waJjEJ
details how to do it (toward the bottom).



--
Darren Schreiber
CEO / Co-Founder





On 10/27/12 11:25 AM, "Mark McDonald" <Ma...@siteserver.com> wrote:

Both, technically. �It's a private install with the trunks/numbers coming

from your hosted cluster.

-Mark

On Oct 27, 2012, at 11:22 AM, Joshua Goldbard <j...@2600hz.com>
wrote:

Mark,

To be clear, this is a private install, and you are not using our
hosted cluster, correct?

Cheers,
Joshua

Sent from my iPad

On Oct 27, 2012, at 11:20 AM, "Mark McDonald" <ma...@siteserver.com>
wrote:

We've been experimenting with a new Kazoo installation and have
everything working well with the exception of adding external numbers

to an account. �Here's what we did so far:

1) Setup an account with 2600hz and purchased a couple of numbers.
2) Created PBX on the 2600hz platform (specifying FreeSwitch as the
platform type)
3) On our Kazoo Installation, we added a Carrier, specifying the same
SIP Server/Realm and User/Pass as specified in 2600hz's platform.

After doing this, we can place calls out and they seem to work fine.
What we're trying to figure out is how to add numbers to our Kazoo

installation so that the numbers can be assigned to an account. �I've

--
You received this message because you are subscribed to a topic in the Google Groups "2600hz-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/2600hz-dev/rMA3Q6dTJV4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 2600hz-dev+...@googlegroups.com.

[Yuriy Nasida]

No problems.

I think you need to add your carrier to offnet database manually.

https://2600hz.atlassian.net/wiki/display/docs/Global+Resources

P.S. It is for global carriers.

Yep I also could not get button "add number" visible :) The reason here - you must to use your 1st account which was created. Only 1st account has this button.

---

Date: Mon, 20 Jan 2014 17:15:09 +0100

From: in...@beltex.nl
To: 2600h...@googlegroups.com
Subject: Re: Adding Numbers to Kazoo

Hi and thanks

I have two trunks and one requires registration for inbound, outbound works great but inbound not as the trunk is not registered.

I have been trying to get the add number button visible for some time now ))))) No luck yet

So inbound routing is not yet working, but ill prop get it working soon

Yuriy Nasida schreef op 20-1-2014 16:55:

Martin,

You don't need to do this with v3. It's old tread :)

You can add DID via admin account (button 'Add number' in 'Number Manager' appl ).

Next, you will have to open inbound carrier IP in database manually. Plus don't forget to add IP adreess of kamailio as well

Look at this manual https://2600hz.atlassian.net/wiki/display/docs/Inbound+Calls+Fail

---

Date: Sun, 19 Jan 2014 15:43:45 -0800
From: in...@beltex.nl
To: 2600h...@googlegroups.com
Subject: Re: Adding Numbers to Kazoo

where should we do it in v3??

Op dinsdag 30 oktober 2012 02:07:22 UTC+1 schreef SupermanSC:

Yuriy,

That's where I was a bit confused - Kazoo won't handle or configure the SIP registrations - you'll need to do this on each of your FreeSwitch servers.  You can do this by creating a /gateways directory in /etc/freeswitch and creating an XML file (2600.xml for example).  In there, put the following:

<include>

  <gateway>

    <param name="realm" value="yoursipealm.sip.2600hz.com"/>

    <param name="username" value="youruser"/>

    <param name="password" value="yourpass"/>

    <param name="register" value="true"/>

  </gateway>

</include>

Either restart Freeswitch, or login (cli) and reloadxml / reload mod_sofia.  Freeswitch will now maintain the connection to 2600's SIP servers and accept incoming INVITE's.  Not sure on what other country's are supported on 2600hz's platform - I'll leave that for someone else.

-Mark McDonald

ma...@siteserver.com

Office: 805.578.2000 x 231

Mobile: 805.857.5614

On Oct 29, 2012, at 6:01 PM, Yuriy Nasida <nas...@live.ru>

 wrote:

Hello guys and thank you for perfect stuff !

I think that I have same issue. I can add DID manually (according your instructions below) and add them to callflow but ...  when I try to make inbound call to new DID,  I recieve '503' sip message. System ask login\password for inbound INVITE but it should not I think. Also I can add DID numbers of USA only. How can I add any DID of other country as well ?

Please advice.

Thanks.

---

From: Ma...@siteserver.com

To: 2600hz-d...@googlegroups.com
Subject: Re: Adding Numbers to Kazoo
Date: Sat, 27 Oct 2012 21:20:09 +0000

Ok, that did it - now I can add numbers to the account, and in turn assign those numbers to a Call Flow.  Problem is, now that the Call Flow is built, I'm not seeing the call get to our system.  If my only reference to 2600hz is in the offnet database (not a specific carrier on any of the individual accounts) using SIP Auth (User/Pass), how does the system route that call to an account on our system?

-Mark

On Oct 27, 2012, at 2:07 PM, Mark McDonald <Ma...@siteserver.com>

 wrote:

account/96/fa/9c45a8a060f4b371274b1214b11f 96fa9c45a8a060f4b371274b1214b11f

So under that document as well?

-Mark

On Oct 27, 2012, at 1:57 PM, Jon Blanton <jbla...@2600hz.com>

 wrote:

pvt_wnm_allow_additions must be added to the account doc in the "accounts" db and in the account's database

-Jon

Mark McDonald wrote:

:)  I didn't think you'd like that - this is fire walled off and will be rebuilt by the end of the day.

 wrote:

You have not properly added the flag to your account that allows you to add numbers.

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:121 (<0.15099.5>) account is not authorized to create a new number: false

Also don't post your auth-token in the future please :-)

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[28].png>

Darren Schreiber

CEO / Co-Founder

 visit: www.2600hz.com

 sip:dar...@2600hz.com

 tel: 415-886-7901

From: Mark McDonald <Ma...@siteserver.com>
Reply-To: "2600h...@googlegroups.com" <2600h...@googlegroups.com>

Date: Saturday, October 27, 2012 1:03 PM
To: "<2600h...@googlegroups.com>" <2600h...@googlegroups.com>
Subject: Re: Adding Numbers to Kazoo

{"auth_token":"7a393d40195286551d5eadfccc015789","status":"error","message":"unauthorized","error":"500","data":{"unauthorized":"Not authorized to perform requested number operation"},"request_id":"7a96968333d3b10d127bad68d067f1a1"}

Here's the grep from the logs with the most relevant information I could see:

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|crossbar_bindings:489 (<0.15099.5>) routing v1_resource.execute.put.phone_numbers matches v1_resource.execute.put.phone_numbers

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:104 (<0.15099.5>) attempting to create number 8051231234 for account 96fa9c45a8a060f4b371274b1214b11f

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_util:82 (<0.15099.5>) number '8051231234' can be reconciled, proceeding

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_number:737 (<0.15099.5>) The number could not be found

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:121 (<0.15099.5>) account is not authorized to create a new number: false

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_number:707 (<0.15099.5>) Not authorized to perform requested number operation

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:134 (<0.15099.5>) create number prematurely ended: unauthorized

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|v1_util:834 (<0.15099.5>) halting execution here

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|v1_util:801 (<0.15099.5>) generating error 500 response, unauthorized

-Mark

On Oct 27, 2012, at 12:17 PM, Darren Schreiber <dar...@2600hz.com>

 wrote:

Oh, and to find the errors is simple – open the developer tools in your browser (like in Chrome) and look at the network requests. There will be a Request-ID header in the logs. You can grep that request-id in your server-side logs to find out what the error really was.

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[24].png>

Darren Schreiber

CEO / Co-Founder

 visit: www.2600hz.com

 sip:dar...@2600hz.com

 tel: 415-886-7901

From: Mark McDonald <Ma...@siteserver.com>
Reply-To: "2600h...@googlegroups.com" <2600h...@googlegroups.com>

Date: Saturday, October 27, 2012 12:14 PM
To: "<2600h...@googlegroups.com>" <2600h...@googlegroups.com>
Subject: Re: Adding Numbers to Kazoo

There must be something as I can try to add anything (+18055551818, +18185551215, etc) and I get the same error (There was an error when trying to acquire +1xxxxxxxxxx, would you like to retry?)  I'm going to work with this a bit more and will post a more detailed response.  From what I'm able to find via Google Searches, we're also missing some offnet database updates that we need to get in place - right now we're defining a Carrier for each account which we don't want to do.

We're updating our internal wiki as we go through this process start to finish and I'll update the 2600hz wiki as soon as we're completed with the items we found to be lacking in the documentation.  There appear to be huge gaps in regards to the offnet and carrier documents (unless I'm missing something)...

-Mark

On Oct 27, 2012, at 12:04 PM, Darren Schreiber <dar...@2600hz.com>

 wrote:

That means the number is already in the system assigned to another account, or was at some point assigned to another account. It won't allow you to assign it again to a different account unless you clear it out.

Go into your database, port 5984, in the numbers/+1805 database. Find the +1805203xxxx doc. Delete it. Then try to add it again.

If you go on the wiki and search for "Number Lifecycle" you'll see what we're working to implement. It's not complete. It will allow master accounts to hold numbers and sub-accounts to be assigned said numbers, and prevent people from adding numbers who aren't authorized. All the back-end code is actually there but the front-end is not.

There is a separate wiki document for the API calls to do this yourself which I believe do work, in full, and allow the behavior you desire. But the documentation is currently lacking on that, so I'm going to call that incomplete for now as well (unless you can read the Erlang code and figure it out, in which case, feel free to contribute to the docs so that we can get this wrapped up)

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[17].png>

Darren Schreiber

CEO / Co-Founder

 visit: www.2600hz.com

 sip:dar...@2600hz.com

 tel: 415-886-7901

From: Mark McDonald <Ma...@siteserver.com>
Reply-To: "2600h...@googlegroups.com" <2600h...@googlegroups.com>

Date: Saturday, October 27, 2012 12:01 PM
To: "<2600h...@googlegroups.com>" <2600h...@googlegroups.com>
Subject: Re: Adding Numbers to Kazoo

We've added the pvt_wnm_allow_additions to both the superduper account and the sub account (test customer), which in turn adds the "Add Number" field in the Number Manager, however when trying to add a number (+1805203xxxx), it returns:

There was an error when trying to acquire +1805203xxxx, would you like to retry? (xxxx is obviously the rest of the number)

We're unclear as to whether we should be/there is a way to add a number to the system globally and then under the sub account choose that number and assign it to a Call Flow, or if the number should be directly assigned to the customer account.

-Mark

On Oct 27, 2012, at 11:27 AM, Darren Schreiber <dar...@2600hz.com>

 wrote:

For your private install you must manually modify the the user document in
the database to grant permission to add numbers manually.

https://groups.google.com/forum/#!msg/2600hz-dev/wpHDH9I8WU0/6gzwP-waJjEJ
details how to do it (toward the bottom).



--
Darren Schreiber
CEO / Co-Founder





On 10/27/12 11:25 AM, "Mark McDonald" <Ma...@siteserver.com> wrote:

Both, technically.  It's a private install with the trunks/numbers coming

from your hosted cluster.

-Mark

On Oct 27, 2012, at 11:22 AM, Joshua Goldbard <j...@2600hz.com>
wrote:

Mark,

To be clear, this is a private install, and you are not using our
hosted cluster, correct?

Cheers,
Joshua

Sent from my iPad

On Oct 27, 2012, at 11:20 AM, "Mark McDonald" <ma...@siteserver.com>
wrote:

We've been experimenting with a new Kazoo installation and have
everything working well with the exception of adding external numbers

to an account.  Here's what we did so far:

1) Setup an account with 2600hz and purchased a couple of numbers.
2) Created PBX on the 2600hz platform (specifying FreeSwitch as the
platform type)
3) On our Kazoo Installation, we added a Carrier, specifying the same
SIP Server/Realm and User/Pass as specified in 2600hz's platform.

After doing this, we can place calls out and they seem to work fine.
What we're trying to figure out is how to add numbers to our Kazoo

installation so that the numbers can be assigned to an account.  I've

[BelTex ISP]

Oh ill check that! thanks

I will check the ofnet thing, but i see the call comming in, there is no route so i get a 606 (if i remember correct) nope nope nope error.

I figured it was because i could not add the number, added it as an inbound callflow though and the route works from internal traffic so i guess u are right

Thanks Yuriy

Yuriy Nasida schreef op 20-1-2014 18:15:

No problems.

I think you need to add your carrier to offnet database manually.

https://2600hz.atlassian.net/wiki/display/docs/Global+Resources

P.S. It is for global carriers.

Yep I also could not get button "add number" visible :) The reason here - you must to use your 1st account which was created. Only 1st account has this button.

---

Date: Mon, 20 Jan 2014 17:15:09 +0100
From: in...@beltex.nl
To: 2600h...@googlegroups.com
Subject: Re: Adding Numbers to Kazoo

Hi and thanks

I have two trunks and one requires registration for inbound, outbound works great but inbound not as the trunk is not registered.

I have been trying to get the add number button visible for some time now ))))) No luck yet

So inbound routing is not yet working, but ill prop get it working soon

Yuriy Nasida schreef op 20-1-2014 16:55:

Martin,

You don't need to do this with v3. It's old tread :)

You can add DID via admin account (button 'Add number' in 'Number Manager' appl ).

Next, you will have to open inbound carrier IP in database manually. Plus don't forget to add IP adreess of kamailio as well

Look at this manual�https://2600hz.atlassian.net/wiki/display/docs/Inbound+Calls+Fail

---

Date: Sun, 19 Jan 2014 15:43:45 -0800
From: in...@beltex.nl
To: 2600h...@googlegroups.com
Subject: Re: Adding Numbers to Kazoo

where should we do it in v3??

Op dinsdag 30 oktober 2012 02:07:22 UTC+1 schreef SupermanSC:

Yuriy,

That's where I was a bit confused - Kazoo won't handle or configure the SIP registrations - you'll need to do this on each of your FreeSwitch servers. �You can do this by creating a /gateways directory in /etc/freeswitch and creating an XML file (2600.xml for example). �In there, put the following:

<include>

� <gateway>

� � <param name="realm" value="yoursipealm.sip.2600hz.com"/>

� � <param name="username" value="youruser"/>

� � <param name="password" value="yourpass"/>

� � <param name="register" value="true"/>

� </gateway>

</include>

Either restart Freeswitch, or login (cli) and reloadxml / reload mod_sofia. �Freeswitch will now maintain the connection to 2600's SIP servers and accept incoming INVITE's. �Not sure on what other country's are supported on 2600hz's platform - I'll leave that for someone else.

-Mark McDonald

ma...@siteserver.com

Office: 805.578.2000 x 231

Mobile: 805.857.5614

On Oct 29, 2012, at 6:01 PM, Yuriy Nasida <nas...@live.ru>

�wrote:

Hello guys and thank you for perfect stuff !

I think that I have same issue. I can add DID manually (according your instructions below) and add them to callflow but ... �when I try to make inbound call to new DID, �I recieve '503' sip message. System ask login\password for inbound INVITE but it should not I think. Also I can add DID numbers of USA only. How can I add any DID of other country as well ?

Please advice.

Thanks.

---

From:�Ma...@siteserver.com

To: 2600hz-d...@googlegroups.com
Subject: Re: Adding Numbers to Kazoo
Date: Sat, 27 Oct 2012 21:20:09 +0000

Ok, that did it - now I can add numbers to the account, and in turn assign those numbers to a Call Flow. �Problem is, now that the Call Flow is built, I'm not seeing the call get to our system. �If my only reference to 2600hz is in the offnet database (not a specific carrier on any of the individual accounts) using SIP Auth (User/Pass), how does the system route that call to an account on our system?

-Mark

On Oct 27, 2012, at 2:07 PM, Mark McDonald <Ma...@siteserver.com>

�wrote:

account/96/fa/9c45a8a060f4b371274b1214b11f�96fa9c45a8a060f4b371274b1214b11f

So under that document as well?

-Mark

On Oct 27, 2012, at 1:57 PM, Jon Blanton <jbla...@2600hz.com>

�wrote:

pvt_wnm_allow_additions must be added to the account doc in the "accounts" db and in the account's database

-Jon

Mark McDonald wrote:

:) �I didn't think you'd like that - this is fire walled off and will be rebuilt by the end of the day.

�wrote:

You have not properly added the flag to your account that allows you to add numbers.

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:121 (<0.15099.5>) account is not authorized to create a new number: false

Also don't post your auth-token in the future please :-)

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[28].png>

Darren Schreiber

CEO / Co-Founder

�visit:�www.2600hz.com

�sip:dar...@2600hz.com

�tel:�415-886-7901

From:�Mark McDonald <Ma...@siteserver.com>
Reply-To:�"2600h...@googlegroups.com" <2600h...@googlegroups.com>
Date:�Saturday, October 27, 2012 1:03 PM
To:�"<2600h...@googlegroups.com>" <2600h...@googlegroups.com>

Subject:�Re: Adding Numbers to Kazoo

{"auth_token":"7a393d40195286551d5eadfccc015789","status":"error","message":"unauthorized","error":"500","data":{"unauthorized":"Not authorized to perform requested number operation"},"request_id":"7a96968333d3b10d127bad68d067f1a1"}

Here's the grep from the logs with the most relevant information I could see:

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|crossbar_bindings:489 (<0.15099.5>) routing v1_resource.execute.put.phone_numbers matches v1_resource.execute.put.phone_numbers

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:104 (<0.15099.5>) attempting to create number 8051231234 for account 96fa9c45a8a060f4b371274b1214b11f

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_util:82 (<0.15099.5>) number '8051231234' can be reconciled, proceeding

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_number:737 (<0.15099.5>) The number could not be found

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:121 (<0.15099.5>) account is not authorized to create a new number: false

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_number:707 (<0.15099.5>) Not authorized to perform requested number operation

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:134 (<0.15099.5>) create number prematurely ended: unauthorized

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|v1_util:834 (<0.15099.5>) halting execution here

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|v1_util:801 (<0.15099.5>) generating error 500 response, unauthorized

-Mark

On Oct 27, 2012, at 12:17 PM, Darren Schreiber <dar...@2600hz.com>

�wrote:

Oh, and to find the errors is simple � open the developer tools in your browser (like in Chrome) and look at the network requests. There will be a Request-ID header in the logs. You can grep that request-id in your server-side logs to find out what the error really was.

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[24].png>

Darren Schreiber

CEO / Co-Founder

�visit:�www.2600hz.com

�sip:dar...@2600hz.com

�tel:�415-886-7901

From:�Mark McDonald <Ma...@siteserver.com>
Reply-To:�"2600h...@googlegroups.com" <2600h...@googlegroups.com>
Date:�Saturday, October 27, 2012 12:14 PM
To:�"<2600h...@googlegroups.com>" <2600h...@googlegroups.com>

Subject:�Re: Adding Numbers to Kazoo

There must be something as I can try to add anything (+18055551818, +18185551215, etc) and I get the same error (There was an error when trying to acquire +1xxxxxxxxxx, would you like to retry?) �I'm going to work with this a bit more and will post a more detailed response. �From what I'm able to find via Google Searches, we're also missing some offnet database updates that we need to get in place - right now we're defining a Carrier for each account which we don't want to do.

We're updating our internal wiki as we go through this process start to finish and I'll update the 2600hz wiki as soon as we're completed with the items we found to be lacking in the documentation. �There appear to be huge gaps in regards to the offnet and carrier documents (unless I'm missing something)...

-Mark

On Oct 27, 2012, at 12:04 PM, Darren Schreiber <dar...@2600hz.com>

�wrote:

That means the number is already in the system assigned to another account, or was at some point assigned to another account. It won't allow you to assign it again to a different account unless you clear it out.

Go into your database, port 5984, in the numbers/+1805 database. Find the +1805203xxxx doc. Delete it. Then try to add it again.

If you go on the wiki and search for "Number Lifecycle" you'll see what we're working to implement. It's not complete. It will allow master accounts to hold numbers and sub-accounts to be assigned said numbers, and prevent people from adding numbers who aren't authorized. All the back-end code is actually there but the front-end is not.

There is a separate wiki document for the API calls to do this yourself which I believe do work, in full, and allow the behavior you desire. But the documentation is currently lacking on that, so I'm going to call that incomplete for now as well (unless you can read the Erlang code and figure it out, in which case, feel free to contribute to the docs so that we can get this wrapped up)

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[17].png>

Darren Schreiber

CEO / Co-Founder

�visit:�www.2600hz.com

�sip:dar...@2600hz.com

�tel:�415-886-7901

From:�Mark McDonald <Ma...@siteserver.com>
Reply-To:�"2600h...@googlegroups.com" <2600h...@googlegroups.com>
Date:�Saturday, October 27, 2012 12:01 PM
To:�"<2600h...@googlegroups.com>" <2600h...@googlegroups.com>

Subject:�Re: Adding Numbers to Kazoo

We've added the�pvt_wnm_allow_additions to both the superduper account and the sub account (test customer), which in turn adds the "Add Number" field in the Number Manager, however when trying to add a number (+1805203xxxx), it returns:

There was an error when trying to acquire +1805203xxxx, would you like to retry? (xxxx is obviously the rest of the number)

We're unclear as to whether we should be/there is a way to add a number to the system globally and then under the sub account choose that number and assign it to a Call Flow, or if the number should be directly assigned to the customer account.

-Mark

On Oct 27, 2012, at 11:27 AM, Darren Schreiber <dar...@2600hz.com>

�wrote:

For your private install you must manually modify the the user document in
the database to grant permission to add numbers manually.

https://groups.google.com/forum/#!msg/2600hz-dev/wpHDH9I8WU0/6gzwP-waJjEJ
details how to do it (toward the bottom).



--
Darren Schreiber
CEO / Co-Founder





On 10/27/12 11:25 AM, "Mark McDonald" <Ma...@siteserver.com> wrote:

Both, technically. �It's a private install with the trunks/numbers coming

from your hosted cluster.

-Mark

On Oct 27, 2012, at 11:22 AM, Joshua Goldbard <j...@2600hz.com>
wrote:

Mark,

To be clear, this is a private install, and you are not using our
hosted cluster, correct?

Cheers,
Joshua

Sent from my iPad

On Oct 27, 2012, at 11:20 AM, "Mark McDonald" <ma...@siteserver.com>
wrote:

We've been experimenting with a new Kazoo installation and have
everything working well with the exception of adding external numbers

to an account. �Here's what we did so far:

1) Setup an account with 2600hz and purchased a couple of numbers.
2) Created PBX on the 2600hz platform (specifying FreeSwitch as the
platform type)
3) On our Kazoo Installation, we added a Carrier, specifying the same
SIP Server/Realm and User/Pass as specified in 2600hz's platform.

After doing this, we can place calls out and they seem to work fine.
What we're trying to figure out is how to add numbers to our Kazoo

installation so that the numbers can be assigned to an account. �I've

[BelTex ISP]

Too bad that those kind of things can not be automated.

Yuriy Nasida schreef op 20-1-2014 18:15:

No problems.

I think you need to add your carrier to offnet database manually.

https://2600hz.atlassian.net/wiki/display/docs/Global+Resources

P.S. It is for global carriers.

Yep I also could not get button "add number" visible :) The reason here - you must to use your 1st account which was created. Only 1st account has this button.

---

Date: Mon, 20 Jan 2014 17:15:09 +0100
From: in...@beltex.nl
To: 2600h...@googlegroups.com
Subject: Re: Adding Numbers to Kazoo

Hi and thanks

I have two trunks and one requires registration for inbound, outbound works great but inbound not as the trunk is not registered.

I have been trying to get the add number button visible for some time now ))))) No luck yet

So inbound routing is not yet working, but ill prop get it working soon

Yuriy Nasida schreef op 20-1-2014 16:55:

Martin,

You don't need to do this with v3. It's old tread :)

You can add DID via admin account (button 'Add number' in 'Number Manager' appl ).

Next, you will have to open inbound carrier IP in database manually. Plus don't forget to add IP adreess of kamailio as well

Look at this manual�https://2600hz.atlassian.net/wiki/display/docs/Inbound+Calls+Fail

---

Date: Sun, 19 Jan 2014 15:43:45 -0800
From: in...@beltex.nl
To: 2600h...@googlegroups.com
Subject: Re: Adding Numbers to Kazoo

where should we do it in v3??

Op dinsdag 30 oktober 2012 02:07:22 UTC+1 schreef SupermanSC:

Yuriy,

That's where I was a bit confused - Kazoo won't handle or configure the SIP registrations - you'll need to do this on each of your FreeSwitch servers. �You can do this by creating a /gateways directory in /etc/freeswitch and creating an XML file (2600.xml for example). �In there, put the following:

<include>

� <gateway>

� � <param name="realm" value="yoursipealm.sip.2600hz.com"/>

� � <param name="username" value="youruser"/>

� � <param name="password" value="yourpass"/>

� � <param name="register" value="true"/>

� </gateway>

</include>

Either restart Freeswitch, or login (cli) and reloadxml / reload mod_sofia. �Freeswitch will now maintain the connection to 2600's SIP servers and accept incoming INVITE's. �Not sure on what other country's are supported on 2600hz's platform - I'll leave that for someone else.

-Mark McDonald

ma...@siteserver.com

Office: 805.578.2000 x 231

Mobile: 805.857.5614

On Oct 29, 2012, at 6:01 PM, Yuriy Nasida <nas...@live.ru>

�wrote:

Hello guys and thank you for perfect stuff !

I think that I have same issue. I can add DID manually (according your instructions below) and add them to callflow but ... �when I try to make inbound call to new DID, �I recieve '503' sip message. System ask login\password for inbound INVITE but it should not I think. Also I can add DID numbers of USA only. How can I add any DID of other country as well ?

Please advice.

Thanks.

---

From:�Ma...@siteserver.com

To: 2600hz-d...@googlegroups.com
Subject: Re: Adding Numbers to Kazoo
Date: Sat, 27 Oct 2012 21:20:09 +0000

Ok, that did it - now I can add numbers to the account, and in turn assign those numbers to a Call Flow. �Problem is, now that the Call Flow is built, I'm not seeing the call get to our system. �If my only reference to 2600hz is in the offnet database (not a specific carrier on any of the individual accounts) using SIP Auth (User/Pass), how does the system route that call to an account on our system?

-Mark

On Oct 27, 2012, at 2:07 PM, Mark McDonald <Ma...@siteserver.com>

�wrote:

account/96/fa/9c45a8a060f4b371274b1214b11f�96fa9c45a8a060f4b371274b1214b11f

So under that document as well?

-Mark

On Oct 27, 2012, at 1:57 PM, Jon Blanton <jbla...@2600hz.com>

�wrote:

pvt_wnm_allow_additions must be added to the account doc in the "accounts" db and in the account's database

-Jon

Mark McDonald wrote:

:) �I didn't think you'd like that - this is fire walled off and will be rebuilt by the end of the day.

�wrote:

You have not properly added the flag to your account that allows you to add numbers.

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:121 (<0.15099.5>) account is not authorized to create a new number: false

Also don't post your auth-token in the future please :-)

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[28].png>

Darren Schreiber

CEO / Co-Founder

�visit:�www.2600hz.com

�sip:dar...@2600hz.com

�tel:�415-886-7901

From:�Mark McDonald <Ma...@siteserver.com>
Reply-To:�"2600h...@googlegroups.com" <2600h...@googlegroups.com>
Date:�Saturday, October 27, 2012 1:03 PM
To:�"<2600h...@googlegroups.com>" <2600h...@googlegroups.com>

Subject:�Re: Adding Numbers to Kazoo

{"auth_token":"7a393d40195286551d5eadfccc015789","status":"error","message":"unauthorized","error":"500","data":{"unauthorized":"Not authorized to perform requested number operation"},"request_id":"7a96968333d3b10d127bad68d067f1a1"}

Here's the grep from the logs with the most relevant information I could see:

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|crossbar_bindings:489 (<0.15099.5>) routing v1_resource.execute.put.phone_numbers matches v1_resource.execute.put.phone_numbers

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:104 (<0.15099.5>) attempting to create number 8051231234 for account 96fa9c45a8a060f4b371274b1214b11f

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_util:82 (<0.15099.5>) number '8051231234' can be reconciled, proceeding

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_number:737 (<0.15099.5>) The number could not be found

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:121 (<0.15099.5>) account is not authorized to create a new number: false

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wnm_number:707 (<0.15099.5>) Not authorized to perform requested number operation

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|wh_number_manager:134 (<0.15099.5>) create number prematurely ended: unauthorized

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|v1_util:834 (<0.15099.5>) halting execution here

Oct 27 19:58:43 db01 2600hz[3062]: |7a96968333d3b10d127bad68d067f1a1|v1_util:801 (<0.15099.5>) generating error 500 response, unauthorized

-Mark

On Oct 27, 2012, at 12:17 PM, Darren Schreiber <dar...@2600hz.com>

�wrote:

Oh, and to find the errors is simple � open the developer tools in your browser (like in Chrome) and look at the network requests. There will be a Request-ID header in the logs. You can grep that request-id in your server-side logs to find out what the error really was.

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[24].png>

Darren Schreiber

CEO / Co-Founder

�visit:�www.2600hz.com

�sip:dar...@2600hz.com

�tel:�415-886-7901

From:�Mark McDonald <Ma...@siteserver.com>
Reply-To:�"2600h...@googlegroups.com" <2600h...@googlegroups.com>
Date:�Saturday, October 27, 2012 12:14 PM
To:�"<2600h...@googlegroups.com>" <2600h...@googlegroups.com>

Subject:�Re: Adding Numbers to Kazoo

There must be something as I can try to add anything (+18055551818, +18185551215, etc) and I get the same error (There was an error when trying to acquire +1xxxxxxxxxx, would you like to retry?) �I'm going to work with this a bit more and will post a more detailed response. �From what I'm able to find via Google Searches, we're also missing some offnet database updates that we need to get in place - right now we're defining a Carrier for each account which we don't want to do.

We're updating our internal wiki as we go through this process start to finish and I'll update the 2600hz wiki as soon as we're completed with the items we found to be lacking in the documentation. �There appear to be huge gaps in regards to the offnet and carrier documents (unless I'm missing something)...

-Mark

On Oct 27, 2012, at 12:04 PM, Darren Schreiber <dar...@2600hz.com>

�wrote:

That means the number is already in the system assigned to another account, or was at some point assigned to another account. It won't allow you to assign it again to a different account unless you clear it out.

Go into your database, port 5984, in the numbers/+1805 database. Find the +1805203xxxx doc. Delete it. Then try to add it again.

If you go on the wiki and search for "Number Lifecycle" you'll see what we're working to implement. It's not complete. It will allow master accounts to hold numbers and sub-accounts to be assigned said numbers, and prevent people from adding numbers who aren't authorized. All the back-end code is actually there but the front-end is not.

There is a separate wiki document for the API calls to do this yourself which I believe do work, in full, and allow the behavior you desire. But the documentation is currently lacking on that, so I'm going to call that incomplete for now as well (unless you can read the Erlang code and figure it out, in which case, feel free to contribute to the docs so that we can get this wrapped up)

--

<773BD915-519F-42B9-8DB7-78EE7BD2EAC4[17].png>

Darren Schreiber

CEO / Co-Founder

�visit:�www.2600hz.com

�sip:dar...@2600hz.com

�tel:�415-886-7901

From:�Mark McDonald <Ma...@siteserver.com>
Reply-To:�"2600h...@googlegroups.com" <2600h...@googlegroups.com>
Date:�Saturday, October 27, 2012 12:01 PM
To:�"<2600h...@googlegroups.com>" <2600h...@googlegroups.com>

Subject:�Re: Adding Numbers to Kazoo

We've added the�pvt_wnm_allow_additions to both the superduper account and the sub account (test customer), which in turn adds the "Add Number" field in the Number Manager, however when trying to add a number (+1805203xxxx), it returns:

There was an error when trying to acquire +1805203xxxx, would you like to retry? (xxxx is obviously the rest of the number)

We're unclear as to whether we should be/there is a way to add a number to the system globally and then under the sub account choose that number and assign it to a Call Flow, or if the number should be directly assigned to the customer account.

-Mark

On Oct 27, 2012, at 11:27 AM, Darren Schreiber <dar...@2600hz.com>

�wrote:

For your private install you must manually modify the the user document in
the database to grant permission to add numbers manually.

https://groups.google.com/forum/#!msg/2600hz-dev/wpHDH9I8WU0/6gzwP-waJjEJ
details how to do it (toward the bottom).



--
Darren Schreiber
CEO / Co-Founder





On 10/27/12 11:25 AM, "Mark McDonald" <Ma...@siteserver.com> wrote:

Both, technically. �It's a private install with the trunks/numbers coming

from your hosted cluster.

-Mark

On Oct 27, 2012, at 11:22 AM, Joshua Goldbard <j...@2600hz.com>
wrote:

Mark,

To be clear, this is a private install, and you are not using our
hosted cluster, correct?

Cheers,
Joshua

Sent from my iPad

On Oct 27, 2012, at 11:20 AM, "Mark McDonald" <ma...@siteserver.com>
wrote:

We've been experimenting with a new Kazoo installation and have
everything working well with the exception of adding external numbers

to an account. �Here's what we did so far:

1) Setup an account with 2600hz and purchased a couple of numbers.
2) Created PBX on the 2600hz platform (specifying FreeSwitch as the
platform type)
3) On our Kazoo Installation, we added a Carrier, specifying the same
SIP Server/Realm and User/Pass as specified in 2600hz's platform.

After doing this, we can place calls out and they seem to work fine.
What we're trying to figure out is how to add numbers to our Kazoo

installation so that the numbers can be assigned to an account. �I've