<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel">
    <title>gmane.comp.telephony.pbx.asterisk.devel</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31594"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31593"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31592"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31591"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31590"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31589"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31588"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31587"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31586"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31585"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31584"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31583"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31582"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31581"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31580"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31579"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31578"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31577"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31576"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31575"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31594">
    <title>Re: res_jabber call backs</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31594</link>
    <description>
I believe there is some work being done on Asterisk receiving 
messages and processing them, but perhaps not exactly what you're 
looking for (yet?)  Maybe you could add those features for presence 
or event callback.  It sounds like you're talking about using XMPP as 
an API - or am I misunderstanding your question?


As a side note, take a look here at the work that Philippe Sultan is doing:

  http://svn.digium.com/view/asterisk/team/phsultan/jabberreceive/

  http://lists.digium.com/pipermail/asterisk-users/2008-June/213525.html

This is _really_ interesting stuff, and creative use of XMPP combined 
with Asterisk should allow all sorts of IM-based call transactions. 
I'd encourage anyone with interest in UC work to take a look at this 
branch, test the apps, and report your results so this can be merged 
into mainline if it seems stable and worthwhile.


Next thing I'd like to see: XMPP events being received unsolicited 
and starting a dialplan event sequence with regexp parsing of the IM 
strings, send</description>
    <dc:creator>John Todd</dc:creator>
    <dc:date>2008-08-21T16:07:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31593">
    <title>Re: 56k SS7 using TE122.</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31593</link>
    <description>
They can be T1 based as well.  In any case, this is a question that is 
being handled on the Asterisk-ss7 list, so please tune in there for more 
info :-)

Matthew Fredrickson
Digium, Inc.



_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

</description>
    <dc:creator>Matthew Fredrickson</dc:creator>
    <dc:date>2008-08-21T01:52:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31592">
    <title>Re: 56k SS7 using TE122.</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31592</link>
    <description>I think 56K A-links are DDS, not T1-based.

Mark A Jenks wrote:



</description>
    <dc:creator>Alex Balashov</dc:creator>
    <dc:date>2008-08-21T01:26:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31591">
    <title>sip notify to reset cisco 79x1 phones</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31591</link>
    <description>Hi, if anyone have interest to implement into sip_notify mechanism to 
also send custom sip message bodies to phones...
I'm attaching packet dump, that callmanager6 use to reset java based 
phones (79x1)
currently, we are able to put sip header, using sip_notify.conf:
Event: service-control
Content-Lenght: 82
but callmanager also use message body, where is placed actual action to 
reset or restart phones...
action=reset\n




_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev</description>
    <dc:creator>Pavel Jezek</dc:creator>
    <dc:date>2008-08-20T22:38:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31590">
    <title>56k SS7 using TE122.</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31590</link>
    <description>_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev</description>
    <dc:creator>Mark A Jenks</dc:creator>
    <dc:date>2008-08-20T21:17:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31589">
    <title>Re: specific storage directory for CDR data instead of LOG_DIR</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31589</link>
    <description>On Wed, 20 Aug 2008 10:13:25 -0500
Russell Bryant &lt;russell&lt; at &gt;digium.com&gt; wrote:


That's even better, awesome :)

</description>
    <dc:creator>Caio Begotti</dc:creator>
    <dc:date>2008-08-20T16:05:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31588">
    <title>Re: specific storage directory for CDR data instead of LOG_DIR</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31588</link>
    <description>
http://bugs.digium.com/view.php?id=12876

Ready for testing.  :)

</description>
    <dc:creator>Russell Bryant</dc:creator>
    <dc:date>2008-08-20T15:13:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31587">
    <title>Re: n_way conference call</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31587</link>
    <description>
This mailing list is for topics related to the development of Asterisk.

Your question is more appropriate for the asterisk-users mailing list
and has a higher probability of getting answered there.

Good luck,
</description>
    <dc:creator>Sean Bright</dc:creator>
    <dc:date>2008-08-20T15:13:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31586">
    <title>Re: n_way conference call</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31586</link>
    <description>
Please try your question on the asterisk-users mailing list, as that is 
the most appropriate place to ask this type of question.

Good luck,

</description>
    <dc:creator>Russell Bryant</dc:creator>
    <dc:date>2008-08-20T15:12:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31585">
    <title>Re: specific storage directory for CDR data insteadof LOG_DIR</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31585</link>
    <description>
Can you pass the CDR logging to syslog?  That way, the log can be on
another machine.  Most embedded devices are real estate poor.  Seems
to me that would be the best way to handle it.  Allow CDR to log to
syslog so it could log to say local6 on another machine.

Ciao,

David A. Bandel
</description>
    <dc:creator>David A. Bandel</dc:creator>
    <dc:date>2008-08-20T15:08:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31584">
    <title>specific storage directory for CDR data instead ofLOG_DIR</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31584</link>
    <description>Morning!

Someone at #asterisk-br on IRC asked how to storage CDR data
somewhere else because he was running Asterisk in an embedded device
with no persistent logging (on RAM). At first I thought about using
the spool dir, but it seemed hackish because you might care about CDR
and still don't use monitoring or voicemail etc.

I've added a new ast_config_AST_CDR_DIR for a quick test and it did
the trick. If it's not found then Asterisk will still use 
ast_config_AST_LOG_DIR for that as a fallback and no, it's not a
default value in my test even for new instalattions, it's only an
alternative path inside asterisk.conf.

