[cisco-voip] CCM 5, need to find out who called 911

[Lelio Fulgenzi]

wget? i believe it supports transmitting userid/password combo.

if the URL is arg/parameter based and not cgi post with no URL info then it 
should theoretically possibly might work. ;)

----- Original Message ----- 
From: "Voll, Scott" <Scott.Voll at wesd.org>
To: "Pete Fabian" <pfabian at telesphere.com>; "Jonathan Charles" 
<jonvoip at gmail.com>
Cc: "cisco-voip at puck-nether.net" <cisco-voip at puck.nether.net>
Sent: Thursday, July 19, 2007 11:53 AM
Subject: Re: [cisco-voip] CCM 5, need to find out who called 911


> It is nice in 4.x to have access to the DB so you can automate the
> process and send emails based on someone calling 911.  since you don't
> have direct db access this is a more manual process unless someone has a
> better option.
>
> scott
>
> -----Original Message-----
> From: Pete Fabian [mailto:pfabian at telesphere.com]
> Sent: Thursday, July 19, 2007 8:51 AM
> To: 'Jonathan Charles'; Voll, Scott
> Cc: 'cisco-voip at puck-nether.net'
> Subject: RE: [cisco-voip] CCM 5, need to find out who called 911
>
> I have always gone into car > CDR > Search > By User/Extension and
> search
> for 911 and 9911
>
> This has always worked reliably for me on 4.x and 5.x
>
>
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jonathan
> Charles
> Sent: Thursday, July 19, 2007 8:39 AM
> To: Voll, Scott
> Cc: cisco-voip at puck-nether.net
> Subject: Re: [cisco-voip] CCM 5, need to find out who called 911
>
> OK, I got data from a live system...
>
> This works.
>
> Basically, you get a txt file (change it to a CSV and open it with
> Excel), the finalCalledParty is there... just a matter of searching
> for 911 and then scrolling over to callingPartyNumber
>
> I found the evil-doer
>
>
> Jonathan
>
> On 7/19/07, Jonathan Charles <jonvoip at gmail.com> wrote:
>> OK, making some progress here...
>>
>> I went into CAR, and if you go to Go to CDR - Export CDR/CMR and
>> export the data for the day in question, you get a TXT file with the
>> following headers:
>>
>> There are a lot:
>>
>>
> cdrRecordType,globalCallID_callManagerId,globalCallID_callId,origLegCall
> Iden
> tifier,dateTimeOrigination,origNodeId,origSpan,origIpAddr,callingPartyNu
> mber
> ,callingPartyUnicodeLoginUserID,origCause_location,origCause_value,origP
> rece
> denceLevel,origMediaTransportAddress_IP,origMediaTransportAddress_Port,o
> rigM
> ediaCap_payloadCapability,origMediaCap_maxFramesPerPacket,origMediaCap_g
> 723B
> itRate,origVideoCap_Codec,origVideoCap_Bandwidth,origVideoCap_Resolution
> ,ori
> gVideoTransportAddress_IP,origVideoTransportAddress_Port,destLegIdentifi
> er,d
> estNodeId,destSpan,destIpAddr,originalCalledPartyNumber,finalCalledParty
> Numb
> er,finalCalledPartyUnicodeLoginUserID,destCause_location,destCause_value
> ,des
> tPrecedenceLevel,destMediaTransportAddress_IP,destMediaTransportAddress_
> Port
> ,destMediaCap_payloadCapability,destMediaCap_maxFramesPerPacket,destMedi
> aCap
> _g723BitRate,destVideoCap_Codec,destVideoCap_Bandwidth,destVideoCap_Reso
> luti
> on,destVideoTransportAddress_IP,destVideoTransportAddress_Port,dateTimeC
> onne
> ct,dateTimeDisconnect,lastRedirectDn,pkid,originalCalledPartyNumberParti
> tion
> ,callingPartyNumberPartition,finalCalledPartyNumberPartition,lastRedirec
> tDnP
> artition,duration,origDeviceName,destDeviceName,origCallTerminationOnBeh
> alfO
> f,destCallTerminationOnBehalfOf,origCalledPartyRedirectOnBehalfOf,lastRe
> dire
> ctRedirectOnBehalfOf,origCalledPartyRedirectReason,lastRedirectRedirectR
> easo
> n,destConversationId,globalCallId_ClusterID,joinOnBehalfOf,comment,authC
> odeD
> escription,authorizationLevel,clientMatterCode
>>
>> The box I ran it on is a test box with no call detail... I have the
>> cust sending me the data for that day...
>>
>> I will tell you what I find (it looks like a simple CSV, so this may
>> not be that bad...
>>
>>
>>
>> Jonathan
>>
>>
>> On 7/19/07, Jonathan Charles <jonvoip at gmail.com> wrote:
>> > I think we are screwed:
>> >
>> > admin:
>> > admin:run sql select callingPartyNumber from CallDetailRecord
>> > The specified table (calldetailrecord) is not in the database.
>> > admin:
>> >
>> >
>> > If there is no CDR table.... then again, I am probably running this
> on
>> > the wrong DB...
>> >
>> >
>> > Jonathan
>> >
>> > On 7/19/07, Jonathan Charles <jonvoip at gmail.com> wrote:
>> > > I have a sample query:
>> > >
>> > > run sql select name,nodeid from ProcessNode
>> > >
>> > > I figure, maybe the tables didn't change and I can modify my sql
> 2000
> query...
>> > >
>> > >
>> > >
>> > > Jonathan
>> > >
>> > > On 7/19/07, Voll, Scott <Scott.Voll at wesd.org> wrote:
>> > > > Soon as you find out..... let me know ;-)
>> > > >
>> > > > Scott
>> > > >
>> > > > -----Original Message-----
>> > > > From: cisco-voip-bounces at puck.nether.net
>> > > > [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of
> Jonathan
>> > > > Charles
>> > > > Sent: Thursday, July 19, 2007 7:54 AM
>> > > > To: cisco-voip at puck-nether.net
>> > > > Subject: [cisco-voip] CCM 5, need to find out who called 911
>> > > >
>> > > > So, since they took away all of our SQL queries when they went
> to
>> > > > Linux, it doesn't change the fact that we still need to know who
>> > > > called 911.
>> > > >
>> > > > So, how do we do it?
>> > > >
>> > > > I have posted this request before, and it has been ignored... I
> am
>> > > > debating on opening a TAC case to find out how...
>> > > >
>> > > >
>> > > >
>> > > > Jonathan
>> > > > _______________________________________________
>> > > > cisco-voip mailing list
>> > > > cisco-voip at puck.nether.net
>> > > > https://puck.nether.net/mailman/listinfo/cisco-voip
>> > > >
>> > >
>> >
>>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>