Caller id issue - version 1.3.0 Brazil GVT carrier

(1/2) > >>

Ricardo:
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:
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:
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:
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:
Quote from: Ricardo on January 11, 2012, 04:03:24 pm

Brazilian 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?

Navigation

[0] Message Index

[#] Next page