Login Timed out Cotact Network Admin

Dear kijaz,

Requesting again: Can you confirm if you are getting response from the sip servers by checking your diagnostic logs for x-lite. Also ping to those sip servers to check if you are getting response and what is your response time?

You can change the sip port to any any other as I have changed and confirmed it, I have used 5063 on xlite for voipbuster and also with braintel and both works fine.

Miraz - I don't understand quite what you mean by using different ports?

It wouldn't work for us, we have our SIP server bound to 5060. It's the only port it "listens" on.

It's possible that voipbuster etc offer more than one.

Kijaz - we use port 5060 because it is the industry standard/adopted port for SIP. I'll see if we can bind additional ports to a single server, so we can listen on more than one.

That's the best I can do - if the problem is with your ISP, the only way to resolve the problem would be for you to move ISP.

Dean

Hi Dean,
I haven't used voipuser account for quite some time, tonight I will check different port number settings with voipuser, On one of my x-pro installs I changed the listining port to 8891 and used bbpglobal, braintel, fwd and voipbuster and was able to make calls and listen succesfuly.
One more thing port 5060 is for listening purposes and kijaz should be able to register for sip proxy for his service providers?

Quote:

I changed the listining port to 8891

I suspect you're talking about an audio (RTP) port, as that is something that is decided on between 2 clients, and you can set it to whatever you like.

Quote:

One more thing port 5060 is for listening purposes and kijaz should be able to register for sip proxy for his service providers?

No. Port 5060 is the SIP port for registrations to our SIP server. Our SIP server is set to "listen" for registrations coming in on port 5060 - registrations coming in on any other port will be ignored (in fact they're blocked at our firewall). It won't work.

I'm making some enquiries as to whether we can bind more than one port to the SIP server though. If we can, it may solve the problem, at least until Kijaz's ISP discovers it and decides to block that one also.

Could be a game of cat and mouse with this, but as long as I pick some completely random number for the additional port, and as long as we don't have thousands of voipuser users at Kijaz's ISP, we might get away with it for a little while yet.....

Dean

You were right Dean about my port 5060 listening, now I have more understanding after your explanation on this issue and registration on port 5060.
We have to wait for kijaz response for further solutions, he can go to www.testmyvoip.com to see what that site says about his sip connections and post a reply.

I am from Pakistan and facing the same problem, I have changed the two different ISP but problem is same I think 5060 is blocked by PTCL

I'm in Australia and also getting "login timed out". It was all working fine, I also have 3 other SIP services registered - all using port 5060 so I know my ISP is blocking. Looking at the logs I see no reply at all from the voipuser.org sip server.

My current settings are domain: sip.voipuser.org, sip proxy: sip.voipuser.org. The last thing I got when it was working was that I had no more access to PSTN outbound, but if I can't login anymore how can I get credit for people calling me

Another thing, I have tried (before this current saga) to change my SIP password via the web site, but it has never worked - is it just me or is it really impossible to change you sip account password?

I hope this is resolved soon, maybe some commercial telco is blocking 5060 somewhere, I don't know if Pakistan would be via same networks as Australia to the UK voipuser.org servers????

I have tested with testyourvoip.com but it is also indicating 5060 is blocked which confirms it is blocked at national level.

Dean! your support is required is it possible for you to bind another port?

dean anxiously awaiting your response..

Quote:

anxiously awaiting your response..

It may take a little while - I don't make server changes like that lightly, or without sounding it off the software creators first.

I'll let you know as soon as I have some news. I will do everything I can to see if we can work around this, but I do anticipate a cat and mouse game with a few ISP's

Dean

From Canada:
Earlier today, no problem, - no changes..... Now x-lite says "Login timed out - contact network admin".....

I'm in Belgium and also experiencing exactly the same problem, since about 14:00 (GMT). I have not made any configuration changes .

Beacon

Beacon/Chris - this is too much of a coincidence.

I had been trying something on the server. Can you please try again now for me?

I believe that we are indeed seeing large-scale blocking of common voip ports by ISP's, but I don't think that the problem of today from about 2pm is related.

It's important to isolate port blocking from other issues where possible. I think it may be a day or so until we really know what's going on with the ISP's.

Thanks,

Dean

I am able to login again now (Canada)......

Chris - thanks. Yours and Beacons problem there was unrelated, and is now fixed...

I am still however certain that we are seeing widespread blocking of port 5060 by ISP's....

Dean