Re: [SR-Users] What is the mechanism used for sending push notification from Kamailio, For both IOS and Android?

2018-02-12 Thread Mojtaba 
Hello Arunbalan,
Please read about TSILO module In kamailio, Also there is simple way
to implement concept of push notification as you needed.
With Regards.
Mojtaba Esfandiari.S

On Tue, Feb 13, 2018 at 10:19 AM, Arun NV  wrote:
> I am creating custom phone client, which uses Kamailio as a proxy and it's
> required to send push notification from Kamailio to the clients when a call
> towards the client reached on Kamailio. I found a module for APNS here
> https://github.com/tvntsr/push. But I am developing both Android and IOS
> clients. So What mechanism I can use for the Android side?
>
> Is there any module available for GCM(Google Cloud Messaging) in Kamailio?
>
> Thank you,
> Arunbalan
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>



-- 
--Mojtaba Esfandiari.S

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] LCR options as of 2018

2018-02-12 Thread Francisco Valentin Vinagrero 
Thanks Daniel,

Mtree + Dispatcher makes a lot of sense for my use case. I will try to 
implement the LCR with that.

Cheers, Francisco.

From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: Monday, February 12, 2018 14:22
To: Kamailio (SER) - Users Mailing List ; 
Francisco Valentin Vinagrero 
Subject: Re: [SR-Users] LCR options as of 2018


Hello,

On 12.02.18 13:52, Francisco Valentin Vinagrero wrote:
Hello,

I am configuring a Kamailio node that will interface with 3 carriers and will 
implement Least Cost Routing for around 900 destinations.

I have already implemented a quick prototype with the LCR module and I have 
been reading the CarrierRoute doc and the CGrates site.

I don't really need advanced functionality, just:

-  Re-routing to a backup carrier when the main one is not available.

-  Ping with OPTIONS to all carriers so I can detect if any of them is 
not available (à la Dispatcher)

-  Translate prices from a central DB to routing priorities.

-  Get some accounting post-call info about the routing decision (acc 
module)


So far, while testing the LCR module I have had some issues with the rule IDs 
being integers that auto-increment, so the LCR rules need to be referenced from 
the rule_target table using this numeric ID. I can see some issues when scaling 
this to 900 lcr_rules and 2700 lcr_rule_targets with 3 priorities.

In addition to that, I think the OPTIONS mechanism is just used by the lcr 
module when a gateway is marked as defunct, but the gateways are not actively 
monitored in the normal status. Is this correct?

I have been considering CarrierRoute, which has a slightly simpler table 
structure, but I can't find any other advantage for my use case. Regarding 
CGrates, it looks great but it looks like it exceeds my current needs.

For those who have implemented LCR in your kamailios, am I missing something 
regarding performance, scalability, etc?

Are there any newer modules that can implement this, or maybe just a 
dispatcher-on-steroids setup will do the trick?


Look also at drouting module, the latest version should do OPTIONS keep alives 
using keepalive module, otherwise it is a lcr implementation as well -- I 
haven't tested myself the keep alive feature, though.

As for me, typically I go in this case for a combination of mtree + dispatcher. 
I have mtree translating from longest prefix to a dispatcher group id, inside 
dispatcher group you can use priority based routing. This works just fine even 
when you end up in several dispatcher groups with same destinations but 
different order based on priority per group.

You can even map the prefix in mtree to dispatcher group + dispatching 
algorithm, latest version supports having many columns loaded in the value and 
then you can use script operations to split.

Cheers,
Daniel


--

Daniel-Constantin Mierla

www.twitter.com/miconda -- 
www.linkedin.com/in/miconda

Kamailio Advanced Training - March 5-7, 2018, Berlin - 
www.asipto.com

Kamailio World Conference - May 14-16, 2018 - 
www.kamailioworld.com
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Very inconsistent calls

2018-02-12 Thread Wilkins, Steve 
Thank you.  Yes I have been doing packet capturing and it does appear that 
sometimes there is a missing ACK back from Kamailio; it is just so, so 
confusing as to why sometimes (often, depending the provider) it works.  Your 
thoughts do help though!

-Steve

