[SMS Message Length]

@FASTDEVICE  can you provide a real use case and trackable numbers from/to (you can send the number in private) ?

1) when you use the /v2/.../sms api you can send messages with more than 160 characters, we do segmentation or use udh depending on the number provider

2) when your webhook is called (after a text is received for the number), you should receive the ALL text, again, provider may use udh or segmentation. in the case of segmentation we reassemble before delivering to webhook or device

thanks

 

[SMS Message Length]

7 minutes ago, FASTDEVICE said:

but not the one from 2600hz

not sure what that means. 

 

8 minutes ago, FASTDEVICE said:

Do we have to perform the re-assembly?  

depends on your carrier and how you connect to your carrier

[SMS Message Length]

that depends mostly from the providers & apps & gateways. Our implementation does segmentation & reassembly

https://en.wikipedia.org/wiki/Segmentation_and_reassembly

 

[Kamailio not switching to Secondary Rabbitmq]

11 hours ago, abuzooz said:

I have 2 Rabbitmq servers in my zone

that's not supported, you should cluster instead. not supported doesn't mean it won't work, it means you'll need to be prepared for things not working as you may expect.

the kamailio log doesn't show nothing that's not expected, you need to provide real logs (not images), and you should start kamailio, wait for things to be running, kill first rabbitmq, kamailio should connect to 2nd rabbitmq. but as stated above..., this won't work in the long term for a lot of reasons, you're on your own on proceeding with this configuration.

[AWS Connector: Setting up an Amazon Web Services Connection]

10 hours ago, Emily R said:

If you used the West Region as noted earlier, your host is s3us-west-1.amazonaws.com.

you don't need to provide the "host" if you're using aws. the "host" is used for s3 compatible servers like minio or when cnames are used.

[SMS Messaging User Guide]

@Joshua did you check this ? 

 

[SMS is now enabled on Hosted Platforms]

Hi Dhruv,

the SMS and XMPP settings are useless, all you have to do is to enable presence.

note however that, a message will be delivered  to all registered devices until one replies with success.

for example, if you have 3 (A,B,C) registered devices belonging to a user with a sms enabled number,

an incoming message to that number will be delivered to the A device, if it fails, its delivered to B device , if it fails its delivered to C device, if it fails its dropped.

if device A is a yealink you may have receive the message (tho you expected it in bria).

so, i would recommend to

1) create 2 new users

2) assigned the Bria devices to those users

3) move the sms enabled numbers to those users, or get new ones

4) try it out

i have successfully worked with bria & linphone & yealink

[Add custom field/attribute to Users and CDRs Schemas]

assuming you're running 4.3 releases, if you install kazoo-freeswitch >= 4.3.16 without change, it should work oob.

make sure to look into freeswitch logs for kazoo initiated commands to set the cav variable

 

don't do this, this is a developer setting, it will degrade your system

2 hours ago, abuzooz said:

<param name="send-all-headers" value="true" />

[S3 Storage for Call Recordings]

20 minutes ago, simonp22 said:

In my PUT storage request I have now added the host field in to the attachment settings and set it to "s3-eu-west-2.amazonaws.com".

the host field is used for custom s3 providers, you shouldn't be doing that.

[Terminating Call too early]

you can always go back to the kazoo version that worked for you. the source code is in github.

 

[Terminating Call too early]

[Terminating Call too early]

4 hours ago, bsimpson72515 said:

We are using a newer version of Kazoo with an older web service

please, be more specific.

4 hours ago, bsimpson72515 said:

<Redirect method="GET">http://209.142.178.205:57113/Keefe_2//keefe/TimedOut?redirect=confirm</Redirect>#015#012</Response>'

Jan  7 16:05:57 pintransfer 2600hz[1137]: |call-711CE674-8013-3810-000C-2F@72.82.244.65|pivot_call:478(<0.2694.0>) finding translator for content type text/html; charset=utf-8
Jan  7 16:05:57 pintransfer 2600hz[1137]: |call-711CE674-8013-3810-000C-2F@72.82.244.65|pivot_call:392(<0.2507.0>) pivot call terminating: normal

looks like your redirect action is returning text/html ?

[Call recording PUT request to https]

https is supported oob. you should look with your provider

[escript: Failed to open file sup.escript]

On 9/13/2019 at 2:38 PM, Jayachandra said:

What i have noticed is that the sup version installed in the directory /opt/kazoo/_rel/kazoo/lib/ is 4.3.55 but it is searching for 4.3.54 directory.

the problem is in your symlink.

you probably created the symlink then upgrade/update made a new release which will change the folder where sup is, 4.3.54 when created, 4.3.55 after update/upgrade

[2600hz stable and staging repos Broken]

@Mark McDonald repo is fixed

[Where to get started on OAuth2]

On 2/14/2019 at 9:02 PM, KevinPGi said:

our expectation is that the user logs into the portal, gets redirected to our OAuth2 provider, and then we redirect back to Kazoo

what portal are you expecting the user to logon ?

you tipically have a landing page for auth like in https://monster.sandbox.2600hz.com/ where the user can login with his kazoo credentials or with a oauth provider.

depending on the level of integration you want, you may redirect immediately from the landing page to your oauth login url.

if you have your own identity provider oauth app, then you need to configure it as a provider (see google & office365 docs in system_auth database) and create an application to reference that provider.

do you have discovery url for your oauth provider ? any documentation for it ?

 

[Upscalling in 1 zone]

no, i meant that to use 2+ rabbitmq servers in one zone (not failover) , you need to cluster them

 

[Upscalling in 1 zone]

2 hours ago, Jean-Francois Charlebois said:

I know that on 3.22 we could not have 2 Rabbitmqs work at the same time, we had to switch one off but now the 4.2 both can work at the same time

this is only valid if you cluster rabbitmq servers on the same zone.

 

as for the number of erlang vm's (kazoo), freeswitch servers, kamailio servers, there's no limit on kazoo imposing that.

 

[Intercom to multiple phones?]

On 4/5/2018 at 3:09 PM, Alex Aristides said:

multi phone page within call flows and it seems to be 2 way and causing a lot of issues

you can set 1 way or 2 way in the callflow

[Park on Polycom phones?]

@esoare every kamailio box is aware of fast-pickup. In 4.0 and previous, fast-pickup cookie was created in omnipresence and notify was sent with a direct queue to targeted kamailio boxes. as of 4.1, notify is broadcasted (via amqp) and kamailio boxes will check if they have subscribers for the presence-id and will notify the phones if they have. The fast -pickup cookie is created with known values that can be converted by every kamailio box.

[Park on Polycom phones?]

10 hours ago, extremerotary said:

Please note that not all Kamailio boxes are aware of the 'fast pickup' target-uri across other boxes

this is not correct as of 4.1

[Call Recording - When Transferring a Call]

if you set "record everything", that is the expected behaviour.

 

[Call recording per channel]

thanks for feedback. i'll create a PR for that.

thanks

[Call recording per channel]

a quick at the code shows that the problem maybe related to region encoding, upstream library expects string() not binary().

if you can edit & compile in your environment, you can try this.

in core/kazoo_attachments/kzt_att_s3.erl line 40

-    Region = maps:get('region', Map, 'undefined'),

+    Region = case maps:get('region', Map, 'undefined') of

+                 'undefined' -> 'undefined';

+                 Bin -> kz_term:to_list(Bin)

+             end,

 

[Call recording per channel]

nxdomain seems like a dns issue. can you paste your data storage configuration ? (scramble the creds)