- Joined
- Oct 31, 2007
- Messages
- 133
- Reaction score
- 0
Running 5.1.4393
All of our incoming DIDs ring Ring Groups rather than extensions (so we can add and remove extensions that handle them as needed).
However, it appears that if a Ring Group only contains a single extension, even if that extension is specified to use phone status for busy indication (as the phone can support multiple calls), if that extension is already on a call, and a call comes in to the associated DID, the ring group won't call the extension, but instead takes the phone unregistered action (which, in this case, was to forward to another extension which in turn is set to always forward to a mobile).
Note that even though the phone was not busy according to the phone status, 3CX did not carry out the busy action (or the ring action), but instead carried out the not registered action - even though the phone was registered, on a call, and showing as on a call on the status display during the call and registered on hang up.
In short, 3CX is incorrectly treating an extension on a call as not registered in ring group handling.
All of our incoming DIDs ring Ring Groups rather than extensions (so we can add and remove extensions that handle them as needed).
However, it appears that if a Ring Group only contains a single extension, even if that extension is specified to use phone status for busy indication (as the phone can support multiple calls), if that extension is already on a call, and a call comes in to the associated DID, the ring group won't call the extension, but instead takes the phone unregistered action (which, in this case, was to forward to another extension which in turn is set to always forward to a mobile).
Note that even though the phone was not busy according to the phone status, 3CX did not carry out the busy action (or the ring action), but instead carried out the not registered action - even though the phone was registered, on a call, and showing as on a call on the status display during the call and registered on hang up.
In short, 3CX is incorrectly treating an extension on a call as not registered in ring group handling.
Code:
17:57:39.539 Call::Terminate :[CM503008]: Call(25): Call is terminated
17:57:39.489 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:801
17:57:39.469 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:801
17:57:39.449 Call::RouteFailed :[CM503014]: Call(25): Attempt to reach [sip:[email protected]:5060] failed. Reason: Not Registered
17:57:39.399 Call::RouteFailed :[CM503014]: Call(25): Attempt to reach [sip:[email protected]:5060] failed. Reason: Not Registered
17:57:39.399 CallCtrl::onSelectRouteReq :[CM503015]: Call(25): Target is not registered: RingAll801:
17:57:39.369 Line::printEndpointInfo :[CM505003]: Provider:[MyNetFone] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [ENSR2.5.4] Transport: [sip:10.10.10.40:5060]
17:57:39.369 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:801
17:57:39.229 CallCtrl::onIncomingCall :[CM503001]: Call(25): Incoming call from 0123456789@(Ln.10000@MyNetFone) to [sip:[email protected]:5060]