[Users] record routing problems

[Bogdan-Andrei Iancu]

Hi Danish,

yes that's the problem - if you set an IP as alias, the lack of a port 
number will be interpreted as a wildcard...

regards,
bogdan

Danish Samad wrote:

>Hi bogdan,
> 
> Thanks for your reply. I was surfing through some old mails and found
>out that record routing is dependent on the alias and listen values.
>After I added port values to these parameters the problem was solved.
>
>Regards,
>Danish
>On Mon, 2006-06-05 at 12:23 +0300, Bogdan-Andrei Iancu wrote:
>  
>
>>Hi Danish,
>>
>>openser sees the sip:1313263 at 192.168.1.21:5070 RURI from local as local 
>>- as the debug info shows, the after_strict routing processing is done.
>>
>>What aliases and listen do you have set in the script?
>>
>>regards,
>>bogdan
>>
>>Danish Samad wrote:
>>
>>    
>>
>>>Hi,
>>>
>>>I am trying to run the following setup.
>>>
>>>
>>>  Xten<-->Openser<-->Asterisk
>>>openser ip = 192.168.1.21:5060
>>>asterisk ip = 192.168.1.21:5070
>>>xten = 192.168.1.35:5070
>>>
>>>Xten is registered with openser and calls with particular prefixes are 
>>>forwarded to asterisk. I record route all messages passing through 
>>>openser. The initial INVITE and 200 OK messages are exchanged 
>>>successfully but the associated ACK messages are not processed 
>>>properly by openser. Part of the 200 OK received by xten is shown below
>>>
>>>      
>>>