atom feed4 messages in com.digium.lists.asterisk-dev[asterisk-dev] AMI originate - 2 call...
FromSent OnAttachments
Stephen ColesNov 24, 2008 7:03 am 
Jared SmithNov 24, 2008 7:20 am 
Sergey TamkovichNov 26, 2008 1:46 am 
Steve DaviesNov 26, 2008 2:14 am 
Subject:[asterisk-dev] AMI originate - 2 callerid (local and remote)
From:Sergey Tamkovich (se@voipsolutions.ru)
Date:Nov 26, 2008 1:46:25 am
List:com.digium.lists.asterisk-dev

Jared Smith wrote:

On Mon, 2008-11-24 at 15:04 +0000, Stephen Coles wrote:

In the originate command you can set callerID ? there should be 2 one for local and one for the remote side of the connection

Actually, the way it works is that the CallerID information you specify is sent to the "Channel" leg of the call, and that the other one can be specified in the dialplan using the CALLERID() dialplan function.

To take your earlier example:

Action: originate Channel: SIP/220 Exten: 321654 Priority: 1 Callerid: ?Computer Dial: Bob Smith? <321654>

You could simply put this in the dialplan:

exten => 321654,1,Set(CALLERID(name)=Steve) exten => 321654,n,Set(CALLERID(num)=01231453123) exten => 321654,n,Dial(SIP/some_provider/${EXTEN})

Does that make sense?

End how to make that usable (callable) by multiple users? Should we create different context for each caller? That is kinda inconvenient, isn't it?

May be the idea of having 2 callerids in the originate(callfiles) isn't that bad?

marklogic user conference