search for: linkedid

Hi asterisk-users, We have recently moved to the 13.x branch of Asterisk from 11.x, and we're trying to correlate CDR records from multiple-legs for billing purposes. As part of this change we have added 'linkedid' to our CDR table schema in an attempt to join the multiple records into one billable record. The call path can be simplified as (transport types in brackets): SIP Phone---(SIP)---Asterisk Svr1---(IAX)---Asterisk Svr2---(IAX)---Asterisk Svr3---(SIP)---PSTN As per the CDR spec, I expected the...

An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20130630/18883d29/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: 1371568201.486360-80.csv.zip Type: application/zip Size: 1674 bytes Desc: not available URL:

...ower <Calum.Power at aad.gov.au<mailto:Calum.Power at aad.gov.au>> wrote: Hi asterisk-users, We have recently moved to the 13.x branch of Asterisk from 11.x, and we're trying to correlate CDR records from multiple-legs for billing purposes. As part of this change we have added 'linkedid' to our CDR table schema in an attempt to join the multiple records into one billable record. The call path can be simplified as (transport types in brackets): SIP Phone---(SIP)---Asterisk Svr1---(IAX)---Asterisk Svr2---(IAX)---Asterisk Svr3---(SIP)---PSTN As per the CDR spec, I expected the...

...they are structured, and what they express. If you have ANYTHING to do with CDRs, then it is critical you become involved in the design process for the new system! Or suffer with the results! What's going on? I wrote up two modes of CDR generation: Leg-Based, and Simple. A new field, "linkedID", that can be used to link CDRs as part of the same total call. Leg-Based is (or can be) very detailed. Every CDR has a type, like CALL, AXFER, BXFER, PARK, etc. Depending on what actions occur during a call, a call can be split up into several "legs". A dialplan func to insert an e...

...C, A is still paying A => B > Good Question: Can Simple CDRs be used in xfer situations? Let's take a look. In this particular situation, 3 channels are involved: A, B, and C. Therefore, you will get 3 CDRs. CDR1: A -> B start: e1a ans: e2 end: e4 Party: B disp: ANSW linkedID: abc9 CDR2: A start: e1 ans: e1 end: e6 Party: A disp: ANSW linkedID: abc9 CDR3: B -> C start: e4 ans: e5 end: e6 Party: C disp: ANSW linkedid: abc9 CDR2 covers A (see the Party field), CDR1 covers B, CDR3 covers C. A's CDR could be used to bill A for his ca...

...ivilege: call,all Channel: SIP/192.168.40.105-000000c5 ChannelState: 6 ChannelStateDesc: Up CallerIDNum: 1234 CallerIDName: <unknown> ConnectedLineNum: <unknown> ConnectedLineName: <unknown> Language: en AccountCode: 11 Context: ABC Exten: 3002 Priority: 8 Uniqueid: 1521724388.197 Linkedid: 1521724388.197 Extension: 3002 Application: AGI AppData: agi:async [03/22 08:13:32.220] DEBUG[1228] manager.c: Examining AMI event: Event: AsyncAGIStart Privilege: agi,all Channel: SIP/192.168.40.105-000000c5 ChannelState: 6 ChannelStateDesc: Up CallerIDNum: 1234 CallerIDName: <unknown> Con...

...://lists.digium.com/pipermail/asterisk-users/attachments/20140507/fa128a47/attachment.html> -------------- next part -------------- server*CLI> core show channel PJSIP/7000-00000001 -- General -- Name: PJSIP/7000-00000001 Type: PJSIP UniqueID: 1399382022.1 LinkedID: 1399382022.0 Caller ID: 7000 Caller ID Name: (N/A) Connected Line ID: 7001 Connected Line ID Name: 7001 Eff. Connected Line ID: 7001 Eff. Connected Line ID Name: 7001 DNID Digits: (N/A) Language: de State: Up (6) NativeFormats: (alaw) WriteFormat: g722 ReadFo...

...tion(Data) SIP/1064-00000044 (None) Up Playback(demo-congrats) 1 active channel 0 active calls 86 calls processed elx2*CLI> core show channel SIP/1064-00000044 -- General -- Name: SIP/1064-00000044 Type: SIP UniqueID: 1329515589.179 LinkedID: 1329515589.179 Caller ID: 1064 Caller ID Name: device Connected Line ID: (N/A) Connected Line ID Name: (N/A) DNID Digits: (N/A) Language: en State: Up (6) Rings: 0 NativeFormats: 0x3c0002 (gsm|h261|h263|h263p|h264) WriteFormat: 0x2 (gsm) Re...

...<5edb1920-3774-4ba3-8c4d-23e8fd04519c> I'd expect those channel to immediately go away, but they just stay around: asterisk*CLI> core show channel CBAnn/207-0000067f;1 -- General -- Name: CBAnn/207-0000067f;1 Type: CBAnn UniqueID: 1398809161.20186 LinkedID: 1398809161.20186 Caller ID: (N/A) Caller ID Name: (N/A) Connected Line ID: (N/A) Connected Line ID Name: (N/A) Eff. Connected Line ID: (N/A) Eff. Connected Line ID Name: (N/A) DNID Digits: (N/A) Language: en State: Up (6) NativeFormats: (nothing) WriteFormat: unkn...

