IP Office Twinned Calls Forwarding to Twin Destination- Resolved- AT&T sending premature connect msg 8

[SamIPOfficeSupport]

Hello IP Office Gurus, lurkers, and fellow internet users,

I have run into a weird problem. The twinning function is causing the call to the local IP Office user to drop. A call presents to the user but once it starts twinning the call that rings the desk phone is dropped.. so that the call is no longer available (or visible) to the local phone extension. The person calling in is not dropped, and they can be picked up at the twinned location. So, once twinning occurs, the incoming call is made unavailable to the desk phone.. If you have any ideas, please let me know.

 

[bahmonkeys]

From what I read the original issue was a caller hitting an extension which is then twinned to another extension.

Is this a DDI number going straight to an extension and not a huntgroup?

On that extension go to telephony, supervisor settings and untick inhibit offswitch transfer

Test again

 

[Matchbanker]

Thanks for the information! Happened to me too

 

[SamIPOfficeSupport]

Matchbanker - That's good news. Glad it worked out!

Hi bachmonkeys,

That setting was not ticked, but good idea to check that along the way. We determined that the carrier was sending an early connect message to the IP Office when twinning started. It was making it so that the incoming call would ring the IP Office phone for about half a ring, and then forward to the twinning destination (an external number) once the premature connect was received. The external number could answer the call, but because the CO sent the connect message, the twinned call was no longer available to the IP Office phone, only to the twinning destination. The above monitor log is proof of this happening to UserNameReplaced. No IP Office settings were adjusted to fix this problem, only multiple calls to AT&T BVoip support asking them to uncheck the "send early connect" on their router. I hope this helps you.