[Serdev] Wildcard Symbols Used in Destination Patterns Cisco Gateways

[Klaus Darilion]

Do you already use the LCR module?

You can't make routing logic by registering gateways with wildcard 
destination.

regards,
klaus

You can also use external routing logic by using exec().



Francesco Bottà wrote:

> Hi Klaus,
> 
> I would handle also gateway (located in Small Business Enviroment) with destination pattern that ranges from URI XXX to URI YYY, and for me may be very useful to correlate the lcr table with the location table...static forwarding in this scenario isn't useful....and also, if I know that a gw isn't really registered, then SER go to the next gw in the list and will try with this new loaded gw if it's registered.....what do you think??
> 
> Many thanx
> 
> Verbal
> 
> 
> ----- Original Message ----- 
> From: "Klaus Darilion" <klaus.mailinglists at pernau.at>
> To: "Francesco Bottà" <francesco.botta at eutelia.it>
> Cc: <serdev at lists.iptel.org>
> Sent: Thursday, March 10, 2005 5:34 PM
> Subject: Re: [Serdev] Wildcard Symbols Used in Destination Patterns Cisco Gateways
> 
> 
> 
>>What do you want to achieve?
>>
>>SIP AORs does not support wildcards - they will be trated as normal 
>>letters. If you need wildcard routing, use regular expressens, e.g:
>>
>>if (uri =~ "^sip:\+43664[0-9]+ at .*$") {
>>   # will match for all numbers beginning with +43664
>>   ...
>>   forward to gateway1 ....
>>   ...
>>} else {
>>   ...
>>   forward to gateway1 ....
>>   ...
>>}
>>
>>
>>regards,
>>klaus
>>
>>Francesco Bottà wrote:
>>
>>
>>>Hi SIP Gurus,
>>>
>>>is there a way to register with SER a dial-peer pots configured over a digital Cisco interface, that includes wildcards symbols like '[', ']', '*', '?', 'T', and so on???
>>>I've tryed to workaround this 'issue' but the Registrar (SER) always send me SIP/2.0 400 Bad Request with this HF-->P-Registrar-Error: Error while parsing AOR.
>>>
>>>I should to escape the wildcards symbols'? And in a Cisco documention (Extending SIP Register Support on Gateway ) I've read this hints:
>>>
>>>      1 You need to modify the proxy/registrar behavior to correctly route calls for wildcard patterns or destination pattern with a range. Proxy server or registrars that do not match a wildcard patterns or destination pattern with a range should be ignored for that specific request.
>>>     
>>>
>>>
>>>The wildcards symbols used in Cisco destination pattern are copliant with the AOR's parser in SER?
>>>
>>>
>>>Any suggestions??
>>>
>>>Many thanx
>>>
>>>Verbal
>>>
>>>_______________________________________________
>>>Serdev mailing list
>>>serdev at lists.iptel.org
>>>http://lists.iptel.org/mailman/listinfo/serdev
>>>
>>>
>>
> 
>