Re: [SR-Users] Kamailio drouting failure not working

Hi, Actually now when clicking Cancel button it's rerouting to next gateway , I just want to stop that and end the call at this level , that's why I'm trying to filter on code 486 and exit when this condition is met. But it's not working :( Any help please. Regards, Ali

Re: [SR-Users] Kamailio drouting failure not working

Hi Can you please inform me in what location is the output of xlog ? Regards, Ali From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Dmitri Savolainen Sent: Tuesday, May 26, 2015 6:20 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Kamailio d

Re: [SR-Users] Kamailio drouting failure not working

Hi, Actually now when clicking Cancel button it's rerouting to next gateway , I just want to stop that and end the call at this level , that's why I'm trying to filter on code 486 and exit when this condition is met. But it's not working :( Any help please. Regards, Ali From: s

Re: [SR-Users] Kamailio drouting failure not working

Hello, On 26/05/15 19:02, Ali Taher wrote: > Hi > > As mentioned before, i tried > >> if (t_check_status("486")){ >> >> exit; >> >> } >> > in failure_route but didnt work. what you do above is not to re-route in case the reply code is 486. If you want to re-route only i

Re: [SR-Users] Kamailio drouting failure not working

Hello, maybe is better to try first without filtering on reply code inside failure route apart of canceled transaction. Once you get that going, then you can start putting rules on reply codes. Cheers, Daniel On 26/05/15 17:55, Ali Taher wrote: > > Hi, > > > > In wireshark, I’m getting *Status

Re: [SR-Users] usage of t_flush_flags() in event_route

Hello, I haven't used this event route and the flags, if they don't persist afterwards, then maybe it needs a patch to be fixed. Hugh implemented it, iirc, not sure if he was looking at this aspect. Cheers, Daniel On 26/05/15 16:14, Andrew Pogrebennyk wrote: > Hi Daniel and others, > I'm having

Re: [SR-Users] Kamailio with public ip, users behind nat

On 26/05/15 14:04, Daniel Tryba wrote: > On Tuesday 26 May 2015 13:34:51 MtK - SmartMtK wrote: >> I understood I need to install RTPproxy, but all tutorials out there are >> for servers behind nat, and they talk about the server's private IP, which >> does not exists in this case. >> >> how would

Re: [SR-Users] Kamailio drouting failure not working

Hi, In wireshark, I’m getting Status: 486 Busy Here | , when cancel button is clicked. Isnt’ that meaning that the reply code is 486? Regards, Ali Taher Technical Support Engineer T&F M W A +961-5-457437 Ext 215 +961-70-010600

Re: [SR-Users] Kamailio drouting failure not working

Hi As mentioned before, i tried >> if (t_check_status("486")){ >> >> exit; >> >> } >> in failure_route but didnt work. Regards, Ali Sent from my iPhone > On May 26, 2015, at 7:45 PM, Dmitri Savolainen wrote: > > yes, status code 486 in sip flow has to match 486 transaction

Re: [SR-Users] Kamailio drouting failure not working

yes, status code 486 in sip flow has to match 486 transaction status in script 2015-05-26 19:21 GMT+03:00 Ali Taher : > Hi, > > > > In wireshark, I’m getting *Status: 486 Busy Here | *, when cancel button > is clicked. > > Isnt’ that meaning that the reply code is 486? > > > > Regards, > > Ali

Re: [SR-Users] Kamailio drouting failure not working

Hi, In wireshark, I’m getting Status: 486 Busy Here | , when cancel button is clicked. Isnt’ that meaning that the reply code is 486? Regards, Ali From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Dmitri Savolainen Sent: Tuesday, May 26, 2015 6:20 PM To: Ka

Re: [SR-Users] Kamailio drouting failure not working

Sorry, I did not read the question carefully. Really 486 usually send by phone, when clicking ignore so this statement before "use_next_gw()" usually works: if (t_check_status("486")){ exit; } but may be your phone generate smth else (not 486). i use smth like this before use_next_gw()

Re: [SR-Users] Kamailio drouting failure not working

Hi, Below is failure_route content: failure_route[1] { if(t_is_canceled()) { exit; } if (use_next_gw()) { t_relay(); exit; } else { t_reply ("503", "Service not available"); exit; } } Noting that phone is showing :

Re: [SR-Users] Kamailio drouting failure not working

show failure_route content and response from phone (while clicking on ignore) 2015-05-26 17:33 GMT+03:00 Ali Taher : > Hi, > > > > Thanks for your fast reply. > > > > I tried below condition in failure_route but still rerouted to next > destination when clicking on ignore. > > > > Appreciate yo

Re: [SR-Users] Kamailio drouting failure not working

Hi, Thanks for your fast reply. I tried below condition in failure_route but still rerouted to next destination when clicking on ignore. Appreciate your help. Regards, Ali Taher Technical Support Engineer T&F M W A +961-5-457437 Ext 215 +961-70

Re: [SR-Users] Kamailio drouting failure not working

486 is a busy error; you may use in faulure_route : if ( t_is_canceled() ){ exit; } 2015-05-26 17:09 GMT+03:00 Ali Taher : > Hi, > > > > Thanks for your reply , it’s working fine now. > > Yet, when a call is rerouted to a gateway which cancel it (by clicking on > ignore button),

[SR-Users] usage of t_flush_flags() in event_route

Hi Daniel and others, I'm having a problem with acc module if I'm using the event_route/ branch-failure: say, the call comes from the app server and goes to the registered user. We arm the the failure route and per-branch failure route for the 302 redirect from the UA. We explicitly reset the accou

Re: [SR-Users] Kamailio drouting failure not working

Hi, Thanks for your reply , it’s working fine now. Yet, when a call is rerouted to a gateway which cancel it (by clicking on ignore button), call is then rerouted to next gateway which is not correct. I tried to add this condition : If(t_check_status(“486”)) { exit;} in failure_route

Re: [SR-Users] Kamailio drouting failure not working

if (t_check_status("[34][0-9][0-9]")) { exit; } request timeout == 408 error, so "if (use_next_gw()) {" never called -- Savolainen Dmitri ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@list

Re: [SR-Users] Kamailio with public ip, users behind nat

On Tuesday 26 May 2015 13:34:51 MtK - SmartMtK wrote: > I understood I need to install RTPproxy, but all tutorials out there are > for servers behind nat, and they talk about the server's private IP, which > does not exists in this case. > > how would I configure RTPproxy and Kamailio to allow use

[SR-Users] Kamailio with public ip, users behind nat

Hi, I'm trying to install Kamailio on a server with a public IP, but my users are mostly at their homes (a.k.a behind NAT). I understood I need to install RTPproxy, but all tutorials out there are for servers behind nat, and they talk about the server's private IP, which does not exists in this cas

Re: [SR-Users] Kamailio drouting failure not working

Hello, I added below parameters but still didn't rerouted to second destination :( modparam("drouting", "ruri_avp", '$avp(dr_ruri)') modparam("drouting", "attrs_avp", '$avp(dr_attrs)') regards, Ali Taher Technical Support Engineer T&F M W A +961-5-45

Re: [SR-Users] Kamailio drouting failure not working

Hello, iirc, you have to set some parameter that is related to AVP storing the addresses for re-routing. Look at the readme of the module, see the parameters that have avp in name or something similar. Cheers, Daniel On 26/05/15 12:27, Ali Taher wrote: > > Hello, > > > > Below are parameters u

Re: [SR-Users] Kamailio drouting failure not working

Hello, Below are parameters used for drouting module : modparam("drouting", "db_url","mysql://kamailio:ali@localhost/kamailio") modparam("drouting", "drd_table", "dr_gateways") modparam("drouting", "drr_table", "dr_rules") modparam("drouting", "drg_table", "dr_groups") modparam("droutin

Re: [SR-Users] Header field Contact not changed on kamailio 4.2

Hello, do you see the xlog message "Contact modified" in syslog? Maybe that part of config is not executed due to other conditions. You can enable cfgtrace for debugger module and see what actions are executed from configuration file. Cheers, Daniel On 25/05/15 10:04, Зуев Михаил wrote: > > Hi a

Re: [SR-Users] Kamailio drouting failure not working

Hello, what are the parameters for drouting module? Cheers, Daniel On 26/05/15 11:14, Ali Taher wrote: > > Dears, > > > > I’m trying drouting module in kamailio , it’s working good when first > gateway in the list is up , yet when first gateway is unrecheable , > it’s not rerouted to second de

Re: [SR-Users] dbcassandra schema files

Hello, few of them are available in the source code, at: utils/kamctl/dbcassandra/kamailio/ But I guess not up to date if you test with master branch. I haven't used cassandra yet to be able to help more, but we can add any schema definitions in the repository in order to help everyone using cas

[SR-Users] Kamailio drouting failure not working

Dears, I'm trying drouting module in kamailio , it's working good when first gateway in the list is up , yet when first gateway is unrecheable , it's not rerouted to second destination, meaning that fail over is not working. Kindly find attached wireshark trace I'm getting . Below is db

[SR-Users] Development open again for master branch

Hello, as branch 4.3 was created to host the upcoming release series 4.3, new features can be now pushed to master branch. They will be part of the next future release, likely to be numbered 4.4. Any fixes that affect existing code in branches 4.3 or older version have to be backported - push fir

[SR-Users] Branch 4.3 created

Hello, the GIT branch 4.3 was created, it will host the release series 4.3.x. To get this branch from GIT, you can use: git clone https://github.com/kamailio/kamailio.git kamailio cd kamailio git checkout -b 4.3 origin/4.3 Notes about installing Kamailio from this branch are available at: - h