asterisk users - Feb 2015 - Asterisk 13 - sorcery realtime for pjsip publish objects

Matt Hoskins wrote:
> Good Morning,
>
> After further investigation, I found that the res_pjsip_publish_asterisk
> module does not use the realtime sorcery wizard, but instead only reads
> from the configuration files.  I've been able to patch the module,
using
> the logic from the other modules to learn how to make the sorery
> configuration read from the other sorcery wizards and it's now working
for
> the asterisk-publication.  This thread probably belongs on the
> asterisk-dev list.  I've never submitted a patch to the asterisk
project,
> and I doubt my code follows your standards.  I'm wondering - is there
> planned support for asterisk-publication to be realtime-aware?  If so, I
> can continue to do my development on 13.2.0 and simply wait for it to get
> fixed in a future point release.  Or, if submitting the patch is the best
> course of action - I can do that too.
The guidelines for filing an issue are here[1] and include links for 
submitting a patch. I know of noone currently working on it.

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

-- 
Joshua Colp
Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org

On Thu, Feb 19, 2015 at 9:15 AM, Joshua Colp <jcolp at digium.com> wrote:
> Matt Hoskins wrote:
>
>> Good Morning,
>>
>> After further investigation, I found that the
res_pjsip_publish_asterisk
>> module does not use the realtime sorcery wizard, but instead only reads
>> from the configuration files.  I've been able to patch the module,
using
>> the logic from the other modules to learn how to make the sorery
>> configuration read from the other sorcery wizards and it's now
working for
>> the asterisk-publication.  This thread probably belongs on the
>> asterisk-dev list.  I've never submitted a patch to the asterisk
project,
>> and I doubt my code follows your standards.  I'm wondering - is
there
>> planned support for asterisk-publication to be realtime-aware?  If so,
I
>> can continue to do my development on 13.2.0 and simply wait for it to
get
>> fixed in a future point release.  Or, if submitting the patch is the
best
>> course of action - I can do that too.
>>
>
I've got some free time and can take a look.  Give me the issue number
after you've created it.

>
> The guidelines for filing an issue are here[1] and include links for
> submitting a patch. I know of noone currently working on it.
>

>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20150219/da13311e/attachment.html>

Awesome!



https://issues.asterisk.org/jira/browse/ASTERISK-24811







Matt Hoskins | NPG Corp | Systems Architect

816.749.2815 (Internal: ext. 10015)







From: asterisk-users-bounces at lists.digium.com 
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of George Joseph
Sent: Thursday, February 19, 2015 10:19 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Asterisk 13 - sorcery realtime for pjsip 
publish objects



On Thu, Feb 19, 2015 at 9:15 AM, Joshua Colp <jcolp at digium.com> wrote:

Matt Hoskins wrote:

Good Morning,

After further investigation, I found that the res_pjsip_publish_asterisk
module does not use the realtime sorcery wizard, but instead only reads
from the configuration files.  I've been able to patch the module, using
the logic from the other modules to learn how to make the sorery
configuration read from the other sorcery wizards and it's now working for
the asterisk-publication.  This thread probably belongs on the
asterisk-dev list.  I've never submitted a patch to the asterisk project,
and I doubt my code follows your standards.  I'm wondering - is there
planned support for asterisk-publication to be realtime-aware?  If so, I
can continue to do my development on 13.2.0 and simply wait for it to get
fixed in a future point release.  Or, if submitting the patch is the best
course of action - I can do that too.



I've got some free time and can take a look.  Give me the issue number after
you've created it.




The guidelines for filing an issue are here[1] and include links for 
submitting a patch. I know of noone currently working on it.







  _____


Spam 
<http://spamaway.npgco.com/canit/b.php?i=01NSgiMT3&m=f30b1af83c0e&t=20150219&c=s>
Not spam 
<http://spamaway.npgco.com/canit/b.php?i=01NSgiMT3&m=f30b1af83c0e&t=20150219&c=n>
Forget previous vote 
<http://spamaway.npgco.com/canit/b.php?i=01NSgiMT3&m=f30b1af83c0e&t=20150219&c=f>

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20150219/aa0203de/attachment.html>