Skip to main content

Routing 'Extension' from inbound trunk, and sending 'Internal Caller ID' on outbound trunk

Posted by amagurie on Fri, 04/04/2008

Hi,

We are currently testing thirdlane, we have it trunked to our legacy phone system via SIP. We have call routing setup between the two system, but have the following problems and was hoping someone can help us out:

1. When we call a extension on the legacy system from thirdlane (outbound route _2XX etc), Asterisk is sending 'External Caller ID Number' instead of 'Internal Caller ID', in freePBX they have an option available in there outbound route configuration called 'Intra Company Route' which preserves internal caller ID.

I could update (or create new) script 'tl-dialout-1-trunk', to include a similar option. Is this best option? and if so, is there anyway to get these included into future version as to not have to worry about updates or fixes that get released.

2. When we call a extension on the thirdlane system from the legacy system using extension, we have to create a inbound route for each extension inorder for the call to go through. Is this the only way to set it up?

Any help is much appreciated.

Thanks
Allister


Submitted by eeman on Sat, 04/05/2008 Permalink

[bgnv-extension-outbound]

use=feature

friendlyname=Dial Out (1 trunk)

description

This script handles dialing using 1 trunk to redial an extension as an outbound number while preserving internal callerid. This would be useful when calling another branch PBX where you want the internal extension numbers to remain the callerid. example:

<br> taking calls to 6XX redials on an outbound trunk as +150231525XX

<br> making a speed dial, like *23 strip all 3 digits and dial +15025551212

args=1,How long to ring,text:2,Trunk,trunk:3,String to prepend,text:4,Number of digits to strip,text:5,Dial command options,text

body

exten => s,1,Dial(${ARG2}/${ARG3}${MACRO_EXTEN:${ARG4}},${ARG1},${ARG5})

I made a feature code instead of outbound route to match my pattern and just ran the script that way, accessing the trunk directly.

another option would consist of using a switch => and dundi for sending intra-office calls.

as for your second question you could change the context to from-inside instead of from-outside