Key system line appearances.

Sippy

Member
Joined
Nov 11, 2007
Messages
105
Reaction score
1
This is a link to an asterisk script that will put line appearances on phones like a key system. I got this from Mark Sumpter at Dreamwave Networks. They have a cool phone that has great sound quality.

I wish this could be put in a module because I don't know how to do scripts like this.


http://www.asterisk.org/node/48342
 
It's included in the Aastra apps on this site.

Emulating a SLA is one of the biggest development goals we have for our FX-16 PBX and if anyone has any updated asterix code that would be helpful let me know.

Ward would you be able to link me to that Aastra ap?:banghead:
 

I think the best way to answer this is to post the discussion we are currently having in our developmental meeting. This response is from Mike T. that was a Panasonic dealer for almost 25 years and we are wanting to develop our SLA along these lines.

Panasonic has 3 conditions whereby a line can be handled under a programmable key.



1. Standard C.O. (Central Office) lines that may or may not be squared (squared meaning the same arrangement is identical on every phone). ie. line 1,2,3,4,5 etc..



2. Pooled lines. One key has access to multiple lines. Seldom used but desirable when in a multi-

tenant arrangement and there aren't enough keys to handle all the lines.



3. Group C.O. A poor choice of name, however, this is a good function for IP phone systems. Rather than having a specific line assigned to each key, any line can float into the pool. When placed on hold, however, it appears under the same key location on each set. Very much like parking with the addition that the parked calls flash on hold on every set. This is ideal because it will make no difference whether it is a conventional line or a SIP derived trunk. On the 26P and 28P sets the 3 or 6 line keys next to the display can be used for holding on that particular set. The lighted keys along the side, however, can be used as system hold keys that are common to all the phones. based upon user requirements, a few or many keys can be used to provide key system mimicking. Panasonic uses dual color LEDs to indicate calls placed on hold at the set (green) vs. calls held by other sets (red).



Timed held line reminder is a good feature but poorly implemented in most systems because the re-call is too aggressive and thus, annoying. A pleasant reminder tone every 15 seconds should suffice. I turn this feature off on the Panasonic system as the reminder ringing is loud and constant which users dislike. Every system where I left it on, I was asked to turn it off.
Subsequent Email:Panasonic allowed for 3 functions of keys set up for trunk access.



1. Direct 1:1 line appearance with hold and flashing. Calls on hold made at the originating set

flashed in green. It flashed red on all other sets. If another set picked up the line it would turn to

green on that set and red on all the others. If the call was then placed on hold it would flash green

on that set and flash red on all the others. If the user pushed the 'HOLD' button twice in succession the call could only be taken off hold from the set that put it on hold. All other phones would show steady red in this case. It was called 'Exclusive Hold.'



2. A key could be assigned as a pooled loop key. This saved buttons on the sets. More than one line could be accessed via a single key. For example, a system could have OPX stations (FXS) from another system arriving in a trunk group of say, four lines. There is no need to occupy four keys when one will suffice. The key would turn red when all of the lines were in use. It would remain dark as long as lines were available. Calls on that key would flash just like in the above example.



3. Floating loop keys. It makes no difference which line would go onto a key.A set would be set up with say 5 of these 'parking' keys. as many as five calls, regardless of what type of trunk the lies were associated with, as many as five calls could be held on these keys. The operation and indications of which are also as described in scenario #1 above. This is, IMO the best method to use if the customer has more lines than available buttons or has a mixture of POTS and SIP trunks. This way the limit for all phones functioning in a key system scenario will be only limited by the number of keys reserved for this type of function.



All three situations as described above should be available as this combination offers the greatest

flexibility.
 
Last edited by a moderator:
Best reference site I found on the trials and tribulations of Shared Line Appearance (SLA) operation is at http://www.smartvox.co.uk/astfaq_asterisk_sla.htm


Very well written, and full credit to John Quick at Smartvox Limited in the UK for a very thorough and well written article.


To see Asterisk behaving quite well as a Shared Line Appearance / Key Telephone System www.konnectoffice.com/konnect-business-phones-kts

Regards.
Thanks for the links... The smartvox link is especially well documented and written and should be a huge help to us and anyone else:D...
 
Has anyone seen a custom implementation of SCA ,shared extensions or call appearance (not SLA). I DON'T MEAN SOMETHING LIKE IT or anything to do with parking...

Rather than an extension or key position being tied to a trunk I'm talking about an extension like 720 appearing on multiple sip phones where lights an hold working exactly like a keyset but again not trunk related.

I've heard all the arguments and suggestions to emulate but wondered if anyone had custom coded something.

brian
 
SLA is not supported by Digium / Asterisk, and therefore the best anyone can do is emulation and workarounds.

Joe
 
Hi.. appreciate the reply. Yeah I knew that but I think with the right sip phone, right ver of asterisk, maybe a little custom code (perhaps hint driven) and or some custom C, Perl etc. I thought someone might have put something together... perhaps that fellow Ethan.. For someone who does this kind of coding all the time I don't think it would be that hard to get it working on a static installation, forget about upgrades though.

brian
 
The problem with SLA is that you need an intermediate cleint that can register the extenisions to Asterisk as an intermediary and then interface between the phones and the Asterisk. So far, no one has written anything like that and much of the community scorns the idea.

I come from a large proprietary systems background and SLA is just a given on those systems. I'm just hoping that FreeSwitch and FreePBX 3.0 will bring the other features we want to the table before too long.
 
There are hints of a big announcement at Astricon. Rumor has it that it might be a code rewrite.

If so, lets hope they implement SLA
 

Members online

Forum statistics

Threads
26,687
Messages
174,410
Members
20,257
Latest member
Dempan
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.
Back
Top