[SR-Users] dispatcher: set $du in failure_route

Daniel-Constantin Mierla miconda at gmail.com
Thu Sep 19 21:10:46 CEST 2013

On 9/18/13 4:53 PM, Grant Bagdasarian wrote:
> My Dispatcher table has been extended with more columns and also 
> functions as our routing table.
> I've modified the names of the columns Dispatcher uses to match the 
> columns of the routing table.
> One of the columns contains the address which is used to set the $du 
> value.
> So, for every request I'm executing a stored procedure using sqlops to 
> select the address of the SBC (for $du) and the set id to use for the 
> dispatcher.
> If I'm correct, the dispatcher table is loaded into memory once 
> Kamailio is started or the table is reloaded.
> In case the first destination fails, how would I get the address of 
> the next SBC to reset the $du value in failure_route?
> I think I can do it using the setid and the next priority, but how do 
> I access these two values in failure_route?
> Are there any other solutions to this, perhaps other modules with 
> similar functionality as the dispatcher module?

The setid and next hop address are stored in AVPs, the names of the avps 
are set via module parameters. See readme starting at:


In failure route, before calling ds_next_*(), the first avps store the 
values used for next destination. You can probably use them for your db 


> *From:*sr-users-bounces at lists.sip-router.org 
> [mailto:sr-users-bounces at lists.sip-router.org] *On Behalf Of *Alex 
> Balashov
> *Sent:* Wednesday, September 18, 2013 4:23 PM
> *To:* Kamailio (SER) - Users Mailing List
> *Subject:* Re: [SR-Users] dispatcher: set $du in failure_route
> Of course.
> Grant Bagdasarian <GB at cm.nl <mailto:GB at cm.nl>> wrote:
> Hello,
> Can the $du value also be set in a failure_route? For instance in the 
> case the first destination fails.
> I'm currently setting the $du value before I'm calling the 
> ds_next_domain function in request_route.
> We have multiple carriers which are connected to different SBCs.
> In case $du is not re-set in failure_route, Kamailio will try to send 
> the INVITE to the carrier directly, bypassing the SBC, correct?
> Regards,
> Grant
> ------------------------------------------------------------------------
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org  <mailto:sr-users at lists.sip-router.org>
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> --
> Sent from my mobile, and thus lacking in the refinement one might 
> expect from a fully fledged keyboard.
> Alex Balashov - Principal
> Evariste Systems LLC
> 235 E Ponce de Leon Ave
> Suite 106
> Decatur, GA 30030
> United States
> Tel: +1-678-954-0671
> Web: http://www.evaristesys.com/, http://www.alexbalashov.com
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Oct 21-24; Miami, Nov 11-13, 2013
   - more details about Kamailio trainings at http://www.asipto.com -

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20130919/1a2d97c6/attachment.html>

More information about the sr-users mailing list