...keep getting this error: [Feb 9 16:21:43] WARNING[2088]: cdr_odbc.c:160 execute_cb: cdr_odbc: Error in ExecDirect: -1, query is: INSERT INTO cdr (calldate,clid,src,dst,dcontext,channel,dstchannel,lastapp,lastdata,duration,billsec,disposition,amaflags,accountcode,uniqueid,userfield,peeraccount,linkedid,sequence) VALUES ({ts '2016-02-09 16:21:28'},?,?,?,?,?,?,?,?,?,?,?,?,?,?,? ,?,?,?) [Feb 9 16:21:43] WARNING[2088]: res_odbc.c:612 ast_odbc_direct_execute: SQL Execute error! Verifying connection to asterisk [asterisk]... [Feb 9 16:21:43] WARNING[2088]: cdr_odbc.c:160 execute_cb: cdr_odb...

I'm having an issue with CDR. Basically, I expect to have all "legs" of a call having the same linkedid and differing only by the sequence value. That does happen, but I'm getting null dst values after doing an attended transfer. I'm not sure if this is a bug or I'm doing something wrong. I'm running Asterisk 13.2.0. Here's the console log, step by step: First, I receive a call...

...nnel: Local/1000 at mycontext-0000000b;1 ChannelState: 0 ChannelStateDesc: Down CallerIDNum: <unknown> CallerIDName: <unknown> ConnectedLineNum: <unknown> ConnectedLineName: <unknown> Language: en AccountCode: Context: mycontext Exten: 1000 Priority: 1 Uniqueid: mycallerid.1 Linkedid: mycallerid.1 Event: Newchannel Privilege: call,all Channel: Local/1000 at mycontext-0000000b;2 ChannelState: 4 ChannelStateDesc: Ring CallerIDNum: <unknown> CallerIDName: <unknown> ConnectedLineNum: <unknown> ConnectedLineName: <unknown> Language: en AccountCode: Context:...

...ivilege: agi,all Channel: SIP/192.168.40.105-00001338 ChannelState: 6 ChannelStateDesc: Up CallerIDNum: 1234 CallerIDName: <unknown> ConnectedLineNum: <unknown> ConnectedLineName: <unknown> Language: en AccountCode: 11 Context: ABC Exten: 3002 Priority: 8 Uniqueid: 1521665055.4920 Linkedid: 1521665055.4920 Result: %F7%EF%F0%F4z%7C%EE%EF%F6%FCkWDDLO%5Cm%EF%7B__%60h%FE%E0%D4%D5%D9%DA%DD%E2%E8%E1%DC%DE%E0%F3%EC%EF%7C%ED%ED%EC%FAx~oov%F9%F2%F6%EB%ED%FA%FD%F9%FEvjXGFMKWg%FF%7Cdidew%E8%D9%D9%D8%D6%DA%DF%E3%E3%E2%E5%E9%EA%E1%E6%EF%E9%F8%F8%F6%FD%F8%7C~%7D%FC%F9%F7%ED%F4%F6%F9oh%60JFMKP%5Do%...

...annels during its lifetime, these fields might be useless. I could set them to the successful first target of a dial attempt... and leave them blank otherwise? If you really need/care about these fields, then maybe this mode is not proper for you. You can use linkedid to find all the other channels that may have conversed with this one. disposition --- See above discussion. dst dstchannel --- Since a channel could be connected to several other channels during its lifetime, these fields might be useless. I could set them...

Dear list. This is probably a complex subject but is that right to consider: a) each distinct linkedid field value in a mysql CEL table as a unique call? b) the duration of a call as the period (eventtime fields) between BRIDGE_END and BRIDGE_START events of the same linkedid sequence? (not considering transfers) Just a start ... Tks. -------------- next part -------------- An HTML attachment was...

Hi, when one does "Set(CDR(var)=value)" in dialplan, the value is only set for one record in the cdr table, but not the linked ones (the ones with the same linkedid). E.g. if you do something like same => n, Set(CDR(var)=value) same => n,Dial(Local/something&Local/something2) like only the original CDR record with have "var" set to "value", but the ones created from "Dial" won't. Is it possible to set the C...

...elp! :) Lastly, a "core show channel" on a hanging call, obfuscated: [root at voip asterisk]# asterisk -rx 'core show channel SIP/customer01-0000dfa4' -- General -- Name: SIP/customer01-0000dfa4 Type: SIP UniqueID: voip-1683277216.81923 LinkedID: voip-1683277216.81923 Caller ID: 49xxxxxxxxxx Caller ID Name: (N/A) Connected Line ID: (N/A) Connected Line ID Name: (N/A) Eff. Connected Line ID: (N/A) Eff. Connected Line ID Name: (N/A) DNID Digits: 49xxxxxxxxx Language: en State: Ring (4) NativeFormats: (alaw...

...-----+---------+----------+--------+ | calldate | clid | src | dst | dcontext | channel | dstchannel | lastapp | lastdata | duration | billsec | disposition | amaflags | accountcode | userfield | uniqueid | linkedid | sequence | peeraccount | phoneno | callerid | userid | +---------------------+------+-----+-------+---------------------+---------------------------------------------------+-------------------+---------+--------------------------+----------+---------+-------------+----------+-------------+---...

I've taken the liberty of starting a new thread to discuss the design of the Asterisk CDR mechanism. The discussion has been kindly initiated by murf putting together a proposal: http://svn.digium.com/svn/asterisk/team/murf/RFCs. After reading the proposal I still don't think it's the right way to go. To my mind adding more channel variables increases the complexity in a situation

...nhancements. Also, keep in mind, that we have a new facility being groomed for merging into trunk: http://svn.digium.com/svn/asterisk/team/group/newcdr which will introduce some new concepts that will help in forming billing records; it is single-event based, and introduces a new channel value, linkedid, which is spread between channels that 'interact', thus allowing you to more easily collect events that are related via transfers, conferences, parking, holding, etc. So, please, please, please, test these branches against your implementations, and report any problems you see, so we can so...