[OpenSER-Users] openser msilo problem

[Daniel-Constantin Mierla]

Hello,

changes in configuration script take place once you restart openser.

Cheers,
Daniel


On 03/20/08 09:01, Devesh wrote:
> Hi Daniel,
>
> Thank you very much.
> Now it's resolved.
> It was exactly authorization problem. Thanks for your support.
> One question (may not be good) but, Is there any timer internally used to
> refresh all cache because same script(after a change) was working after few
> hours.(i.e. changes took place after few hrs.)
> Or is it m/c dependent?
>
>
> Thanks & Regards
> Devesh Bissa
> persistent system ltd.
>  
>  
>
> -----Original Message-----
> From: Daniel-Constantin Mierla [mailto:miconda at gmail.com] 
> Sent: Tuesday, March 18, 2008 4:51 PM
> To: Devesh
> Cc: Users at lists.openser.org
> Subject: Re: [OpenSER-Users] openser msilo problem
>
> Hello,
>
> On 03/18/08 13:02, Devesh wrote:
>   
>> Hi Daniel,
>>           Again thanks.
>> I have commented authentication part from file openser.cfg . But this is
>>     
> not
>   
>> working for me . 
>>     
> there might be other problems.
>   
>> Where should I change in file.
>>   
>>     
> that is hard to tell :-)
>
> I would recommend you to install ngrep, wireshark or other network 
> sniffing tool and watch the sip traffic. It will help to troubleshoot 
> better, you will see where sip messages are sent and where (if) are blocked.
>
> Cheers,
> Daniel
>
> PS. please cc to mailing list.
>
>   
>> Thanks & Regards
>> Devesh Bissa
>> persistent system ltd.
>>  
>>  
>>
>> -----Original Message-----
>> From: Daniel-Constantin Mierla [mailto:miconda at gmail.com] 
>> Sent: Tuesday, March 18, 2008 3:27 PM
>> To: Devesh
>> Cc: users at openser.org
>> Subject: Re: [OpenSER-Users] openser msilo problem
>>
>> Hello,
>>
>> seems that you authenticate the MESSAGEs sent by msilo -- filter out 
>> these ones, the source IP should be localhost.
>>
>> Cheers,
>> Daniel
>>
>>
>> On 03/18/08 11:49, Devesh wrote:
>>   
>>     
>>> Hi Daniel,
>>>           Thanks for your reply.
>>> I am not able to grep any message because this utility is not on my
>>>     
>>>       
>> machine.
>>   
>>     
>>> I am sending you MSILO log.(attached)
>>> Please guide me where I am wrong.
>>>
>>>
>>> Thanks & Regards
>>> Devesh Bissa
>>> persistent system ltd.
>>>  
>>>  
>>>
>>> -----Original Message-----
>>> From: Daniel-Constantin Mierla [mailto:miconda at gmail.com] 
>>> Sent: Tuesday, March 18, 2008 2:30 PM
>>> To: Deveshb
>>> Cc: users at lists.openser.org
>>> Subject: Re: [OpenSER-Users] openser msilo problem
>>>
>>> Hello,
>>>
>>> On 03/14/08 16:17, Deveshb wrote:
>>>   
>>>     
>>>       
>>>> Hi, 
>>>>     I have install openser with msilo module . Offline messages stored
>>>>     
>>>>       
>>>>         
>>> there
>>>   
>>>     
>>>       
>>>> but it's not deliver to client( I am using X-Lite).
>>>> it gives me following error 
>>>> DBG:maxfwd:is_maxfwd_present: max_forwards header not found!
>>>> DBG:uri:has_totag: no totag
>>>> DBG:tm:t_lookup_request: start searching: hash=3841, isACK=0
>>>> DBG:tm:matching_3261: RFC3261 transaction matching failed
>>>> DBG:tm:t_lookup_request: no transaction found
>>>>   
>>>>     
>>>>       
>>>>         
>>> these are not errors, are debug messages.
>>>
>>> Grab the SIP traffic for this case and and send here, that will show 
>>> where the message is delivered. Sample command:
>>>
>>> ngrep -d any -qt -W byline port 5060
>>>
>>> Cheers,
>>> Daniel
>>>
>>>
>>>
>>>   
>>>     
>>>       
>>>> Could you please help me .
>>>>
>>>> Thank you
>>>> Devesh
>>>>   
>>>>     
>>>>       
>>>>         
>>> DISCLAIMER
>>> ==========
>>> This e-mail may contain privileged and confidential information which is
>>>     
>>>       
>> the property of Persistent Systems Ltd. It is intended only for the use of
>> the individual or entity to which it is addressed. If you are not the
>> intended recipient, you are not authorized to read, retain, copy, print,
>> distribute or use this message. If you have received this communication in
>> error, please notify the sender and delete all copies of this message.
>> Persistent Systems Ltd. does not accept any liability for virus infected
>> mails.
>>   
>>     
>>>   
>>>     
>>>       
>> DISCLAIMER
>> ==========
>> This e-mail may contain privileged and confidential information which is
>>     
> the property of Persistent Systems Ltd. It is intended only for the use of
> the individual or entity to which it is addressed. If you are not the
> intended recipient, you are not authorized to read, retain, copy, print,
> distribute or use this message. If you have received this communication in
> error, please notify the sender and delete all copies of this message.
> Persistent Systems Ltd. does not accept any liability for virus infected
> mails.
>   
>>   
>>     
>
>
> DISCLAIMER
> ==========
> This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.
>