Home

Call Queue - Frequent "Response Code 480"

%3CLINGO-SUB%20id%3D%22lingo-sub-381774%22%20slang%3D%22en-US%22%3ECall%20Queue%20-%20Frequent%20%22Response%20Code%20480%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-381774%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20else%20had%20problems%20with%20answering%20calls%20from%20a%20call%20queue%2C%20especially%20today%3F%20Since%20we%20moved%20calling%20to%20Teams%20a%20few%20weeks%20ago%20we've%20had%20the%20occasional%20issue%20where%20a%20call%20wouldn't%20be%20retrieved%20from%20the%20queue%20when%20answering%20on%20the%20first%20attempt%20(user%20would%20hear%20silence%2C%20caller%20would%20still%20be%20hearing%20the%20on-hold%20music).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EToday%2C%20though%2C%20almost%20every%20call%20has%20taken%20multiple%20attempts%20to%20retrieve%20from%20the%20call%20from%20the%20queue%20(I've%20seen%20up%20to%206%20attempts%20to%20retrieve%20a%20single%20call).%20This%20is%20with%20using%20the%20Teams%20desktop%20app%2C%20by%20the%20way.%20When%20I%20go%20to%20the%20Teams%20Admin%20Center%20and%20look%20at%20the%20answering%20user's%20call%20history%2C%20all%20of%20the%20answer%20attempts%20have%20an%20%22Response%20Code%20480%22.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-381774%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-390651%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20Queue%20-%20Frequent%20%22Response%20Code%20480%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390651%22%20slang%3D%22en-US%22%3E%3CP%3EHello%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F727%22%20target%3D%22_blank%22%3E%40Stephan%20Swinford%3C%2FA%3E%20%2C%3CBR%20%2F%3EWe%20are%20facing%20the%20same%20issue%20in%20our%20company.%20Mostly%20it%20is%20480%2C%20but%20today%20I%20found%20408.%3CBR%20%2F%3EI'm%20working%20with%20the%20Microsoft%20Support%20on%20that%20issue%20right%20now%2C%20so%20as%20soon%20as%20we%20find%20a%20root%20cause%20and%20the%20resolution%2C%20I'll%20share%20it%20with%20the%20community.%3C%2FP%3E%3CP%3ECheeris%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-653874%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20Queue%20-%20Frequent%20%22Response%20Code%20480%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-653874%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310362%22%20target%3D%22_blank%22%3E%40EzioAuditore%3C%2FA%3E%26nbsp%3B%20Have%20you%20ever%20got%20to%20the%20bottom%20of%20this%20issue.%20We%20are%20having%20the%20exact%20same%20issue%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-750325%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20Queue%20-%20Frequent%20%22Response%20Code%20480%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-750325%22%20slang%3D%22en-US%22%3ESame%20issue..%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-750755%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20Queue%20-%20Frequent%20%22Response%20Code%20480%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-750755%22%20slang%3D%22en-US%22%3E%3CP%3EUpdating%20that%20we%20haven't%20really%20had%20any%20issues%20with%20Call%20Queues%20since%20our%20tenant%20was%20upgraded%20about%20a%20month%20ago%20and%20resource%20accounts%20were%20moved%20from%20S4B%20Admin%20to%20Teams%20Admin.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-751141%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20Queue%20-%20Frequent%20%22Response%20Code%20480%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-751141%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20issue%20was%20resolved%20by%20our%20third%20party%20SBC%20provider%2C%20unfortunately%20I%20don't%20have%20the%20exact%20changes%20they%20made%20on%20the%20SBC.%20But%20after%20they%20traced%20the%20logs%20on%20the%20SBC%20they%20where%20able%20to%20pinpoint%20the%20issue%20and%20make%20the%20required%20changes%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-751375%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20Queue%20-%20Frequent%20%22Response%20Code%20480%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-751375%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20been%20working%20on%20an%20issue%20with%20Office%20365%20Support%20where%2C%20if%20a%20Skype%20for%20Business%20Online%20user%20has%20their%20line%20forwarded%20(say%2C%20to%20their%20voicemail)%20and%20dials%20a%20call%20queue%2C%20the%20agent%20hears%20silence%20and%20the%20caller%20continues%20to%20hear%20hold%20music.%20The%20caller%20gets%20a%20%22missed%20call%22%20notification%20email%20and%20Response%20Code%20480%20shows%20up%20in%20the%20call%20log.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

Has anyone else had problems with answering calls from a call queue, especially today? Since we moved calling to Teams a few weeks ago we've had the occasional issue where a call wouldn't be retrieved from the queue when answering on the first attempt (user would hear silence, caller would still be hearing the on-hold music).

 

Today, though, almost every call has taken multiple attempts to retrieve from the call from the queue (I've seen up to 6 attempts to retrieve a single call). This is with using the Teams desktop app, by the way. When I go to the Teams Admin Center and look at the answering user's call history, all of the answer attempts have an "Response Code 480".

6 Replies
Highlighted

Hello@Stephan Swinford ,
We are facing the same issue in our company. Mostly it is 480, but today I found 408.
I'm working with the Microsoft Support on that issue right now, so as soon as we find a root cause and the resolution, I'll share it with the community.

Cheeris

Highlighted

@EzioAuditore  Have you ever got to the bottom of this issue. We are having the exact same issue

Highlighted
Same issue..
Highlighted

Updating that we haven't really had any issues with Call Queues since our tenant was upgraded about a month ago and resource accounts were moved from S4B Admin to Teams Admin.

Highlighted

Our issue was resolved by our third party SBC provider, unfortunately I don't have the exact changes they made on the SBC. But after they traced the logs on the SBC they where able to pinpoint the issue and make the required changes

Highlighted

I've been working on an issue with Office 365 Support where, if a Skype for Business Online user has their line forwarded (say, to their voicemail) and dials a call queue, the agent hears silence and the caller continues to hear hold music. The caller gets a "missed call" notification email and Response Code 480 shows up in the call log.