-Original Message-
From: sr-users [mailto:sr-users-boun...@lists.kamailio.org] On Behalf Of 
Michael Young
Sent: Monday, February 12, 2018 8:59 AM
To: 'Kamailio (SER) - Users Mailing List' 
Subject: Re: [SR-Users] Very inconsistent calls

Do that google search. You aren't the only person who experiences that.

For instance, it can be caused by having multiple UAs behind a NAT 
router\firewall with a poor connection tracking implementation. The firewall 
can get confused and at times route an ACK to the wrong UA (As Brandon Armstead 
said, "this issue occurs when ACK is not routed to proper contact.")  Without 
details on your topology, no one here would be able to help you troubleshoot 
further or make other suggestions.

There is no substitute for packet capturing and a clear understanding of the 
call flow. 

Michael

-Original Message-
From: sr-users [mailto:sr-users-boun...@lists.kamailio.org] On Behalf Of 
Wilkins, Steve
Sent: Monday, February 12, 2018 6:26 AM
To: Kamailio (SER) - Users Mailing List 
Subject: Re: [SR-Users] Very inconsistent calls

But very often a call will stay up indefinitely!  This is what is strange.

-Original Message-
From: sr-users [mailto:sr-users-boun...@lists.kamailio.org] On Behalf Of 
Michael Young
Sent: Sunday, February 11, 2018 9:07 PM
To: 'Kamailio (SER) - Users Mailing List' 
Subject: Re: [SR-Users] Very inconsistent calls

And just to add to Alex's comment -- in my experience this is almost always a 
firewall issue. Whenever I see a call drop in 32 seconds, it is usually because 
a firewall did not allow the ACK through. 

Google "Asterisk drops calls after 32 seconds" and you get 1,180,000 results... 
 and the problem is not Asterisk itself. 

Michael

-Original Message-
From: sr-users [mailto:sr-users-boun...@lists.kamailio.org] On Behalf Of Alex 
Balashov
Sent: Sunday, February 11, 2018 7:27 PM
To: Kamailio (SER) - Users Mailing List 
Subject: Re: [SR-Users] Very inconsistent calls



> I have found that calls are very inconsistent.  I use Kamailio 5, 
> Asterisk 14.  When certain Providers like (Sorenson, ZVRS) make calls 
> into a WebRTC client (tryit-jssip), sometime the calls stay up until I 
> close them (10-15 minutes), others times those calls drop in 30 
> seconds.  This is extremely confusing...does anyone else experience 
> this type of behavior?

It is hard to speculate without a capture, and indeed there are lots of moving 
parts with WebRTC. However, the typical reason why an established call would 
drop after ~30 sec (32, to be precise) is that the end-to-end ACK from the 
caller, which completes the required "three-way handshake"
for call establishment, does not reach the callee. This is because it's not 
constructed correctly by the calling UA, not routed correctly by intermediate 
entities, or isn't sent at all by the calling UA.

--
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Kamailio Memory Settings

2018-02-12 Thread Duarte Rocha 
Hey.

I have some questions about memory settings.

I can see the default values with "kamailio -I" and change the current
values with "kamailio -M 12 -m 128". How do i see the active settings and
how do i change the default value?

I want to setup a proxy capable to handle 150CPS, 6k active calls, with
Dispatcher, Database, Number Normalizations and other operations. What are
good settings for CPU, RAM Memory, PKG_SIZE and SHM_SIZE?

Thanks for the help,

Best Regards,

Duarte Rocha
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] LCR options as of 2018

2018-02-12 Thread Francisco Valentin Vinagrero 
Hello,

I am configuring a Kamailio node that will interface with 3 carriers and will 
implement Least Cost Routing for around 900 destinations.

I have already implemented a quick prototype with the LCR module and I have 
been reading the CarrierRoute doc and the CGrates site.

I don't really need advanced functionality, just:

-  Re-routing to a backup carrier when the main one is not available.

-  Ping with OPTIONS to all carriers so I can detect if any of them is 
not available (à la Dispatcher)

-  Translate prices from a central DB to routing priorities.

-  Get some accounting post-call info about the routing decision (acc 
module)


