[SR-Users] with 302 response dispatcher list .

[Daniel-Constantin Mierla]

Hello,

do you need dispatcher for providing something else? Or just to keep the
list of addresses grouped by id? There can be other variants if
dispatcher is not needed for something else.

Cheers,
Daniel

On 04.03.21 09:19, Devang Dhandhalya wrote:
> my scenario is : i have dispatcher list 
>
> # dispatcher destination sets (groups)
> #
>
> # line format
> # setid(int) destination(sip uri) flags(int,opt) priority(int,opt)
> attributes(str,opt)
>
> # proxies
> 2 sip:172.19.56.21:5060 <http://172.19.56.21:5060> 0 1
> 2 sip:172.19.56.22:5060 <http://172.19.56.22:5060> 0 2
>
> # gateways
> 1 sip:192.168.0.11:5060 <http://192.168.0.11:5060> 0 1
> 1 sip:192.168.0.22:5060 <http://192.168.0.22:5060> 0 2
> 1 sip:192.168.0.33:5060 <http://192.168.0.33:5060> 0 3
>
> when call coming from first time client to kamailio . kamailio just
> need to send 302 response to the client with all destination ip of
> group id 1 priority wise  in its contact header field   . in easy way 
>
> client ------------------> kamailio 
>                  302    33(3) 22(2) 11(1) 
>            <---------------
>
> and when call coming second time from client to kamailio . kamailio
> need to send group id 2 all destination ip in 302 response in its
> contact header field . 
>
> client ------------------> kamailio 
>                  302    22(2) 21(1)  
>            <---------------
>
> can any one suggest me how to do this thing from kamailio side ? use
> of append_branch is good option but how to configure  this scenario . 
>
> Thanks in advance
> Devang
>
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our
> website, any views or opinions presented in this email are solely
> those of the originator and do not necessarily represent those of the
> Company or its sister concerns. Any liability (in negligence, contract
> or otherwise) arising from any third party taking any action, or
> refraining from taking any action on the basis of any of the
> information contained in this email is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for
> the use of the addressee(s) and contains information that is
> PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination,
> distribution, or copying of this communication is prohibited. Please
> inform originator if you have received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of
> viruses, trojans, similar or new contaminants/malware, interceptions
> or interference, and may not be compatible with your systems. You
> shall carry out virus/malware scanning on your own before opening any
> attachment to this e-mail. The sender of this e-mail and Company
> including its sister concerns shall not be liable for any damage that
> may incur to you as a result of viruses, incompleteness of this
> message, a delay in receipt of this message or any other computer
> problems. 
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20210304/472126ae/attachment.htm>