Failed to aquire SLA slot error

Discussion in '3CX Phone System - General' started by leejor, Aug 2, 2010.

Thread Status:
Not open for further replies.
  1. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,839
    Likes Received:
    298
    Took the plunge. Backed up then deleted Version 7.1, rebooted PC. Installed latest Ver 9 download. Applied 3CX restore. I noticed, before I put in the Version 9 Demo key that call limit showed as -1. That changed to 2 when demo key applied. OK, got one error message when doing the restore of 3CX files.

    Important Notification 3CX Phone System version 9
    --------------------------------------------------
    Due to changes in the forwarding rules design and the addition of profiles, some extension rules could not be restored from previous versions to version 9.

    This is a list of rules that could not be converted.

    The following rules could not be converted for extension: 205
    Rule 1: Hours_Type:AllHours; Condition: NoAnswer; Call_Type: ExternalCallsOnly; Forward_To: VoiceMail; ExternalNo: ; InternalNo: 250

    My system has four extension in a ring group with the incoming calls going to the VM box of Ext 250 when there is no answer. Ext 250 appears twice on my system, a key on an SPA842 and a line on an SPA2102. Never any issues with Ver 7.1 for close to a year.
    Everything seemed to be fine however I received a late night call that did not go into the Voicemail of Extension 250. I confirmed all of the call forwarding rules, which were fine.

    This was the log...

    01:32:49.375 [CM503003]: Call(7): Call to sip:202@192.168.248.200 has failed; Cause: 487 Request Terminated; from IP:192.168.248.201:5061
    01:32:49.265 [CM503020]: Normal call termination. Reason: Not found
    01:32:49.265 [CM503016]: Call(7): Attempt to reach <sip:800@192.168.248.200:5060> failed. Reason: Not Found
    01:32:49.265 [todo] Call(7): Can not call sip:250@192.168.248.250:5060: there's no free SLA appearance
    01:32:49.265 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.265 [todo] Call(7): Can not call sip:250@192.168.248.222:5060: there's no free SLA appearance
    01:32:49.265 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.265 [todo] Call(7): Can not call sip:250@192.168.248.224:5060: there's no free SLA appearance
    01:32:49.265 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.250 [CM503003]: Call(7): Call to sip:202@192.168.248.200 has failed; Cause: 487 Request Terminated; from IP:192.168.248.250:5062
    01:32:49.234 [CM503003]: Call(7): Call to sip:201@192.168.248.200 has failed; Cause: 487 Request Terminated; from IP:192.168.248.201:5060
    01:32:49.203 [todo] Call(7): Can not call sip:250@192.168.248.250:5060: there's no free SLA appearance
    01:32:49.203 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.203 [todo] Call(7): Can not call sip:250@192.168.248.222:5060: there's no free SLA appearance
    01:32:49.203 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.203 [todo] Call(7): Can not call sip:250@192.168.248.224:5060: there's no free SLA appearance
    01:32:49.203 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.140 [todo] Call(7): Can not call sip:250@192.168.248.250:5060: there's no free SLA appearance
    01:32:49.140 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.140 [todo] Call(7): Can not call sip:250@192.168.248.222:5060: there's no free SLA appearance
    01:32:49.140 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.140 [todo] Call(7): Can not call sip:250@192.168.248.224:5060: there's no free SLA appearance
    01:32:49.140 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.125 [CM503003]: Call(7): Call to sip:201@192.168.248.200 has failed; Cause: 487 Request Terminated; from IP:192.168.248.250:5061
    01:32:49.125 [CM503003]: Call(7): Call to sip:211@192.168.248.200 has failed; Cause: 487 Request Terminated; from IP:192.168.248.221:5060
    01:32:49.093 [todo] Call(7): Can not call sip:250@192.168.248.250:5060: there's no free SLA appearance
    01:32:49.093 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.093 [todo] Call(7): Can not call sip:250@192.168.248.222:5060: there's no free SLA appearance
    01:32:49.093 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.093 [todo] Call(7): Can not call sip:250@192.168.248.224:5060: there's no free SLA appearance
    01:32:49.093 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.031 [todo] Call(7): Can not call sip:250@192.168.248.250:5060: there's no free SLA appearance
    01:32:49.031 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.031 [todo] Call(7): Can not call sip:250@192.168.248.222:5060: there's no free SLA appearance
    01:32:49.031 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:49.031 [todo] Call(7): Can not call sip:250@192.168.248.224:5060: there's no free SLA appearance
    01:32:49.031 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:29.031 [CM503025]: Call(7): Calling RingAll800:250Ext.250211Ext.211201Ext.201202Ext.202@[Dev:sip:202@192.168.248.201:5061]
    01:32:29.015 [CM503025]: Call(7): Calling RingAll800:250Ext.250211Ext.211201Ext.201202Ext.202@[Dev:sip:202@192.168.248.250:5062]
    01:32:29.015 [CM503025]: Call(7): Calling RingAll800:250Ext.250211Ext.211201Ext.201202Ext.202@[Dev:sip:201@192.168.248.201:5060]
    01:32:29.000 [CM503025]: Call(7): Calling RingAll800:250Ext.250211Ext.211201Ext.201202Ext.202@[Dev:sip:201@192.168.248.250:5061]
    01:32:28.984 [CM503025]: Call(7): Calling RingAll800:250Ext.250211Ext.211201Ext.201202Ext.202@[Dev:sip:211@192.168.248.221:5060]
    01:32:28.984 [todo] Call(7): Can not call sip:250@192.168.248.250:5060: there's no free SLA appearance
    01:32:28.984 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:28.984 [todo] Call(7): Can not call sip:250@192.168.248.222:5060: there's no free SLA appearance
    01:32:28.984 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:28.984 [todo] Call(7): Can not call sip:250@192.168.248.224:5060: there's no free SLA appearance
    01:32:28.984 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    01:32:28.968 [CM503004]: Call(7): Route 1: RingAll800:250Ext.250211Ext.211201Ext.201202Ext.202@[Dev:sip:250@192.168.248.224:5060,Dev:sip:250@192.168.248.222:5060,Dev:sip:250@192.168.248.250:5060,Dev:sip:211@192.168.248.221:5060,Dev:sip:201@192.168.248.250:5061,Dev:sip:201@192.168.248.201:5060,Dev:sip:202@192.168.248.250:5062,Dev:sip:202@192.168.248.201:5061]
    01:32:28.937 [CM505002]: Gateway:[689] Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3102-5.1.7(GW)] PBX contact: [sip:10002@192.168.248.200:5060]
    01:32:28.937 [CM503001]: Call(7): Incoming call from 1XXXXXX2990@(Ln.10002@689) to <sip:800@192.168.248.200:5060>
    01:32:28.937 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10002 forwards to DN:800

    I can place calls from Ext 250, it shows as registered, can access it's voicemail box just fine. However if I try ringing 250 from another extension, this is the log I get...


    09:25:36.312 [CM503020]: Normal call termination. Reason: Not found
    09:25:36.312 [CM503016]: Call(10): Attempt to reach <sip:250@192.168.248.200> failed. Reason: Not Found
    09:25:36.312 [todo] Call(10): Can not call sip:250@192.168.248.250:5060: there's no free SLA appearance
    09:25:36.312 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    09:25:36.312 [todo] Call(10): Can not call sip:250@192.168.248.222:5060: there's no free SLA appearance
    09:25:36.312 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    09:25:36.312 [todo] Call(10): Can not call sip:250@192.168.248.224:5060: there's no free SLA appearance
    09:25:36.312 Failed to acquire SLA slot for DN 250; TODO: Do proper message
    09:25:36.265 [CM503004]: Call(10): Route 1: Ext:Ext.250@[Dev:sip:250@192.168.248.224:5060,Dev:sip:250@192.168.248.222:5060,Dev:sip:250@192.168.248.250:5060]
    09:25:36.250 [CM503001]: Call(10): Incoming call from Ext.201 to <sip:250@192.168.248.200>

    Once again I get Failed to acquire SLA slot for DN 250; TODO: Do proper message

    Haven't seen that one before.

    Luckily I still have 7.1 on a backup PC, so I'm still in business. Any Ideas?
    Thanks
     
  2. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    You can either disable SLA support by setting SLA_ENABLED custom parameter to 0, or specify desired number of SLA slot per subscription by changing (or adding) SLA_ONSUBSCRIBE custom parameter. I.e. SLA_ONSUBSCRIBE=2 will create 2 SLA slots on subscription.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,839
    Likes Received:
    298
    Thanks, will try that.
    What are the advantages (or disadvantages , other than my issue) of enabling/disabling the SLA slots, or even having a default of, say, two subscriptions per set? Why would this issue not have cropped up in the past (versions) for me?
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,839
    Likes Received:
    298
    I set SLA_ENABLED to 1, tried putting in 2 in SLA_ONSUBSCRIBE but the pop up says it is either on or off (1or 0), 2 didn't make a difference.. An internal call to Ext 250 results now in key 1 ringing on the SPA942 but the other appearance of Ext 250 does not ring. As before the logs show that "there is no free SLA appearance". The call goes to busy (terminated) rather than VM as it is supposed to.
     
  5. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    Strange, in Windows Management Console (at least) I can set any number for SLA_ONSUBSCRIBE. If you have 3 phones that share Ext. 250 - you need at least 3 slots available.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,839
    Likes Received:
    298
    Thanks, will give it another shot this evening. Ext 250, on occasion, does have 3 appearances, but not at the moment.I will set a higher value. I've had a quick go over the manual, is this change (for users with multiple number appearances) documented? I'm sure that this is going to affect a number of users when upgrading.
     
  7. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,839
    Likes Received:
    298
    Changed SLA_ONSUBSCRIBE to 3, downloaded the latest update and restarted. Seems to work OK now. The SLA_ONSUBSCRIBE option still shows that the two options are on or off, 0 or 1, you need to change that to indicate that it may need to be a higher number.

    I did not have the line appearance on my SPA942 set as "shared". If one were using multiple appearances of an extension using ATA's or as I have, a non shared key, should this require SLA to be activated?
     
Thread Status:
Not open for further replies.