[Serusers] mdump() errors

[Daniel-Constantin Mierla]

You find relevant information about how the msilo methods behave and the 
impact of module's parameters on them, in the README file of the module.

When the user goes offline, mdump() returns immediately. When the user 
goes online, mdump() dumps all messages stored for user which is found 
in URI of To header.

When a message is stored (calling mstore()), msilo is able to notify the 
sender that the destination is offline -- that happens only if you set 
registrar parameter. If you don't filter out the messages sent by 
mdump() and you process them in a failure route where you call mstore() 
then, of course, you will get the message stored and a notification message.

If you send me the config file, I will take a look.

Daniel

On 7/22/2004 3:47 PM, Dave Bath wrote:

>The problem seems to be something to do with sip_registrar sending
>messages... 
>
>I don't quite understand how mdump() works... because when admin logs
>off/logs in.. I see in the log that msilo is trying to send messages to
>test1 as well? And of course this user is still offline... surely
>mdump() should only send the messages for the user who has just
>registered... 
>
>Any ideas?
>
>-----Original Message-----
>From: Daniel-Constantin Mierla [mailto:daniel at iptel.org] 
>Sent: 22 July 2004 14:10
>To: Dave Bath
>Cc: serusers at lists.iptel.org
>Subject: Re: [Serusers] mdump() errors
>
>you may need to filter the messages coming from msilo (ser host) and not
>
>call failure route for those (if src_ip==127.0.0.1 or src_ip==ser_ip 
>skip failure route).
>
>Daniel
>
>On 7/22/2004 2:51 PM, Dave Bath wrote:
>
[...]