Call external numbers from my Special Line

why did you not set the default callerid of the tenant?

your from header is empty, your remote party id header is empty.

no callerid = no call in most systems.

Hello Erik,

You are correct as always :)

New stupid question, how do i get the callerid to be dynamic? I dont want to use the same outgoing number for all users that have a special line.

why are they special lines instead of extensions? The information that specifies that you can override the default callerid is done in the ASTDB and is set for user extensions hence why it asks you all of that information.

a Special line that did all of that would be called ... wait for it... a user extension.

Special lines are perfect for ATA's that provide dialtone to a fax machine or maybe the front lobby phone.

I have a extension with a linksys registered to it and i wanted to test a x-lite from my computer. Thats why i was trying the special lines.

it might just be easier for you to make another user extension.. dont give it vm, change the internal callerid to the original user extension, and set the external callerid to whatever you want...

then go back to userextension-A and change its script to tl-multidevice-exten

special lines are great but extenuating specific needs are what the user extension was created for.

Hello,

Did as you said and it works perfectly. Thank you for the help.

Digging up an old post. Looking at the special lines, the setup contains a field for caller ID and callerid name, but it seems that no matter what we set in these, the default for the tenant is used. (The tenant is allowed to set their own callerid). Anyone have any ideas how to make these work.

We are using special lines for softphones that users twin to their multi-device extension .

I will check, but i thinks that setting caller id on special lines is not supported and we should just remove it from the UI to avoid confusion

Doug,

This may be an asterisk thing combined with the softphone and the way is delivers data...

Try setting trustrpid=no in the special line options with the other settings you mentioned.

Doug. PLEASE STOP RESURRECTING 10 year old posts! Please just make a new post. The answers from 10 years ago and 100% NOT relevant to anything in production now. An overwhelming number of those posts are posts that I had replied to and its making it difficult for me to stay on the forums with notifications about remarks 10yrs ago.

Alex, DO NOT REMOVE the callerid fields from special lines. Otherwise the call made from the special line to an internal device will have NO CallerID.

Doug, the purpose of the Callerid fields in special lines is to populate the entry in sip.conf and has nothing to do with dialplan. Special Lines are a mechanism to make sip.conf entries _exclusively_ as opposed to 'user extensions' that make multiple entries into multiple systems like extensions.conf, sip.conf, voicemail.conf, etc etc.

special Lines = sip.conf entries
special mailboxes = voicemail.conf entries
feature codes = extensions.conf entries

if extension 520 needs a second phone to ring when you dial 520, then the proper way to to this is by using Special Lines.

single-tenant example
1. create a special line 520a (SIP/520a)
2. set callerid of 520a to 520 and the name of the person
3. go into User Extensions for 520 and change the script to tl-multidev-exten
4. select 520a as the other device to ring

when 520a calls someone internally the callerid will correctly show 520 so that the recipient can return the call. There is no way to return a call to 520a as there is no dialplan for 520a nor is 520a capable of being dialed from a telephone.

If you need to use special lines for a different device AND that device needs to have a PSTN callerid number for outbound calling then you will have to create a new outbound route using the '-passthrough' scripts. Your callerid IS being set to what you told it to, however regular dial-trunk scripts also determine the extension settings based on the Channel ID of the sip channel. There is no table of data specific to 520a. Special Lines do not get these settings, thats what User Extensions are for. Special Lines are only for having a GUI to put manual entries into sip.conf for ancillary devices, not an end-run around thirdlane licensing, which would likely happen if they were given all the same tools as a user extension. A door intercom, panic button, ATA, Paging amplifier, etc, is primarily the purpose of special lines. They also work great as a second phone on an extension, hence why you need to set the callerid.

This leaves you 3 choices

1. deal with default callerid
2. special code the device to always prepent some digit(s) to whatever is dialed and modify outbound routes to use passthrough for that pattern
3. use a User Extension for this device instead of a special line.

99.999% of the time option 1 is perfectly acceptable to someone needing a second device for their phone. For the 0.001% with that PITA special request, they'll just have to eat the cost of another licensed seat to do that.
Option 2 is a no-cost alternative but is a terrible solution if you also need to make internal calls because the recipient is going to see the PSTN number, not the inside extension.