Hello, > I'm not a astGUIclient user, but I'm puzzled by the following statement: > > mattf <[EMAIL PROTECTED]> wrote: > > > > In Asterisk v1.0.5 when you place an outbound phonecall(Zap, SIP, IAX2), > > once the call picks up, Asterisk will change the callerid to the number that > > you just dialed, no matter if you set a custom callerID for that call. > > What you've said there suggests that the CallerID is being set to the > DESTINATION number, which sounds to me not what CallerID should be at all. > CallerID normally indicates the source of a call.
Just wanted to say that Flash Operator Panel users will have the same problem. I'm puzzled too. IMHO there's something missing or wrong in the new callerid handling. If you trace the manager events and try to match the callerid via Uniqueid, you will notice that the only way to have a match is *after* the call is bridged. That means that you cannot find the callerid of a call before you pick up the phone. At least thats what I'm seing on Asterisk 1.0.5. (did not try with HEAD) So, the callerid is plain useless (Users expect to see the callerid before picking it up, dont't they?) It would be nice to have the callerid available on the manager when a phone is RINGING and before picking it up. I did not look at the Local channels, and it seems that it makes things harder.. but I still think that we do not have to code workarounds on manager based applications. We need to have an event in the manager informing the callerid of the caller in the RINGING event or associated directly with the Uniqueid of the callee. Personally I had to downgrade app_dial.c to a previous releaes to get the callerid as before. Just my 2 cents... -- Nicol�s Gudi�o Buenos Aires - Argentina _______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
