Koozali.org: home of the SME Server

Inward hairpin to Outward

Offline apmuthu

  • *
  • 244
  • +0/-0
Inward hairpin to Outward
« on: December 04, 2009, 06:55:48 AM »
Using SARK/SAIL v2.3.x how do we answer a SIP Trunk incoming call and send it out to a SIP Trunk outbound specific number? This way we can have many Incoming SIP Trunks send out calls to as many specific PSTN numbers dialed out using SIP Trunks.

Offline SARK devs

  • ****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Re: Inward hairpin to Outward
« Reply #1 on: December 04, 2009, 09:36:32 AM »
You can trunk-switch manually using multiple DiD entries driving callgroups (aka aliases) which have the destination numbers and trunks in them.  It isn't documented but you can force which trunk is used in a call group entry by including the peer name in the call group reference - like this...

SIP/{external number}@{peername}

So, if you want to be really smart, you can have a call group (ring group) with both forced and route-selected entries in it...

If you are intending to receive a DiD range and forward them all to the same number then you can create a DiD class to deal with all of them in a single entry.

Kind Regards

S

Offline apmuthu

  • *
  • 244
  • +0/-0
Re: Inward hairpin to Outward
« Reply #2 on: December 04, 2009, 05:03:04 PM »
Thankyou indeed!

The Call Groups did the job!

The image at the DocsWiki seems to be for an older (or newer?) version of SAIL.


Offline SARK devs

  • ****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Re: Inward hairpin to Outward
« Reply #3 on: December 04, 2009, 09:33:27 PM »
This shot is from 2.2.4 I think.  It's a fairly recent release because it is using the term "Call Groups" instead of the older "Aliases"

Kind Regards

S
« Last Edit: December 04, 2009, 09:35:04 PM by SARK devs »

Offline apmuthu

  • *
  • 244
  • +0/-0
Re: Inward hairpin to Outward
« Reply #4 on: December 05, 2009, 03:16:07 AM »
The screenshot is from Version: sail-2.3.1-20

What is the purpose of the Serial # in SARK -> Global Settings? And where is it stored?

Offline SARK devs

  • ****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Re: Inward hairpin to Outward
« Reply #5 on: December 05, 2009, 07:37:06 AM »
It is used to manage our commercial customer support agreements.  It is stored internally within SAIL.


Offline apmuthu

  • *
  • 244
  • +0/-0
Re: Inward hairpin to Outward
« Reply #6 on: December 07, 2009, 03:12:36 PM »
I just upgraded to SAIL v2.4.1-2 released a couple of days ago. In the Call Groups (edit of an entry) Menu, the form label Number(s) to be redirected to in v2.3.1-20 is now group in v2.4.1-2 - a very cryptic and unjustifiable change indeed! This is also evident in the Call Groups List Page as well. The v2.4.1-2 screenshot below can be compared with the one in an earlier post in this thread.

Call Groups Edit Menu in SAIL v2.4.1-2



Offline SARK devs

  • ****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Re: Inward hairpin to Outward
« Reply #7 on: December 07, 2009, 04:14:13 PM »
Yes - perhaps not a good choice.... 

However, the beauty of 2.4 is that you can change the heading if you don't like it - without compromising your sail install!...

Simply look up the heading in the tool-tip edit panel and change it to something more appropriate.

All done.. and it won't compromise future roll-outs.


Best

S

Offline apmuthu

  • *
  • 244
  • +0/-0
Re: Inward hairpin to Outward
« Reply #8 on: December 08, 2009, 01:28:24 AM »
Thanks for the Info.

Yes, in the Tool Tip Edit Menu, it is the groupstring element Name whose Legend can be changed from the default group to Call Group or something more representative of the form field to be filled in / displayed. This will result in the Source field being changed from Core to User.

The SAIL v2.4.1-2 screenshot after replacement is shown below:



Offline SARK devs

  • ****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Re: Inward hairpin to Outward
« Reply #9 on: December 08, 2009, 08:01:00 AM »
Correct - there are two ToolTip/Help databases, core, which is supplied as part of the release, and user which can be freely modified.  The message handler will always look first in the user database when a message is requested.


Kind Regards

S