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
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
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
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...
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
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
ram
Hi,
my mistake - it's about the 1.3 version, so the correct uri is: http://www.openser.org/docs/modules/1.3.x/mi_datagram.html
thanks and regards, bogdan
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
ram
Users mailing list Users@openser.org http://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
On 6/28/07, Henning Westerholt henning.westerholt@1und1.de wrote:
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:
Hi
is this 1.3.X can be used in production ?
ram
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
Hi Juha,
there are 3 MI commands used by SEMS : t_reply, t_uac_cancel, t_uac_dlg, but only t_reply and t_uac_dlg are effected by the syntax changes.
As it will be difficult to have 2 syntaxes in openser (and as the parser is a general one with no knowledge about the parsed function), I would suggest to generate a patch for SEMS to will ensure the compatibility with openser new interface - on a first look, the changes are minor and I will happy to assist in building the patch.
regards, bogdan
Juha Heinanen wrote:
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...
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
-
Bogdan-Andrei Iancu -
Henning Westerholt -
jh＠tutpro.com -
ram