internationalisation

[Yumminova Telecom]

Hi

Can someone shed a light on the future?

Im thinking on how to deal with internationalisation and especially how Kazoo will deal with that if it will at one time.
(will it?)

So we can create regexes in number_manager, but mostly for specific country´s if i look at them.
Im wondering if the dev team has plans to change this, i can imagine that if u run a cloud/cluster, its kind of silly to deploy a new one per country for that purpose alone (i can image having a cluster per country for other reasons though) Also, one may have clients that are based in a place and have numbers from different country´s

And it kind of takes the cloud out of the cloud.

So i have some ideas but i need to know the vision of the dev team on it, else it wold be wasted energy.

Comming from a porta system, i liked the way they do it, being able to specify the country, region and city so that a client can dial as they are used to.
So if thats something kazoo can support, i can create a tool to create rules easily and give them.

I suppose that if each account would have its own number_manager doc, we could do it rather easily (im no programmer )) then we could set the proper regexes in that doc and be done with it.

Can someone react on this, so i can decide what to do if i can do smth?

[Luis Azedo]

Hi,

there is already support for this in kazoo.

you can configure a dial_plan json object by account/user/device here's an example

dial_plan : {

   "^(\\d{9})$": {

       "description": "Portugal",

       "prefix": "+351"

   },

   "^(\\d{10})$": {

       "description": "USA",

       "prefix": "+1"

   },

   "^0(\\d{9,})$": {

       "description": "UK",

       "prefix": "+44"

   }

}

this dial plan is applied for outbound calls.

so what's missing ?

global list of country/regexes that would be copied or referenced by dial_plan object to account/user/device, but i think we'll get to that.

hope this helps.

--
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/d/optout.

[James Aimonetti]

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

On 2014-08-21 10:58, Luis Azedo wrote:
> Hi,
>
> there is already support for this in kazoo. you can configure a
> dial_plan json object by account/user/device here's an example
>
> dial_plan : { "^(\\d{9})$": { "description": "Portugal", "prefix":
> "+351" }, "^(\\d{10})$": { "description": "USA", "prefix": "+1" },
> "^0(\\d{9,})$": { "description": "UK", "prefix": "+44" } }
>
> this dial plan is applied for outbound calls.
>
> so what's missing ?

Probably documentation!!! :)

- --
James Aimonetti
Lead Systems Architect / Impressionable Scallywag
"I thought I fixed that"

2600Hz | http://2600hz.com
sip:ja...@2600hz.com
tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJT9jSsAAoJENTKa+JPXCVgZ/YIAJy6ELop+8h8eJwHye0CyLjQ
LFOAV8eAniau9Myr5sH44bl6aXtggNQUcasB68rMciqPSztItvO8mIsS4iPvB6rj
92zec3HxBTDXB5mhpmMUaj08IQlJb9VZDxParkhZ6JTjRnR7TVfFjJ/9LYX0MFq/
OidIew7INFJV+zRleQEUqJTVeDy2RD+ErkdHEN9x7Umo9qaWPFfGRpAyCnt8r4iL
xvGgND//X4SkOl7QQaEjwcBYeh4WIY02C7t9bM/6aeoFpwA308B+5EwVDLYTLDnp
BYxSyto4tW6/m2MRPJ1QrY3kQ1nfPjCe/1FNo0F1BQj0vHYFaIAhNdX/6CaUWtM=
=Co4l
-----END PGP SIGNATURE-----

[James Aimonetti]

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

Perhaps more helpful, Luis, could you update
https://github.com/2600hz/kazoo/blob/master/applications/crossbar/doc/internationalization/numbers.md
with a section on setting per-device/user/account dialplans?

iQEcBAEBAgAGBQJT9jUHAAoJENTKa+JPXCVgSdoH/3CKzYFQChKopxsvvWHFQzOB
j7noZ1GZwLPaTwQHQo9o+ZySP3LEPTDKa/976zxGqk2kFsefc6Q7FMXswna0lsFD
SGMPKBwRholwX2JkMvUNgjRin9t+fVKhaweRzYN0J/SMNnXvDCEhqQCLzxaWI+31
QgbiPMjU/09qyL2ny6i80gDN5GF+1qv0zm2oosh7nKwWNYBXW10AhJDMzjcrJuvQ
hde0W8FILWnXgRfb+EmpmWheY+6RXXIIbRroTykoU/510MQiktgTCXsA/zjH5rlK
5U1t3PE2WTjvwXlmBsrgHjUK5Tr3eT5wqnqta3emdwuwADPPxEwjMUwajCxDa4g=
=VaTQ
-----END PGP SIGNATURE-----

[Yumminova Telecom]

Thats great info!! Its a bit vague for me to implement it but after there are some instructions i woud; certainly manage.

If u provide the docs i can update that .md file, i forked already, i will also add it to the wiki

Thanks!

Op donderdag 21 augustus 2014 20:06:02 UTC+2 schreef James Aimonetti:

sip:...@2600hz.com

[James Aimonetti]

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

We're actually moving docs to these markdown files, and will be
building a proper docs website, mined from these files. So any updates
should be targeted here in the kazoo repo. We're finding keeping docs
in the repo is more convenient to developers actually keeping them up
to date, because we can catch it in code review that the developer
hasn't added/updated the appropriate docs.

These docs will be a great place for non-Erlang folks to contribute,
especially these more "user guide" style docs (versus the reference
docs in "/crossbar/doc/").

Migrating docs off the wiki to the kazoo apps' doc folders would be
greatly appreciated too. Just issue a pull request per migrated doc so
we don't have to slog through a ton of docs to accept one pull request! :)

Let us know if you have any questions or ideas for improvement.

On 2014-08-21 11:15, Yumminova Telecom wrote:
> Thats great info!! Its a bit vague for me to implement it but after
> there are some instructions i woud; certainly manage.
>
> If u provide the docs i can update that .md file, i forked already,
> i will also add it to the wiki
>
> Thanks!
>
> Op donderdag 21 augustus 2014 20:06:02 UTC+2 schreef James
> Aimonetti:
>>

>>>>>> <javascript:>. For more options, visit

>>>>>> https://groups.google.com/d/optout.
>>>>>>
>>>>
>>>>
>>>>
>>>>
>
>>
>

- --
James Aimonetti
Lead Systems Architect / Impressionable Scallywag
"I thought I fixed that"

2600Hz | http://2600hz.com

sip:ja...@2600hz.com

tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJT9j1pAAoJENTKa+JPXCVg+csH/iUTKjJIqVNdv46/fdycfbmJ
BXrTYl8PTgqOxNvKbFUVpyDfbPpXaqVel5RN1vNJ66u5se/j/aKg6ekr7zBFh8AG
3MTzENYPDOdl9bMsX6xDDsuZh5x2oj/9JN5HJMvUD521LbnHeF6Q5RZVFkgqfQzY
YYIx25w1ErnM2BUohlzFTKfrPW9dJR2Si+neF6cytafIcCfTVKCK0llgcjSi1M62
htfepJowEdmt6wTGdPuEiIAi+6gFalYhXgiAy6HhIs8ICrDeSJbZZvANy12S785B
cVp13HizQag9UHa76QllNF8NXXRka0s7vlw/goMOhc7vOf7JOLW1EtFjj0ZEZmw=
=n1Kw
-----END PGP SIGNATURE-----

[Yumminova]

