Narrative:

I had climbed aircraft X to 41;000 ft. And handed him off to the next sector. I went on to some other tasks. When I came back; aircraft X was still handing off and about 2 1/2 or less from their airspace. I called them on the six line immediately for a handoff; and they would not answer or take the handoff. I heard them saying; 'we're on the four line.' I had the high altitude sectors at the lows; and the landline keys are in different spots than what we are accustomed to when the highs are open in their usual location. Because of this; I was more concerned about them answering me on the line I called them on; which they could hear just fine; rather than look back down at the vscs and now try to find the 4 line. Just then; I saw a limited data block at 41;000 ft. Who appeared to be traffic in their airspace; so I got off the line and stopped my aircraft's climb to 40;000 ft. And got back on the line for a handoff that they still wouldn't take. Finally; I got them on the line and they said; 'stop him at FL370;' and then they took the handoff; after the aircraft had updated into their airspace. About 2 minutes later; I had another aircraft that had been handing off to them which got 2 minutes flying time from their boundary. I called them for a handoff on this aircraft. When they answered; they responded; 'that's a little early to be calling on that.'I had asked if we did something to upset them and explained the two minute from the boundary rule we attempt to not go past before calling for a handoff. They didn't respond. To me; they were clearly not being professional. During the shift yesterday; I had called for a d-side (assist) due to those sectors not taking handoffs or answering the landlines during moderately busy traffic. I did not have a d-side during today's incident.

Related reports:

Google
 

Original NASA ASRS Text

Title: Center Controller reported the adjacent sector intentionally delayed in accepting a handoff causing the Controller to have an airspace deviation.

Narrative: I had climbed Aircraft X to 41;000 ft. and handed him off to the next sector. I went on to some other tasks. When I came back; Aircraft X was still handing off and about 2 1/2 or less from their airspace. I called them on the six line immediately for a handoff; and they would not answer or take the handoff. I heard them saying; 'We're on the four line.' I had the high altitude sectors at the lows; and the landline keys are in different spots than what we are accustomed to when the highs are open in their usual location. Because of this; I was more concerned about them answering me on the line I called them on; which they could hear just fine; rather than look back down at the VSCS and now try to find the 4 line. Just then; I saw a limited data block at 41;000 ft. who appeared to be traffic in their airspace; so I got off the line and stopped my aircraft's climb to 40;000 ft. and got back on the line for a handoff that they still wouldn't take. Finally; I got them on the line and they said; 'Stop him at FL370;' and then they took the handoff; after the aircraft had updated into their airspace. About 2 minutes later; I had another aircraft that had been handing off to them which got 2 minutes flying time from their boundary. I called them for a handoff on this aircraft. When they answered; they responded; 'That's a little early to be calling on that.'I had asked if we did something to upset them and explained the two minute from the boundary rule we attempt to not go past before calling for a handoff. They didn't respond. To me; they were clearly not being professional. During the shift yesterday; I had called for a D-side (Assist) due to those sectors not taking handoffs or answering the landlines during moderately busy traffic. I did not have a D-side during today's incident.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.