NEW MODULE: Datagram implementation for MI

Hi,

thanks to Ancuta Onofrei, we added today a new transport
implementation 
for the Management Interface (MI). This is Datagram (via
unix and 
network sockets) and it completes the migration to MI (after
fifo), but 
not the last from the transport implementations .

It is in alpha stage, so more testing is needed.

NOTE that all MI commands are available via datagram
interface; also the 
syntax of the commands and replies is exactly as for FIFO.

For more info, please see the online documentation:
   http://www.openser.org/docs/modules/1.2.x/mi_datagram.
html
or ask on the mailing list.

Any feedback - bugs or improvements - are welcomed.

Also I want to bring in discussion a related subject -
dropping the old 
unix sockets implementation from the core.
Before doing it I would like to know who is still using it
and if there 
are any issues with migrating to the new implementation.

Regards,
Bogdan

_______________________________________________
Users mailing list
Usersopenser.org
htt
p://openser.org/cgi-bin/mailman/listinfo/users

Bogdan-Andrei Iancu writes:

 > Also I want to bring in discussion a related subject -
dropping the old 
 > unix sockets implementation from the core.
 > Before doing it I would like to know who is still
using it and if there 
 > are any issues with migrating to the new
implementation.

openser/sems communication is currently using unix sockets. 
openser
send request to sems by t_write_unix().  if the new module
works and
behaves the same way as current unix socket implementation,
it is ok
with me to drop the old implementation.

-- juha

_______________________________________________
Users mailing list
Usersopenser.org
htt
p://openser.org/cgi-bin/mailman/listinfo/users

Hi Juha,

I was expecting SEMS integration to be one of the issues
.

t_write_unix() was not changed at all, but I do not sure
what MI 
commands SEMS triggers from openser. If you could let me
know which are 
the functions (most probably from TM), I will take a look at
the 
compatibility aspect.

regards,
bogdan

Juha Heinanen wrote:
> Bogdan-Andrei Iancu writes:
>
>  > Also I want to bring in discussion a related
subject - dropping the old 
>  > unix sockets implementation from the core.
>  > Before doing it I would like to know who is still
using it and if there 
>  > are any issues with migrating to the new
implementation.
>
> openser/sems communication is currently using unix
sockets.  openser
> send request to sems by t_write_unix().  if the new
module works and
> behaves the same way as current unix socket
implementation, it is ok
> with me to drop the old implementation.
>
> -- juha
>
>   


_______________________________________________
Users mailing list
Usersopenser.org
htt
p://openser.org/cgi-bin/mailman/listinfo/users

Bogdan-Andrei Iancu writes:

 > t_write_unix() was not changed at all, but I do not
sure what MI 
 > commands SEMS triggers from openser. If you could let
me know which are 
 > the functions (most probably from TM), I will take a
look at the 
 > compatibility aspect.

sems replies to t_write_unix() call using t_reply on its
reply socket.
on the same socket it sends invite/bye/etc. requests using
t_uac_dlg
message.  this code is all in AmSipDialog.cpp file:

http://svn.berlios.de/wsvn/
sems/trunk/core/AmSipDialog.cpp?op=file&rev=0&sc=0

and for sending requests, in its AmSipDialog::sendRequest
function.

i have heard rumors that a new sems/ser interface in on the
works, but i
don't know details.  i'll ask the sems list.

-- juha

_______________________________________________
Users mailing list
Usersopenser.org
htt
p://openser.org/cgi-bin/mailman/listinfo/users

On Donnerstag, 28. Juni 2007, ram wrote:
> For more info, please see the online documentation:
>   http://www.openser.org/docs/modules/1.2.x/mi_datagram.
html
> or ask on the mailing list.
>
> not able to access above url

The right URL is:

http://www.openser.org/docs/modules/1.3.x/mi_datagram.
html

Cheers,

Henning

_______________________________________________
Users mailing list
Usersopenser.org
htt
p://openser.org/cgi-bin/mailman/listinfo/users

On Donnerstag, 28. Juni 2007, you wrote:
> Hi
>
> is this 1.3.X can be used in production ?

No, this is the current development, e.g. svn trunk. 1.3
will be the next 
release. For production you should use 1.2.1 or the 1.2
branch in svn.

Cheers,

Henning


_______________________________________________
Users mailing list
Usersopenser.org
htt
p://openser.org/cgi-bin/mailman/listinfo/users