Hi James
James Aimonetti schreef op 21-8-2014 20:41:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> We're actually moving docs to these markdown files, and will be
> building a proper docs website, mined from these files. So any updates
> should be targeted here in the kazoo repo. We're finding keeping docs
> in the repo is more convenient to developers actually keeping them up
> to date, because we can catch it in code review that the developer
> hasn't added/updated the appropriate docs.

I understand that, and a good idea, its must be "hell" to keep up

>
> These docs will be a great place for non-Erlang folks to contribute,
> especially these more "user guide" style docs (versus the reference
> docs in "/crossbar/doc/").

But that requires ready knowledge of what im looking at i suppose, where
would i migrate a " my phone is not registering" walkthrough?
I would love to help, ill check it out and see what i can do

[Yumminova]

per example:

applications/acdc/doc/

I would migrate how to articles and such about call center there?
Do you need a certain structure, to seperate the tech stuff from the
user stuff?

James Aimonetti schreef op 21-8-2014 20:41:

[James Aimonetti]

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

On 2014-08-21 11:50, Yumminova wrote:
> per example:
>
> applications/acdc/doc/
>
> I would migrate how to articles and such about call center there?
> Do you need a certain structure, to seperate the tech stuff from
> the user stuff?

This is what we're trying to figure out. For now, better to have the
content somewhere in the repo than not. We can always re-arrange it
when we have a better layout plan. Plus, I find 'grep' to be the best
search engine! :)

Put it in the app you think most appropriate (problems registering
might go under /applications/registrar/doc/troubleshooting.md for
instance, stuck BLF troubleshooting in
/applications/omnipresence/doc/troubleshooting.md).

We're not married to a format or layout, so suggestions are welcome
for improving it. For my money, having it on my filesystem to searched
using all the *nix text tools is the best. Maybe we can even create
man pages one day!

>
>
> James Aimonetti schreef op 21-8-2014 20:41: We're actually moving

> -- James Aimonetti Lead Systems Architect / Impressionable
> Scallywag "I thought I fixed that"
>
> 2600Hz | http://2600hz.com sip:ja...@2600hz.com tel:415.886.7905
> irc:mc_ @ freenode
>>
>

- --
James Aimonetti
Lead Systems Architect / Impressionable Scallywag
"I thought I fixed that"

2600Hz | http://2600hz.com
sip:ja...@2600hz.com
tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJT9k/QAAoJENTKa+JPXCVghfIH+gIRwlhZcCfCsupHbl00apQJ
OWzw/O0ddBTQG4fKk8VaTSYyq4NhKnatfvVniPclYJJrk1DGhQtO8GFqFJpH28C5
K0fIqlmeLsSvG2tasPx/Y22wSRA/f6V0VhgqGdOMYfnIJwmj6K3kNboGMhKukI+V
BqtpG3nz/qgmmCnJgOMxjd8IKYfJT/Un/L1/7iBX44ioqU795Q7UgQkor2xgPhIh
0H98/KOVIi3GhR1YomWCJm9KBbthXmWsP7EBo3JWOp96knJ2igLGdUGj26RiRilb
zla7VpQUR0sYZZP1YedjeypOz5DX5iZy0e8Jr/gMFIm/QAZz6CF/o7ajQRyTYbA=
=papJ
-----END PGP SIGNATURE-----

[Yumminova]

haha but then u would have to find people to read them ))))

I will give it a go, somewhere this week, in my spare time ))


James Aimonetti schreef op 21-8-2014 22:00:

[Yumminova Telecom]

Hi James

I get an error when pulling via Git
Clone of 'g...@github.com:2600hz/cluster.git' into submodule path 'whapps/cluster' failed

That prevents my from pulling fresh sources,

I see that the cluster files are gone and wont be available, as seems to be the case with whapps phone, but how can i ignore them and why are they in the repo?

But the reason i wanted to pull is to point u to  https://github.com/floere/phony

it might be useless, but it might help a lot with normalizations of anything to E.164, solving that once and for all.
Of course i am no developer, and actually have no clue )) Keep that in mind so u can smile instead of look grumpy ))

Op donderdag 21 augustus 2014 22:20:58 UTC+2 schreef Yumminova Telecom:

[Yumminova Telecom]

Hi Luis,

It would help a lot if i knew where to insert that info, that would be great!

Op donderdag 21 augustus 2014 19:58:54 UTC+2 schreef Luis Azedo:

[Luis Azedo]

Hi,

use the account, user , device documents inside accountdb

[Yumminova]

Thanks,

Is there a preference? I can imagine that per example the user entry could be valid for all devices from that user.
Feels kind of silly to set it per device, but if needed no problem there.

Could i set it in the design docs to have it as default?

Thanks Luis!

Luis Azedo schreef op 23-8-2014 18:24:

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/_P8crisJapw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 2600hz-dev+...@googlegroups.com.

[Luis Azedo]

Hi,

we apply the first in order , device -> user -> account.

you can set it one time at account level if all your users / devices are in the same country.

[Yumminova]

Great! Thanks so much for explaining this!

Ill update the docs right away

Luis Azedo schreef op 23-8-2014 19:03:

[Yumminova Telecom]

Luis i know im spamming the list, sorry about that.

I have created my first doc on this subject and created a pull request.
Please review this if posible, if u agree mostly on what i did i can create some more, if not i can change but do not have to waste more time on doing it wrong

Op zaterdag 23 augustus 2014 19:03:57 UTC+2 schreef Luis Azedo:

[Yumminova Telecom]

HI Luis,

Is there a way not only to prefix but to strip a leading zero?
Or should that be handled by the E164 convertors in the number_manager?

Op donderdag 21 augustus 2014 19:58:54 UTC+2 schreef Luis Azedo:

Hi,

[Eamon]

Is this not already covered above in Luis post
account/user/device dial plan ?

[M Splinter Yumminova Telecom]

Concerning stripping, in don't see that

Op 24 aug. 2014 22:36 schreef "Eamon" <eamon....@gmail.com>:

Is this not already covered above in Luis post
account/user/device dial plan ?

--
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/_P8crisJapw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 2600hz-dev+...@googlegroups.com.

[Luis Azedo]

Hi,

check the UK sample, it is stripping the leading 0.

On Sun, Aug 24, 2014 at 9:30 PM, Eamon <eamon....@gmail.com> wrote:

Is this not already covered above in Luis post
account/user/device dial plan ?

[Yumminova]

My bad!! Sorry, i did not see that as i thought regexes could not do that at all ))

Anyway, i have created a doc on it an issued a pull request, thanks for your time

Luis Azedo schreef op 24-8-2014 23:13:

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/_P8crisJapw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 2600hz-dev+...@googlegroups.com.

[Eamon]

Hi 

I added the UK example to the account,user,and device but it didn't work, am i missing something else? the device used was under the admin account

   "^0(\\d{9,})$": {

       "description": "UK",

       "prefix": "+44"

[Yumminova]

Although documentation of Kazoo does not state this, multiple sources state that one should not use the admin account for usage, but create at least one account below that to work with.
Why? No idea
Second: is this what u have put in the DB doc? Im missing some lines that are in the example given.

After u made the changes u must issue a sup command, which one is unclear to me so i could not put that in the doc about this. Someone might add that though.
I just run a whole bunch of them ))

