Hi Michael,
a way could be to have two different dispatcher sets (one for each mvno).
Then you could store the dispatcher set associated to each user in the
usr_preferences table and use it in the routing script.
Something like this in your routing script:
avp_db_load("fU", "$avp(dispatcher-set)");
ds_select_dst("$avp(dispatcher-set)", "4");
Regards,
Federico
On Tue, Dec 15, 2015 at 1:27 PM, Michael Nielsen <mic.nie...@gmail.com>
wrote:
> The reason for my question is that we are 2 mvno's who wants to share a
> single sip mvno trunk - and want to have our individual customers routed
> according to who owns them - but also have the dispatcher functionallity
> for "load-balancing".
>
> On Tue, Dec 15, 2015 at 1:23 PM, Michael Nielsen <mic.nie...@gmail.com>
> wrote:
>
>> Hello everyone,
>>
>> I know kamailio can be configured into almsot everything for SIP - and
>> that the dispatcher function is already build for dispatching between
>> multiple sbc's etc...
>>
>> Is it possible to use the dispatcher for routing between multiple sbc's
>> accroding to called subscriber?
>> So I can make it somewhat multi-tentant.
>>
>> So subscriber A always is routed to 1 or more specific sbc's and
>> subscriber B to 1 or more other spcific sbc's?
>>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
