Default External Caller ID

make sure callerid= is not set on the sip trunk. that will overwrite inbound calls on that channel driver.

Erik,

I have a little more info from the client.

It only happens when a certain DID is the inbound route, other clients with DIDs on the same trunk provider are not having this issue. Its route is:

DID to hunt list.
Hunt list to 2 extensions.
'Other numbers to dial', set to cell phone number.

The problem is only showing up on the forward to cellphone portion of the call.

?????

thanks

its working as designed then.. that 'forwarded' call is an outbound call and therefore outbound dialing rules apply. the call is being placed to Local/1234567890@from-inside-tenant just as if some handset placed the call, except that in this case there is no handset with a bunch of ASTDB options to check to see how to handle the call (ie what your external callerid is, if you have VM, do youwant a FM/FM etc). So it then assigns the default tenant callerid to the call. Direct extension options work entirely different, the source channel is something like SIP/102-tenantc. The dialplan looks up /TL/tenantc/102/forward to see if forwarding is set, another DB key to see if preserve original callerid is set, another key to see if the tenant is allowed to overide callerid etc etc. In this case the source channel is SIP/yourcarrier, so there isnt going to be an extension with a bunch of options in ASTDB for the tl-dialout-base script to use.

theres really no fix for this, because in order to call the cell phone in the first place a completely 2nd call is being routed to the cellphone and then bridged back to the original call.

originalcall -> dial (local/tn) -> dial (sip/carrier/tn)

about the only workaround you have, and its kinda ugly, is to make a new outbound route... something like

_81NXXNXXXXXX that uses the dialout-passthru script.. then alter the 'other number to dial' the number adding the extra #'s in front that you set for your pattern (8 in this case but it could be anything)

If the outbound call is originating from the huntlist, you should be able to add o to the dial command options and give the tenant permission to override callerid.

chris have you tested that? tl-dialout-base seems to assign tenant level callerid first which would overwrite anything on the chan_local channel

It appears you are correct and this doesn't work. Would this have worked at some time in the past? I have a few tenants set up in this manner and I could have sworn this was working when I set it up. Nobody complained so I assumed it was still working properly.