After that u need to check your freeswitch debug log plus your platform log to see whats happening with a call.
U can also check  the call history in the GUI, u should see two legs there, i would suspect that the inbound leg would show the dialed number and the outbound leg the transformed.

Take care: dealing with this requires a math brain, regex experience and nice configured devices. many softphones do some translation like adding a + sign, if u dont take that into account u will search in the wrong places )

So better really check locally and on the platform what your client sents to the platform, then see what kazoo bakes of it depending on the regexes in the account, but also the reconsile regex (is that true???)

From that u would be able to get it going, but again u need to take into account a lot of variables.

Im having work done on a dial plan generator that would create those rules for us, but it will take some time as im no programmer.

The local rules i have them here, for almost the complete world, it would be great if we could set the country code and region code and some rules on what to do in the gui, and run a javascript to then create and store that rule on the account, user or device. I tried to have someone look at the GUI and how to add something in a clean way, but not many developers are familiair with how the GUI is done now.

Eamon schreef op 25-8-2014 15:52:

[Luis Azedo]

Hi Eamon,

why do you say it didn't work ? it didn't translate "0...." to "+44...." ?

if you're adding the values directly in the db with futton you will need to flush the caches.

sup callflow_maintenance flush

sup crossbar_maintenance flush

sup whistle_couch_maintenance flush

[Eamon]

Hi Luis

Yes number did not translate tried sub account device and flush cache 

it works if i update e164 converter in num_manager doc and also if i dial the full e164 number so the outbound trunk is ok

Eamon

[Luis Azedo]

but how did you confirmed that it didn't translate ?

do you have a device document you can share so i can check the the dial_plan ?

[Yumminova]

Better do it on account level, unless u only have people from that region on your platform.
I must say that it id not work for us yet as well, but im looking into it.

If u want Luis, and share your ip, i can give u access to futon, but here is the file, we only test on the first line the rest needs to be updated, taken from an other system

we dial 0622222222

{
   "_id": "fd0557c26c70451fe10281c8bbcfd8c8",
   "_rev": "25-fb26bd459dc95b9d7be451fdbfb478a4",
   "dial_plan": {
       "^+0(\\d{9,})$": {
           "description": "Mob test",
           "prefix": "+31"
       },
       "^\\+316\\d{8}$": {
           "description": "NLTo Mobile",
           "prefix": "+316"
       },
       "^\\+31800\\d{4,7}$": {
           "description": "NLTo Toll Free",
           "prefix": "+31800"
       },
       "^\\+3190\\d{5,8}|8[47]\\d{7}$": {
           "description": "NLTo Service",
           "prefix": "+3190"
       },
       "^\\+31([1-57]\\d{4,8}|8[58]\\d{7})$": {
           "description": "NLTo International",
           "prefix": "+31"
       },
       "^\\+(112|14\\d{2,4})$": {
           "description": "NLTo Special, emergency DOUBTS ON FORMAT may need to use safety region code base don the client location",
           "prefix": "+"
       }
   },
   "call_restriction": {
       "tollfree_us": {
           "action": "inherit"
       },
       "toll_us": {
           "action": "inherit"
       },
       "emergency": {
           "action": "inherit"
       },
       "caribbean": {
           "action": "inherit"
       },
       "did_us": {
           "action": "inherit"
       },
       "international": {
           "action": "inherit"
       },
       "unknown": {
           "action": "inherit"
       }
   },
   "notifications": {
       "voicemail_to_email": {
       },
       "fax_to_email": {
       },
       "deregister": {
       },
       "first_occurrence": {
           "sent_initial_registration": true
       }
   },
   "provision": {
   },
   "apps": [
   ],
   "name": "obscured",
   "realm": "sip.obscured.nl",
   "billing_id": "e1cd20c3a257e7fb6566d08d0c5fcf4b",
   "ui_metadata": {
       "ui": "kazoo-ui",
       "version": "v3.14-3"
   },
   "timezone": "America/Los_Angeles",
   "caller_id": {
   },
   "caller_id_options": {
   },
   "media": {
       "bypass_media": "auto"
   },
   "music_on_hold": {
   },
   "id": "fd0557c26c70451fe10281c8bbcfd8c8",
   "created": 63575596785,
   "available_apps": [
       "voip",
       "userportal",
       "accounts",
       "developer",
       "numbers"
   ],
   "pvt_whitelabel_domain": "manage.obscured.nl",
   "pvt_account_id": "fd0557c26c70451fe10281c8bbcfd8c8",
   "pvt_account_db": "account%2Ffd%2F05%2F57c26c70451fe10281c8bbcfd8c8",
   "pvt_modified": 63575865282,
   "pvt_created": 63575596785,
   "pvt_enabled": true,
   "pvt_tree": [
       "e1cd20c3a257e7fb6566d08d0c5fcf4b"
   ],
   "pvt_api_key": "05c8aac5089e47252267f0dc1de0bd2039199b8663bbb9738e77ba3dc0b39cfe",
   "pvt_vsn": "1",
   "pvt_type": "account"
}

Luis Azedo schreef op 25-8-2014 19:05:

[Luis Azedo]

what kazoo version are you running ?

[Yumminova]

Latest i could get, installed 4 days ago

R15B i think is installed

Luis Azedo schreef op 25-8-2014 19:20:

[Luis Azedo]

kazoo version not erlang version.

yum info Kazoo*

[Yumminova]

I cant issue that command right now, of of my repo´s is down, the 2600hz repo in this case

oh it worked, (not the 2600hz repo)

Installed Packages
Name        : kazoo-R15B (why y thought it was Kazoo version)
Arch        : x86_64
Version     : 3.12
Release     : 23.el6
Size        : 161 M
Repo        : installed
From repo   : 2600hz_R15B
Summary     : Kazoo telephony platform
URL         : http://www.2600hz.org/
License     : MPL1.1
Description : Kazoo

Name        : kazoo-configs
Arch        : noarch
Version     : 3.0
Release     : 70.el6
Size        : 468 k
Repo        : installed
From repo   : 2600hz_base
Summary     : Configuration for the Kazoo platform
URL         : http://www.2600hz.org/
License     : MPL1.1
Description : Configuration files for the various components that make up the Kazoo platform.

Name        : kazoo-json-c
Arch        : x86_64
Version     : master
Release     : 0.el6
Size        : 111 k
Repo        : installed
From repo   : 2600hz_base
Summary     : A JSON implementation in C
URL         : https://github.com/json-c/json-c/wiki
License     : MIT
Description : JSON-C implements a reference counting object model that allows you to easily
            : construct JSON objects in C, output them as JSON formatted strings and parse
            : JSON formatted strings back into the C representation of JSON objects.

Name        : kazoo-kamailio
Arch        : x86_64
Version     : 4.0
Release     : 46.el6
Size        : 9.5 M
Repo        : installed
From repo   : 2600hz_base
Summary     : Kamailio (former OpenSER) - the Open Source SIP Server
URL         : http://kamailio.org/
License     : GPL
Description : Kamailio (former OpenSER) is an Open Source SIP Server released under GPL, able
            : to handle thousands of call setups per second. Among features: asynchronous TCP,
            : UDP and SCTP, secure communication via TLS for VoIP (voice, video); IPv4 and
            : IPv6; SIMPLE instant messaging and presence with embedded XCAP server and MSRP
            : relay; ENUM; DID and least cost routing; load balancing; routing fail-over;
            : accounting, authentication and authorization; support for many backend systems
            : such as MySQL, Postgres, Oracle, Radius, LDAP, Redis, Cassandra; XMLRPC control
            : interface, SNMP monitoring. It can be used to build large VoIP servicing
            : platforms or to scale up SIP-to-PSTN gateways, PBX systems or media servers
            : like Asteriskâ
                            ¢, FreeSWITCHâ
                                          ¢ or SEMS.

