Hi Daniel,
It works... thanks alot for your help.
Mac.
2014-04-25 0:48 GMT+02:00 Maciej Bylica :
> Hi Daniel,
>
> I am about to do this on Fri and will give you feedback soon.
>
> Thanks
> Mac.
>
>
>
> Can you try the patch from commit:
>>
>> -
>&
didn't have time to troubleshoot more yet.
>
> Cheers,
> Daniel
>
> On 24/04/14 17:10, Maciej Bylica wrote:
>
> Hello
>
> Do you need any other data to verify?
>
> Thanks.
>
>
> 2014-04-23 12:11 GMT+02:00 Maciej Bylica :
>
> Hi Daniel,
>
>
Hello
Do you need any other data to verify?
Thanks.
2014-04-23 12:11 GMT+02:00 Maciej Bylica :
> Hi Daniel,
>
> Here is debug you requested.
>
> DEBUG: [parser/msg_parser.c:623]: parse_msg(): SIP Request:
> DEBUG: [parser/msg_parser.c:625]: parse_msg(): method:
Hi Daniel,
Here is debug you requested.
DEBUG: [parser/msg_parser.c:623]: parse_msg(): SIP Request:
DEBUG: [parser/msg_parser.c:625]: parse_msg(): method:
DEBUG: [parser/msg_parser.c:627]: parse_msg(): uri: <
sip:43111223344@10.10.10.5>
DEBUG: [parser/msg_parser.c:629]: parse_msg():
Hello,
I am working on version: kamailio 4.1.2 (x86_64/linux) and heaving troubles
with drouting module.
The problem i am facing is that kamailio cannot enter routeid that is
provided inside dr_rule table.
My last try was to use standard script file with placing following data
before t_relay
e[11] {
# In case of failure, send it to an alternative route:
if (t_check_status("415|408|404|5[0-9][0-9]")) {
if (!next_gw()) {
t_reply("503", "Service not available, no more
gateways");
exit;
ing
> t_check_trans() before they are processed by TM and therefore ACC.
>
> On 07/09/2010 08:03 AM, Maciej Bylica wrote:
>
>> Dear ALL,
>>
>> I have configured Kamailio 1.5 from svn with radius (radiusclient-ng)
>> support for acc.
>> All seem to work okay,
Dear ALL,
I have configured Kamailio 1.5 from svn with radius (radiusclient-ng)
support for acc.
All seem to work okay, except one thing.
>From time to time I am receiving following radius error (debug from
radius server on different ip)
Fri Jul 9 12:22:58 2010 : Error: rlm_sql (sql): Couldn't up
Juha,
> as you see in above, there is priority column in lcr table. use that
> and arrange so that each gw group has only one gw. then you will be
> sure in which order gws are tried.
Thanks a lot for Your help.
Maciej.
___
SIP Express Router (SER) a
Juha,
> it is weight column, not priority column. weight gives a probability of
> the gw being chosen from among gws of the same group.
What other parameters are taken into account while defining probability?
Is that means, that to achieve 100% predictable "routing" (not to
count on probability)
Hi,
My script is almost done.
I am wondering how weights are calculated in order to choose proper gws list.
For this test I've modified gw table in following way (the same weights).
LCR table points to grp_id=1.
++--+++--+--+
> if dp_translate matches a dialplan match_exp then corresponding attr
> value is assigned to attrs_pvar. you can then prefix $rU with that
> value and call load_gws().
>
Thanks Juha. I am about to implement what You've said.
Maciej.
___
SIP Express R
Hi Juha,
> no you can't. searching for longest matching prefix would not really
> slow if prefix could be regex.
>
> dialplan module supports regexs. perhaps you can you that to produce an
> attribute that you can match to lcr prefixes.
What do You mean by saying that?
How to produce an attribu
Hi again,
Last question in this topic i hope.
Could I use regex in prefix column (lcr table)?
I just want to have a minimum number of entries created there, and to
block the rest of prefixes in this way.
Thx,
Maciej.
2010/6/21 Iñaki Baz Castillo :
> 2010/6/20 Maciej Bylica :
>>
Hi Iñaki,
> You can inspect manually (via script) the calling number and set the
> "from_uri" pseudo variable according to it. Would it be valid?
> Setting "48" and "48221112233" in the lcr entries is not valid as when
> the CLI is 48221112233 both entries would match it (perhaps randomly
> or bas
>> This occurs because the rules with id=1 and id=3 do match the INVITE
>> so if the first fails (longest matching prefix) the other will be
>> executed. This is how LCR works.
>>
>> Use load_gws() with a pseudo-variable as I recommend you in the other
>> mail so you won't rely on the From URI but
> In db:
> ++---+++--+
> | id | prefix | from_uri | grp_id | priority |
> ++---+++--+
> | 1 | 48 | 48 | 1 | 1 |
> | 2 | 48 | 49
2010/5/12 Maciej Bylica :
> 2010/5/12 Iñaki Baz Castillo :
>> 2010/5/12 Maciej Bylica :
>>> Hi ALL,
>>>
>>> I have a problem to configure LCR module to work properly (kamailio rel.
>>> 1.5)
>>> The task in my case is to handle:
>>> 1
2010/5/12 Iñaki Baz Castillo :
> 2010/5/12 Maciej Bylica :
>> Hi ALL,
>>
>> I have a problem to configure LCR module to work properly (kamailio rel. 1.5)
>> The task in my case is to handle:
>> 1) All calls coming with CLD number prefix 482223344 from my MGW
>
Hi ALL,
I have a problem to configure LCR module to work properly (kamailio rel. 1.5)
The task in my case is to handle:
1) All calls coming with CLD number prefix 482223344 from my MGW
(77.77.77.77) towards kamilio and direct them to sip world
(88.88.88.88)
2) Calls with CLD starting with 48 comin
>>> 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 better to fetch for THE SAME data three
>>> times instead of just
Hi Alex,
> 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_route.
Yes you are right. So it is not by my m
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 better to fetch for THE SAME data three
times instead of just one.
Am I right?
But neverth
/4/13 Daniel-Constantin Mierla :
> Hello,
>
> On 4/13/10 10:40 AM, Maciej Bylica wrote:
>>
>> Hi Daniel,
>>
>> The main reason is that i have running configuration exactly on 1.5
>> I am not sure if i can easly copy&paste all stuff from 1.5 (especially
>&g
12/10 8:58 PM, Maciej Bylica wrote:
>>
>> Hi Daniel,
>>
>> Thx for reply. I am about to run through these modules.
>>
>
> btw, you said you are playing with 1.5, any particular reason? 3.0 has a lot
> better core architecture and new features.
>
> Cheer
er, or sometimes you can use
> combined approach, with other modules such as dispatcher.
>
> Cheers,
> Daniel
>
> On 4/12/10 5:23 PM, Maciej Bylica wrote:
>>
>> I guess i can use SQLOps module plus already configured carrierroute
>> to achieve my goal:
>>
I guess i can use SQLOps module plus already configured carrierroute
to achieve my goal:
- call routing based on calling number prefix
- load balancing
- failure routing
Maciej.
> Dear ALL,
>
> I am playing around with kamailio 1.5.
> Could somebody explain me what module best fit to route the c
Dear ALL,
I am playing around with kamailio 1.5.
Could somebody explain me what module best fit to route the call on
the basis of number A (calling number).
What is more all rules should be able to be modified directly from mysql db.
I've run through 3.0 modules and figured out that there is drout
28 matches
Mail list logo
