Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

2 Glitches after 4.2.14 upgrade transfers and incoming display

Status
Not open for further replies.

Larryataccess

IS-IT--Management
May 23, 2008
56
US
I am having two glitches now after my upgrade to 4.2.14(no big surpise normal Avaya)
1. When my user transfers(using the transfer button on the phone) it used to ring for awhile and then go to the users VM now it rings awhile and if the user does not answer it rings back to the user that did the transfer.
2. Inbound Calls used to show the phone number when they were ringing in but now it say "Voicemail" until you answer and then after to you answer it showes the Caller ID.

There were no setting changes just the upgrade that caused this. I know this is probably stupid but I have not found it in my searches online.

 
if user 1 transfers to user 2 it always goes back to user 1 if user 2 does not answer.
 
To what is the Forward on no answer set on the user, to a shortcode?

If so, add a shortcode without a * in it.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
 
what is your system/telephony default no answer time set to?

what is your user/telephony transfer return time set to?

Joe W.

FHandw., ACS

If you can't be good, be good at it!
 
Is that on the User, or on the System?

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
 
The user timers overrule the sytem timers, so check the user ones if they are still default.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
 
agree to bas, what is the users no answer time set to

Joe W.

FHandw., ACS

If you can't be good, be good at it!
 
These are the user settings
No answer time is 15
Wrap up time is 2
Transfer return time is 25
 
that looks good to me, check the forward on no answer settings if there is something checked on

Joe W.

FHandw., ACS

If you can't be good, be good at it!
 
Open the System Status then you will see whats happening!

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
 
Did you reboot the VMPro server after the upgrade?

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
 
did you maybe build on an ancient Indian burial ground? :-(
this is a mystery, i was ready to suggest a reboot on both system and VM, but that is done I see

Joe W.

FHandw., ACS

If you can't be good, be good at it!
 
Better, open the monitor and make a trace on this.
Then copy/paste it here.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
 
Are you sure you are looking at the user timers for the person transferring the call, not the person receiving the call?

Disable the "transfer recall" from this user and see does the call then go to voicemail.

Failing all this, open SSA, trace the call and post.

Re part 2 - trace this also and describe how the call gets to the agent.
 
I will try a reboot tonight of both if you think it will help any? It is wierd that it worked before the upgrade but not after.
 
I actually doubt that the upgrade did that to the system, but a trace would be helpful for the troubleshooting as bas and TT said.

Joe W.

FHandw., ACS

If you can't be good, be good at it!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top