[asterisk-users] CID NAME NOT FOUND
Richard Mudgett
rmudgett at digium.com
Tue Oct 8 15:56:57 CDT 2013
On Tue, Oct 8, 2013 at 1:50 PM, Doug Lytle <support at drdos.info> wrote:
> >> You might want to look at this link for some hints about what may be
> going on:
> >>
> https://wiki.asterisk.org/wiki/display/AST/Manipulating+Party+ID+Information
>
> I've been pouring over that document for hours and am not really getting
> any further then I had.
>
> I guess I need to explain my situation a little more.
>
> I'm currently using CID as a means of directing and identifying station to
> station calls between facilities. We have agreements with our carries that
> allow me to set CID to whatever I choose.
>
> So, to allow our users to make seamless calls between facilities using the
> PSNT, with minimal wait times, I use callerid.
>
> Format is:
>
> [accesscode] [destination extension] [source extension]
>
> The access code is 2 digits, destination is 4 and source is 4.
>
> Asterisk then breaks out the original CID, changes it to the employee's
> name, extension and then send it to the destination extension.
>
> Reading the wiki documents really give me reasons why callerid reverts
> back to what was on the channel originally. Other then it says:
>
>
> - Caller ID: The Caller ID information describes who is originating a
> call.
> - Connected Line ID: The Connected Line ID information describes who
> is connected to the other end of a call while a call is established.
>
> But I see no way of updating an answered call using CONNECTEDLINE.
>
Normal dialplan does not execute while a call is connected. That is what
the interception macro/routines are for. That is where you use
CONNECTEDLINE to manipulate the connected line party information as it is
passing through Asterisk. You can also block the connected line update
when the call initially connects using the Dial 'I' option.
Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20131008/6ce63969/attachment.html>
More information about the asterisk-users
mailing list