Name        : kazoo-librabbitmq
Arch        : x86_64
Version     : master
Release     : 0.el6
Size        : 261 k
Repo        : installed
From repo   : 2600hz_base
Summary     : RabbitMQ C AMQP client library
URL         : https://github.com/alanxz/rabbitmq-c
License     : MIT
Description : Kazoo RabbitMQ C AMQP client library

Name        : kazoo-ui
Arch        : noarch
Version     : v3.14
Release     : 3.el6
Size        : 5.7 M
Repo        : installed
From repo   : 2600hz_base
Summary     : Kazoo User Interface
URL         : http://www.2600hz.org/
License     : MPL1.1
Description : Kazoo user interface.

Available Packages
Name        : kazoo-bigcouch-R15B
Arch        : x86_64
Version     : 0.4.x
Release     : 1.el6
Size        : 24 M
Repo        : 2600hz_R15B
Summary     : Bigcouch database for Kazoo
URL         : http://www.2600hz.org/
License     : MPL1.1
Description : BigCouch is a dynamo-style distributed database based on Apache CouchDB

Name        : kazoo-freeswitch-R15B
Arch        : x86_64
Version     : 1.4.6
Release     : 4.el6
Size        : 14 M
Repo        : 2600hz_R15B
Summary     : FreeSWITCH open source telephony platform
URL         : http://www.freeswitch.org/
License     : MPL1.1
Description : This is a build of FreeSWITCH (http://www.freeswitch.org/) by 2600hz.  All credit and respect goes to
            : those hard-working folks!  Hope to see you at ClueCon (https://www.cluecon.com/)
            :         --Karl Senior Bit Herder 2600hz
            :
            : FreeSWITCH is an open source telephony platform designed to facilitate the creation of voice
            : and chat driven products scaling from a soft-phone up to a soft-switch.  It can be used as a
            : simple switching engine, a media gateway or a media server to host IVR applications using
            : simple scripts or XML to control the callflow.
            :
            : We support various communication technologies such as SIP, H.323 and GoogleTalk making
            : it easy to interface with other open source PBX systems such as sipX, OpenPBX, Bayonne, YATE or Asterisk.
            :
            : We also support both wide and narrow band codecs making it an ideal solution to bridge legacy
            : devices to the future. The voice channels and the conference bridge module all can operate
            : at 8, 16 or 32 kilohertz and can bridge channels of different rates.
            :
            : FreeSWITCH runs on several operating systems including Windows, Max OS X, Linux, BSD and Solaris
            : on both 32 and 64 bit platforms.
            :
            : Our developers are heavily involved in open source and have donated code and other resources to
            : other telephony projects including Kazoo, sipXecs, OpenSER, Asterisk, CodeWeaver and OpenPBX.

Name        : kazoo-freeswitch-R15B-debuginfo
Arch        : x86_64
Version     : 1.4.6
Release     : 4.el6
Size        : 26 M
Repo        : 2600hz_R15B
Summary     : Debug information for package kazoo-freeswitch-R15B
URL         : http://www.freeswitch.org/
License     : MPL1.1
Description : This package provides debug information for package kazoo-freeswitch-R15B.
            : Debug information is useful when developing applications that use this
            : package or when debugging this package.

Name        : kazoo-freeswitch-R15B-devel
Arch        : x86_64
Version     : 1.4.6
Release     : 4.el6
Size        : 147 k
Repo        : 2600hz_R15B
Summary     : Development package for FreeSWITCH open source telephony platform
URL         : http://www.freeswitch.org/
License     : MPL1.1
Description : FreeSWITCH development files

Name        : kazoo-json-c-devel
Arch        : x86_64
Version     : master
Release     : 0.el6
Size        : 17 k
Repo        : 2600hz_base
Summary     : Development headers and library for json-c
URL         : https://github.com/json-c/json-c/wiki
License     : MIT
Description : This package contains the development headers and library for json-c.

Name        : kazoo-kamailio-debuginfo
Arch        : x86_64
Version     : 4.0
Release     : 46.el6
Size        : 4.0 M
Repo        : 2600hz_base
Summary     : Debug information for package kazoo-kamailio
URL         : http://kamailio.org/
License     : GPL
Description : This package provides debug information for package kazoo-kamailio.
            : Debug information is useful when developing applications that use this
            : package or when debugging this package.

Name        : kazoo-librabbitmq-devel
Arch        : x86_64
Version     : master
Release     : 0.el6
Size        : 42 k
Repo        : 2600hz_base
Summary     : Development files for the librabbitmq package
URL         : https://github.com/alanxz/rabbitmq-c
License     : MIT
Description : RabbitMQ C AMQP client library. This package contains files needed to
            : develop applications using librabbitmq.

Name        : kazoo-prompts
Arch        : noarch
Version     : 3.0
Release     : 0.el6
Size        : 17 M
Repo        : 2600hz_base
Summary     : Audio prompts for the Kazoo platform
URL         : http://www.2600hz.org/
License     : MPL1.1
Description : Audo prompts files to match the voice streamed from Kazoo Media Manager.

Luis Azedo schreef op 25-8-2014 19:37:

yum info Kazoo*

[Darren Schreiber]

The 2600hz repo is being worked on. One of our hardware nodes went down. There are two nodes, though, so it should still go through, but if not, it will be fixed as soon as our support company fixes it.

[Yumminova]

Ok, thats sad! Good luck with that!

Darren Schreiber schreef op 25-8-2014 19:47:

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/_P8crisJapw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 2600hz-dev+...@googlegroups.com.

[Luis Azedo]

it should work, i have it working.

can you share the no_match callflow for that account ?

[Yumminova]

the second node has the same ip as your webserver, but i could not find a repo there ))

No stress it give me a good reason to try cloudconverter on Kazoo

Darren Schreiber schreef op 25-8-2014 19:47:

The 2600hz repo is being worked on. One of our hardware nodes went down. There are two nodes, though, so it should still go through, but if not, it will be fixed as soon as our support company fixes it.

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/_P8crisJapw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 2600hz-dev+...@googlegroups.com.

[Yumminova]

Hi Luis

I have no clue what this does, but this is it



{
   "_id": "83c15f5f179008cfc9c26349be63f9c0",
   "_rev": "1-a216210d875790207918feb6f04bf00d",
   "featurecode": {
   },
   "numbers": [
       "no_match"
   ],
   "flow": {
       "children": {
       },
       "data": {
       },
       "module": "resources"

   },
   "ui_metadata": {
       "ui": "kazoo-ui",
       "version": "v3.14-3"
   },

   "pvt_type": "callflow",
   "pvt_vsn": "1",

   "pvt_account_id": "fd0557c26c70451fe10281c8bbcfd8c8",
   "pvt_account_db": "account%2Ffd%2F05%2F57c26c70451fe10281c8bbcfd8c8",

   "pvt_created": 63576027837,
   "pvt_modified": 63576027837
}

