Revision: 5840
http://opensips.svn.sourceforge.net/opensips/?rev=5840view=rev
Author: bogdan_iancu
Date: 2009-07-07 07:25:33 + (Tue, 07 Jul 2009)
Log Message:
---
- updated DB schema for Load-Balancer module (one more column added and version
increased)
Modified
Revision: 5842
http://opensips.svn.sourceforge.net/opensips/?rev=5842view=rev
Author: bogdan_iancu
Date: 2009-07-07 09:42:49 + (Tue, 07 Jul 2009)
Log Message:
---
backport from trunk (rev #5787 - #5797):
- reworked the entire re-connect mechanism in mysql - as the
Bugs item #2817434, was opened at 2009-07-06 16:06
Message generated for change (Comment added) made by bogdan_iancu
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=1086410aid=2817434group_id=232389
Please note that this message will contain a full copy of the
Bugs item #2815413, was opened at 2009-07-01 23:16
Message generated for change (Settings changed) made by bogdan_iancu
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=1086410aid=2815413group_id=232389
Please note that this message will contain a full copy of the
Revision: 5843
http://opensips.svn.sourceforge.net/opensips/?rev=5843view=rev
Author: bogdan_iancu
Date: 2009-07-07 09:53:08 + (Tue, 07 Jul 2009)
Log Message:
---
- fixed bug introduced with the last enhancements
Modified Paths:
--
Bugs item #2808416, was opened at 2009-06-18 17:24
Message generated for change (Comment added) made by bogdan_iancu
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=1086410aid=2808416group_id=232389
Please note that this message will contain a full copy of the
Bugs item #2797896, was opened at 2009-05-28 15:58
Message generated for change (Settings changed) made by bogdan_iancu
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=1086410aid=2797896group_id=232389
Please note that this message will contain a full copy of the
Bugs item #2779502, was opened at 2009-04-23 16:27
Message generated for change (Comment added) made by bogdan_iancu
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=1086410aid=2779502group_id=232389
Please note that this message will contain a full copy of the
Bugs item #2817434, was opened at 2009-07-06 15:06
Message generated for change (Comment added) made by ibc_sf
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=1086410aid=2817434group_id=232389
Please note that this message will contain a full copy of the comment
Hi Anca!
Nice feature, missing since long time :-)
If I understand the code, this triggers PUBLISH with trying even if
the dialog is not created (e.g. script error after dialoginfo_set()).
In this case, it will stay in trying state for default lifetime.
Wouldn't it be better to send trying
2009/7/7 Klaus Darilion klaus.mailingli...@pernau.at:
Hi Anca!
Nice feature, missing since long time :-)
If I understand the code, this triggers PUBLISH with trying even if
the dialog is not created (e.g. script error after dialoginfo_set()).
In this case, it will stay in trying state for
Iñaki Baz Castillo schrieb:
2009/7/7 Klaus Darilion klaus.mailingli...@pernau.at:
Hi Anca!
Nice feature, missing since long time :-)
If I understand the code, this triggers PUBLISH with trying even if
the dialog is not created (e.g. script error after dialoginfo_set()).
In this case, it
I have a question about the policy for subscriptions to dialog state.
How should this be done? Would a new pres-rules document make sense
for this. Like dialog-rules, same schema.
I could not find any normative specification, did someone find
something related to this?
Regards,
Adrian
2009/7/7 Klaus Darilion klaus.mailingli...@pernau.at:
PUBLISH dialog with trying state is in fact a NOOP and it's not
useful at all from the watcher's perspective. I suggest never to
publish it.
Also, the proceeding state means that a 1xx with no To tag (this is,
a 100) has been received.
For the lack of other pragmatic methods I would implement the following:
A. Suport in OpenXCAP server a new auid, document name dialog-rules
with the clear purpose of providing an authorization policy for dialog
Event
B. Setup the OpenSIPS PA module that handles the dialog event to read
it
2009/7/7 Adrian Georgescu a...@ag-projects.com:
For the lack of other pragmatic methods I would implement the following:
A. Suport in OpenXCAP server a new auid, document name dialog-rules with the
clear purpose of providing an authorization policy for dialog Event
B. Setup the OpenSIPS PA
On Jul 7, 2009, at 4:54 PM, Iñaki Baz Castillo wrote:
2009/7/7 Adrian Georgescu a...@ag-projects.com:
For the lack of other pragmatic methods I would implement the
following:
A. Suport in OpenXCAP server a new auid, document name dialog-rules
with the
clear purpose of providing an
2009/7/7 Adrian Georgescu a...@ag-projects.com:
I think that is the expected approach :)
However, I would like to receive replies in sip-implementors.
I thought we are the SIP implementors ;-)
100% agree :)
--
Iñaki Baz Castillo
i...@aliax.net
On Tue, Jul 7, 2009 at 4:17 PM, Adrian Georgescua...@ag-projects.com wrote:
For the lack of other pragmatic methods I would implement the following:
A. Suport in OpenXCAP server a new auid, document name dialog-rules
with the clear purpose of providing an authorization policy for dialog
Event
Bugs item #2817434, was opened at 2009-07-06 16:06
Message generated for change (Comment added) made by bogdan_iancu
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=1086410aid=2817434group_id=232389
Please note that this message will contain a full copy of the
Revision: 5844
http://opensips.svn.sourceforge.net/opensips/?rev=5844view=rev
Author: bogdan_iancu
Date: 2009-07-07 17:38:14 + (Tue, 07 Jul 2009)
Log Message:
---
- fixed how the NULL values are handled - use Postgres dedicated fucntions for
this.
Based on a patch
Patches item #2817560, was opened at 2009-07-06 20:53
Message generated for change (Comment added) made by bogdan_iancu
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=1086412aid=2817560group_id=232389
Please note that this message will contain a full copy of the
El Martes, 7 de Julio de 2009, Adrian Georgescu escribió:
Inaki,
Should the dialog timeout in this case?
Sorry, what do you mean? I couldn't understand.
--
Iñaki Baz Castillo i...@aliax.net
___
Devel mailing list
Devel@lists.opensips.org
El Martes, 7 de Julio de 2009, Adrian Georgescu escribió:
When a dialog times out, other actions can be triggered like updating
the state for event dialog. Same as we can send BYE messages.
Ok, but in case C crashed, why is useful A receiving a NOTIFY trying telling
that C is receiving a call?
Even if it did crash, the purpose of the module is to notify an
interested party when someone will likely be engaged in a phone call.
If the end-point of the monitored party crashed just before an INVITE
will be sent to it this does not affect anything related to the
purpose of the dialog
Bugs item #2818243, was opened at 2009-07-07 23:54
Message generated for change (Tracker Item Submitted) made by ibc_sf
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=1086410aid=2818243group_id=232389
Please note that this message will contain a full copy of the
26 matches
Mail list logo
