Re: how save information about traffic (tapi 2.1)

From: Grzegorz Grabski (grzegorz.grasbki_at_systell.pl)
Date: 01/04/05


Date: Tue, 4 Jan 2005 23:53:04 +0100

thx,

[CO means one of the few lines in trunk group (it is one B channel)

make CO call means make external call.] - sorry I didn't explain.

I monitor in TB2.0 outside line and two extension line.

> In the regard, how does your TSP model a station to station call?

station to station - one call is OUTBOUND other INTERNAL it's ok.

dwCallID is the same in 2 calls.

when I make outside call - one is EXTERNAL and another OUTBOUND;

dwCallID is the same in 2 calls -

until I make for example - TRANSFER.

After transfer external call to another extension the dwCall is changing.

Where is the problem??

I need all information about call path in my PBX. It's mean:

the call came from 1st trunk group and ring extension 101.

Extension 101 talk few minutes after transfer this call to extension 102,

extension 102 talks few minutes after transfer to extension 104, and 104 to
105.

when I look on Callinfo on extension 105 I have information about TrunGroup
and

that the call was transferred from 104 - rest information I lost.

All the time I have opened to monitor the Outside Line (CO) and all the
extension.

All open lines should be opened in monitor state. Because the owner is
client.

All information I save in database. After saved data I'm looking some best
key to look

on call and have all information.

Is any parameter which doesn't change, after operation witch I explain (fg.
transfer)???

I mean sth like dwCallID.

Best Regards

Pigeon

"Grant Schenck" <schenckg@optonline.net> wrote in message
news:%23vrmh3d8EHA.3616@TK2MSFTNGP11.phx.gbl...
> The answers are fairly TSP (TAPI Service Provider) specific.
>
> In the regard, how does your TSP model a station to station call? I
> assume in that case, you would see 2 calls, an outbound call on one
> TAPI station line and a second inbound on another TAPI station line
> representing the same third party call. I'd expect that the 2 calls
> would share the same LINECALLINFO's dwCallID values.
>
> Given that your TSP models CO lines as TAPI lines also, then I assume
> this would be analogous to the station to station case except that the
> inbound side might be the CO line or station line depending on which
> way the call was originated (outbound by the station user or inbound
> from the CO side.)
>
> Best I can suggest is to try these scenarios using the TAPI browser
> and with the appropriate lines open and see what events you get. Use
> the browser to display the LINECALLINFO of the various calls (double
> click on the call shown in the browser) to check the dwCallIDs of the
> various calls.
> --
> Grant Schenck
> Grant Schenck Software
> schenckg@optonline.net
> http://grantschenck.tripod.com
>
> "Grzegorz Grabski" <grzegorz.grasbki@systell.pl> wrote in message
> news:uLwtXmd8EHA.4072@TK2MSFTNGP10.phx.gbl...
>> hi,
>>
>>
>>
>> I'm working under CTI application (TAPI) - client site,
>>
>> and now I will start work on administrator project.
>>
>> I want have all information about traffic in my PBX, and
>>
>> I should decide how I can take it?
>>
>> I try with:
>>
>> Open all line to monitor (extension line and CO line) and know
>>
>> I have problem because I don't know witch call instant I should
> saved;
>>
>> call witch is under extension or call witch is crated under CO.
>>
>> Both call instate concern the same connection. Its mean if I make
> call from
>> my extension
>>
>> that my TSP create call under extension and under CO (it is fine)
> but
>>
>> should I save all information, or is another way to have all data
> about
>> calls witch
>>
>> was made under PBX (tapi version)?
>>
>>
>>
>>
>> Best Regards
>>
>> Pigeon
>>
>>
>
>



Relevant Pages

  • Re: how save information about traffic (tapi 2.1)
    ... The answers are fairly TSP (TAPI Service Provider) specific. ... how does your TSP model a station to station call? ... > call witch is under extension or call witch is crated under CO. ...
    (microsoft.public.win32.programmer.tapi)
  • Re: how save information about traffic (tapi 2.1)
    ... first i will try witch: ... > The answers are fairly TSP (TAPI Service Provider) specific. ... how does your TSP model a station to station call? ... >> call witch is under extension or call witch is crated under CO. ...
    (microsoft.public.win32.programmer.tapi)
  • Re: NEC NEAX 2000 SMDR format
    ... So I contacted NEC and get their SMDR ... the station number in the SMDR record not matching the actual extension ... a station number 110 in SMDR data is actually ... Your best bet is to talk with a switch technician about a specific ...
    (comp.dcom.telecom.tech)
  • NEC NEAX 2000 SMDR format
    ... So I contacted NEC and get their SMDR ... the station number in the SMDR record not matching the actual extension ... a station number 110 in SMDR data is actually ...
    (comp.dcom.telecom.tech)
  • Re: NEC NEAX 2000 SMDR format
    ... the station number in the SMDR record not matching the actual extension ... a station number 110 in SMDR data is actually ...
    (comp.dcom.telecom.tech)