I sincerely hope that someone that is very knowledgeable about the Obi peruses this post and can conjure up some answers for me. I am finding myself a little desperate here.....
My setup is as follows: I have TWO GV numbers associated with my Obi box (SP1 and SP2). Please keep in mind that neither of the GV numbers associated with my Obi are set to forward to any "normal" phone via Google's server, so I cannot achieve the "Simul-Ring" syndrome that so many enjoy (to borrow a Vonagism). Instead, they are
only set to forward to Google chat. Reason being, I have yet
another GV number already linked directly to my cell phone as far as Google is concerned, and since they don't allow one to funnel more than one GV number to the same destination phone, I was hoping my Obi could serve to work around that limitation.
If I set my Obi to execute a call_forward_no_answer of its associated GV number to my cell phone, even if set to do so after only one incoming ring, my cell phone does not start to ring until about the fourth ring that the originating caller hears. If that isn't bad enough, even if I answer my cell the instant it first rings, more often than not, the caller does
NOT connect with me, and they are diverted to the GV voice mail. By that, I mean to say that the call connects about 40% and winds up at voicemail 60% of the time.
If I set it to unconditionally forward, which I presume should be an almost instantaneous forwarding, it takes about two rings before my cell phone rings, and most of the time I can successfully field the call on the cell, but occasionally same thing happens and the caller still winds up at GV voice mail. Granted, this is a much rarer occurrence than when employing the call_forward_no_answer, but it unfortunately happens nevertheless. This is more like 70% success vs. 30% failure.
Am I the only one going through this? Does anyone know precisely why this is happening to me? It's an untenable situation and I desperately require some semblance of rectification.
Now, I went ahead an synchronized my laptop's clock with the same time server the Obi employs, namely
pool.ntp.org. I generated calls to my Obi for testing purposes, and the first ring the Obi generates to the attached phone on an incoming call directly coincides with the precise time it occurred, according the Obi call history, however, a 13 or 16 second delay always comes after that before my cell phone rings. Why is this delay happening? I have checked the syslog and there is always a similar delay among the avalanche of syslog entries that occur in very quick succession. The delay is always here:
2012-03-09 23:31:09 kernel.debug 192.168.1.110 RTP:Start->4a7d7f7f:19305(80);0;0;0:0:0;1(57)\n
2012-03-09 23:31:22 kernel.debug 192.168.1.110 GTALK:sess callsess_17 state changed from 2 to 5\n
Notice the 13 second delay between the entriesFurthermore,
the [SLIC] CID to deliver: does not get thrown to the syslog server during busy or unconditional call forwarding and is only occurring during Call_Forward_No_Answer.
Does anyone out there know what is going on here?