I have set up Linphone, the Internet SIP telephone software, and my brother, who is also using Linphone can call me but I can't call him.
If I run it from a terminal window there are no error messages but the call just times out. I can call a computer on the internal network without problems.
I, and my brother, are using ADSL and I have a 4-port ethernet router with a firewall enabled. The firewall is set to allow anything out and the appropriate ports (5060 & 7078) are open for incoming calls.
If I call my own internal address I get a popup window saying 'User is busy' but if I call my own external (Internet) address I get nothing and it eventually times out.
I have now run out of ideas (doesn't take much) and would very much appreciate any new suggestions.
Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
mmmm this sounds like NAT issues. Whilst you have enabled the ports, are they actually *pointed* at something - or are they just under "acceptable" in NAT?
J
J wrote:
mmmm this sounds like NAT issues. Whilst you have enabled the ports, are they actually *pointed* at something - or are they just under "acceptable" in NAT?
Further to that, or perhaps more explicitly, it looks as if you need to port-forward from the firewall to the internal desktop. How else is incoming traffic going to know where to go?
Cheers, Laurie.
Laurie Brown laurie@brownowl.com wrote:
J wrote:
mmmm this sounds like NAT issues. Whilst you have enabled the ports, are they actually *pointed* at something - or are they just under "acceptable" in NAT?
Further to that, or perhaps more explicitly, it looks as if you need to port-forward from the firewall to the internal desktop. How else is incoming traffic going to know where to go?
Incoming traffic is not a problem it's outgoing traffic that disappears into the void (No response the other end to my call).
.
Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
On Fri, Feb 06, 2004 at 02:45:26PM +0000, J wrote:
mmmm this sounds like NAT issues. Whilst you have enabled the ports, are they actually *pointed* at something - or are they just under "acceptable" in NAT?
Erm, that would be correct if it was it not being able to contact him, this is the other way round, he can't contact other people. Nice thought though <G>
Brett Parker wrote:
On Fri, Feb 06, 2004 at 02:45:26PM +0000, J wrote:
mmmm this sounds like NAT issues. Whilst you have enabled the ports, are they actually *pointed* at something - or are they just under "acceptable" in NAT?
Erm, that would be correct if it was it not being able to contact him, this is the other way round, he can't contact other people. Nice thought though <G>
Its still a possibility. He hasnt said he's recieved any calls, and when you set up the phone call, it usually requires both users to be dialable - he said he can call himself (effectivly) which is without going through the firewall.
The systems usually work by first you connect to them, and then they connect back to you, hence them both requiring to be firewalled correctly.
J
On Fri, 2004-02-06 at 15:07, J wrote:
Its still a possibility. He hasnt said he's recieved any calls, and when you set up the phone call, it usually requires both users to be dialable
- he said he can call himself (effectivly) which is without going
through the firewall.
In the first post he said: "my brother, who is also using Linphone can call me but I can't call him." So he can receive calls.
The systems usually work by first you connect to them, and then they connect back to you, hence them both requiring to be firewalled correctly.
Like youve said, the problem is after he's connected to his brother the program trys to connect back but can't. Maybe a different port is used for the connection back to a caller then the ports used to call some one. May asking on the Linphone site or mailing list would be a better place of info on this problem(unless some ALUG'er is going to dig in the code?).
- Dennis Dryden
On Fri, Feb 06, 2004 at 03:38:56PM +0000, Dennis Dryden wrote:
On Fri, 2004-02-06 at 15:07, J wrote:
Its still a possibility. He hasnt said he's recieved any calls, and when you set up the phone call, it usually requires both users to be dialable
- he said he can call himself (effectivly) which is without going
through the firewall.
In the first post he said: "my brother, who is also using Linphone can call me but I can't call him." So he can receive calls.
The systems usually work by first you connect to them, and then they connect back to you, hence them both requiring to be firewalled correctly.
Like youve said, the problem is after he's connected to his brother the program trys to connect back but can't. Maybe a different port is used for the connection back to a caller then the ports used to call some one. May asking on the Linphone site or mailing list would be a better place of info on this problem(unless some ALUG'er is going to dig in the code?).
Hrm - I think that this document says it all really: http://www.linphone.org/doc/us/manual/x137.html?PHPSESSID=e496d49b3c0b292bf1...
So, choice of 2, set the router to shift all packets towards himself, or set up a SIP proxy.
Cheers,
Brett Parker brettp@users.sourceforge.net wrote:
Hrm - I think that this document says it all really: http://www.linphone.org/doc/us/manual/x137.html?PHPSESSID=e496d49b3c0b292bf1...
So, choice of 2, set the router to shift all packets towards himself, or set up a SIP proxy.
I've already read that.
Remember that my brother can send from behind his router/firewall but he never receives any calls when I try to send.
He doesn't need a SIP proxy so why should I?
Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Remember that my brother can send from behind his router/firewall but he never receives any calls when I try to send.
Question - can he receive calls from other users OR are you sure your packets arnt getting there (badly phrased - i mean is your definition of calls not arriving the application dosnt detect it or does the OS refuse to acknowledge anything as well?)
J
J j.e.taylor@uea.ac.uk wrote:
Question - can he receive calls from other users OR are you sure your packets arnt getting there (badly phrased - i mean is your definition of calls not arriving the application dosnt detect it or does the OS refuse to acknowledge anything as well?)
Our problem is that we know of no other users! If we did it might help a great deal.
My problem is that I don't know if my packets are getting out or if they are whether they are not getting to his computer for whatever reason.
Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
On Fri, Feb 06, 2004 at 08:02:20PM +0000, Barry Samuels wrote:
J j.e.taylor@uea.ac.uk wrote:
Question - can he receive calls from other users OR are you sure your packets arnt getting there (badly phrased - i mean is your definition of calls not arriving the application dosnt detect it or does the OS refuse to acknowledge anything as well?)
Our problem is that we know of no other users! If we did it might help a great deal.
My problem is that I don't know if my packets are getting out or if they are whether they are not getting to his computer for whatever reason.
You may find that playing around with a packet sniffer (tcpdump) and seeing which way packets on the network go to which machine etc. may provide you with some clues. I would suspect that the problem is a firewall on one of the machines, although not knowing how this software works it is hard for me to say which one :) Are there any logs for the firewalls that you could look at?
If tcpdump looks like it is a bit heavy to interpret you may find that using ethereal as a front end may help you http://www.ethereal.com/ trouble is that I can't really give you a quick and dirty guide as to how they work, you will have to give them a go yourself.
Adam
adam@thebowery.co.uk wrote:
You may find that playing around with a packet sniffer (tcpdump) and seeing which way packets on the network go to which machine etc. may provide you with some clues. I would suspect that the problem is a firewall on one of the machines, although not knowing how this software works it is hard for me to say which one :) Are there any logs for the firewalls that you could look at?
If tcpdump looks like it is a bit heavy to interpret you may find that using ethereal as a front end may help you http://www.ethereal.com/ trouble is that I can't really give you a quick and dirty guide as to how they work, you will have to give them a go yourself.
I have temporarily swapped my ADSL for a modem which, of course, bypasses the router and firewall. This has made no difference in that I still cannot instigate a call so I think that the problem is probably not within my own computer.
That, at least, is a small step forward.
Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
I have temporarily swapped my ADSL for a modem which, of course, bypasses the router and firewall. This has made no difference in that I still cannot instigate a call so I think that the problem is probably not within my own computer.
Sorry if I get this wrong, head hurts - you still cant instigate a call with the modem ... doesnt that imply it *IS* within your own computer, and not with router and firewall?
J
On Fri, Feb 06, 2004 at 05:19:59PM +0000, Barry Samuels wrote:
Brett Parker brettp@users.sourceforge.net wrote:
So, choice of 2, set the router to shift all packets towards himself, or set up a SIP proxy.
I've already read that.
Remember that my brother can send from behind his router/firewall but he never receives any calls when I try to send.
What settings has he got on his router? Can you emulate the same settings with yours?
Cheers,
J j.e.taylor@uea.ac.uk wrote:
Its still a possibility. He hasnt said he's recieved any calls, and when you set up the phone call, it usually requires both users to be dialable
- he said he can call himself (effectivly) which is without going
through the firewall.
The systems usually work by first you connect to them, and then they connect back to you, hence them both requiring to be firewalled correctly.
I did say in the first paragraph that my brother can call me. That is to say he initiates a call and I get a ringing tone on my speakers.
I cannot do the same. If I initiate a call he gets nothing.
Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
-
adam＠thebowery.co.uk -
Brett Parker -
Brett Parker -
bsamuels＠beenthere-donethat.org.uk -
Dennis Dryden -
J -
Laurie Brown