[SR-Users] with 302 response dispatcher list .
Daniel-Constantin Mierla
miconda at gmail.com
Fri Mar 5 12:43:11 CET 2021
You say you do not need to use dispatcher module for other purposes, but
then you want to use only that file format for input.
This sounds like trying to stretch on using a file format when it is
maybe not the best variant. You do not aim for getting the thing done,
but to be done only in a particular way. It does not mean it is not
possible, but that would require someone else to be spending more time
for you to find/show a solution that you want in a particular way. In
this case, probably the solution is in reading careful the documentation
of the modules.
Cheers,
Daniel
On 05.03.21 11:46, Devang Dhandhalya wrote:
> Thank you sir for giving this much method .
>
> but in my case i want to take Destination address from
> dispatcher.list file only . and from there when every call coming i
> need to send response 302 and in that contact header i need to add
> those destination by group id . so any XAVP variable use in my case or
> any other way to solve this issue ?
>
> Thanks in Advance
> Devang
>
> On Fri, Mar 5, 2021 at 9:34 AM Devang Dhandhalya
> <devang.dhandhalya at ecosmob.com <mailto:devang.dhandhalya at ecosmob.com>>
> wrote:
>
>
>
> On Thu, Mar 4, 2021 at 6:22 PM Devang Dhandhalya
> <devang.dhandhalya at ecosmob.com
> <mailto:devang.dhandhalya at ecosmob.com>> wrote:
>
> Thank you sir for giving this much method .
>
> but in my case i want to take Destination address from
> dispatcher.list file only . and from there when every call
> coming i need to send response 302 and in that contact header
> i need to add those destination by group id . so any XAVP
> variable use in my case or any other way to solve this issue ?
>
> Thanks in Advance
> Devang
>
> On Thu, Mar 4, 2021 at 6:09 PM Daniel-Constantin Mierla
> <miconda at gmail.com <mailto:miconda at gmail.com>> wrote:
>
> Hello,
>
> then maybe you can keep the list of addresses in database
> and use sql_query() (from sqlops) to retrieve them and
> build the headers using $dbr(...).
>
> Or if you want caching, see the htable module.
>
> If you do not want to use a database system, see db_text
> to use with htable or just read file content with corex
> module.
>
> Further flexibility can be added by using other embedded
> scripting languages, e.g., app_lua.
>
> Cheers,
> Daniel
>
> On 04.03.21 12:31, Devang Dhandhalya wrote:
>> Hello
>>
>> Right now i am not using dispatcher for routing purpose .
>> but i add destination in dispatcher.list and i need to
>> set all those list of destination addresses grouped by
>> id in 302 response in contact header field .
>> .
>> Thanks in advanced
>> Devang
>>
>> On Thu, Mar 4, 2021 at 4:43 PM Daniel-Constantin Mierla
>> <miconda at gmail.com <mailto:miconda at gmail.com>> wrote:
>>
>> 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 <mailto:sr-users at lists.kamailio.org>
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
>>
>> --
>> Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com>
>> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
>> Funding: https://www.paypal.me/dcmierla <https://www.paypal.me/dcmierla>
>>
>>
>> *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.
>
> --
> Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com>
> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
> Funding: https://www.paypal.me/dcmierla <https://www.paypal.me/dcmierla>
>
>
> *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.
--
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/20210305/38c5ff4d/attachment.htm>
More information about the sr-users
mailing list