OBI100 SIP URI call problem
DavidNewton01:
Quote from: hwittenb on April 28, 2013, 07:09:24 am
To get a better idea of what is happening you should run the syslog on your OBi. With that you can look at the sip signalling. OBihai has instructions on how to do that and a syslog download link here:
http://www.obitalk.com/forum/index.php?action=printpage;topic=707.0
Thanks a lot. I will follow your suggestion to get the call log. BTW, I found that if I change the SP1 register server and proxy server from my local server to any external server, then the SIP URI call can go through. I am not sure if this a bug or it is supposed to be. From the help for URI box below AuthUserName and AuthPassword, it seems that the domain is related to proxy server.
hwittenb:
Quote from: DavidNewton01 on April 30, 2013, 07:04:47 am
BTW, I found that if I change the SP1 register server and proxy server from my local server to any external server, then the SIP URI call can go through. I am not sure if this a bug or it is supposed to be.
You found one of the undocumented secrets.
DavidNewton01:
Quote from: hwittenb on April 30, 2013, 07:38:18 am
You found one of the undocumented secrets.
Probably not many people use local proxy/registar server, so this problem does not have impact. But I still believe this is a bug. It seems that the URI box under the AuthPassword is basically ignored, it doesn't matter what input in this box. I have tested another OBI100 and have the same result.
BTW, thanks a lot for pointing the right direction for me.
azrobert:
Quote from: DavidNewton01 on April 30, 2013, 07:52:47 am
Probably not many people use local proxy/registar server, so this problem does not have impact.
Is the local proxy server that is causing your problems an Asterisk server?
I've been testing URI calling to free 800# termination providers and I'm having the same problem.
I'm testing Future9, Denetron, IPKall, Sipbroker and CallWithUs.
My test shows the cause of the problem is Asterisk whether local or remote.
I have the same problem when SPx is register to a local PBX in a Flash or PBXes.org.
The exception to the problem is CallWithUs ALWAYS works.
I found this fixes the problem:
Services Providers -> ITSP Profile A/B -> SIP
X_DiscoverPublicAddress: Unchecked
X_PublicIPAddress: xx.xx.xx.xx:5061 (xx.xx.xx.xx = your external modem address)
hwittenb,
I found that when the 800# provider is defined directly on the SPx trunk it works.
Concerning OBi to OBi uri calling. When the called OBi is registered to an Asterisk server the call works with the default X_DiscoverPublicAddress or with a non-Asterisk provider and the following settings:
X_DiscoverPublicAddress: Unchecked
X_PublicIPAddress: 192.168.1.100:5061 (your local OBi address)
It looks like the OBi doesn't know when to use the internal or external addresses.
Can you comment on CallwithUs and the OBi to OBi calling.
Thanks
DavidNewton01:
Quote from: azrobert on April 30, 2013, 04:00:29 pm
Is the local proxy server that is causing your problems an Asterisk server?
Thanks a lot for sharing your experience. Yes, the local proxy server my SP1 registered is an asterisk server. But the external server which makes the URI works is also an asterisk server, this is different from your observation. I have tested CallCentric, direct call from a SPA3000, and direct call from LinPhone in Ubuntu without registration. They all behave the same. Same as your test for CallWithUS, The SIP URI call from another asterisk server always work too.
Navigation
[0] Message Index
[#] Next page
[*] Previous page