Luis Azedo schreef op 25-8-2014 20:04:

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/_P8crisJapw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 2600hz-dev+...@googlegroups.com.

[Luis Azedo]

just noticed that your rule is wrong

  "dial_plan": {
       "^+0(\\d{9,})$": {
           "description": "Mob test",
           "prefix": "+31"
       },

should be (dropping the '+')

  "dial_plan": {
       "^0(\\d{9,})$": {
           "description": "Mob test",
           "prefix": "+31"
       },

Best

On Mon, Aug 25, 2014 at 6:15 PM, Yumminova <in...@yumminova.eu> wrote:

[Luis Azedo]

also note that the double \\  shows only when editing, the value display in futton should be ^0(\d{9,})$

description

UK

prefix

+44

[Yumminova]

Oh Sh..., sorry man, u see im no coder and staring at code, trying to understand what it does, and especially regexes makes me see double

Its actually correct,i test with a sip phone that insists it should add a +
I removed that function and have put these two rules (the above still applies)

   "dial_plan": {
       "^+0(\\d{9,})$": {
           "description": "Mob test",
           "prefix": "+31"
       },
       "^06(\\d{8,})$": {
           "description": "Mob test1",
           "prefix": "+31"
       }
   },



But no luck ((

Aug 25 21:24:44 sip1 2600hz[16165]: |frees...@free1.obscured.eu|ecallmgr_fs_route:131 (<0.915.0>) processing dialplan fetch request 786e1e4c-2c8d-11e4-9315-7566a867a1c7 (call ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.) from frees...@free1.obscured.eu
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|ts_route_req:24 (<0.19094.54>) received a request asking if trunkstore can route this call
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|ts_route_req:35 (<0.19094.54>) call began on the network
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_route_req:23 (<0.19095.54>) received a request asking if callflows can route this call
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_util:433 (<0.19095.54>) searching for callflow in account%2Ffd%2F05%2F57c26c70451fe10281c8bbcfd8c8 to satisfy '0622222222'
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|ts_callflow:48 (<0.19101.54>) request is not for a trunkstore account
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_util:482 (<0.19095.54>) lookup callflow patterns for 0622222222 in account%2Ffd%2F05%2F57c26c70451fe10281c8bbcfd8c8
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_util:433 (<0.19095.54>) searching for callflow in account%2Ffd%2F05%2F57c26c70451fe10281c8bbcfd8c8 to satisfy 'no_match'
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_route_req:40 (<0.19095.54>) callflow 83c15f5f179008cfc9c26349be63f9c0 in fd0557c26c70451fe10281c8bbcfd8c8 satisfies request
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_route_req:141 (<0.19095.54>) callflows knows how to route the call! sent park response
Aug 25 21:24:44 sip1 2600hz[16165]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|ecallmgr_fs_route:245 (<0.9645.16>) received affirmative route response for request 786e1e4c-2c8d-11e4-9315-7566a867a1c7
Aug 25 21:24:44 sip1 2600hz[16165]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|ecallmgr_fs_route:251 (<0.9645.16>) node frees...@free1.obscured.eu accepted route response for request 786e1e4c-2c8d-11e4-9315-7566a867a1c7
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_route_win:21 (<0.19121.54>) callflow has received a route win, taking control of the call
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_route_win:39 (<0.19121.54>) setting initial information about the call
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_attributes:365 (<0.19121.54>) initiating endpoint is owned by 64264035150d3842bffb002746c8fc8b
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_attributes:148 (<0.19121.54>) internal caller id <Robert Yummi> martexx
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_route_win:180 (<0.19121.54>) bootstrapping with caller id type internal: "Robert Yummi" martexx
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_endpoint:523 (<0.19121.54>) failed to create endpoint: call_forward_not_appropriate
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_endpoint:571 (<0.19121.54>) building a SIP endpoint
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_attributes:148 (<0.19121.54>) internal caller id <Robert Yummi> martexx
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_attributes:301 (<0.19121.54>) callee id <Robert Yummi> 0622222222
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_route_win:260 (<0.19121.54>) call has been setup, beginning to process the call
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_exe:658 (<0.19124.54>) executing callflow 83c15f5f179008cfc9c26349be63f9c0
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_exe:659 (<0.19124.54>) account id fd0557c26c70451fe10281c8bbcfd8c8
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_exe:660 (<0.19124.54>) request 06222...@sip.obscured.nl
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_exe:661 (<0.19124.54>) to 06222...@sip.obscured.nl:5060
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_exe:662 (<0.19124.54>) from mar...@sip.obscured.nl
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_exe:663 (<0.19124.54>) CID Robert Yummi martexx
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_exe:665 (<0.19124.54>) inception on-net: using attributes for an internal call
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_exe:668 (<0.19124.54>) authorizing id 2a0342ea1cb95fdc0b8b318031252c29
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_exe:588 (<0.19124.54>) moving to action 'cf_resources'
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_attributes:144 (<0.19131.54>) emergency caller id <Robert Yummi> martexx
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_attributes:137 (<0.19131.54>) external caller id <Robert Yummi> martexx
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_exe:622 (<0.19131.54>) action cf_resources died unexpectedly (error): badarg
Aug 25 21:24:44 sip1 2600hz[16112]: |0000000000|Undefined:Undefined (emulator) Error in process <0.19131.54> on node 'whistl...@sip1.obscured.eu' with exit value: {{nocatch,badarg},[{cf_exe,'-spawn_cf_module/3-fun-1-',4,[{file,"src/cf_exe.erl"},{line,624}]}]}#012#012
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_exe:433 (<0.19124.54>) action cf_resources died unexpectedly: {{nocatch,badarg},[{cf_exe,'-spawn_cf_module/3-fun-1-',4,[{file,"src/cf_exe.erl"},{line,624}]}]}
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_exe:316 (<0.19124.54>) continuing to child '_'
Aug 25 21:24:44 sip1 2600hz[16112]: |ZGRlZjQyZDk1MWY5ZmJjNGQwNDc2MDE3YjFiYzE0ZmY.|cf_exe:321 (<0.19124.54>) wildcard child does not exist, we are lost...hanging up

Luis Azedo schreef op 25-8-2014 21:12:

[Luis Azedo]

get a decent sip phone or configure it not to include the '+'.

or if you want to leave like that (don't do that, really) you need to put \\ before the '+'

the '+' without backslash is interpreted as part of regex (one or more).

[Eamon]

Hi Luis

Please see device doc, the log file from the carrier side just shows the number dialed no translation

http://pastie.org/9502175 

[Yumminova]

done that now

   "dial_plan": {
       "^\\+06(\\d{8,})$": {

           "description": "Mob test",
           "prefix": "+31"
       },

       "^06(\\d{9,})$": {

           "description": "Mob test1",
           "prefix": "+31"
       }

where can i find the id of a callflow?

 call began on the network
Aug 25 21:45:46 sip1 2600hz[16112]: |NGE1ZTE1ODEwZDMxYTI0OGE4ZmE5ODRkNjY3ZDZmMGI.|ts_callflow:48 (<0.27488.54>) request is not for a trunkstore account
Aug 25 21:45:46 sip1 2600hz[16112]: |NGE1ZTE1ODEwZDMxYTI0OGE4ZmE5ODRkNjY3ZDZmMGI.|cf_route_req:23 (<0.27484.54>) received a request asking if callflows can route this call
Aug 25 21:45:46 sip1 2600hz[16112]: |NGE1ZTE1ODEwZDMxYTI0OGE4ZmE5ODRkNjY3ZDZmMGI.|cf_util:433 (<0.27484.54>) searching for callflow in account%2Ffd%2F05%2F57c26c70451fe10281c8bbcfd8c8 to satisfy '0611111111'
Aug 25 21:45:46 sip1 2600hz[16112]: |NGE1ZTE1ODEwZDMxYTI0OGE4ZmE5ODRkNjY3ZDZmMGI.|cf_util:482 (<0.27484.54>) lookup callflow patterns for 0611111111 in account%2Ffd%2F05%2F57c26c70451fe10281c8bbcfd8c8
Aug 25 21:45:46 sip1 2600hz[16112]: |NGE1ZTE1ODEwZDMxYTI0OGE4ZmE5ODRkNjY3ZDZmMGI.|cf_util:433 (<0.27484.54>) searching for callflow in account%2Ffd%2F05%2F57c26c70451fe10281c8bbcfd8c8 to satisfy 'no_match'
Aug 25 21:45:46 sip1 2600hz[16112]: |NGE1ZTE1ODEwZDMxYTI0OGE4ZmE5ODRkNjY3ZDZmMGI.|cf_route_req:40 (<0.27484.54>) callflow 83c15f5f179008cfc9c26349be63f9c0 in fd0557c26c70451fe10281c8bbcfd8c8 satisfies request

It seems to get handled by a flow, but i cant confirm that its the one i created

sorry to take your time, but the upside is that i would be able to explain it lateron

Luis Azedo schreef op 25-8-2014 21:44:

[Yumminova]

Same here. im calling it a night and will puzzle a bit further tomorow.

Eamon schreef op 25-8-2014 22:08:

[Eamon]

Hi

i upgraded to 3.12 made test call again still no translation debug from freeswitch

http://pastie.org/private/zi40mosjg66rpp02aoso5a

...

[Luis Azedo]

Hi Eamon,

please provide your system_config/number_manager doc , your dialplan rules and the number you are dialing.

you may have a conflict between the reconciles and dialplan

[Yumminova]

Luis Eaon

Om working on some rules with a guy that loves it

i can give rules for Eaon as well, it may be conflict in reconsile, account doc, device doc, user doc.....

Luis Azedo schreef op 26-8-2014 15:56:

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/_P8crisJapw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 2600hz-dev+...@googlegroups.com.

[Eamon]

Hi Luis

Number_manager doc is http://pastie.org/9504626

i noticed that my accounts.json http://pastie.org/9504631     is not the same as the github version, i have no dial_plan reference in the schemas of the accounts or device

even though i completed an update  

https://github.com/2600hz/kazoo/blob/master/applications/crossbar/priv/couchdb/schemas/accounts.json

...

[Luis Azedo]

Hi Eamon,

can you provide  your dialplan rules and the number you are dialing.

--

[Eamon]

Hi Luis

i'm dialing 0449337500 

},
   "ringtones": {
   },
   "dial_plan": {
       "^044(\\d{7,})$": {
           "description": "test",
           "prefix": "35344"
       }
   },
   "call_restriction": {

...

[Luis Azedo]

this should work, your regex in number doc doesn't modify the number

do you have dial_plan rules at user or account level ?

baffb05eb102f786627781cbc0017342

d42b0c619707afb0fd917ced3e81a830

or..

the no_match callflow may have params to not apply the dial_plan, do_not_normalize, bypass_e164

--

[Eamon]

Hi Luis

copy of docs i don't see any other dial_plan in user or account docs. The callflow i checked from the developer api don't know if that's correct ?

account:   http://pastie.org/9505019

user:        http://pastie.org/9505040

callflow:    http://pastie.org/9505055

...

[Eamon]

Hi Luis

Checked dial plan and a test server, its works fine, any idea where i should look in order to get the active server working ?

...

[Yumminova Telecom]

Hi

Let me "hyjack" this thread ))

In reference to the first post here, are there plans to deal with this differently?
I have been playing a week now, and although one can get far with regexes on different docs, there will always be problems creating smth that works all the time if that is posible at all. I do not want to offend anyone or compare apples and pears, but lync, 3cx, porta all seem to have approx the same way of dealing with this:

Set the country and city/region and then apply one of the x numbers of default rulesets. Those rules can be community maintained, i can sponsor the basic rules for all EU country´s to get started.

As u guys are more far from silly then i am i guess u realized this to and i was wondering if Monster is prepared for this and perhaps stores that info in the DB already.
It would be silly to create it now only to be absolete lateron


Op zaterdag 30 augustus 2014 22:48:44 UTC+2 schreef Eamon:

...

[Aaron Shames]

Hello all, this is my first post here. 

First and foremost, thanks to all of the Kazoo developers and supporters, this is an amazing project!

I am horrible with regexs, I was hoping someone could assist with configuration for the most simple possible dial plan / dialing rules to allow for internationalization.

How would I configure the dialplan to force all users to dial in E.164 format?  Everyone in the world has to dial the exact same way, all incoming DIDs will hit the system as E164, and we will send all calls out to carriers in E164.  This will allow number normalization as well so in the future when I do allow for easier dialing depenidng on users locals, all numbers will still be stored in E164 format.

This should be a 1 line dialplan which perhaps just strips off the "+" in front?  Any help and examples would be appreciated!  Thanks in advance!

Aaron

[Luis Azedo]

Hi Eamon,

check the system_config_config/number_manager document for differences.

--

[Luis Azedo]

Hi,

you must take in consideration that the dial_plan (as discussed here) is part of the API not a UI feature.

regexes will get you where you want, when you refer lync or 3cx, you are indeed comparing apples and oranges, we expose the way the backend translates the numbers, it can be used for country prefixes or anything else like carrier route selection or others.

i do understand that for the common user that just wants to put the country code this may be frustrating but, you can always sponsor some work on that or do it yourself and contribute back to the community if you wish.

eventually, we will get to the point to manage global regexes (countries for example) and apply them to the dial_plan (use reference to global instead of value).

--

[Yumminova]

Hi Luis

I understand that, thats why i asked, as its silly to contribute that right now, if monster has that already and if that will be at one point available to the rest of the world instead of some chosen ones ))

As  its all API the GUI is less relevant in any case, it would just be handy to have a more easy way to deal with it.

"eventually, we will get to the point to manage global regexes (countries for example) and apply them to the dial_plan (use reference to global instead of value)."

Indeed smth like that was what i was thinking off, just to make life easier. If its a cloud/cluster setup it feels silly to start a new cluster per country just because of smth like this ))
But setting dial plans and such manually on (per example) 1500 customer, with various locations in various states and various users on different locations in the world is a little 1999 ))

