Trying to use OBI202 as a Proxy to GV from Freeswitch
ubergoober:
I have it working now. Registered or not, I was still getting the 486 busy. I took your advice on setting the inbound call route on SP4 to {sp}.
What was really missing was in the google voice portion on SP1. It's inbound call route field needed the addition of {sp4(authusername@freeswitchIPADDRESS):sp}, before the pre-existing contents, which were {ph1,ph2}. This part I took from the obihai 20x admin guide page 118.
I plan on writing up my configuration and posting it on the fusionpbx forums, on the Freeswitch confluence pages and I'll reply back to this thread with a link to those pages.
Thanks for contributing, Restamp.
Tom
ubergoober:
Although I'm able to place a call outbound, I'm getting mixed results depending on how long it takes for the far end to answer the call. For instance, if I call a voicemail system at work that picks up on the first ring, I receive a 200 OK from the OBI and all is well.
However, if I call my own work extension that takes five rings before it forwards to voicemail, I exceed 30 or 32 seconds and the OBI returns a 503, at which time Freeswitch presents me with fast busy tone.
I have combed through as many settings as I can stand, so I e-mailed OBI support. Not bothering to explain why, they blame it on Google Voice.
When I call the same number with one of the handsets connected to the OBI phone ports, there is no timeout behavior at 30-32 seconds. The phone continues to ring and is answered by voicemail. It's only when I use a SIP client that I encounter the 503 which is sent by the OBI. My reasoning is there's something about the proxy function that times out at 30-32 seconds, but whether or not there's a setting to control it or what that setting is called, I cannot tell.
So, I replied asking them to re-examine their answer. Maybe it won't change, but I always mistrust quick no answers when I have no means of gauging the knowledge level of the first responder.
Also, the way I think about this is that Asterisk users appear to be successful using the OBI as a proxy. Why would it not work with Freeswitch? Admittedly the settings differ.
What do you think?
azrobert:
The SIP protocol has several timers. The only one I'm familiar with is TimerB, but I don't think it applies to your problem. I'm sure there is documentation on the Web for these timers or you can just increase all the timers that are set to 32 seconds.
The timers on the OBi are found here:
Service Providers -> ITSP Profile x SIP
ubergoober:
Time permitting, I'm investigating the timers.
Obihai support is so wonderful and helpful. They completely ignored my e-mail, and when I resubmitted my request to them via their web form, they maintained that very high level of responsiveness that I as a paid support customer have come to expect.
Can I get my $10 back? Seriously, Obihai. At least tell me you've checked your facts and stand by your answer rather than ignoring a paying customer. It might keep me from nagging a Polycom product manager I know.
ubergoober:
I've investigated the SIP timers using this article:
https://andrewjprokop.wordpress.com/2013/07/02/understanding-sip-timers-part-i/
I know Andrew. He's a pretty smart guy and his articles on SIP are worth reading. Unfortunately, having gained some insight and getting very excited, I'm finding that changing the timers on the SIP profile B doesn't have any effect. The obi still generates the 503 response, ending the call attempt.
Navigation
[0] Message Index
[#] Next page
[*] Previous page