11 May
2009
11 May
'09
12:31 p.m.
i recently added a new feature to k msilo module and now took a look how
does s msilo compare to k's. it turns out that k msilo module has lots
of stuff that is missing from s version.
there seems to be one difference though. in s module there is this:
registrar (string)
The SIP address used to inform users that destination of their message
is not online and the message will be delivered next time when that
user goes online. If the parameter is not set, the module will not
send any notification. All requests intended for this SIP address will
not be stored for lately delivery.
Default value is "NULL".
Example 5. Set the registrar parameter
...
modparam("msilo", "registrar", "sip:registrar@iptel.org")
and the corresponding thing in k is this:
1.3.3. from_address (string)
The SIP address used to inform users that destination of their
message is not online and the message will be delivered next
time when that user goes online. If the parameter is not set,
the module will not send any notification. It can contain
pseudo-variables.
Default value is "NULL".
Example 1.3. Set the "from_address" parameter
...
modparam("msilo", "from_address",
"sip:registrar@example.org")
modparam("msilo", "from_address", "sip:$rU@example.org")
in my opnion the difference is so small that we could adopt k version of
msilo as is.
comments?
-- juha
11 May
11 May
1:32 p.m.
New subject: [SR-Dev] msilo comparison
On 11-05 12:31, Juha Heinanen wrote:
i recently added a new feature to k msilo module and
now took a look how
does s msilo compare to k's. it turns out that k msilo module has lots
of stuff that is missing from s version.
there seems to be one difference though. in s module there is this:
registrar (string)
The SIP address used to inform users that destination of their message
is not online and the message will be delivered next time when that
user goes online. If the parameter is not set, the module will not
send any notification. All requests intended for this SIP address will
not be stored for lately delivery.
Default value is "NULL".
Example 5. Set the registrar parameter
...
modparam("msilo", "registrar", "sip:registrar@iptel.org")
and the corresponding thing in k is this:
1.3.3. from_address (string)
The SIP address used to inform users that destination of their
message is not online and the message will be delivered next
time when that user goes online. If the parameter is not set,
the module will not send any notification. It can contain
pseudo-variables.
Default value is "NULL".
Example 1.3. Set the "from_address" parameter
...
modparam("msilo", "from_address",
"sip:registrar@example.org")
modparam("msilo", "from_address", "sip:$rU@example.org")
in my opnion the difference is so small that we could adopt k version of
msilo as is.
comments?
There is more, the ser version of the module has a different database table,
we use uids to identify owners of stored messages. This is something we use
and need to preserve.
Jan.
1:57 p.m.
New subject: [SR-Dev] msilo comparison
Jan Janak writes:
There is more, the ser version of the module has a
different database table,
we use uids to identify owners of stored messages. This is something we use
and need to preserve.
ok, we'll have two msilo modules then.
may be it would be a good idea to record these on a wiki page, i.e, what
are the reasons for two versions of each module?
-- juha
4:04 p.m.
New subject: [SR-Dev] msilo comparison
On 11-05 13:57, Juha Heinanen wrote:
Jan Janak writes:
http://sip-router.org/wiki/migration/module_differences
So far only msilo is listed there.
Jan.
There is more, the ser version of the module has
a different database table,
we use uids to identify owners of stored messages. This is something we use
and need to preserve.
ok, we'll have two msilo modules then.
may be it would be a good idea to record these on a wiki page, i.e, what
are the reasons for two versions of each module?
5705
days inactive
5705
days old
3 comments
2 participants
participants (2)
-
Jan Janak -
jh＠tutpro.com