Ticket #860 (closed Feature Requests: duplicate)

Opened 4 years ago

Last modified 1 year ago

Support InBound Routing of Calls by Channel ID as well as DID

Reported by: wardmundy Assigned to: p_lindheimer
Priority: minor Milestone: 2.6
Component: Core - Trunks/Routing Version:
Keywords: inbound incoming routing channel id Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

A number of providers (mostly low cost and free ones) don't support DID routing because they don't really advertise support for Asterisk. It would be extremely helpful to be able to route these incoming calls to various contexts or extensions based upon the channel ID. For example, here's the way we did way back in the AMP days:

[all-incoming] exten => s,1,NoOp?(Default incoming SIP call path activated for ${CHANNEL}) exten => s,2,GotoIf?($[${CHANNEL:0:14} = SIP/67812334567]?custom-broadvoice-in,6781234567,1) exten => s,3,GotoIf?($[${CHANNEL:0:12} = SIP/yourname]?custom-axvoice-in,8431234567,1) exten => s,4,GotoIf?($[${CHANNEL:0:8} = SIP/6234]?custom-stanaphone-in,3471234567,1) exten => s,5,GotoIf?($[${CHANNEL:0:17} = SIP/67.43.155.130]?custom-callpacket-in,7071234567,1) exten => s,6,GotoIf?($[${CHANNEL:0:14} = SIP/5151234567]?custom-freedigits-in,5151234567,1) exten => s,7,Goto(from-internal-custom,99,1)

Change History

05/28/06 06:30:28 changed by wozto1s

  • milestone set to 2.2.

07/08/06 01:24:12 changed by webrainstorm

At the moment you can do it specifying the wanted DID in the register string appending '/DID' to it

eg.: username:password@sip.provider.com/1234

Then create an inbound route for DID 1234

Should work for now

09/12/06 06:34:47 changed by RobThomas

  • milestone changed from 2.2 to 3.0.

Should I recycle the zaptel channel stuff into this? I'll probably remove the from-zaptel in 2.2 and go back to from-pstn (The idea with using a different context was is if it broke badly, it was easy enough to change back).

Moving to 3.0

11/13/07 13:56:57 changed by p_lindheimer

  • confirmation set to Confirmed.
  • component changed from Other Module to Core - Trunks/Routing.
  • engine_version changed.
  • svn_rev changed.
  • priority changed from major to minor.
  • version deleted.
  • milestone changed from 2.4 to 3.0.
  • owner set to p_lindheimer.

01/16/08 18:13:32 changed by WAudette

  • status changed from new to closed.
  • resolution set to fixed.
  • milestone changed from 3.0 to 2.4.

If I am not mistaken, this feature has been added in FreePBX v2.4.

Ward, please feel free to reopen this ticket if this is not what you were looking for...

Sincerely,

WAudette...

01/16/08 18:28:39 changed by WAudette

  • status changed from closed to reopened.
  • resolution deleted.
  • milestone changed from 2.4 to 3.0.

Note: I was mistaken in closing out this ticket per a conversation noted with Philippe

[18:43] <philippel> I added it explicitly for zap channels, not other channels [18:43] <philippel> he is asking effectively to do it based on trunk [18:44] <philippel> which is a good thing and when we redo trunks and routing stuff we can address

William...

07/15/08 17:19:25 changed by p_lindheimer

  • milestone changed from 2.5 to 3.0.

moving to 3.0 when we look at routing/trunks overhaul hopefully

08/25/09 19:22:40 changed by p_lindheimer

  • status changed from reopened to closed.
  • resolution set to duplicate.

There are some partial proposals in #3549 that need further development per the comments there so I am going to close this and defer it to #3549