Trust me, I don't WANT you to look at my code, it's butt-ugly! lol, lust
kidding... -- but at http://www.astsee.com/ you can download the source
code to my AstSee project -- it may provide some insight into what needs
to be (or CAN be) gleaned from asterisk. I struggled with all this a
year
Thanks all :)
Appreciate it.
On Feb 1, 2008 12:04 PM, Ex Vito <[EMAIL PROTECTED]> wrote:
> I've struggled with this recently. In short:
>
>
> - Observed behaviour is expected as of asterisk 1.2 and later,
> as previously described by Mojo
>
> - If you want to get the caller id for the c
I've struggled with this recently. In short:
- Observed behaviour is expected as of asterisk 1.2 and later,
as previously described by Mojo
- If you want to get the caller id for the channel calling (dialling)
into that channel for that specific Newstate: Ringing event, you
can
The snippet is asterisk telling you "I'm just letting you know that the
correct caller id for Channel: SIP/103-098500d8 is CallerID: 103"
This is absolutely correct, it's just not a piece of information you
expected to be receiving at that point.
You probably also received a packet like that wi
remove the brackets around
("Devraj Mukherjee" <101>)
Regards
Kev
Devraj Mukherjee wrote:
> Hi everyone,
>
> My manager interface seems to be producing wrong CallerIDs when
> internal extensions call each other. Can anyone see anything wrong in
> the configuration snippets pasted below? The foll
Hi everyone,
My manager interface seems to be producing wrong CallerIDs when
internal extensions call each other. Can anyone see anything wrong in
the configuration snippets pasted below? The following instance has
extension 101 call 103. The phone does show the right caller ID, but
notice that th
