Caller id issue - version 1.3.0 Brazil GVT carrier

Ricardo · December 05, 2011, 05:22:03 PM

Hi,

For some reason, after obi110 was updated to 1.3.0 latest version, the caller id is not working properly.
GVT carrier uses FSK and the trigger is after first ring. When I connect the line directly to the phone, I observe that the caller id is quick displayed on the phone.
I changed the ring delay from 500 to 6500ms in obi110. The behaviour is very strange. After I change the ring dealy, when I call to my landline number using my mobo, I realize that sometimes the caller id doesn't work, works once, twice and till three times in sequence and remains a lot of calls without identify. So, it's completely random.
Please, I'd like very much to have the caller id working again to use the trusted callers feature and auto attendant.

Thanks,
Ricardo

Stewart · December 05, 2011, 05:44:52 PM

On the failing calls, what shows in the OBi's call history? If the calling number appears there, the trouble is with sending caller ID to the Phone port, rather than receiving it from the Line port.

You could use Localphone to send calls to your OBi. Your mobile number would be associated with your Localphone account and you would set an iNum as the contact. You call a local BR access number and it rings your OBi's iNum (free from Localphone, Callcentric, VoIP.ms, etc.) There would be no problem recognizing your number, and quality would likely be better than using the analog connection. This would also have the advantage of not tying up the landline (if you have other family members who might be at home using it), and would allow you to call out on the landline, e.g. if you have a plan offering "free" calls to certain destinations that would not be free from your mobile, or if you wanted to send the landline number as caller ID.

Ricardo · December 05, 2011, 06:48:53 PM

Hi, Stewart! On the failing calls, they don't appear in the OBi's call history.

I use a google voice account and a cordless panasonic phone connect to the Obi's phone port. I use GV to make calls to other area code and international calls through the cordless phone.

I don't know why this random caller id detect. I remember it worked properly using some 1.3.0 subversion.

Do you have a hint?

Thanks,
Ricardo

Ricardo · January 11, 2012, 04:03:24 PM

Just a note

After upgrading to build 2669, it is now worst: the caller-id seldom works (1 of 15 received calls). I really would like a help from support team, else I have to split the telco line and plug one directly to one cordless phone and buy another cordless to connect to Obi110 device. It is not a good option.

I already changed ringdelay parameter in line port from 1000 to 6500.

Brazilian carrier - GVT. Caller-id FSK.

Thanks.

Stewart · January 11, 2012, 08:38:02 PM

Quote from: Ricardo on January 11, 2012, 04:03:24 PMBrazilian carrier - GVT. Caller-id FSK.

What's the ring cadence? Possibly, carrier is sending caller ID after a pair of rings, but OBi is "listening" after the first, or vice-versa. In which case, changing the Ring Detection parameters may help.

Do you have a way to capture the signal on the analog line, to see what is being sent, and when it occurs relative to the ringing?

Ricardo · January 12, 2012, 04:29:08 AM

Hi, Stewart.

Som ring information I got from a document I found at www.futurel.bg/datasheets/2/si3050.pdf
I set a ring user-def 1 in profile A with pattern 60;(2+4)
I set this ring in line port.
Ring detection parameters (I tried a lot of values):
freq min 13
freq max 83
threshold 13.5-16.5
other parameters are set to default

I could try capture the ring. May you help me how can I do it? I have a analog modem. Is it enough?

Today at morning I changed the ring user-def 1 to bellcore-5 in line port and the cid worked 7 times consecutive. After that, don't detect more. It is very strange (and the ring is very strange too :-) ).

Thanks.

Stewart · January 12, 2012, 09:06:10 AM

I'm very confused. The caller ID could fail in two ways -- either (1) the OBi fails to read it correctly from the LINE port, or (2) it fails to send it properly to the PHONE port. Since you reported that the failing calls didn't get logged in Call History, I concluded that the failure was type (1) and limited my suggested changes to that area. However, you now have credible evidence that the opposite is true.

If it fails again, please recheck what Call History shows, and also see whether anything logged in syslog shows that caller ID is or is not being read. If it's clear that sending is what's failing, tweaking ring Voltage, Frequency or Waveform will likely help, even if you revert to the original cadence.

Ricardo · January 12, 2012, 05:53:59 PM

Thanks, Stewart, for the prompt reply. I will make some tests and I'll post the results, including syslog information.

I'll try to do it in this weekend.

Regards.

Ricardo · January 16, 2012, 05:11:10 PM

Hi, Stewart. I tested CID making calls from 2 different mobile numbers (618xx1481x and 618xx8468x). As expected, sometime the CID works, sometime not.
I think I didn't tell that if I make call from google chat to the user I use in the ATA using IP dialing, the calling username always is showed in phone display (There isn't google voice number service in Brazil.)
I realized that when CID works, CID information shows in syslog immediately after the ring on detection.

