I use a perl script to parse the syslog data and this script logs my calls. Outbound GV call information is missing in the latest firmware build 2669.
Are there any plans to add it back? Some of us use the call data with home automation systems and other programs.
Previously (in builds 2651 and prior) I'd see something like this for an outbound call following the button presses (with SYSLOG set to level 7):
[<7> FXS:New Call:1316****657]
[<7> FXS:New State:incall]
[<7> FXS: State=incall, flags=1]
[<7> FXS:Stop Ring]
Have you checked the new firmware, build 2675? I don't need the info (yet) but it would be interesting to know.
I don't see that, but I do see the DTMF showing up and the number I dialed showing up in the SIP message.
From: <sip:14153767253@chicago.voip.ms>;tag=as08b52071
02-01-2012 11:34:12 Kernel.Debug 192.168.1.105 [DSP] ---- S/W DTMF OFF @ 610990 ms----
02-01-2012 11:34:12 Kernel.Debug 192.168.1.105 [DSP] ---- S/W DTMF ON (level: 0) : 3, @ 610810 ----
Etc, etc.
I haven't tried the newest build 2675. However, it looks like it works with your VOIP provider :) If you don't mind me asking, which provider are you using? I guess it's not google voice?
VoIP.ms.
Edit:I'll check later and see what GV brings up.
Any chance of this ever being fixed?!? EVen the newest firmware still does not display outgoing call data in syslog (for GV).
I am not seeing any "<7> FXS:" here with syslog message level at 7. Although I'm using an OBi202 (Build 3397), I do see several entries beginning with "<7> GTALK:" during an outbound GV call as well as "<7> CCTL:NewCallOn Term " -- have you checked for those? Perhaps the syntax has changed. :-\
Of course, it might be completely different between the 202 and the 100/110,
pc44
Just to confirm, you can see dialed calls in syslog with the obi202?
etc6849,
This might interest you. Using the OBi202 I can see my outgoing call in the syslog. I made several different tests. Showing relevant portions of the syslog. I think calls via phone port is what you are wanting to confirm. It works on the OBi202. You can test for yourself on the OBi100/110.
OBi202->GV (Direct call from phone connected on OBi202) CID OK
<7> CCTL:NewCallOn Term 16[1] ->5145551111,5145551111 172.16.240.10 22/09 13:49:24.656
OBI202->sip (calls were made using the OBiAPP with OBi202 as gateway) CID OK
<7> CCTL:NewCallOn Term 10[0] 290123456->5145551111,5145551111 172.16.240.10 22/09 12:02:41.187
OBI202->Google Voice Using speed dial (calls were made using the OBiAPP with OBi202 as gateway): CID OK on the speed dial call only
<7> CCTL:NewCallOn Term 3[0] 290123456->, 172.16.240.10 22/09 13:27:31.390 (No CID here)
<7> CCTL:NewCallOn Term 16[1] ->5145551111,5145551111 172.16.240.10 22/09 13:27:45.656 (CID after hitting speed dial)
etc6849,
QBZappy confirmed outgoing calls. I just received an incoming call today and thought I would post my edited log if it is of any help. It appears incoming Caller ID is functioning as well via syslog:
<7> CCTL:NewCallOn Term 1[0] ->, IP_Address 23/09 15:05:22.392
<7> [SLIC] Command: 0, 3, 0, 0, 4, 1087619968, IP_Address 23/09 15:05:22.395
<7> [SLIC] CID to deliver: '' 1XXXXXXXXXX IP_Address 23/09 15:05:22.396
and voicemail status check as well...
<7> GTALKVM:Check VM Succ IP_Address 23/09 14:55:11.380
<7> GTALKVM:state changed from 1 to 0 IP_Address 23/09 14:55:11.380
<7> GTALKVM:VM:0 IP_Address 23/09 14:55:11.381
pc44