On 8/4/2015 4:51 AM, Olle E. Johansson wrote:
On 04 Aug 2015, at 13:14, Chad wrote:
Hi list,
I need a little help, I am a business owner trying to get Kamailio up and
running as a SIP load balancer.
I hired a Kamailio consultant to help me do so, but Kamailio is not working and
I am getting
On 04/08/15 16:41, Daniel Tryba wrote:
> On Tuesday 04 August 2015 15:12:31 Daniel-Constantin Mierla wrote:
>> Anyhow, I can't remember any changes in ack processing that could add to
>> this. Are you doing accounting of ACK requests?
> Ehh, yes, accounting in mysql. That explains +/- 0.01 delay
Maybe a bit offtopic, but I can't find a rtpengine mailinglist and know the
Sipwise guys are reading this list.
Since upgrading to 4.2.x and rtpengine instead of rtpproxy I'm seeing problems
with calls being terminated by upstream provider after a bit more than 5m. The
INVITE process looks okay
On Tuesday 04 August 2015 15:12:31 Daniel-Constantin Mierla wrote:
> Anyhow, I can't remember any changes in ack processing that could add to
> this. Are you doing accounting of ACK requests?
Ehh, yes, accounting in mysql. That explains +/- 0.01 delay in routing the
ACK. I think the previously it
Yeah I don't see any registration requests in TCPDUMP or in the kamailio
log. This is what I have in the code (masked sensitive values):
loadmodule "uac.so"
modparam("uac", "reg_db_url",
"mysql://xxx@localhost/kamailio")
modparam("uac", "reg_timer_interval", 60)
modparam("uac", "reg_retr
Hello,
hmmm, quite interesting that the ack takes longer, because invite is
typically larger and also in kamailio likely to be transaction
processing, while ack is just sent out stateless.
Anyhow, I can't remember any changes in ack processing that could add to
this. Are you doing accounting of A
Thanks, i'll make sure those settings are in.
So if I add the account to the table, how do I make sure the outbound call
uses that account?
Thanks
Keith
On Tue, Aug 4, 2015 at 12:19 PM, M S wrote:
> Make sure to enable and set reg_timer_interval and reg_retry_interval
> appropriately. Otherwis
> On 04 Aug 2015, at 13:14, Chad wrote:
>
> Hi list,
> I need a little help, I am a business owner trying to get Kamailio up and
> running as a SIP load balancer.
> I hired a Kamailio consultant to help me do so, but Kamailio is not working
> and I am getting conflicting information.
>
> My K
Well, your provider is right, the top most VIA header define the sender
address where the replies are expected. Each hop in the path adds its own
VIA at top till the request reaches the final destination. At final
destination, the list of VIA headers reflects the reply path from top to
bottom (i.e.
Make sure to enable and set reg_timer_interval and reg_retry_interval
appropriately. Otherwise failing registrations will be disabled and will
not be reattempted.
Thank you.
On Tue, Aug 4, 2015 at 1:13 PM, Keith wrote:
> Thanks for the quick response. I have already tried to use the db method
Thanks for the quick response. I have already tried to use the db method
but can't see the registration requests going out. Is there something you
have to do to force the registration attempts?
Thanks
Keith
On Tue, Aug 4, 2015 at 11:48 AM, M S wrote:
> If you have just one or two carriers requir
Hi list,
I need a little help, I am a business owner trying to get Kamailio up and
running as a SIP load balancer.
I hired a Kamailio consultant to help me do so, but Kamailio is not working and
I am getting conflicting information.
My Kamailio consultant and my VOIP provider are telling me 2 d
If you have just one or two carriers requiring registration, then you can
using this,
http://kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_auth%28%29
If you have many carriers or want db based backend for periodic
registration then look at reg_* module parameters in UAC module,
http
Hi,
I have a carrier who require registration, I have looked at the uac module
but can't see how to do this.
Anyone point me in the right direction?
Thanks
Keith
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists
Since switching to 4.2.5 (from 3.x) a customer has problems with a buggy user
agent (IMHO). What I am seeing now is:
provider kamailio customer
INVITE1->
INVITE1->
<-Trying
<-Trying
<-200 OK
<-200 OK
ACK1->
INVITE2->
15 matches
Mail list logo