Hello, I recently tried an upgrade of CVS on my test server today and found that the res/res_parking.c file is completely gone. This is where I had to go into the code every time I do an upgrade and change the code to allow for doublehash transfers instead of single hash transfers: That means that you need to hit the pound key twice to initiate a transfer instead of once. Because of our inbound call center we need to do transfers and we also need to be able to hit the pound key once without transferring, so a single pound transfer option is unacceptable. Where did the code go? How can I apply the doublehash patch? I know there are several other people out there that go through what I do every time we upgrade the CVS so I'll ask again for a config option in the parking.conf to allow for doublehash as a config. The code change to allow for doublehash transfers is quite small and shouldn't be too hard to add as a config option. And whoever can get this pushed through I'll buy you dinner at Astricon :) If someone is currently using doublehash on a recent CVS could you be so kind as to email me a copy of your patch? Thanks, MATT---
On Fri, 23 Jul 2004 12:00:22 -0400, mattf <mattf@vicimarketing.com> wrote:> That means that you need to hit the pound key twice to initiate a > transfer instead of once. Because of our inbound call center we need to do > transfers and we also need to be able to hit the pound key once without > transferring, so a single pound transfer option is unacceptable. > > Where did the code go? How can I apply the doublehash patch? I know there > are several other people out there that go through what I do every time weres_parking has become res_features so look there somewhere Jason
At 12:00 PM -0400 on 7/23/04, mattf wrote:>Hello, > >I recently tried an upgrade of CVS on my test server today and found that >the res/res_parking.c file is completely gone. This is where I had to go >into the code every time I do an upgrade and change the code to allow for >doublehash transfers instead of single hash transfers: > That means that you need to hit the pound key twice to initiate a >transfer instead of once. Because of our inbound call center we need to do >transfers and we also need to be able to hit the pound key once without >transferring, so a single pound transfer option is unacceptable. > >Where did the code go? How can I apply the doublehash patch? I know there >are several other people out there that go through what I do every time we >upgrade the CVS so I'll ask again for a config option in the parking.conf to >allow for doublehash as a config. The code change to allow for doublehash >transfers is quite small and shouldn't be too hard to add as a config >option. > >And whoever can get this pushed through I'll buy you dinner at Astricon :) > >If someone is currently using doublehash on a recent CVS could you be so >kind as to email me a copy of your patch? > >Thanks, > >MATT---I hate being a "me too" poster, but the double-hash patch I have implemented four times now, and I know at least three other people who have also gone well out of their way to put that patch into their system. Making this an "official" modification would be ideal, in my opinion, especially if it is selectable (default=single #, to retain previously expected functionality.) JT
John Todd wrote:> At 12:00 PM -0400 on 7/23/04, mattf wrote: >> Hello, >> >> I recently tried an upgrade of CVS on my test server today and found >> that the res/res_parking.c file is completely gone. This is where I >> had to go into the code every time I do an upgrade and change the >> code to allow for doublehash transfers instead of single hash >> transfers: >> If someone is currently using doublehash on a recent CVS could you >> be so kind as to email me a copy of your patch?> I hate being a "me too" poster, but the double-hash patch I have > implemented four times now, and I know at least three other people > who have also gone well out of their way to put that patch into their > system. Making this an "official" modification would be ideal, in my > opinion, especially if it is selectable (default=single #, to retain > previously expected functionality.)I secound that motion. This is something that should have been done many moons ago.
Hello, Well it gets me half way there, pressing ## does work with this patch, but pressing # once doesn't send a hash tone out, it gets muted while it waits to hear another tone. any way around this so you can press a single hash and have it send a tone through? That's the way the original doublehash patch worked and that's how we need this one to work. Thanks, MATT--- -----Original Message----- From: Olle E. Johansson [mailto:oej@edvina.net] Sent: Friday, July 23, 2004 12:59 PM To: asterisk-users@lists.digium.com Subject: Re: [Asterisk-Users] Doublehash transfers John Todd wrote:> I hate being a "me too" poster, but the double-hash patch I have > implemented four times now, and I know at least three other people who > have also gone well out of their way to put that patch into their > system. Making this an "official" modification would be ideal, in my > opinion, especially if it is selectable (default=single #, to retain > previously expected functionality.)Friends, I think this was one of the reasons parking.conf was changed to "features.conf". Let's help test this patch and see if it will help you. If not, add your features: http://bugs.digium.com/bug_view_page.php?bug_id=0002010 /O _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users