So far, while testing the LCR module I have had some issues with the rule IDs 
being integers that auto-increment, so the LCR rules need to be referenced from 
the rule_target table using this numeric ID. I can see some issues when scaling 
this to 900 lcr_rules and 2700 lcr_rule_targets with 3 priorities.

In addition to that, I think the OPTIONS mechanism is just used by the lcr 
module when a gateway is marked as defunct, but the gateways are not actively 
monitored in the normal status. Is this correct?

I have been considering CarrierRoute, which has a slightly simpler table 
structure, but I can't find any other advantage for my use case. Regarding 
CGrates, it looks great but it looks like it exceeds my current needs.

For those who have implemented LCR in your kamailios, am I missing something 
regarding performance, scalability, etc?

Are there any newer modules that can implement this, or maybe just a 
dispatcher-on-steroids setup will do the trick?

Cheers,
Francisco.

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Very inconsistent calls

2018-02-12 Thread Wilkins, Steve 
But very often a call will stay up indefinitely!  This is what is strange.

-Original Message-
From: sr-users [mailto:sr-users-boun...@lists.kamailio.org] On Behalf Of 
Michael Young
Sent: Sunday, February 11, 2018 9:07 PM
To: 'Kamailio (SER) - Users Mailing List' 
Subject: Re: [SR-Users] Very inconsistent calls

And just to add to Alex's comment -- in my experience this is almost always a 
firewall issue. Whenever I see a call drop in 32 seconds, it is usually because 
a firewall did not allow the ACK through. 

Google "Asterisk drops calls after 32 seconds" and you get 1,180,000 results... 
 and the problem is not Asterisk itself. 

Michael

-Original Message-
From: sr-users [mailto:sr-users-boun...@lists.kamailio.org] On Behalf Of Alex 
Balashov
Sent: Sunday, February 11, 2018 7:27 PM
To: Kamailio (SER) - Users Mailing List 
Subject: Re: [SR-Users] Very inconsistent calls



> I have found that calls are very inconsistent.  I use Kamailio 5, 
> Asterisk 14.  When certain Providers like (Sorenson, ZVRS) make calls 
> into a WebRTC client (tryit-jssip), sometime the calls stay up until I 
> close them (10-15 minutes), others times those calls drop in 30 
> seconds.  This is extremely confusing...does anyone else experience 
> this type of behavior?

It is hard to speculate without a capture, and indeed there are lots of moving 
parts with WebRTC. However, the typical reason why an established call would 
drop after ~30 sec (32, to be precise) is that the end-to-end ACK from the 
caller, which completes the required "three-way handshake"
for call establishment, does not reach the callee. This is because it's not 
constructed correctly by the calling UA, not routed correctly by intermediate 
entities, or isn't sent at all by the calling UA.

--
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Very inconsistent calls

2018-02-12 Thread Wilkins, Steve 
But the weird part is that one call may stay up until I hang up(10 -15 
minutes), the other for 30 seconds, that's with using the same UA  and no 
changes to any scripts.

-Original Message-
From: sr-users [mailto:sr-users-boun...@lists.kamailio.org] On Behalf Of Alex 
Balashov
Sent: Sunday, February 11, 2018 8:27 PM
To: Kamailio (SER) - Users Mailing List 
Subject: Re: [SR-Users] Very inconsistent calls



> I have found that calls are very inconsistent.  I use Kamailio 5, 
> Asterisk 14.  When certain Providers like (Sorenson, ZVRS) make calls 
> into a WebRTC client (tryit-jssip), sometime the calls stay up until I 
> close them (10-15 minutes), others times those calls drop in 30 
> seconds.  This is extremely confusing...does anyone else experience 
> this type of behavior?

It is hard to speculate without a capture, and indeed there are lots of moving 
parts with WebRTC. However, the typical reason why an established call would 
drop after ~30 sec (32, to be precise) is that the end-to-end ACK from the 
caller, which completes the required "three-way handshake"
for call establishment, does not reach the callee. This is because it's not 
constructed correctly by the calling UA, not routed correctly by intermediate 
entities, or isn't sent at all by the calling UA.

--
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users