Koozali.org: home of the SME Server

SAIL - Zap ext. missing from FOP?

Offline gippsweb

  • *****
  • 232
  • +0/-0
    • Wots I.T.?
SAIL - Zap ext. missing from FOP?
« on: October 30, 2006, 07:30:54 AM »
Hi Jeff

Since upgrading from 2.1.11-214 to 2.1.14-340 our zap extensions are not showing up in FOP, is this by design?
Also trunks use to be named by (I think) description, now trunks are just showing as Trunk 1, Trunk 2, etc.
I have a strange problem with caller ID from one of the extensions, but thats a job for another day, it's almost beer o clock here.

Cheers

Mark

Offline SARK devs

  • *****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
SAIL - Zap ext. missing from FOP?
« Reply #1 on: October 30, 2006, 09:13:10 AM »
Hi Mark,

You got us mate.  As you probably figured we don't say much about FOP in our docs and that's because we have never really felt that it was quite good enough for an "industrial" deployment.  However, every now and again we have a little bit of a mess around with it and we did the last pass on it sometime around 336/340 (can't remember exactly without looking at the changelogs).

Anyhow, we'd never been happy with trunk definition (how do you know how many to allocate to each line and so forth) so we introduced "Trunk pooling", which we've never seen anywhere else but the FOP documentation implies that it's possible.  Turns out that it works great.  We now have twelve trunks in the pool.  As a call arrives (SIP or IAX - not ZAP just yet) it grabs the next available trunk slot from the pool and "lights it up".  That's why they are now just called Trunk1, Trunk2 etc. You can figure out which trunk it is from because it shows DNID. We think it's pretty cool, but no ZAP at the moment.  Probably in -346(ish).  

Let us know what you think.  Currently we are just beginning to deploy it as a display-only-assist to operators in some of our larger sites.  If you want a ZAP-as-well version to test then give us a shout and we'll cook one up for you.  
 
Kind Regards

Offline gippsweb

  • *****
  • 232
  • +0/-0
    • Wots I.T.?
SAIL - Zap ext. missing from FOP?
« Reply #2 on: October 30, 2006, 11:42:03 PM »
It isn't really an issue, it use to be handy just to note if the line had been hung up correctly by the system.

I've had a couple of instances of >1400min calls logged by CDR when it hasn't hung up.

Haven't been able to isolate the cause yet.(working on it).

I think the trunk pooling is a great idea, although most of the ITSP's here in oz only allow single outgoing calls even using iax.