CALL HISTORY
==========
Call 6   01/16/2012 18:17:01

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number
Direction   Inbound   Inbound
18:17:01   Ringing
18:17:10   End Call
Call 7   01/16/2012 18:16:37

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number   618xx1481x
Direction   Inbound   Inbound
18:16:37   Ringing
18:16:46   End Call
Call 8   01/16/2012 18:16:10

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number
Direction   Inbound   Inbound
18:16:10   Ringing
18:16:24   End Call
Call 9   01/16/2012 18:15:20

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number   618xx8468x
Direction   Inbound   Inbound
18:15:20   Ringing
18:15:40   End Call
Call 10   01/16/2012 18:14:50

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number   618xx8468x
Direction   Inbound   Inbound
18:14:50   Ringing
18:15:04   End Call
Call 11   01/16/2012 18:14:22

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number
Direction   Inbound   Inbound
18:14:22   Ringing
18:14:32   End Call
Call 12   01/16/2012 18:14:03

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number
Direction   Inbound   Inbound
18:14:03   Ringing
18:14:07   End Call
Call 13   01/16/2012 18:13:31

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number
Direction   Inbound   Inbound
18:13:31   Ringing
18:13:46   End Call
Call 14   01/16/2012 18:13:05

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number   618xx1481x
Direction   Inbound   Inbound
18:13:05   Ringing
18:13:13   End Call
Call 15   01/16/2012 18:12:32

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number   618xx1481x
Direction   Inbound   Inbound
18:12:32   Ringing
18:12:42   End Call
Call 16   01/16/2012 18:12:05

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number
Direction   Inbound   Inbound
18:12:05   Ringing
18:12:19   End Call
Call 17   01/16/2012 18:11:34

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number
Direction   Inbound   Inbound
18:11:34   Ringing
18:11:53   End Call
Call 18   01/16/2012 18:10:55

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number   618xx1481x
Direction   Inbound   Inbound
18:10:55   Ringing
18:11:09   End Call
Call 19   01/16/2012 18:10:13

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number
Direction   Inbound   Inbound
18:10:13   Ringing
18:10:37   End Call
Call 20   01/16/2012 18:09:23

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number   618xx8468x
Direction   Inbound   Inbound
18:09:23   Ringing
18:09:42   End Call
Call 21   01/16/2012 18:04:10

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number
Direction   Inbound   Inbound
18:04:10   Ringing
18:04:29   End Call
Call 22   01/16/2012 17:59:35

Terminal ID   LINE1   PHONE1
Peer Name
Peer Number
Direction   Inbound   Inbound
17:59:35   Ringing
17:59:59   End Call

SYSLOG:
=======

Fail to detect CID:
===================
Jan 16 17:59:34 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:00:02 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:00:02 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
Boot (I restarted ATA):
=======================
Jan 16 18:00:59 192.168.25.245 [PR] prompt transcoding done!!
Jan 16 18:02:30 192.168.25.245 PARAM Cache Write Back(256 bytes)
Jan 16 18:02:32 192.168.25.245 Reboot is scheduled in 1 seconds
Jan 16 18:02:33 192.168.25.245 Reboot checking.....
Jan 16 18:02:33 192.168.25.245 Final Cleanup before reboot....
Jan 16 18:02:34 192.168.25.245 Goodbye! Reboot Now. (reason: 4)
Jan 16 18:02:45 192.168.25.245 Start Main Service Now
Jan 16 18:02:45 192.168.25.245 Voice Main
Jan 16 18:02:45 192.168.25.245 [CPT] --- FXS s/w tone generator (ringback) ---
Jan 16 18:02:45 192.168.25.245 BASESSL:load cert:5
Jan 16 18:02:45 192.168.25.245 BASESSL:Load certificate ok
Jan 16 18:02:45 192.168.25.245 XMPP:State changed from: 0 to:1
Jan 16 18:02:45 192.168.25.245 GTT:Init xmpp node ok
Jan 16 18:02:46 192.168.25.245 [SLIC]:Slic#0 ON HOOK
Jan 16 18:02:51 192.168.25.245 [CPT] --- FXS s/w tone generator (sit_1) ---
Jan 16 18:02:54 192.168.25.245 GTALKVM:VM not enabled
Jan 16 18:02:54 192.168.25.245 GTT:xmpp service up
Jan 16 18:02:57 192.168.25.245 [CPT] tone compression done - 12383 !!
Jan 16 18:02:59 192.168.25.245 PROV: Start to download files ...
Jan 16 18:02:59 192.168.25.245 PROV: Invalid server name, Skipped
Jan 16 18:04:09 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:04:32 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:04:32 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
Jan 16 18:05:01 192.168.25.245 [PR] prompt transcoding done!!
Jan 16 18:08:23 192.168.25.245 [SLIC]:Slic#0 OFF HOOK
Jan 16 18:08:23 192.168.25.245 [CPT] --- FXS h/w tone generator (dial)---
Jan 16 18:08:26 192.168.25.245 [SLIC]:Slic#0 ONHOOK
OK:
===
Jan 16 18:09:23 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:09:23 192.168.25.245 ------ caller id (pcm_id: 1) received! ------------
Jan 16 18:09:23 192.168.25.245

