Started by StudioD, June 13, 2016, 10:41:47 PM
Quote from: StudioD on September 13, 2016, 03:00:19 PMI haven't solved it either. CC gave me a new number, I disabled all my call treatments and it's still happening. It seems like I've ruled out all the configuration issues.I'm beginning to wonder if it's a defective Obi failing to send a ring signal to the phone. I'm using Panasonic cordless phones that have worked for years without an issue on both copper and fiber from Verizon.
Quote from: voipmvtalk on September 13, 2016, 03:35:23 PMQuote from: StudioD on September 13, 2016, 03:00:19 PMI haven't solved it either. CC gave me a new number, I disabled all my call treatments and it's still happening. It seems like I've ruled out all the configuration issues.I'm beginning to wonder if it's a defective Obi failing to send a ring signal to the phone. I'm using Panasonic cordless phones that have worked for years without an issue on both copper and fiber from Verizon.I have a ticket open with CC right now and hoping they can shed some light on this. I would think if Obi is defective then GV would not be 100% ring consistency and mine seems to be if I only use GV. I'm using ATT phone on mine but it has a ringing base station so I don't think it is our phones.I think it must be one of the following:1) CC is not ringing the Obi for some reason TBD2) The obi is receiving a signal from CC but is not seeing that as a call to ring action 100% of the time. In my case the 2nd call placed from same number rings all the time. It's as if you have to "prime the pump" for it to work. I wonder if the first call it does a cname or SIP lookup but doesn't complete it in time for call initiation. Once it is done though it is cached so that is why the 2nd call always works from the same calling number in short periods. Cache expires after X period and then that call is a "fresh" phone and once again fails on initial call. Calls made shortly after though work ok.Now when I call direct it always seems to work so I wonder if there is some failing or slow handoff of the caller id number from google's call to CC which causes initial fail. When calling CC direct no failures so the telco's are handing off the number faster perhaps. Just a guess. I hope CC has some advice. I dumped my xfinity for GV then realized no name callerID so did the CC thing. if they can't fix I may go back to xfinity where I started. Oddly enough xfinity charges me less for having phone service than if I remove it. Triple play is cheaper than double play. Go figure. I also found that out after porting to ATT so I could then port to GV. Now I'm in $10 at CC. $20 ATT port. $20 GV port and $5.95/month for the CC number (tried that as I heard the "free" ones could be the issue...nope). Now might be in for charge to port it all back to xfinity! LOL. Too funny
QuotePort 2 - SP2 with another GV number set for outgoing calls on Phone 2 port. Incoming calls are GV/SP2 and also CC/SP3. Google chat unchecked.
Quote from: SteveInWA on September 13, 2016, 05:07:36 PMQuotePort 2 - SP2 with another GV number set for outgoing calls on Phone 2 port. Incoming calls are GV/SP2 and also CC/SP3. Google chat unchecked. This is behaving as if you may have Google Chat actually check-marked/enabled, as well as forwarding the calls to your Callcentric number, causing contention to ring that phone port.Try deleting the SP2 configuration completely off of your OBiTALK dashboard. Then, try some test calls to your GV number, to see if they reliably ring SP3-->Phone 2 via Callcentric every time. If that's the case, then it suggests a problem with your Google Voice configuration for that particular GV phone number.
Quote from: voipmvtalk on September 13, 2016, 09:36:15 PMI waited 30 minutes and same thing. First call no ring. Second call ring ok. CC just responded to my ticket and said they will attempt to troubleshoot as well now.
Quote from: SteveInWA on September 14, 2016, 12:56:13 PMWell, regarding your router, if it has a "SIP ALG" setting, that setting should be DISABLED. I don't know how that translates to "SIP Passthrough". I am just guessing here, that SIP Passthrough ENabled = SIP ALG DISabled. The goal is for your router to NOT act on the SIP packets, so that sounds right.I'm sticking with my original hunch that you have some sort of network (router) configuration problem. What model router is this? Did you replace it or update it when the problem started?