[Spce-user] Best way to force gateway?
Daniel Grotti
dgrotti at sipwise.com
Tue Jan 29 08:52:12 EST 2019
Yes, I think you can create a 2 peering server with same ip:port.
--
Daniel Grotti
Head of Customer Support Sipwise GmbH
e: dgrotti at sipwise.com Europaring F15
t: +43(0)130120332 A-2345 Brunn Am Gebirge
w: www.sipwise.com FN: 305595f FG: LG Wiener Neustadt
On 1/29/19 2:45 PM, Henk wrote:
> Hi Daniel,
>
> Now I understand what you mean. Indeed a better solution.
> Is it allowed to use a peering server twice? I know mediator will
> complain with "medmysql.c:1043 [<unknown>]: Skipping duplicate IP
> ...", but it seems that is only an innocent warning.
>
> Regards,
>
> Henk
>
> On 29-1-2019 14:23, Daniel Grotti wrote:
>> You still can use the caller prefix or caller pattern in the peering
>> rules in order to match the peers.
>>
>> --
>> Daniel Grotti
>>
>> Head of Customer Support Sipwise GmbH
>> e: dgrotti at sipwise.com Europaring F15
>> t: +43(0)130120332 A-2345 Brunn Am Gebirge
>> w: www.sipwise.com FN: 305595f FG: LG Wiener Neustadt
>>
>> On 1/29/19 2:21 PM, Henk wrote:
>>> Hi Daniel,
>>>
>>> If I understand you correctly, that will route all users to this
>>> peering and that is not my purpose. I have to route only some
>>> special users to this route, as the normal 'high quality' route is
>>> too expensive e.g. a NoCLI route. So these users are not allowed to
>>> take the quality route, even when the cheap route fails.
>>>
>>> Is it possible to strip the prefix before rating? Normally this is
>>> done on the user level, but then forcing a specific gateway is not
>>> possible anymore.
>>>
>>> Regards,
>>>
>>> Henk
>>>
>>>
>>> On 29-1-2019 13:14, Daniel Grotti wrote:
>>>> Hi Henk,
>>>> yes there is indeed.
>>>> you can create another PEERING GROUP with your cheap peering server
>>>> inside, using the "normal" peering rules as the other "classic"
>>>> peerings.
>>>> The only need to do is to assign a highest priority to this GROUP.
>>>> So your peer will be selected as first option always.
>>>>
>>>> Please check documentation to see how to set priority to the
>>>> peering group.
>>>>
>>>> Regards,
>>>>
>>>>
>>>> --
>>>> Daniel Grotti
>>>>
>>>> Head of Customer Support Sipwise GmbH
>>>> e: dgrotti at sipwise.com Europaring F15
>>>> t: +43(0)130120332 A-2345 Brunn Am Gebirge
>>>> w: www.sipwise.com FN: 305595f FG: LG Wiener Neustadt
>>>>
>>>> On 1/28/19 5:05 PM, Henk wrote:
>>>>> Hi,
>>>>>
>>>>> Some of my customers are using cheap routes and I want to force
>>>>> them to take a predefined gateway. At the moment I'm using a
>>>>> prefix like 800 for this (this country-code doesn't exist).
>>>>> The problem is, that while it's easy to select the correct
>>>>> gateway, with a callee pattern like ^sip:800.* , the prices with
>>>>> prefix must exist, resulting in pricelists with destination
>>>>> patterns like ^(80[0-2])?31800 if the gateway is used for routes
>>>>> without prefix and with prefix 800..802.
>>>>> While working correctly, it's not exactly good for speed with
>>>>> lists >40000 entries and going through multiple lists.
>>>>>
>>>>> So my question, is there a better way to do this?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Henk
>>>>>
>>>>> _______________________________________________
>>>>> Spce-user mailing list
>>>>> Spce-user at lists.sipwise.com
>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com
>>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
More information about the Spce-user
mailing list