One can always use the api in the onboarding process or set it in any other way, but i see some value in having it in the GUI, its the rasons they exist, Kazoo does not need a GUI to do its magica but its there so that says smth ))))

Cheers!

Luis Azedo schreef op 1-9-2014 16:54:

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/_P8crisJapw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 2600hz-dev+...@googlegroups.com.

[Yumminova Telecom]

Hi Luis

I have given the creation of some default rules a shot and am looking to commit them.
However i got a remark that those rules where so so wrong, but it was a rather empty response.

I do not require you to explain everything, but perhaps a quick glimpse to see if its really that bad or not, could u do that?

https://github.com/yumminova/kazoo/tree/master/applications/crossbar/doc/internationalization

European reconsile regex and E.164 converters

Yumminova.eu

/////////////////////////////////////////////////////////////////////////////

"default": {

"reconcile_regex": "^\\+?[1-9]\\d{5,}$|^0\\d{5,}$|^00\\d{5,}$",

"e164_converters": {

"^00(\\d*)$": {

"prefix": "+"

},

"^([1-9]\\d{7,})$": {

"prefix": "+"

}

},

/////////////////////////////////////////////////////////////////////////

And some default regexes for EU countries and certain cities, so that a user could adopt them to their specific needs.

"dial_plan": {

"^00(\\d{5,})$": {

"description": "international",

"prefix": "+"

},

"^0(\\d{5,})$": {

"description": "NL national",

"prefix": "+31"

},

"^([1-9]\\d{4,})$": {

"description": "NL Amsterdam  local",

"prefix": "+3120"

}

}

Op donderdag 21 augustus 2014 19:31:52 UTC+2 schreef Yumminova Telecom:

Hi

Can someone shed a light on the future?

Im thinking on how to deal with internationalisation and especially how Kazoo will deal with that if it will at one time.
(will it?)

So we can create regexes in number_manager, but mostly for specific country´s if i look at them.
Im wondering if the dev team has plans to change this, i can imagine that if u run a cloud/cluster, its kind of silly to deploy a new one per country for that purpose alone (i can image having a cluster per country for other reasons though) Also, one may have clients that are based in a place and have numbers from different country´s

And it kind of takes the cloud out of the cloud.

So i have some ideas but i need to know the vision of the dev team on it, else it wold be wasted energy.

Comming from a porta system, i liked the way they do it, being able to specify the country, region and city so that a client can dial as they are used to.
So if thats something kazoo can support, i can create a tool to create rules easily and give them.

I suppose that if each account would have its own number_manager doc, we could do it rather easily (im no programmer )) then we could set the proper regexes in that doc and be done with it.

