Hi Alex
Yeah I think we may out of luck.
Do you know how to send the session-timer = refuse flag to try though? I
didn't see how to do it looking at the SST module.
I hope all is going well with you and thanks again for your help.
All the best.
Will
On Thu, Feb 19, 2015 at 4:15 PM, Alex Balas
You can try it, but if they shove SST reinvites down your throat despite no indicated support for them from the client, or the client sends SST headers despite no indicated support from the carrier, there are deep
Hi Alex
Ok, not the 200 ok from the carrier from the initial invite has the
supported heard, but it is stripped by the first box that receives it in
our system.
The carrier still sends the second invite however.
Is there any way we can signal to the carrier not to send the second invite
-- perha
Tom,
This list is for users, but we do have a list just for business requests:
http://lists.kamailio.org/cgi-bin/mailman/listinfo/business
We also have a business directory:
http://www.kamailio.org/w/business-directory/
You'll have great luck with both of the above.
Fred Posner
The Palner Gr
On 02/19/2015 06:26 PM, Alex Balashov wrote:
onreply_route[MAIN_REPLY] {
if(t_check_status("200")) {
if_is_present_hf("Supported"))
Sorry:
if(is_present_hf("Supported"))
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 3
Hi Alex
Thanks so much.
I will try it right now.
All the best.
Will
On Thu, Feb 19, 2015 at 3:27 PM, Alex Balashov
wrote:
> On 02/19/2015 06:26 PM, Alex Balashov wrote:
>
> onreply_route[MAIN_REPLY] {
>>if(t_check_status("200")) {
>> if_is_present_hf("Supported"))
>>
>
Since timer is Supported: but not Required:, you're almost certainly
safe to simply remove it in Kamailio, even though, of course, strictly
speaking, that is not RFC 3261-compliant proxy behaviour.
As a simple test, try:
request_route {
...
# Handle initial INVITE.
t_on_
Hi Alex
In the test case I have right now we send the carrier an invite.
Our invite to the carrier doesn't have either the required or the supported
headers.
There 200 ok however has the following supported header:
Supported: timer, path, replaces
Thanks again for the assistance.
All the best
Will,
Can we see the Required and/or Supported headers of both
1) The initial INVITE
2) The 200 OK response to that initial INVITE?
Thanks,
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web: http://www.
Good morning,
I'm looking for someone who, according to my guidelines set kamailio and
connect the asterisk.
Kamailio to act as a proxy server to accept registrations sip and locate.
Pay for the correct configuration.
Please contact me with people interested.
Regards
Tom
_
Hi All
Wow, thanks so much for the conversation on sorting this out.
I think you are right, it is likely a session timer issue.
I found this tag on the 200 ok from the carrier:
Session-Expires: 300;refresher=uas
It may not help anything but I would like to try setting the session-timer
= refus
Hi,
On 02/19/2015 12:59 PM, Andres wrote:
We have struggled with this issue ourselves. The problem was that we
did not want our SIP server to behave like an open relay. We were
seeing that the session-timer Re-Invites have a Request-URI with the IP
of the other
endpoint instead of the Proxy.
Well ... kamailio is a proxy (not a B2BUA), and in dialog requests should
not point at the proxy.
If you are paranoid about it, then you can alter signalling by mangling and
de-mangling the Contact header for requests and reply to achieve that.
Regards,
Ovidiu Sas
On Thu, Feb 19, 2015 at 12:59 PM
On 2/18/15 9:44 PM, Will Ferrer wrote:
Hi Alex
Thanks so much for the reply.
Is there anything that we could do perhaps that is a more creative
solution, for instance not passing the re-invite all the way to the
softphone and just responding from the kamailio box handling the call?
We tried
On 19 Feb 2015, at 15:44, Michael Young wrote:
> Some carriers require session timers -- even if you refuse them in
> Asterisk\Freeswitch\etc, the call will disconnect when the timer fires off.
> I wouldn't rely on this as a possible solution in this situation.
>
The standard is written in a wa
My experience is that the more common approach is an informal implementation of
dead peer detection using reinvites, albeit without the formal complications of
SSTs (e.g. refresher roles). For instance, Metaswitch takes this approach.
If that's the case here, nothing will be warmer or colder fro
Some carriers require session timers -- even if you refuse them in
Asterisk\Freeswitch\etc, the call will disconnect when the timer fires off.
I wouldn't rely on this as a possible solution in this situation.
Michael
-Original Message-
From: sr-users [mailto:sr-users-boun...@lists.sip-rou
If session timers, you can accept or refuse in UAS. Eg asterisk peer settings :
session-timer = accept | refuse | originate.
> On 19 Feb 2015, at 14:26, Daniel Tryba wrote:
>
>> On Thursday 19 February 2015 03:44:25 Will Ferrer wrote:
>> Hopefully there is something clever we could do to corr
On Thursday 19 February 2015 03:44:25 Will Ferrer wrote:
> Hopefully there is something clever we could do to correct the problem, it
> is preventing us from using alot of our carriers since the re-invite breaks
> our clients softphones.
What kind of reInvites are this? If they are session timer r
Sure, but Will's question was about whether the problem can be fixed via Kamailio per se.
Using a B2BUA would possibly be a solution.
--FC
Sent from my 6 plus
> On Feb 19, 2015, at 05:12, Alex Balashov wrote:
>
> Hi Will,
>
> Unfortunately, there's not a clever workaround at your disposal here, of all
> scenarios. The SDP payload in the 200 OK must mimic that endpoint's previous
Hi all
I need to check a given uri against dispatcher destination entries. I see that
it's possible in kamailio 4.2 using ds_is_from_list which allows "uri"
parameter but it's not available in version 3.3.
Moving to 4.x is not an option this time.
Any hints about how to check this? Raw sql + s
Hi Will,Unfortunately, there's not a clever workaround at your disposal here, of all scenarios. The SDP payload in the 200 OK must mimic that endpoint's previous SDP answer in order for there to be media continui
We also need to check the core file from the crash.
/O
On 19 Feb 2015, at 09:30, Daniel-Constantin Mierla wrote:
> Hello,
>
> can you send the REGISTER request received by kamailio and your config to me?
>
> As you receive it over TLS, you can get the register by adding the next line
> in kam
Hello,
the solution with deleting my.cnf is quite strange, I would say. Perhaps
it has to do with type auto-conversion in mysql, my.cnf was probably
setting a strict rule on that.
The db_extra columns should be defined as varchar - kamailio is writing
the values as string.
Cheers,
Daniel
On 17/
Hello,
the ctl module is creating the socket file with a user id other than
what kamailio is running. Look at ctl readme to see how to set the user
and group for socket file.
On the other hand, this is a message printed at shutdown, when you stop
kamailio, it is harmless.
Cheers,
Daniel
On 17/0
Hello,
can you send the REGISTER request received by kamailio and your config
to me?
As you receive it over TLS, you can get the register by adding the next
line in kamailio.cfg at the beginning of request_route:
xlog("received request: [[$mb]]\n");
I will like to double check if the issue is s
27 matches
Mail list logo
