Call transfer on 3904/3903 process

[jaja2468]

We have been notified that the process by which our customer was able to transfer calls has changed. The customer states that call comes in, they hit the soft key for TRANSFER, get dialtone, dial the DN to transfer to and see the soft key for CONNECT. If they hit CONNECT at this point, they are dropped off the call and the 2 parties are connected. If the transfer party answers prior to hitting the CONNECT soft key, the CONNECT option disappears. This is where the customer says something has changed. The CONNECT option never used to disappear.

I have found that in testing, if the transfer party answers, the CONNECT does disappear, and I have to press the key appearance for the dialtone that the call came into. I am then given the option to CONNECT.

Is this the correct process or is the customer correct that something is different. To be honest, I never noticed how transfer worked prior to this coming up.

 

[GHTROUT]

I'm thinking it isn't all phones. You could do a forced download of the phones to get the systems latest firmware. In FAQs for this group, there are the steps.

In other words, I've seen phones get dumb like this before. The Forced Download fixed it in my case.

--
Nortel Resources at GHTROUT.com | Connect with me on LinkedIn
--

 

[jaja2468]

Is this the process you are referring to? faq798-4738

And do you think the way the customer described the transfer process is correct?

 

[yyrkroon]

The Connect button shouldn't disappear. Update the firmware on the set as GH suggested should correct this problem. Older release Taurus sets sometime goes stupid and needed to be updated.

 

[jaja2468]

This has worked. I am having issue with a couple of the sets retreiving the firmware version. After I enter the FWVU command, I get NPR039 which tells me there is a response timeout from the Taurus set.

I don't want to proceed with a DL on those sets because it would seem I don't have a connection to them. I disabled/enabled the TN and I have unplugged and plugged back in the set. Is there some other course of action I can take?

 

[johnpoole]

idu 4 0 0 0

against the tn (ld 32).. that will return the serial number of the set if it's plugged in.. you know the download is just for 3900 sets i assume,

john poole
bellsouth business
columbia,sc

 

[tmford]

Has your customer recently upgraded their switch? We had the exact same problem after going to 6.0 and a patch fixed it. Downloading firmware also worked but the patch was an easier soloution.

 

[jaja2468]

@tmford, yes the PBX was upgraded to 6.0. What was the patch you loaded. This an 81C PBX.

 

[jaja2468]

@johnpoole, yes these are all 3900 sets. Will the idu command verify that I will be able to communicate with the set and proceed with the DL?

 

[tmford]

I do not remember the patch number but I have 29326 circled on my notes from that problem. Sorry it has been a while. Good Luck!!!

 

[johnpoole]

yes

john poole
bellsouth business
columbia,sc

 

[jaja2468]

Well the idu command also timed out. The phones are in service and plugged in. Is it possible there is just an issue with these particular sets and I will have to change them out?