501/601 Blind Transfer
Submitted by lancekoster on Mon, 12/17/2007 - 10:15am.
Hello PollyCom
When a call is transfered no MOH is heard by the caller unless a blind transfer is initiated. The end user's forget to push blind and they just hit transfer, The caller hears no MOH and thinks they got disconnected. Is ther anyway to enable MOH for both transfer methods
Thanks
Lance
501/601 Blind Transfer
Tue, 12/18/2007 - 1:38pm
It sounds like Trixbox supports blind transfers by handing the call off to a media server until the new call is complete. For attended transfers, the caller stays with the transfering phone until the transfer is completed. The transferring phone has no access to the MOH media server as the transfer function is local. This is what I would expect for attended transfers as the caller is still connected to the transferring phone, unless I've missed something. What does Trixbox say should happen?
Dave Finney
SE, Polycom
Blind but not deaf
Wed, 12/19/2007 - 12:17am
OK so what your saying is thats what it should do---If TRANSFER stays local how do we get a ring tone out of the polycom during the transfer. Or can we switch the funtionality of TRANSFER AND BLIND and change BLIND to ANOUNCE. End users don't relate to BLIND. I know they should read the book, But they dont. This continues to be a ongoing issue with every install. People think they got disconnected, call back and yell then they call me and yell, something has to be done with this PLEASE help.
Thanks Lance
blind but not deaf
Wed, 12/19/2007 - 3:50pm
That's the way it works, sorry. The phone doesn't play anything outbound when in transfer or hold mode. If this is an issue, I'd suggest you take it up thru Trixbox and have them log it as a feature request for a future phone release.
If I come up with any brite ideas to make something work, I'll let you know.
Dave Finney
SE, Polycom
I seem to recall this was actually an Asterisk bug
Wed, 12/19/2007 - 4:15pm
This may be what you need
Wed, 12/19/2007 - 4:18pm
Nah, something is mis-configured on your system
Wed, 12/19/2007 - 9:05pm
I REALLY don't like the 2.2 firmware with the new bootrom
Thu, 12/20/2007 - 9:35am
It takes FOREVER to boot the phones, is not compatible with 301's and 500's (we have LOTS installed) and had a problem with the Buddy icons showing correctly. I have stuck with 2.1.2 - It supports all the current phones, and has worked well for us - and this is what I tested last night that worked correctly.
Give it a try - It's not hard to switch back, and it won't disrupt your Endpoint Manager if you switch back.
Get a copy of 2.1.2 and do the following:
yum remove firmware-polycom
rpm -ivh firmware-polycom-2.1.2-2.noarch.rpm
setup-polycom
And then reboot a phone and try it. PM me with an address that can take LARGE attachments if you can't find the RPM and I will send it to you.
Greg
Blind but not deaf
Thu, 12/20/2007 - 10:15am
Greg
So your not having the Problem with the 2.1 firmware, I'm using the 2.2 I'll try your suggestion and Post results----I remember the buddy problem when 2.2 came out -- in a panick we reverted back to the 2.1 sip.config file but left the firware 2.2 and it fixed the Buddy Icon's and we left it that way (our Bad) According to that bug fix http://bugs.digium.com/view.php?id=9650 this problem was resolved but I don"t know if thats the version of Asterisk 2.3.10 uses
Thanks
Lance
Thanks for your reply
Thu, 12/20/2007 - 10:59am
Greg,
I found the sip 2.1.2. .Do I need to downgrade the bootrom as well? I have 4.0 right now.
my other question is can I just replace the files into the tftp folder instead of removing the rpm? if it failes at least I can restore those files back.
Thanks, I appreciate your help
David
I would think you would want to downgrade the Bootrom
Thu, 12/20/2007 - 11:31am
I HATE how long the phones take to boot on the new Bootrom - I start to think that the phone is not working or something is wrong with the network.
Look on the site at Polycom - they have a support matrix for the phones, and 2.1.2 supports ALL of their phones - right now, it is the best by far.
Greg
Downgrading the firmware didn't work
Fri, 12/21/2007 - 11:00am
asterisk 1.4.4
Mon, 12/24/2007 - 12:57pm
The bug report says it is fixed in asterisk 1.4.4 my server with 2.3.0.11 says Asterisk 1.4.16-1 I'm not sure how to upgrade the Asterisk code or even if it's advisable----Greg what ver. of asterisk are you running yours seems to be the only one that works properly.
No, we have multiple sites using 2.2 with Asterisk 1.2.2x
Mon, 12/24/2007 - 1:14pm
and they all get it too! We are currently using 2.3.0.10-80 with Asterisk 1.4.15-21, but it works at our sites that are using 2.2.x also.
You have to be doing something different than we are:
1) How are you loading the Polycom Firmware? From the package manger, from the cli (yum install firmware-polycom) or did you download it from Polycom and are rolling your own?
2) Have you updated FreePBX with all the modules that it will let you have? All our sites have ALL the current modules for FreePBX.
3) Have you messed with the MOH directory? Do you get MOH when you just put a call on hold?
Seriously, we are doing nothing weird - we are just loading the box, accepting the defaults, and getting on with it - there has to be something different somewhere.
Greg
I Hear You
Tue, 12/25/2007 - 2:55pm
2.4 will be out in a couple of days--I'll start from scratch when I install 2.4--see what happens. Well have to rebuild the TFTP anyway because it wont restore from the backup, I'LL make sure I get the Firmware from PolyCom. Whats confusing me is that asterisk Bug Report, it describes the problem exactly
No, not from Polycom
Tue, 12/25/2007 - 4:06pm
The rpm from Trixbox is tweaked so that it works perfectly with the Endpoint Manager - it is the preferred one to install - and if you don't want 2.2.0 (which is what the package manager offers) get the one off of our FTP site (ftp://ftp.bdc-llc.com) - it is the 2.1.2 package from Trixbox before they removed it and put up the 2.2.0 - I install it on all our installs because it a) works with ALL Polycom phones and b) doesn't have the annoying bug where the phones take 4-5 minutes to post and boot.
Greg
Member Since:
2007-04-20