Re: [asterisk-users] CallerID shows wrong values in manager interface
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 or more ago and manged to get it to work fairly as expected. A problem you might notice is that I believe I mistakenly update my internal arrays before asterisk's manager interface has sent a complete packet... argh But you can see me dealing with NewState, NewExten, NewChannel, etc etc and what I do with them :) Moj Devraj Mukherjee wrote: > 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 channel calling (dialling) >> into that channel for that specific Newstate: Ringing event, you >> can use the 'o' flag to the Dial command; in this case you'll get >> old asterisk 1.0 behaviour -- do you really want to depend on >> such an old behaviour ? well I decided I didn't... >> >> - Otherwise, you'll need to track other events (IIRC, at least, Dial, >> AgentCalled, Newstate, etc) in the AMI so as to know who is calling >> who at a given instant >> >> - BEWARE: if memory serves me right (search the list archives in the >> Nov/Dec >> timeframe), the behaviour is not 100% homogeneous for different channel >> types SIP, ZAP, mISDN, IAX, etc. What this means for a simple Dial() from >> one channel to the other is that a) at times you get the Dial >> event first then the >> Newstate: Ringing event; and that b) with other/different >> orig/dest channel types >> you'll get the events in the reverse order... Nothing much but: i) >> you'll have to >> track them either way and ii) it reveals that the AMI events >> aren't 100% clean!!! >> >> :/ >> -- >> exvito >> >> >> On Feb 1, 2008 12:08 AM, Mojo with Horan & Company, LLC >> <[EMAIL PROTECTED]> wrote: >> >>> 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 with the following: >>> Channel: SIP/101- >>> CallerID: 101 >>> telling you, again, the caller id for only that channel. >>> >>> Moj >>> >>> >> ___ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >>http://lists.digium.com/mailman/listinfo/asterisk-users >> >> > > > > ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] CallerID shows wrong values in manager interface
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 channel calling (dialling) > into that channel for that specific Newstate: Ringing event, you > can use the 'o' flag to the Dial command; in this case you'll get > old asterisk 1.0 behaviour -- do you really want to depend on > such an old behaviour ? well I decided I didn't... > > - Otherwise, you'll need to track other events (IIRC, at least, Dial, > AgentCalled, Newstate, etc) in the AMI so as to know who is calling > who at a given instant > > - BEWARE: if memory serves me right (search the list archives in the Nov/Dec > timeframe), the behaviour is not 100% homogeneous for different channel > types SIP, ZAP, mISDN, IAX, etc. What this means for a simple Dial() from > one channel to the other is that a) at times you get the Dial > event first then the > Newstate: Ringing event; and that b) with other/different > orig/dest channel types > you'll get the events in the reverse order... Nothing much but: i) > you'll have to > track them either way and ii) it reveals that the AMI events > aren't 100% clean!!! > > :/ > -- > exvito > > > On Feb 1, 2008 12:08 AM, Mojo with Horan & Company, LLC > <[EMAIL PROTECTED]> wrote: > > 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 with the following: > > Channel: SIP/101- > > CallerID: 101 > > telling you, again, the caller id for only that channel. > > > > Moj > > > > > ___ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > -- "I never look back darling, it distracts from the now", Edna Mode (The Incredibles) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] CallerID shows wrong values in manager interface
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 use the 'o' flag to the Dial command; in this case you'll get old asterisk 1.0 behaviour -- do you really want to depend on such an old behaviour ? well I decided I didn't... - Otherwise, you'll need to track other events (IIRC, at least, Dial, AgentCalled, Newstate, etc) in the AMI so as to know who is calling who at a given instant - BEWARE: if memory serves me right (search the list archives in the Nov/Dec timeframe), the behaviour is not 100% homogeneous for different channel types SIP, ZAP, mISDN, IAX, etc. What this means for a simple Dial() from one channel to the other is that a) at times you get the Dial event first then the Newstate: Ringing event; and that b) with other/different orig/dest channel types you'll get the events in the reverse order... Nothing much but: i) you'll have to track them either way and ii) it reveals that the AMI events aren't 100% clean!!! :/ -- exvito On Feb 1, 2008 12:08 AM, Mojo with Horan & Company, LLC <[EMAIL PROTECTED]> wrote: > 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 with the following: > Channel: SIP/101- > CallerID: 101 > telling you, again, the caller id for only that channel. > > Moj > ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] CallerID shows wrong values in manager interface
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 with the following: Channel: SIP/101- CallerID: 101 telling you, again, the caller id for only that channel. Moj Devraj Mukherjee wrote: > CallerIDName: > State: Ringing > Event: Newstate > Privilege: call,all > Uniqueid: 1201748091.843 > Channel: SIP/103-098500d8 > CallerID: 103 > ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] CallerID shows wrong values in manager interface
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 following instance has
> extension 101 call 103. The phone does show the right caller ID, but
> notice that the manager interface has the CallerID as the target
> number (103).
>
> Thanks a lot for your time.
>
> Manager interface output:
>
> CallerIDName:
> State: Ringing
> Event: Newstate
> Privilege: call,all
> Uniqueid: 1201748091.843
> Channel: SIP/103-098500d8
> CallerID: 103
>
> SIP.conf snippets:
>
> [101]
> type=friend
> callerid=("Devraj Mukherjee" <101>)
> username=101
> secret=password
> context=default
> host=dynamic
> allow=alaw
> [EMAIL PROTECTED]
>
> [103]
> type=friend
> callerid=("System admin Den" <103>)
> username=103
> secret=password
> context=default
> host=dynamic
> allow=all
> [EMAIL PROTECTED]
>
> Extension.conf looks like:
>
> ; Standard POTS line configuration to pickup calls
> exten => _s,1,Wait(2)
> exten => _s,2,Queue(wagga-office-phones,90)
> exten => _s,3,VoiceMail([EMAIL PROTECTED])
> exten => _s,4,Hangup
>
> exten => 101,1,Wait(1)
> exten => 101,2,SetCIDNum(101)
> exten => 101,3,Dial(SIP/101,30,trw)
> exten => 101,4,Voicemail(s101)
> exten => 101,5,Hangup
>
> exten => 103,1,Wait(1)
> exten => 103,2,Dial(SIP/103,30,trw)
> exten => 103,3,Voicemail(s103)
> exten => 103,4,Hangup
>
>
>
--
This message has been scanned for viruses and
dangerous content by Mail Call antivirus software, and is
believed to be clean.
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] CallerID shows wrong values in manager interface
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 the manager interface has the CallerID as the target
number (103).
Thanks a lot for your time.
Manager interface output:
CallerIDName:
State: Ringing
Event: Newstate
Privilege: call,all
Uniqueid: 1201748091.843
Channel: SIP/103-098500d8
CallerID: 103
SIP.conf snippets:
[101]
type=friend
callerid=("Devraj Mukherjee" <101>)
username=101
secret=password
context=default
host=dynamic
allow=alaw
[EMAIL PROTECTED]
[103]
type=friend
callerid=("System admin Den" <103>)
username=103
secret=password
context=default
host=dynamic
allow=all
[EMAIL PROTECTED]
Extension.conf looks like:
; Standard POTS line configuration to pickup calls
exten => _s,1,Wait(2)
exten => _s,2,Queue(wagga-office-phones,90)
exten => _s,3,VoiceMail([EMAIL PROTECTED])
exten => _s,4,Hangup
exten => 101,1,Wait(1)
exten => 101,2,SetCIDNum(101)
exten => 101,3,Dial(SIP/101,30,trw)
exten => 101,4,Voicemail(s101)
exten => 101,5,Hangup
exten => 103,1,Wait(1)
exten => 103,2,Dial(SIP/103,30,trw)
exten => 103,3,Voicemail(s103)
exten => 103,4,Hangup
--
"I never look back darling, it distracts from the now", Edna Mode (The
Incredibles)
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
