[Bristuff-users] Patch for BRIstuff 0.4.0-RC3b to support snom CallerID update
Tzafrir Cohen
tzafrir.cohen at xorcom.com
Mon Jul 7 18:07:32 CEST 2008
On Mon, Jul 07, 2008 at 05:16:20PM +0200, Philipp Walker wrote:
> Hi all,
>
> BRIstuff 0.4.0-RC3b (and possibly in earlier versions, too), all the code
> necessary to update the callerid on snom phones after an attended transfer
> (using "message/sipfrag"; as available in BRIstuff 0.3.0-PRE-1y-p, improved
> in 0.3.0-PRE-1y-r) is there, but it's commented out, unfortunately.
>
> The attached patch (121-sip_changes.diff.patch) removes the comments from the
> few relevant lines in file patches/asterisk/121-sip_changes.diff ,
> 121-sip_changes.diff is the patched version from BRIstuff 0.4.0-RC3b.
> Additionally, I've changed the two lines so that both, caller id name and
> number are shown. This change might also be interresting for BRIstuff 0.3 /
> Asterisk 1.2.
>
> The patch is somewhat tested with snom 320s firmware version 7.1.33. I'll see
> that I can also test the BRIstuff 0.3 / Asterisk 1.2 version of it with snom
> 320s and 360s during the next days/weeks.
> Any chance of getting this change into BRIstuff 0.4? (Who do I have to contact
> to request this?)
Junghanns?
Seriously, though:
Bristuff has many useful fixes. But those never get upstream. And thus
it is a problem to rely on them. Any thoughts on how to better work with
them?
I have been able to communicate with the author, but on a very
non-regular basis. Though he does produce useful code and does respond
to fixes (RC3b includes a libpri fix of ours, but not some small zaptel
svn backport patches we need).
I'm not sure I understand the need for a separate "send_message" channel
operation. And I don't understand the need for the dialplan/prefix
operations in chan_sip.
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen at xorcom.com
+972-50-7952406 mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
More information about the Bristuff-users
mailing list