Is that acceptable or does anyone have anything against it? I still
need to write a patch for cdr/cdr_sqlite*.c and cdr/cdr_custom.c. I
only got it working for the simple cdr-csv backend, that's why I
wanted to ask for input before going ahead.

[]s

</description>
    <dc:creator>Caio Begotti</dc:creator>
    <dc:date>2008-08-20T14:37:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31583">
    <title>n_way conference call</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31583</link>
    <description>_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev</description>
    <dc:creator>ameur brahim</dc:creator>
    <dc:date>2008-08-20T14:24:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31582">
    <title>Re: Possible Deadlock?</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31582</link>
    <description>
oops, sorry about that, Russell is correct, DEBUG_THREADS is the
required option to compile with "core show channels" support. Select
it by doing:

make menuselect

10. Compiler Options -&gt; 3. DEBUG_THREADS

Moy

</description>
    <dc:creator>Moises Silva</dc:creator>
    <dc:date>2008-08-19T22:30:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31581">
    <title>res_jabber call backs</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31581</link>
    <description>Hi all,
As I see, in the asterisk 1.4, jabber is designed to send messages, 
receive answers and display them in the cli.
I think we should add the feature that any asterisk module can register 
some callbacks for a specific jabber user.
Then, from any module, we can request the client using his username and 
register callbacks on message, on presence etc...
So, as soon as a message will be receive, the call back will be fire.

What do you think about that ?

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

</description>
    <dc:creator>Ruddy Gbaguidi</dc:creator>
    <dc:date>2008-08-19T18:24:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31580">
    <title>Re: Possible Deadlock?</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31580</link>
    <description>If I were you, I'd compile Asterisk with DEBUG_CHANNEL_LOCKS,
reproduce the issue and execute command "core show locks", this will
likely be easier to debug.

Moy

On Tue, Aug 19, 2008 at 11:46 AM, Norman Franke &lt;norman&lt; at &gt;myasd.com&gt; wrote:



</description>
    <dc:creator>Moises Silva</dc:creator>
    <dc:date>2008-08-19T17:20:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31579">
    <title>Re: Possible Deadlock?</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31579</link>
    <description>
Minor correction: DEBUG_THREADS, not DEBUG_CHANNEL_LOCKS

</description>
    <dc:creator>Russell Bryant</dc:creator>
    <dc:date>2008-08-19T17:25:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31578">
    <title>Possible Deadlock?</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31578</link>
    <description>I had a deadlock today using 1.4.21.1. I had asterisk dump core to  
explore in GDB. Thread 32 is waiting for the "channels" lock held by  
21 while holding a channel lock. Thread 21 is then waiting for a lock  
on a channel held by 32 while holding a lock on "channels".

However, I can't figure out how thread 32 got the lock in the first  
place. Perhaps from this in the log?

[Aug 19 10:55:26] VERBOSE[25324] logger.c:     -- Got SIP response 480  
"Temporarily Unavailable" back from 172.16.22.30

And it never released the lock? I see in chan_sip.c:12936

                                 /* XXX Locking issues?? XXX */

This has only happened once recently.

Thread 32 (process 25324):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7edd56e in __lll_mutex_lock_wait () from /lib/tls/i686/cmov/ 
libpthread.so.0
#2  0xb7eda179 in _L_mutex_lock_141 () from /lib/tls/i686/cmov/ 
libpthread.so.0
#3  0xb786a918 in ?? ()
#4  0x0807d514 in ast_cdr_start (cdr=0x815a148) at cdr.c:689
#5  0x0807fd3f in ast_mutex_lock (pmute</description>
    <dc:creator>Norman Franke</dc:creator>
    <dc:date>2008-08-19T16:46:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31577">
    <title>Re: sip_devicestate and queue problems</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31577</link>
    <description>
It's waiting on the next release of Zaptel and the release of DAHDI, 
which are currently being tested.

It should be this week unless something goes wrong ...

</description>
    <dc:creator>Russell Bryant</dc:creator>
    <dc:date>2008-08-19T16:07:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31576">
    <title>Re: sip_devicestate and queue problems</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31576</link>
    <description>Ok, I'm testing version SVN-branch-1.4-r138685, at the moment all is ok. 
I see that there is no DNS query anymore, because function ast_setstate 
now breaks SIP channel name string with '-' separator, so never called 
with entire channel name.

Waiting for 1.4.22 to came up... How long do you estimate ?

Thanks!
bye
daniel

Russell Bryant escribió:


_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

</description>
    <dc:creator>Daniel Ferrer</dc:creator>
    <dc:date>2008-08-19T16:02:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31575">
    <title>Re: ExtensionStatus</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31575</link>
    <description>Feel free to post them wherever, just saying that they are more likely to stay on the
radar in the bug tracker.

Philipp Kempgen wrote:

</description>
    <dc:creator>Sean Bright</dc:creator>
    <dc:date>2008-08-19T15:20:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31574">
    <title>Re: ExtensionStatus</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/31574</link>
    <description>Sean Bright schrieb:

When it's about minor issues like this one I'm not sure whether
to post it on the mailing list or on the bug tracker or not to
report them at all. But ok, Mantis - next time.

Grüße,
Philipp Kempgen
</description>
    <dc:creator>Philipp Kempgen</dc:creator>
    <dc:date>2008-08-19T14:38:43</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.telephony.pbx.asterisk.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.telephony.pbx.asterisk.devel</link>
  </textinput>
</rdf:RDF>
