<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to patches</title><link>https://sourceforge.net/p/peers/patches/</link><description>Recent changes to patches</description><atom:link href="https://sourceforge.net/p/peers/patches/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sat, 25 Jun 2011 00:45:38 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/peers/patches/feed.rss" rel="self" type="application/rss+xml"/><item><title>Making Peers an Applet and an Application</title><link>https://sourceforge.net/p/peers/patches/20/</link><description>Just figured out the patch system\!
Please review and apply.
If the patch applied is incomplete, please use http://www.mediafire.com/?3z8enp6uxu68un8</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">anirudh r</dc:creator><pubDate>Sat, 25 Jun 2011 00:45:38 -0000</pubDate><guid>https://sourceforge.netb1130e98a73ad690882da86635af47bdf0e70324</guid></item><item><title>send 200 OK on notify requests</title><link>https://sourceforge.net/p/peers/patches/19/</link><description>some asterisk instances seem to consider user-agents offline if they don't answer notify requests.

To bypass this issue, a patch has been developped by cristian david cepeda piscal. This patch adds a NotifyHandler that simply answer 200 OK to notify requests.

After this modification, asterisk apparently considers peers online and can route calls towards peers.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">yohannmartineau</dc:creator><pubDate>Sat, 12 Feb 2011 12:34:26 -0000</pubDate><guid>https://sourceforge.net09cfadd164780f0ab8d8be3cf10496309ec24526</guid></item><item><title>Wrong order in dialog state and SipListener handling.</title><link>https://sourceforge.net/p/peers/patches/18/</link><description>Within the InviteHandler.handleInitialInvite\(\), order of execution is:
1\. send 180 Ringing
2\. tell SipListener about incoming call
3\. update dialog state/handling.

3\. should be done before 2. because the dialog has the wrong state when calling the SipListener.
If the SipListener decides to immediately accept the call, a 200 Ok will be sent, the dialog will be set from init to confirmed, followed by an attempt to set it from confirmed to early, leading to an IllegalStateException.

Attached patch reverses the order.
Please review and apply.

Hope this helps,
Tom.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">uiltje</dc:creator><pubDate>Tue, 11 Jan 2011 13:39:52 -0000</pubDate><guid>https://sourceforge.netc48f5f18f56fcb84c45a70d6719bfe3cafb0360d</guid></item><item><title>No serialization in client transaction.</title><link>https://sourceforge.net/p/peers/patches/17/</link><description>Multiple SIP responses can be executed in parallel within 1 ClientTransaction \(probably interfering with transaction state handling as well\).

This can lead to 200 OK responses overtaking 180 Ringing responses.

Attached patch serializes this by synchronizing the "receivedResponse\(\)" method.

Hope this helps,
Tom.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">uiltje</dc:creator><pubDate>Wed, 15 Dec 2010 11:08:54 -0000</pubDate><guid>https://sourceforge.net4835a725b1bb0e7f49159a0aa69cf6136753628b</guid></item><item><title>start cseq at 1 instead of 0</title><link>https://sourceforge.net/p/peers/patches/16/</link><description>Some buggy registrars seem to refuse REGISTER with a cseq of 0. This value is valid in RFC3261, but most sip softphones use 1 as their first cseq value.
So it makes sense to use 1 as the first cseq value in peers.
To use 1 as the first cseq value in peers, modify net.sourceforge.peers.sip.core.useragent.UserAgent.UserAgent. In constructor, use cseqCounter = 1;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">yohannmartineau</dc:creator><pubDate>Fri, 29 Oct 2010 13:43:50 -0000</pubDate><guid>https://sourceforge.net68698f5cc985311c1b1f3c6e826f2004da957c48</guid></item><item><title>modified timerE handling</title><link>https://sourceforge.net/p/peers/patches/15/</link><description>On receiving provisional responses \(1xx\) within a non-INVITE client transaction, it is logical to reset the re-transmission timer, as the server side has indicated that it is working on it.

This is currently not happening. The timer is not reset and a retransmission is done when timer E fires regardless.

Attached patch will reset the timer on receiving a provisional response.

Hope this helps,
Tom.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">uiltje</dc:creator><pubDate>Fri, 22 Oct 2010 15:55:20 -0000</pubDate><guid>https://sourceforge.net287600126d8521f6494a2654399fc9e4247574ce</guid></item><item><title>stop sending rtp when not running.</title><link>https://sourceforge.net/p/peers/patches/14/</link><description>When an rtp-stream is  stopped, any packets, waiting to be sent, are still sent.

This patch prevents that.

Hope this helps,
Tom.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">uiltje</dc:creator><pubDate>Fri, 22 Oct 2010 15:47:12 -0000</pubDate><guid>https://sourceforge.netf90de7b04453052211f51a8abceb88a73402b9e3</guid></item><item><title>Timing off on closing rtp streams</title><link>https://sourceforge.net/p/peers/patches/13/</link><description>When refreshing \(dropping and creating\) rtp-streams, time to wait for closure should depend on RtpSession.TIMER.

Attached patch does just that.

Hope this helps,
Tom.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">uiltje</dc:creator><pubDate>Thu, 21 Oct 2010 15:05:06 -0000</pubDate><guid>https://sourceforge.net1d37fd7c35516744cb25a4489179d5eea133c53d</guid></item><item><title>Remove superfluous JPanel</title><link>https://sourceforge.net/p/peers/patches/12/</link><description>Creation of MainFrame.mainPanel is not needed.
The JFrame.getContentPane\(\) will get you the Container needed.

Attached patch gets rid of the JPanel creation.

Hope this helps,
Tom.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">uiltje</dc:creator><pubDate>Thu, 21 Oct 2010 09:48:52 -0000</pubDate><guid>https://sourceforge.net7776b6168a8c5fda7a75d5d2bcd5bac1aeaf0ede</guid></item><item><title>Enhancement of register handler</title><link>https://sourceforge.net/p/peers/patches/11/</link><description>Attached, a patch that enhances the handling of registrations, including:
\- introduction of "Expires" header \(including default\).
\- addition of unregister all \(wildcard\)
\- improved separation of functionality - RegisterHandler  handles REGISTERs under control of InitialRequestManager

Hope this helps,
Tom.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">uiltje</dc:creator><pubDate>Fri, 15 Oct 2010 13:09:52 -0000</pubDate><guid>https://sourceforge.net9617b2589daa7bebec98548fe3ebe44e7b1ee0fa</guid></item></channel></rss>