On 19 April 2010 19:01, Juha Heinanen wrote:
> dotnetdub writes:
>
> If I wanted to for example strip the - character
> what would be the best
> way?TIA.Stephen.
>
> see, for example, textops subst_user('/re/repl/flags').
>
> -- juha
>
Thanks Alex - Juha..
___
dotnetdub writes:
If I wanted to for example strip the - character
what would be the best
way?TIA.Stephen.
see, for example, textops subst_user('/re/repl/flags').
-- juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-u
On 04/19/2010 01:55 PM, dotnetdub wrote:
Hi,
Running 1.53 and also 3.01
I know there are operators to strip() and strip_tail() to remove
characters from the front and end of a uri - what would people recommend
to make sure that the uri only ever contains numerical value?
If I wanted to for exa
Hi,
Running 1.53 and also 3.01
I know there are operators to strip() and strip_tail() to remove characters
from the front and end of a uri - what would people recommend to make sure
that the uri only ever contains numerical value?
If I wanted to for example strip the - character what would be th
Juha-
Vikram had posted a while back on the thread where he explained a bit more
about his resolution and the fact the issue
was occurring with VoipSwitch but not asterisk. Let us know if you want a link
to that.
Thanks for following up.
-Jeff
Original Message -
Juha,
what was the conclusion regarding this? did the problem go away when
you called nat traversal functions both on 180 ringing and 183 session
progress?
Yes. The problem did go away once we started forcing rtpproxy on 180
Ringing also.
Thanks and Regards,
Vikram.
__
Hi all,
I have a kamailio sip server with two trunk connections to two asterisk
servers. The register server is kamailio. I'd like to be able to configure a
load balancing with kamailio between two asterisk servers. How can i do
that? Do you know any good tutorial for configure load balancing with
On 4/19/10 9:54 AM, Alex Balashov wrote:
On 04/19/2010 03:50 AM, Alex Balashov wrote:
On 04/19/2010 03:36 AM, Iñaki Baz Castillo wrote:
AFAIR the main purpose of local_route was to handle the locallly
generated BYE for accounting purposes.
I defined an event_route[tm:local-request] but it
On 04/19/2010 03:54 AM, Alex Balashov wrote:
On 04/19/2010 03:50 AM, Alex Balashov wrote:
On 04/19/2010 03:36 AM, Iñaki Baz Castillo wrote:
AFAIR the main purpose of local_route was to handle the locallly
generated BYE for accounting purposes.
I defined an event_route[tm:local-request] but i
On 4/19/10 1:35 AM, Alex Balashov wrote:
On 04/18/2010 01:21 PM, Maciej Bylica wrote:
Hello,
I am trying to use SQLOps Module in my kamailio 1.5 configuration.
According to your explanations every result of sql_query should be
freed just after using that data.
So it means that there will be
On Monday 19 April 2010, Maciej Bylica wrote:
> > As far as I know, sqlops results are freed at the end of invocation of
> > script processing of a given message, be that a request or a reply. They
> > do not persist for the life of the transaction, and therefore cannot be
> > reused in failure_rou
On 04/19/2010 03:50 AM, Alex Balashov wrote:
On 04/19/2010 03:36 AM, Iñaki Baz Castillo wrote:
AFAIR the main purpose of local_route was to handle the locallly
generated BYE for accounting purposes.
I defined an event_route[tm:local-request] but it does not appear to
fire in this scenario. Is
On 04/19/2010 03:36 AM, Iñaki Baz Castillo wrote:
AFAIR the main purpose of local_route was to handle the locallly
generated BYE for accounting purposes.
I defined an event_route[tm:local-request] but it does not appear to
fire in this scenario. Is it supposed to? Is there a possibility
th
2010/4/19 Alex Balashov :
>> Have you tryed local_route to manage it?
>> It's also called event_route in kamailio 3.0:
>>
>> http://www.kamailio.org/dokuwiki/doku.php/features:new-in-3.0.x#event_route
>
> Interesting idea.
>
> "event_route[tm:local-request] - executed by tm modules when a
> lo
On 04/19/2010 03:28 AM, Iñaki Baz Castillo wrote:
2010/4/19 Alex Balashov:
2) The spoofed BYEs that are generated by the proxy with this setting do not
show up as sequential requests, nor are catchable in script at all. As a
result, BYE events are not written to CDRs with 'acc' and I have no wa
2010/4/19 Alex Balashov :
> 2) The spoofed BYEs that are generated by the proxy with this setting do not
> show up as sequential requests, nor are catchable in script at all. As a
> result, BYE events are not written to CDRs with 'acc' and I have no way of
> knowing when the call actually closed.
Maybe the solution here is to generate a synthetic custom request with
$uac_req() and uac_send_req(), like with method SYNTHETIC_BYE?
The problem is that I cannot populate it with the From URI, Call-ID,
etc. because that information is not available in the
timeout-triggered route to begin with
On 04/19/2010 02:00 AM, Alex Balashov wrote:
(a) Define a $dlg_ctx(timeout_route) and have it write a BYE event
artificially using acc_db_request().
Well, this isn't going to work.
I tried having it write a "201 Initial" event that my triggers can
postprocess as though it were a BYE, a la:
18 matches
Mail list logo