DAA CND 01161808,618xx8468x,,,,
Jan 16 18:09:26 192.168.25.245 [SLIC] CID to deliver: '' 618xx8468x
Jan 16 18:09:27 192.168.25.245 PARAM Cache Write Back(256 bytes)
Jan 16 18:09:45 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:09:45 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
Fail to detect CID:
===================
Jan 16 18:10:12 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:10:16 192.168.25.245 PARAM Cache Write Back(256 bytes)
Jan 16 18:10:40 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:10:40 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
OK:
===
Jan 16 18:10:55 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:10:55 192.168.25.245 ------ caller id (pcm_id: 1) received! ------------
Jan 16 18:10:55 192.168.25.245
DAA CND 01161810,618xx1481x,,,,
Jan 16 18:10:58 192.168.25.245 [SLIC] CID to deliver: '' 618xx1481x
Jan 16 18:10:59 192.168.25.245 PARAM Cache Write Back(256 bytes)
Jan 16 18:11:12 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:11:12 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
Fail to detect CID:
===================
Jan 16 18:11:34 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:11:38 192.168.25.245 PARAM Cache Write Back(256 bytes)
Jan 16 18:11:56 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:11:56 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
Fail to detect CID:
===================
Jan 16 18:12:05 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:12:22 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:12:22 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
OK:
===
Jan 16 18:12:32 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:12:33 192.168.25.245 ------ caller id (pcm_id: 1) received! ------------
Jan 16 18:12:33 192.168.25.245
DAA CND 01161811,618xx1481x,,,,
Jan 16 18:12:35 192.168.25.245 [SLIC] CID to deliver: '' 618xx1481x
Jan 16 18:12:36 192.168.25.245 PARAM Cache Write Back(256 bytes)
Jan 16 18:12:45 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:12:45 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
OK:
===
Jan 16 18:13:04 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:13:05 192.168.25.245 ------ caller id (pcm_id: 1) received! ------------
Jan 16 18:13:05 192.168.25.245
DAA CND 01161812,618xx1481x,,,,
Jan 16 18:13:08 192.168.25.245 [SLIC] CID to deliver: '' 618xx1481x
Jan 16 18:13:17 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:13:17 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
Fail to detect CID:
===================
Jan 16 18:13:31 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:13:35 192.168.25.245 PARAM Cache Write Back(256 bytes)
Jan 16 18:13:49 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:13:49 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
Fail to detect CID:
===================
Jan 16 18:14:03 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:14:10 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:14:10 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
Fail to detect CID:
===================
Jan 16 18:14:22 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:14:35 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:14:35 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
OK:
===
Jan 16 18:14:50 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:14:50 192.168.25.245 [DSP] BG CID detected-1!
Jan 16 18:14:50 192.168.25.245
DAA CND 01161814,618xx8468x,,,,
Jan 16 18:14:53 192.168.25.245 [SLIC] CID to deliver: '' 618xx8468x
Jan 16 18:14:54 192.168.25.245 PARAM Cache Write Back(256 bytes)
Jan 16 18:15:07 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:15:07 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
OK:
===
Jan 16 18:15:20 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:15:21 192.168.25.245 [DSP] BG CID detected-1!
Jan 16 18:15:21 192.168.25.245
DAA CND 01161814,618xx8468x,,,,
Jan 16 18:15:23 192.168.25.245 [SLIC] CID to deliver: '' 618xx8468x
Jan 16 18:15:43 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:15:43 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
Fail to detect CID:
===================
Jan 16 18:16:09 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:16:13 192.168.25.245 PARAM Cache Write Back(256 bytes)
Jan 16 18:16:27 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:16:27 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
OK:
===
Jan 16 18:16:36 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:16:37 192.168.25.245 ------ caller id (pcm_id: 1) received! ------------
Jan 16 18:16:37 192.168.25.245
DAA CND 01161815,618xx1481x,,,,
Jan 16 18:16:40 192.168.25.245 [SLIC] CID to deliver: '' 618xx1481x
Jan 16 18:16:40 192.168.25.245 PARAM Cache Write Back(256 bytes)
Jan 16 18:16:49 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:16:49 192.168.25.245 [DAA]: FXO ONHOOK MONITOR
Fail to detect CID:
===================
Jan 16 18:17:00 192.168.25.245 [DAA]: FXO ring on
Jan 16 18:17:04 192.168.25.245 PARAM Cache Write Back(256 bytes)
Jan 16 18:17:13 192.168.25.245 [DAA]: FXO ring off
Jan 16 18:17:13 192.168.25.245 [DAA]: FXO ONHOOK MONITOR

Can you suggest any changes to the configuration to solve this?

Thanks.

News:

Caller id issue - version 1.3.0 Brazil GVT carrier