| 05:02.06 | *** join/#asterisk-doc brac (i=fugalh@falcon.fugal.net) |
| 05:28.15 | *** join/#asterisk-doc brac (i=fugalh@falcon.fugal.net) |
| 08:15.25 | *** join/#asterisk-doc jbot (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 08:15.25 | *** topic/#asterisk-doc is Welcome to the Asterisk Documentation Project / Idle Chat, a subsidiary of telcomjoshleifvoxmartenterprisesinc --=-- Asterisk: The Future of Telephony: ISBN13: 9780596514051 --==-- 2nd Edition of TFoT now shipping! --> http://tinyurl.com/382dz2 --==-- blitzrage: at the rate I'm (not) thinkin' this morning, I'm afraid to do any work |
| 12:38.08 | *** join/#asterisk-doc snuff-home (n=snuffy@220-253-3-74.VIC.netspace.net.au) |
| 14:20.08 | *** join/#asterisk-doc benji_ (n=benji@100.Red-88-15-181.dynamicIP.rima-tde.net) |
| 14:52.10 | file | hail jsmith |
| 14:52.28 | jsmith | Oh c'mon, I ain't worth all that |
| 14:52.55 | jsmith | Ah, that's better! |
| 14:55.52 | ctooley | mornin |
| 16:05.33 | Juggie | lmadsen! |
| 16:06.08 | lmadsen | Juggie! |
| 16:09.17 | Juggie | whats up |
| 16:09.26 | lmadsen | just on a conference call |
| 16:09.33 | Juggie | sounds 'exciting' |
| 16:09.49 | lmadsen | oh ya... super |
| 16:09.51 | lmadsen | you? |
| 16:09.59 | Juggie | working on some php code. |
| 16:10.18 | Juggie | trying to ignore the loud talkers in my office |
| 16:10.20 | lmadsen | sounds 'exciting' |
| 16:10.30 | lmadsen | you need some good headphones |
| 16:11.06 | Juggie | i do |
| 16:11.19 | Juggie | i'm going to make my boss buy me a pair of noise canceling ones soon |
| 16:11.27 | Juggie | our 1-800 'control room' is next to me |
| 16:11.31 | Juggie | and there is allways 3-4 people in there |
| 16:11.34 | Juggie | and its loud |
| 16:12.02 | lmadsen | oh ya, you totally should |
| 16:12.19 | Juggie | ya he's in a meeting now |
| 16:12.21 | lmadsen | get those bose headphones that you don't even need to listen to music -- it just cancels the noise around you |
| 16:12.34 | lmadsen | (but you can use them to play music to) |
| 16:12.35 | Juggie | but this is the 2nd time in 3 days i've had to complain about the noise level |
| 16:12.36 | lmadsen | too* |
| 16:12.41 | Juggie | they are supposed to keep the door closed |
| 16:12.42 | Juggie | and they dont. |
| 16:12.58 | lmadsen | put up a sign :) |
| 16:13.12 | Juggie | well the control room used to be in the lab |
| 16:13.15 | lmadsen | "Keep this door closed or Juggie will not be happy" |
| 16:13.17 | Juggie | where they could be as loud as they wanted |
| 16:13.20 | Juggie | but now its not |
| 16:14.15 | Juggie | to be honest i dont know what these people actually do. |
| 18:01.19 | ctooley | Is there a way to distinguish the difference between CallerID blocked via Privacy and CallerID not available with a zap channel? |
| 18:25.20 | jsmith | ctooley: On a PRI? |
| 18:25.24 | *** join/#asterisk-doc eharris (n=eharris@cpe-66-25-189-206.austin.res.rr.com) |
| 18:26.57 | eharris | When using an analog TDM trunk card, is there any way to find out from * which of "private" or "unavailable" or "not received" is the reason for no callerid info? |
| 18:32.44 | Juggie | ctooley, on a pri yes |
| 18:32.48 | Juggie | there is a flag for it |
| 18:35.07 | jsmith | eharris: Not on an analog line, I don't think so. |
| 18:35.24 | Juggie | ${CALLINGPRES}: PRI Call ID Presentation variable for incoming calls (See callingpres) |
| 18:42.56 | eharris | Juggie: That's for PRI's. I need the equivalent for analog TDM. |
| 18:43.48 | eharris | I already tried using ${CALLINGPRES} in the hopes that the presentation bits were populated for analog, but it is always zero. |
| 18:58.10 | jsmith | eharris: Those bits only exist for PRI |
| 18:58.22 | jsmith | eharris: Like I said earlier, I don't think so for analog |
| 19:07.27 | eharris | wow, that sucks. Maybe I'll take a shot at hacking the code. |
| 19:10.41 | file | it doesn't seem like something that would be... telco would just send down different cidname/no number... |
| 19:40.06 | Juggie | i dont think the presentation bit is part of the CID |
| 19:58.09 | eharris | file: I know for a fact it is. There is a status byte that provides PRIVATE or UNAVAILABLE. And in any case, asterisk should know if it wasn't received at all. |
| 20:00.51 | ctooley | eharris, that doesn't mean that your telco provides your line with that status byte. It would most likely just either send or not send the caller-id. |
| 20:01.36 | ctooley | The caller-id that phones (and those silly caller-id boxes) use just take the lack of caller-id data as "Private" according to the things I'm reading on the internet. |
| 20:02.22 | ctooley | It would also depend on your line. I do remember that Austin Telco (the old service that SBC bought) was notoriously bad at following "standards" |
| 20:09.17 | eharris | ctooley: the status byte is a required message, and it is definitely provided. That is why any phone or CID display device can tell you "UNAVAILABLE" or "PRIVATE", or the spanish equivalents. That info isn't sent as the actual name, it is provided in the status byte. |
| 20:13.14 | eharris | actually, it is provided by any equipment that provides the standard Multiple Data Message Format (MDMF) format, which includes the calling name. The older SMDF format doesn't provide name or Private/Unavail, but almost no devices use it because they want name. |
| 20:19.07 | eharris | ctooley: here's a reference. The MDMF "number not present" type ID is 0x04, the "name not present" type is "0x08". Unavailable or Private is distinguished by a "P" or "O" in the data types for field types 0x04 and 0x08. |
| 20:19.19 | eharris | ctooley: http://www.microengineeringlabs.com/resources/callerid.htm |
| 20:22.03 | Juggie | we await your patch :) |
| 20:22.49 | eharris | I know that it provides the info because I built my own callerid to serial adapters so I could capture callerid before modems supporting that were available. |
| 20:27.04 | eharris | had to write the code to decode the MDMF packets. |
| 20:27.21 | Juggie | eharris, did you look @ callerid.c? |
| 20:27.39 | eharris | not yet, was just unpacking the source now. |
| 20:27.56 | Juggie | should be an easy fix |
| 20:28.13 | Juggie | the states are there, just no code to set the callerpres |
| 20:28.35 | Juggie | 00630 case 2: /* Number */ |
| 20:28.35 | Juggie | 00631 case 3: /* Number (for Zebble) */ |
| 20:28.35 | Juggie | 00632 case 4: /* Number */ |
| 20:28.35 | Juggie | 00633 res = cid->rawdata[x]; |
| 20:28.35 | Juggie | 00634 if (res > 32) { |
| 20:28.35 | Juggie | 00635 ast_log(LOG_NOTICE, "Truncating long caller ID number from %d bytes to 32\n", cid->rawdata[x]); |
| 20:28.38 | Juggie | 00636 res = 32; |
| 20:28.40 | Juggie | 00637 } |
| 20:28.42 | Juggie | 00638 if (ast_strlen_zero(cid->number)) { |
| 20:28.44 | Juggie | 00639 memcpy(cid->number, cid->rawdata + x + 1, res); |
| 20:28.46 | Juggie | 00640 /* Null terminate */ |
| 20:28.48 | Juggie | 00641 cid->number[res] = '\0'; |
| 20:28.50 | Juggie | 00642 } |
| 20:28.52 | Juggie | 00643 break; |
| 20:28.54 | Juggie | so, 2,3,4 fall into the same block of code |
| 20:28.56 | Juggie | in your mdmf message types |
| 20:29.09 | Juggie | and there is no consideration for what type of number message it was |
| 20:31.03 | eharris | yeah, and 7,8 are treated the same too. |
| 20:31.23 | Juggie | so there you go, you need to interface that with setting the caller presentation. |
| 20:31.43 | eharris | however, below the case statement, it specifically tests for 'O' and 'P' |
| 20:31.59 | eharris | and sets cid->flags appropriately |
| 20:32.23 | eharris | so, how can I access cid->flags from within asterisk? |
| 20:33.31 | eharris | and that code also explains why I'm not getting the "P" or "O" in the fields. It removes it when it detects them. |
| 20:33.56 | Juggie | but do you know for sure that O & P aer in the fields? |
| 20:34.45 | Juggie | because in this scenario a condition that would not work would be if a 4 or 8 was sent w/ no data following it. |
| 20:34.46 | eharris | Juggie: Yes. |
| 20:35.08 | Juggie | eharris, just add some debugging code in and recompile |
| 20:35.18 | eharris | "O" or "P" for message types 4 and 8 is the standard. And I am getting that info from other devices. |
| 20:35.47 | eharris | so that goes back to, how can I access cid->flags from within asterisk. |
| 20:37.44 | eharris | callerid_get() returns the flags along with the name and number. Now to find where that gets called. |
| 20:38.32 | Juggie | http://www.asterisk.org/doxygen/1.4/callerid_8c.html#e498a77170747f2973aa0e9a75a01626 |
| 20:44.48 | Juggie | eharris, try Noop(${CALLERID("pres")}) |
| 20:44.52 | eharris | Juggie: cool. No need to add debugging and recompile, as chan_zap.c already has ast_log(LOG_NOTICE, "CallerID number: %s, name: %s, flags=%d\n", number, name, flags); |
| 20:47.10 | eharris | Juggie: didn't give me anything, but that may be because my test box is running 1.2.13 instead of 1.4.x |
| 20:47.23 | Juggie | o. |
| 20:47.36 | Juggie | check your funcs/func_callerid.c |
| 20:47.51 | Juggie | its in there to return pres |
| 20:47.53 | Juggie | in 1.4 anyway |
| 20:48.07 | eharris | haven't seen that anywhere in the docs tho. |
| 20:48.27 | Juggie | <PROTECTED> |
| 20:48.27 | Juggie | <PROTECTED> |
| 20:49.50 | Juggie | i dont know if the flag code sets that somewhere along the line though |
| 20:52.41 | eharris | I'm upgrading to 1.4.17, I'll test it and see. |
| 20:53.23 | Juggie | otherwise, then i suggest adding some code to fun CALLERID |
| 20:53.25 | Juggie | er, func |
| 20:53.31 | Juggie | to pull out the flags |
| 21:09.11 | *** join/#asterisk-doc snuff-ho1e (n=snuffy@220-253-158-215.VIC.netspace.net.au) |
| 22:47.12 | eharris | Juggie: ERROR[2983]: func_callerid.c:95 callerid_read: Unknown callerid data type '"pres"'. |
| 22:49.54 | eharris | Juggie: where did you see the code in funcs/func_callerid.c to return pres? |
| 22:51.18 | eharris | Juggie: I only see name,num,ani,dnid,rdnis. I'm looking at asterisk-1.4.17 |
| 22:54.07 | eharris | although it does seem to be in svn trunk, doesn't look like its in 1.4.x |
| 22:55.48 | file | ${CALLINGPRES} |