SIP to Talkshoe
azrobert:
I resolved the audio problem by routing the call thru CallCentric.
This was easy for me because I already have a free CallCentric account.
This seems like a lot of trouble for you since you can call them via GV, but you said you wanted a learning experience.
Here is what you have to do:
Get a CallCentric Freedom account here:
http://www.callcentric.com/products/
Add a Speed Dial entry *7501 with a destination talkshoe@sip.talkshoe.com
Add an OBi Speed Dial:
sp4(*7501@callcentric.com;ui=17771234567:password)
"17771234567:password" is your CallCentric account number and password.
azrobert:
Quote from: ianobi on March 26, 2013, 03:23:52 pm
Looks like its worth trying stun.
I tried stun.3cx.com on the OBi and it didn't work.
Diana:
Quote from: ianobi on March 26, 2013, 03:23:52 pm
I just tried and got the same results as azrobert. Then I tried using PhonerLite Softphone - same failure. Then I added in stun server to PhonerLite (stun.ideasip.com) and it now works every time!
However, with stun set on my OBi it still does not work, but that might be something odd about my setup.
Looks like its worth trying stun.
I use:
sp2(talkshoe@66.212.134.192); SP2 is setup with Anveo
In one of my speed dial (28) and was able to make a outgoing call by dialing 28#. I have Stun set at: stun.ideasip.com for SP2.
azrobert:
I registered CallCentric on SP2 without STUN and now the OBi speed dial "sp2(talkshoe@sip.talkshoe.com)" works.
Here is the revised to do list:
Get a CallCentric Freedom account here:
http://www.callcentric.com/products/
Register CallCentric on SP4
Service Providers ==> ITSP Profile D ==> SIP ==> ProxyServer: callcentric.com
Voice Services ==> SP4 Service
AuthUserName: 17771234567
AuthPassword: password
X_RegisterEnable : checked
Now your OBi speed dial "sp4(talkshoe@sip.talkshoe.com)" should work.
Thanks Diana
ianobi:
Diana's post made me think - something I should do more often :)
We have all been using the "fake" SIP provider, which did not work with or without stun. Diana used a "real" SIP provider, which does work with stun.
We have had this problem before with voice gateways using a "fake" SIP provider. Even if you configure stun it does not get used unless you add the paramater to the vg access number, or in our case to the speed dial. With stun configured on my "fake" SIP provider (sp2 in my case) this does not work:
sp2(talkshoe@66.212.134.192)
This does work every time:
sp2(talkshoe@66.212.134.192;op=s)
@ mikefoley
Using your "fake" SIP provider on ITSP Profile D > General:
STUNEnable: check
STUNServer: stun.ideasip.com (or stun server of your choice)
Set speed dial to sp4(talkshoe@66.212.134.192;op=s)
Talk about re-inventing the wheel every day! Now where did I leave my glasses ... :D
Navigation
[0] Message Index
[#] Next page
[*] Previous page