Can someone react on this, so i can decide what to do if i can do smth?

[Luis Azedo]

Hi,

check the comment on pull request. https://github.com/2600hz/kazoo/pull/482

and..., thank you very much for your effort on this.

Best

--

[Yumminova]

Im checking )) believe it

ill update that

Luis Azedo schreef op 2-9-2014 16:50:

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/_P8crisJapw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 2600hz-dev+...@googlegroups.com.

[Luis Azedo]

check the comments on the pull request.

On Tue, Sep 2, 2014 at 8:29 PM, Yumminova <in...@yumminova.eu> wrote:

inline

lazedo schreef op 2-9-2014 16:11:

where did you get these samples from?

take this sample for portugal

   "^00(\\d{5,})$": {
           "description": "international",
           "prefix": "+"
       },

user dials 0012345 -> +35112345 => wrong

// user dials 0031222797002 which is 00 international prefix, the countrycode from NL and the number, becomes +31222797002 and correct is it not?
Where id u get the extra 1 ??

       "^0(\\d{5,})$": {
           "description": "PT national",
           "prefix": "+351"
       },

user dials 012345 -> +3512112345 => wrong

//  Wrong indeed, Portugal does not use a leading zero for interlocal calls, but again u add numbers that i dont, i guess it should be changed but i still fail to see the error.
User dials 012345 should become +35112345 in the above example, if they would use a leading zero

       "^([1-9]\\d{4,})$": {
           "description": "PT Lisbon local",
           "prefix": "+35121"
       }

user dials 12345 -> +351212345 => wrong

// i´m clueless , a user located in Lisboa 21 will dial a local number : 22222> +3512122222 seems fine to me

the same thing happens to other countries.

    "dial_plan": {
           "^00(\\d{5,})$": {
               "description": "international",

               "prefix": "+" // takes any international number, strips the 00 and adds +// seems perfect

           },
           "^0(\\d{5,})$": {
               "description": "NL national",

               "prefix": "+31" // If i want to dial my home from amsterdam i dial 0222797002, this becomes +31222797002, perfect, also catches  0800 0900 06x and such)

           },
           "^([1-9]\\d{4,})$": {
               "description": "NL Amsterdam  local",

               "prefix": "+3120" // If i dial our amsterdam office from an other amsterdam phone i dial 0206666666 > +31206666666, seems fine

           }
}

Luis Azedo schreef op 2-9-2014 16:50:

Hi,

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/_P8crisJapw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 2600hz-dev+...@googlegroups.com.

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

[Yumminova]

Hi Luis

I just did, but i dont see why they are wrong.  My reaction copied below.


Im no regex guru indeed, but if u could point me to the right direction i will have them fixed, i dont understand where the extra digits gets added u show in your example.

where did you get these samples from?

take this sample for portugal

"^00(\d{5,})$": {
"description": "international",
"prefix": "+"
},

user dials 0012345 -> +35112345 => wrong

Wrong assumption i think, i dot add +351, you do that )) I just strip the 00 and replace with +

////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

   "^0(\\d{5,})$": {
       "description": "PT national",
       "prefix": "+351"
   },

user dials 012345 -> +3512112345 => wrong

//U put a 2 here that should not be there

//user dial 012345 we strip the 0 and prefix +351 bcomes +35112345

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

   "^([1-9]\\d{4,})$": {
       "description": "PT Lisbon local",
       "prefix": "+35121"
   }

user dials 12345 -> +351212345 => wrong

User located in Lisboa , the regex is the third inline and starts with a value betwen 1 and 9, this covers all local numbers, only the 9 is false as thats mobile, ill fix that. That localnumber is then replaced by the country and Lisboa region number
12345 becomes +3512112345 and is valid

Dont see the same error u seem to see

[Luis Azedo]

i already replied in the pull request.

let me rephrase the results.

1) 0012345 => +12345 wrong

2) 012345 => +35112345 wrong

3) 12345 => +3512112345 wrong

you are setting the lower limit to 5 which doesn't make sense because dialing rules in portugal require 9 digits always.

also, by setting the lower limit to 5 you are preventing users from dialing 5, 6, 7,8 digit extensions.

can you share the sources you used to make these rules ?

http://www.timeanddate.com/worldclock/dialing.html

http://en.wikipedia.org/wiki/List_of_country_calling_codes

http://en.wikipedia.org/wiki/Telephone_numbers_in_Portugal

http://en.wikipedia.org/wiki/Telephone_numbers_in_the_Netherlands

http://en.wikipedia.org/wiki/Telephone_numbers_in_[country_name_here]

any ?

Best

[Yumminova Telecom]

So:

1) 0012345 => +12345 wrong
2) 012345 => +35112345 wrong
3) 12345 => +3512112345 wrong

//They are wrong because of the five digits, that's sad )) I'll add more detailed instructions and will alter what I can and write explanation so users from a certain region can change to their needs.//

you are setting the lower limit to 5 which doesn't make sense because dialing rules in portugal require 9 digits always.

/
Yes but just as 2600hz did not create all specific rules for all numbers neither did I))
In our situation it makes sense as extensions are max 4 digits but I get your point, I will add this to instructions so that users can create their own rules based on their extensions length and details. That needs to be taken into account in the extensions regex in the GUI as well. As else one would have big problems.
If not it's impossible to have local dialing rules as they can always conflict with local phone numbers (hence it's easier to set this kind of stuff in the GUI to have some solid point to work from)

