• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Target Not Availble (Ring Group)

Status
Not open for further replies.

aerostotle

Joined
Oct 13, 2011
Messages
9
Reaction score
0
13:40:34.390 [CM503007]: Call(5164): Device joined: sip:[email protected]:5066
13:40:34.375 [CM503007]: Call(5164): Device joined: sip:[email protected]:5062
13:40:34.359 [CM505002]: Gateway:[Patton7] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4524 JO EUI 00A0BA05057C R5.8 2011-07-01 H323 SIP FXS FXO M5T SIP Stack/4.0.30.30] PBX contact: [sip:[email protected]:5060]
13:40:34.359 [CM503002]: Call(5164): Alerting sip:[email protected]:5066
13:40:34.031 [CM503025]: Call(5164): Calling PSTNline:7809171211@(Ln.10003@Patton7)@[Dev:sip:[email protected]:5066]
13:40:33.984 [CM503005]: Call(5164): Forwarding: PSTNline:7809171211@(Ln.10005@Patton8)@[Dev:sip:[email protected]:5062,Dev:sip:[email protected]:5064,Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5066]
13:40:33.984 [CM503005]: Call(5164): Forwarding: PSTNline:7809171211@(Ln.10003@Patton7)@[Dev:sip:[email protected]:5066]
13:40:33.968 [CM503016]: Call(5164): Attempt to reach <sip:[email protected]:5060> failed. Reason: Not Registered
13:40:33.968 [CM503017]: Call(5164): Target is not registered: <sip:[email protected]:5060>
13:40:33.968 [CM503016]: Call(5164): Attempt to reach <sip:[email protected]:5060> failed. Reason: Temporarily Unavailable
13:40:33.968 [CM503026]: Call(5164): Target is not available: RingAll800[]

13:40:33.953 [CM503010]: Making route(s) to <sip:[email protected]:5060>
13:40:33.937 [CM505002]: Gateway:[Patton7] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4524 JO EUI 00A0BA05057C R5.8 2011-07-01 H323 SIP FXS FXO M5T SIP Stack/4.0.30.30] PBX contact: [sip:[email protected]:5060]
13:40:33.937 [CM503001]: Call(5164): Incoming call from anonymous@(Ln.10001@Patton7) to <sip:[email protected]:5060>

800 is our receptionist ring group. That ring group is set to ring 4 extensions for 15 seconds, then connect to extension 305 if no answer. 305 is unregistered but forwards to our after-hours call centre (the 7809171211) number. The 4 extensions were free at the time, but this call was immediately ditched by the system. This is a very intermittent problem. Any ideas?
 
Did all four members of the ring group show as registered at the time? Does the log show them registering at a later point?
If you dial 800 from an extension, not in the ring group, does it ring the members?

Being intermittent, it almost sounds like the sets are not re-registering within the "normal" 30 minute default time-out.
 
All of the 4 extensions on the ring group were registered and working properly. Inbound calls were being handled through 800 properly in the minutes before and after the troubled call. I don't get what the 30 minute default time-out is.... :(
 
Or folks are using DND to make themselves unavailable on purpose or by accident. What make/model of phones?
 
Polycom 335. They don't know how to use DND...
 
The 30 minutes being referenced is that the phones have a schedule registration interval. It is possible that the phones dropped off line due to a network issues, but the system thinks they are still registered as the time has not elapsed and the phones did not unregistered as they might as some cases like a commanded reboot or other.

If the system thinks they are stil registered and made an attempt to forward the call and got no response, this might explain the unavailable message.
 
Did this issue just crop up, or has it been this way since the original install? If it began recently, have there been any hardware or firmware/software changes/updates done on the network/system?
 
lneblett: Is it likely that that problem would affect 4 separate extensions, all at the same time, and then restore them all at the same time? It doesn't sound like there would be enough commonality to make that happen.
 
Possibly. If indeed there was some type of network issue and the phones were not able to re-register, then they try to recoverby using an aceILerated registration algorithm. f the network came back then there is some likelihood that the phones all started to re-register at the same or approximately the same time.
 
I figured this one out. Apparently a ring group can only handle one call at at time, meaning if a second person calls before anyone answers the first call, it immediately handles the second call as if it was unanswered. Meaning that if you want a ring group that handles multiple people calling, you need to either use a queue or string multiple ring groups together (ring group 1 sends the call to a clone ring group 2 if it is unanswered).

Design flaw? How hard would it be to allow multiple calls on a single ring group extension?
 
aerostotle - that is good finding - except my system seems to accept multiple calls on a ring group at the same time.

I use them for my incoming calls when my receptionist is on break or at lunch. she forwards her phone to DND and calls goto a Ring Group ringing 5 phones. if another call comes in, another line flashes on those phones.

could it be how your phones are setup - or the extension - not allowing more than 1 call.
 
aerostotle said:
I figured this one out. Apparently a ring group can only handle one call at at time, meaning if a second person calls before anyone answers the first call, it immediately handles the second call as if it was unanswered. Meaning that if you want a ring group that handles multiple people calling, you need to either use a queue or string multiple ring groups together (ring group 1 sends the call to a clone ring group 2 if it is unanswered).

Design flaw? How hard would it be to allow multiple calls on a single ring group extension?


Just tested, ring groups can have more then one call at the same time
 
Ring groups support multiple calls at the same time.

The issue is:
13:40:33.968 [CM503016]: Call(5164): Attempt to reach <sip:[email protected]:5060> failed. Reason: Not Registered
13:40:33.968 [CM503017]: Call(5164): Target is not registered: <sip:[email protected]:5060>
13:40:33.968 [CM503016]: Call(5164): Attempt to reach <sip:[email protected]:5060> failed. Reason: Temporarily Unavailable
13:40:33.968 [CM503026]: Call(5164): Target is not available: RingAll800[]

Until this is understood and fixed, there will be no effective ring group handling. Perhaps a system service did not start or start correctly. Perhaps this is also related to the removal of ring group features in V11 from the free version that I have seen posted throught the forum of late. The version and whether paid or not was not mentioned in this thread.
 
Paid version 10. Will restart services at the close of business.

The problem definitely only occurs when there is already a ringing call on the ring group and at no other time. I guess this is isolated to my system and not a design problem.
 
Did you ever found a solution, it looks like i had this problem just now also. 2 calls on the same time and 1 was transfered to the "Destination if no answer" option.
 
Have you checked that the extensions that are members of the ring-group, all have the setting 'I want to be able to accept more than 1 call at the same time- uses phone status' - selected (ticked)??

You'll find that setting in the 'Phone is Busy' section in the 'Forwarding Rules -> Available' for each extension.

best regards
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,636
Messages
749,003
Members
144,754
Latest member
deanhbs
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.