Re: [asterisk-users] rfc3680, reginfo+xml
Olivier, In principle, Registration/Presence and Call-Processing are separate logical functions but for cost or other reasons one could combine them in one software implementation or one physical box. For most parts, Asterisk is the Registrar in a SIP network and therefore maintains the location table. So, whatever entity runs the RFC 3680 notifier function will need access to Asterisk's location table. This is not the real issue though (the access to this table can be easily granted through the API). The answer to whether RFC 3680 should be built inside Asterisk or outside of it really depends on the kind of scalability one is looking for. The scalability here refers to the number of subscriptions per each AoR (notification fan-out). Basically, you don't want to overload Asterisk with excessive number of subscriptions to the extent that they can negatively impact call/media processing. If you compare this with presence, the PUBLISH method allowed the presentity to inform only one entity (the presence server) of its state changes. The presence server was the one that did the drudgery of maintaining individual subscriptions and notifying the watchers. The presence model assumes that there are multiple watchers subscribing to the state of *a* presentity. RFC 3680 is a bit different than this, however. If you are looking to do free-seating using RFC 3680, I'd imagine that you will need only one subscription for each AoR in Asterisk (so you don't really have a 1:n fan-out issue). In that case, it is probably okay if the RFC 3680 'notifier' function was embedded within Asterisk itself. The current RFC 3265 support in Asterisk code should make the job of supporting RFC 3680 a bit easier. Raj From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Olivier Sent: Wednesday, August 22, 2007 8:27 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] rfc3680, reginfo+xml Thanks for replying, Raj. Do you think such feature should, ideally, be implemented in Asterisk should it be implemented in a dedicated software (presence ?) ? It seems to me it should, though I'm not aware of many devices using this feature, beside SIP hardphones. Would it be difficult to extend current code to comply with this RFC, when rfc3265 mechanism is already in place ? ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] rfc3680, reginfo+xml
Hi, RFC3680 defines a SIP event package for registration. This event package which can be used through NOTIFY-SUBSCRIBE methods, seems very useful for free sitting or presence applications. This package is supported in various SIP phones (at least Thomson ST2030) : when turned on, this feature adds a new login/logout menu among other things. It can also be used to send Welcome notices to mobile users : whenever a mobile user comes in, a SIP MESSAGE is sent by a software application which has previously subscribed to be notified of any registration event related to this mobile user. It appears Asterisk supports SIP NOTIFY-SUBSCRIBE methods. But I couldn't find any trace of this specific Registration Event package support (but I won't swear I searched the right way). How can I make sure this feature is supported or not ? More precisely, this Registration Event package support relies on these headers : SIP SUBSCRIBE reg Event SIP SUBSCRIBE application/reginfo+xml Accept SIP NOTIFY reg Event SIP NOTIFY application/reginfo+xml Content How shall I check ? Regards ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] rfc3680, reginfo+xml
Olivier, This feature is not supported in Asterisk. I can tell this looking at the code. If you want to test this yourself, send Asterisk a SUBSCRIBE message with Event: reg header in it. You can either use an off-the-shelf UA that supports RFC 3680 to do this or you can use SIPp (an open-source SIP test tool) to do this. Since Asterisk does not support reg event-package, it'll respond back with a 489 (Bad Event) response. Raj On 8/22/07, Olivier [EMAIL PROTECTED] wrote: Hi, RFC3680 defines a SIP event package for registration. This event package which can be used through NOTIFY-SUBSCRIBE methods, seems very useful for free sitting or presence applications. This package is supported in various SIP phones (at least Thomson ST2030) : when turned on, this feature adds a new login/logout menu among other things. It can also be used to send Welcome notices to mobile users : whenever a mobile user comes in, a SIP MESSAGE is sent by a software application which has previously subscribed to be notified of any registration event related to this mobile user. It appears Asterisk supports SIP NOTIFY-SUBSCRIBE methods. But I couldn't find any trace of this specific Registration Event package support (but I won't swear I searched the right way). How can I make sure this feature is supported or not ? More precisely, this Registration Event package support relies on these headers : SIP SUBSCRIBE reg Event SIP SUBSCRIBE application/reginfo+xml Accept SIP NOTIFY reg Event SIP NOTIFY application/reginfo+xml Content How shall I check ? Regards ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] rfc3680, reginfo+xml
Thanks for replying, Raj. Do you think such feature should, ideally, be implemented in Asterisk should it be implemented in a dedicated software (presence ?) ? It seems to me it should, though I'm not aware of many devices using this feature, beside SIP hardphones. Would it be difficult to extend current code to comply with this RFC, when rfc3265 mechanism is already in place ? ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