If we would know and set the extension format and length, country code and region code and some rules life would be easier ))//

also, by setting the lower limit to 5 you are preventing users from dialing 5, 6, 7,8 digit extensions.

Yup, that's right, and even ten and up, it was based on a 4 digits extension system to keep it simple, but I guess it's just not simple at all

I will write it up this week, thanks for explanation Luis, much appreciated

[Alexander Mustafin]

Hello, guys. 

Thanks for your examples of internationalization. I've successfully set dial_plan. 

My problem now - is to set account language, because I want to use translated prompts. 

When I try to use 'sup whapps_account_config b5e3c8331af94176436bf5f8f4b12b04 media default_language fr-fr', I have the next error: 'Invalid command or wrong number of arguments, please try again'

My Kazoo version: kazoo-R15B-3.16-17.el6.x86_64

How to solve this problem? Does any other methods exist? Maybe, I may set variable in account?

[James Aimonetti]

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

The docs were wrong. Try:

sup whapps_account_config set b5e3c8331af94176436bf5f8f4b12b04 media
default_language fr-fr

Notice the *set* that was missing. Updating docs now.


- --
James Aimonetti
Lead Systems Architect / Impressionable Scallywag
"I thought I fixed that"

2600Hz | http://2600hz.com
sip:ja...@2600hz.com
tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJUIFEVAAoJENTKa+JPXCVgQhkH/0WDxrNeWZUP8jCYfyAvxHtj
FQgYCcDoKnuUH5+mG4CoxvoZuuPPOfNYL/qJtOnWRVIlscCy5pC21v1gBrzsj2JK
Ht8Q7oYH8GU4Gl6qFCR48cUCtAYno8lodxDfm+3EuuY3Na1Akeq8fdknHJt8WHT2
YdsNYiVttb0BMnryR71MnhnEmKNu65N8+ey/jpxH1THmOLsp0XqS1iLeHjzxlaYo
goxN2F73m+7f1zQzxB1HadekNL4s7NAHw9omVYfFADY8c7noeyqZ8iDm9wKZv9pP
YVVTXKBAodHR9ptq0Eb8Xn6j2MwLACZNjE9QbIj87lNgMupser409LgsH+fPv40=
=56iV
-----END PGP SIGNATURE-----

[Eamon]

Hi 

Did you create a number_manger doc per country code in the system_config to add international DID's or just use the one existing doc and update the reconcile_regex with the prefix details

On Monday, September 22, 2014 at 5:40:56 PM UTC+1, James Aimonetti wrote:

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

Le 2014-09-16 03:25, Alexander Mustafin a écrit :
> Hello, guys.
>
> Thanks for your examples of internationalization. I've successfully
> set dial_plan. My problem now - is to set account language, because
> I want to use translated prompts.
>
> When I try to use 'sup whapps_account_config
> b5e3c8331af94176436bf5f8f4b12b04 media default_language fr-fr', I
> have the next error: 'Invalid command or wrong number of arguments,
> please try again'
>
> My Kazoo version: kazoo-R15B-3.16-17.el6.x86_64
>
> How to solve this problem? Does any other methods exist? Maybe, I
> may set variable in account?
>

The docs were wrong. Try:

sup whapps_account_config set b5e3c8331af94176436bf5f8f4b12b04 media
default_language fr-fr

Notice the *set* that was missing. Updating docs now.


- --
James Aimonetti
Lead Systems Architect / Impressionable Scallywag
"I thought I fixed that"

2600Hz | http://2600hz.com

sip:...@2600hz.com

tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJUIFEVAAoJENTKa+JPXCVgQhkH/0WDxrNeWZUP8jCYfyAvxHtj
FQgYCcDoKnuUH5+mG4CoxvoZuuPPOfNYL/qJtOnWRVIlscCy5pC21v1gBrzsj2JK
Ht8Q7oYH8GU4Gl6qFCR48cUCtAYno8lodxDfm+3EuuY3Na1Akeq8fdknHJt8WHT2

YdsNYiVttb0BMnryR...

[Eamon]

Hi

I have dial plan added to an account that has a device and a PBX connector, the plan works fine with the device but not the connector 

is there another way to enable this ?

Thanks,

On Monday, September 22, 2014 at 5:40:56 PM UTC+1, James Aimonetti wrote:

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

Le 2014-09-16 03:25, Alexander Mustafin a écrit :
> Hello, guys.
>
> Thanks for your examples of internationalization. I've successfully
> set dial_plan. My problem now - is to set account language, because
> I want to use translated prompts.
>
> When I try to use 'sup whapps_account_config
> b5e3c8331af94176436bf5f8f4b12b04 media default_language fr-fr', I
> have the next error: 'Invalid command or wrong number of arguments,
> please try again'
>
> My Kazoo version: kazoo-R15B-3.16-17.el6.x86_64
>
> How to solve this problem? Does any other methods exist? Maybe, I
> may set variable in account?
>

The docs were wrong. Try:

sup whapps_account_config set b5e3c8331af94176436bf5f8f4b12b04 media
default_language fr-fr

Notice the *set* that was missing. Updating docs now.


- --
James Aimonetti
Lead Systems Architect / Impressionable Scallywag
"I thought I fixed that"

2600Hz | http://2600hz.com

sip:...@2600hz.com

tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJUIFEVAAoJENTKa+JPXCVgQhkH/0WDxrNeWZUP8jCYfyAvxHtj
FQgYCcDoKnuUH5+mG4CoxvoZuuPPOfNYL/qJtOnWRVIlscCy5pC21v1gBrzsj2JK
Ht8Q7oYH8GU4Gl6qFCR48cUCtAYno8lodxDfm+3EuuY3Na1Akeq8fdknHJt8WHT2
YdsNYiVttb0BMnryR71MnhnEmKNu65N8+ey/jpxH1THmOLsp0XqS1iLeHjzxlaYo
goxN2F73m+7f1zQzxB1HadekNL4s7NAHw9omVYfFADY8c7noeyqZ8iDm9wKZv9pP
YVVTXKBAodHR9ptq0Eb8Xn6j2MwLACZNjE9QbIj87lNgMupser409LgsH+fPv40=
=56iV

-----END PGP SI...

[James Aimonetti]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dial plans are only processed by callflows (PBX feature). It is not
available to PBX connector (trunkstore).

sip:ja...@2600hz.com

tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----

Version: GnuPG v2

Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCAAGBQJVSmmsAAoJENTKa+JPXCVg7OEH/0G4vbMpYeTxX5z/mD+LIirl
2NXRjq09My9V8i7ozXdarT8t4Ixw4/LYiLWl0pKpwBap5HdaHrJatMz3tAQS4lIg
ER/xTb4wMlXcjhyu1PYHpTCNQVNedgWXufSbjDORpt2yx4N5MKG2QInVmv9DGjix
+GapBcA0gbsFVP27mYulRUafjfxuAaSjPb04xVpRmtrHSdl0tD+H0fwuQzgrH/Qk
BcGjGTWI8xDcR1amNpLv8/d6E/s0bkS2ScWAwpJuJSftN6TGc3JF/6o+Ne0h+rC0
Iu1YR+01l+N45y9k+sWydJTsdN6osvM2plYv68S4WujmGhKoqiCcSQ2X4SPWVCw=
=y2Ly
-----END PGP SIGNATURE-----