[OpenSIPS-Devel] [ opensips-Patches-2846288 ] benchmark module fixes
Patches item #2846288, was opened at 2009-08-28 18:00 Message generated for change (Settings changed) made by bogdan_iancu You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086412aid=2846288group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: 1.5.x Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Stanislaw Pitucha (viraptor) Assigned to: Bogdan-Andrei Iancu (bogdan_iancu) Summary: benchmark module fixes Initial Comment: Trivial fixes: - default bm_granularity changed to 100 (to match documentation) - time difference calculation fix diff taken against 1.5.2 -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2009-08-30 20:09 Message: Patched commited ! Thanks and regards, Bogdan -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086412aid=2846288group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [xcap table] Mapping between doc_type column and XCAP document type?
Hi, could I know the exact mapping which identifies a XCAP document type with a integer value in the xcap table doc_type column? Thanks. -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [xcap table] Mapping between doc_type column and XCAP document type?
app_mapping = {pres-rules : 1,
resource-lists : 2,
rls-services : 3,
pidf-manipulation: 4
}
--
Adrian
On Aug 30, 2009, at 7:10 PM, Iñaki Baz Castillo wrote:
doc_type
___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [xcap table] Mapping between doc_type column and XCAP document type?
El Domingo, 30 de Agosto de 2009, Adrian Georgescu escribió:
app_mapping = {pres-rules : 1,
resource-lists : 2,
rls-services : 3,
pidf-manipulation: 4
}
Thanks Adrian.
--
Iñaki Baz Castillo i...@aliax.net
___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Patches-2847397 ] Better blf support for linksys phones
Patches item #2847397, was opened at 2009-08-30 21:15 Message generated for change (Tracker Item Submitted) made by anmar You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086412aid=2847397group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: 1.5.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Angel Marin (anmar) Assigned to: Nobody/Anonymous (nobody) Summary: Better blf support for linksys phones Initial Comment: With current implementation, if there's no ongoing or terminated dialog registered in the presentity table, presence_dialoginfo sends a notify with empty body as reply to a subscribe. This makes BLF support incomplete for phones that only register to dialog-info event (linksys), so they won't know the state of the subscribed uri until it makes a call. The attached patch adds the ability to presence_dialoginfo to build a dialog-info body that reports the state of a dialog as terminated when there's no dialog, but we have a presentity entry for that user. Something like: ?xml version=1.0? dialog-info xmlns=urn:ietf:params:xml:ns:dialog-info version=0 state=full entity=sip:al...@example.com dialog id=sip:al...@example.com stateterminated/state /dialog /dialog-info The patch also adds a contains_presence api function to presence module so we can check if there's a presence entry registered for a given uri. I've tested it only with linksys spa-9x2 phones, but it's trivial enough to not make any other phone unhappy. This makes support for linksys blf a little better, but it's still missing a similar notify when the monitored user registers after the subscribe. Right now the subscriber won't get notified until it resubscribes. diff against 1.5.3 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086412aid=2847397group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
