Open GoogleCodeExporter opened 9 years ago
Did you ever solve the problem? Thanks Regards,
Original comment by camilo...@gmail.com
on 27 Jan 2009 at 4:01
I don't understand, the behavior is normal.
I defined this behavior because everybody don't want or can't use VoIP on 3G.
Otherwise, I don't know why Siphon doesn't use VPN. Siphon uses Apple's example:
reachibility. Maybe the return value by this code for VPN is specific.
Could you help me to test this feature ?
You can contact me by mail.
Original comment by samuelv0...@gmail.com
on 27 Jan 2009 at 9:02
I'm now back home and don't have the need for the VPN since asterisk is on
local
lan. Not sure when I'll have the opportunity to test this again.
Original comment by jeremy.l...@gmail.com
on 27 Jan 2009 at 2:01
If needed, I could help you test the VPN connectivity-issue. My companys
sip-server
is reachable via vpn.
Original comment by suq...@gmail.com
on 28 Jan 2009 at 2:34
Issue 140 has been merged into this issue.
Original comment by samuelv0...@gmail.com
on 1 Feb 2009 at 1:46
I've had the problem, that using VPN and WiFi i can't connect to my SIP Server,
since Siphon tries to use the
public IP to communicate with the SIP server and not the VPN IP.
Any solution to that yet?
I can help test the VPN connection and would be glad to do so!
Original comment by lukas.pi...@gmail.com
on 1 Mar 2009 at 5:28
I have seen that siphone sends the 3G's IP instead of the local IP provided for
the
VPN server. It sends the register to my server but it sends the wrong IP, so
when my
IP-Pbx is trying to reach it, this is nos posible because the registration IP
it's
not and 192.X.X.X ip what siphon sent at the register message.
Any one can help me. Regards.
Original comment by drolda...@gmail.com
on 3 Mar 2009 at 5:28
This lines of code in call.m (Line 252-253) seem to establish the connection:
status = pjsua_transport_create(PJSIP_TRANSPORT_UDP,
&app_config->udp_cfg, NULL/*&transport_id*/);
Looking into the pjsua_transport_create function, i think, the public ip should
be passed to it, instead of NULL,
else the pjsua_transport_create takes over to lookup the public ip address,
which then results in being either
the 3G or WiFi Gateway, but not the VPN IP.
Maybe this could be solved, if the code checked for the connection being used
by the iPhone (3G/WiFi/VPN)
and passes the ip of the matching connection to the pjsua_transport_create
function.
I'd love to be included in the beta testings to test upcoming Siphon versions
with my Offices VPN connection
Original comment by lukas.pi...@gmail.com
on 8 Mar 2009 at 10:18
I would also be willing to help test any potential fixes. I'm running an
asterisk server that I have to open an L2TP
VPN connection to in order to use. Siphon seems to be passing my WiFi IP
instead of the VPN IP. Here's a copy
of my log file from opening Siphon. After it tries to connect the message
displayed in the app is "Service
Unavailable"
Original comment by masicign...@gmail.com
on 26 Mar 2009 at 7:43
Attachments:
Do you have any solution for using it with a VPN and sending the right VNP IP
address??
Original comment by drolda...@gmail.com
on 8 Apr 2009 at 7:19
Do you have the possibility to get trace from iphone (log) and on server ?
If could you post here or send me by mail.
Like that we can see if the problem is caused by server not receiving the
REGISTER
request or because the REGISTER response is not received by iPhone.
Original comment by samuelv0...@gmail.com
on 27 Apr 2009 at 8:20
Any status updates on this? I too am having the same problem. If I'm connected
via
wifi over the vpn, I see in the logs that it is using my Wifi address instead
of the
VPN. As Lukas was saying it looks like from the code that pjsip is what is
handling
what IP it should use. Apparently it is picking the wrong one. However, I think
Lukas
is wrong about the NULL thing (unless we are looking at different version of
pjsip).
It looks like it can be passed in through the app_config->public_addr which is a
string. According to pjsua.h..
/**
* Optional address to advertise as the address of this transport.
* Application can specify any address or hostname for this field,
* for example it can point to one of the interface address in the
* system, or it can point to the public address of a NAT router
* where port mappings have been configured for the application.
*
* Note: this option can be used for both UDP and TCP as well!
*/
pj_str_t public_addr;
Original comment by danielbl...@gmail.com
on 14 Jul 2009 at 4:07
look issue 225 comment 3 ;-)
Original comment by samuelv0...@gmail.com
on 15 Jul 2009 at 12:59
I am having this same issue, I am willing to do some testing to assist the
resolution
of this problem.
Thanks for your work! Hopefully we can get this working!
Original comment by jfranc...@gmail.com
on 4 Aug 2009 at 4:15
Original issue reported on code.google.com by
jeremy.l...@gmail.com
on 12 Jan 2009 at 11:03