[OpenSIPS-Users] Opensips as a $si differentiator
Maciej Bylica
mbsip at gazeta.pl
Fri Oct 14 15:30:45 CEST 2011
Thanks for prompt feedback.
That is what i was looking for.
Cheers
Maciej
> Hello,
>
> a solution would be checking for the sourceip and using force_send_socket()
> to set a different interface, which will be used by t_relay.
>
>
> if ($si=~"^108\.109\.180\." || $si=~"^10\.10\.10\." {
> force_send_socket(udp:108.109.180.12:5060);
> }
>
> ....
>
> t_relay();
>
>
>
>
> Best Regards
>
> Max M.
>
> Am 14.10.2011 11:26, schrieb Maciej Bylica:
>>
>> Hello,
>>
>> I am in need to build a box which should have some functions of SBC.
>> To be more precisely server will be heaving two interfaces, the first
>> one i could say on access side, the last one on core/private side. I
>> want to implement a kind of call limitation mechanism (by using pike
>> module as a trigger) and to make routing mechanism like following
>> - if $si = X.X.X.X then t_relay the call by using second interface and
>> its subinterface Z1
>> - if $si = Y.Y.Y.Y then t_relay the call by using second interface and
>> its subinterface Z2
>> and so on.
>> So in other words i need to have mechanism that is checking source
>> address of all incoming sip messages and then make decision which
>> subinterface to use for t_relay.
>> Each subinterface will be heaving different ip address to achieve
>> customer differentiation.
>>
>> I am puzzling over how to build such a mechanism, which modules to use?
>>
>> Could you please give me some hints here.
>>
>> Thanks,
>> Maciej
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
More information about the Users
mailing list