What´s happening with www4 Server ?

I have 1 trunk from ser.sipcode.com.br . I can´t register it with www4 server , only the others servers is working fine. But www4_SaoPaulo has the best ping for us.

Please help.

RE: What´s happening with www4 Server ?

I have the same problem . Any news about it ?

RE: What´s happening with www4 Server ?

The same here too. No news at all

RE: What´s happening with www4 Server ?

I have the same problem.

HELP!! GOGOGOGOGO!!!

**problem lost ping ... please help

This post has been edited 1 time(s), it was last edited by dam on 22.10.2010 at 13:50.

RE: What´s happening with www4 Server ?

O Lord. No news att all about it. I`m still having problem with www4 Server. America_Sao Paulo it is not working any more.

Please. Help !

RE: What´s happening with www4 Server ?

www4 was really having some problems (as the Nagios monitoring showed).

However, it is running fine since Monday for me. Have you restarted your account since then?

Regards

RE: What´s happening with www4 Server ?

Zitat:

Originally posted by marcelcalil www4 was really having some problems (as the Nagios monitoring showed). However, it is running fine since Monday for me. Have you restarted your account since then? Regards

I really thank you for your anwer. Off course I did. And www4 it is not working fine to me and some of my friends.

RE: What´s happening with www4 Server ?

centrex.nexus.net.br (talky.com.br)
Off > www4.
ON> www2.

Hello!!!

RE: What´s happening with www4 Server ?

Tijuca,

I am so sorry to hear it.

The last www4 issue reported was this:

[10-25-2010 20:04:01] SERVICE ALERT: www4.pbxes.com;SIP test;CRITICAL;SOFT;3;SIP timeout: No response from SIP server after 15 seconds

(You can see it here https://www1.pbxes.com/status/)

My account was fully restored that day right after the first successful ping.

Sometimes, as we can see on the forum, the system does not recover itself automatically. In these cases we need the moderators' help (as far as I know, only i-p-tel and Diafora have this status).

If the problem is a trunk outage, I spent 7 days without access to my main trunk last month (see: http://www1.pbxes.com/forum/thread.php?t...1283187314&sid=). The final solution, after the system was restored, was to un-register and re-register the trunk (as can be seen in the topic). Although I am not sure about the cause OR the solution.

Abraços de Niterói,

Marcel

RE: What´s happening with www4 Server ?

Zitat:

Originally posted by marcelcalil Tijuca, I am so sorry to hear it. The last www4 issue reported was this: [10-25-2010 20:04:01] SERVICE ALERT: www4.pbxes.com;SIP test;CRITICAL;SOFT;3;SIP timeout: No response from SIP server after 15 seconds (You can see it here https://www1.pbxes.com/status/) My account was fully restored that day right after the first successful ping. Sometimes, as we can see on the forum, the system does not recover itself automatically. In these cases we need the moderators' help (as far as I know, only i-p-tel and Diafora have this status). If the problem is a trunk outage, I spent 7 days without access to my main trunk last month (see: http://www1.pbxes.com/forum/thread.php?t...1283187314&sid=). The final solution, after the system was restored, was to un-register and re-register the trunk (as can be seen in the topic). Although I am not sure about the cause OR the solution. Abraços de Niterói, Marcel

Obrigado Marcel pelas informações, mas o problema continua igual para mim.


Thank you Marcel for your answer, but I`m still have problems with www4 server.

RE: What´s happening with www4 Server ?

I have been looking into this issue for the past couple of days, and I believe this is not a strictly server issue per se. It looks like a connectivity issue between the www4 server and this particular SIP Proxy centrex.nexus.net.br at the 200.143.0.186 IP.

Here is a traceroute from the www2 server to this particular SIP Proxy. It's a long way but at least it gets there properly.

traceroute from www2 to centrex.nexus.net.br (200.143.0.186), 30 hops max, 40 byte packets
1• 63.223.127.1 (63.223.127.1) 1.111 ms 1.391 ms 1.616 ms
2• agg1-sea-g1-33.bb.spectrumnet.us (208.76.184.209) 1.262 ms 1.416 ms 1.477 ms
3• cr2-sea-A-p10.bb.spectrumnet.us (208.76.153.41) 1.206 ms 1.193 ms 1.337 ms
4• 208.173.50.57 (208.173.50.57) 1.396 ms 1.485 ms 1.484 ms
5• s214723-1.savvis-internet.cr2-sel.savvis.net (208.172.88.14) 1.448 ms 1.436 ms *
6• sl-crs2-tac-0-0-5-0.sprintlink.net (144.232.9.151) 5.313 ms 4.990 ms 5.426 ms
7• sl-crs2-chi-0-10-3-0.sprintlink.net (144.232.20.84) 48.671 ms 48.671 ms
8• sl-crs2-chi-0-3-5-0.sprintlink.net (144.232.19.104) 53.086 ms
9• sl-crs1-nsh-0-9-4-0.sprintlink.net (144.232.24.47) 72.150 ms
10• sl-crs2-nsh-0-9-4-0.sprintlink.net (144.232.9.127) 72.150 ms
11• sl-crs2-atl-0-9-0-0.sprintlink.net (144.232.19.238) 78.465 ms
12• sl-crs2-mia-0-8-0-1.sprintlink.net (144.232.20.239) 80.957 ms
13• sl-crs2-mia-0-5-2-0.sprintlink.net (144.232.18.203) 77.117 ms
14• sl-crs2-atl-0-12-0-0.sprintlink.net (144.232.9.124) 74.153 ms
15• sl-crs1-mia-0-0-0-0.sprintlink.net (144.232.25.53) 96.131 ms
16• sl-crs1-mia-0-8-0-2.sprintlink.net (144.232.18.221) 93.198 ms
17• sl-crs1-mia-0-11-2-0.sprintlink.net (144.232.18.217) 103.457 ms
18• sl-st20-mia-1-0.sprintlink.net (144.232.2.197) 95.726 ms
19• 144.232.18.230 (144.232.18.230) 95.319 ms
20• sl-intel11-86162-0.sprintlink.net (144.228.25.230) 222.493 ms
21• sl-intel11-86162-0.sprintlink.net (144.228.25.230) 222.452 ms *
22• 144.223.162.154 (144.223.162.154) 220.076 ms
23• * * *
24• 201-70-206-6.intelignet.com.br (201.70.206.6) 193.602 ms
25• h200-215-189-118.ipb.diveo.net.br (200.215.189.118) 194.767 ms
26• 201-70-206-6.intelignet.com.br (201.70.206.6) 192.236 ms
27• 200.143.0.186 (200.143.0.186) 193.174 ms 192.314 ms 192.265 ms

The traceroute from the www4 server is not getting there properly, since there are several MPLS statements that should not have been leaking in the traceroute. The issue is affecting the particular Telefonica network inside Brazil, and it looks like there is a routing loop between the Telefonica edge network and the Diveo access network. Since Telefonica seems to be their upstream provider, they should be in a better position to ask for the repair of the routing issue.

traceroute from www4 to centrex.nexus.net.br (200.143.0.186), 30 hops max, 40 byte packets
1• 67-231-245-209.turnkeyinternet.net (67.231.245.209) 0.718 ms 0.690 ms 1.179 ms
2• c6509-ny1-i0ge11.turnkeyinternet.net (208.85.1.9) 0.978 ms 0.646 ms 0.651 ms
3• jm20-ny1-ge-0-1-0.turnkeyinternet.net (64.128.116.1) 0.586 ms 0.547 ms 0.813 ms
4• turnkey-ge-rtr1.alb.twtelcom.net (66.195.77.149) 0.581 ms 0.608 ms 0.564 ms
5• ash1-pr2-xe-1-2-0-0.us.twtelecom.net (66.192.245.102) 9.362 ms 9.455 ms 9.570 ms
6• Xe3-0-3-0-grtmiabr4.red.telefonica-wholesale.net.122.142.94.in-a (94.142.122.162) 41.107 ms
7• Xe10-2-0-0-grtmiabr6.red.telefonica-wholesale.net (213.140.36.230) 58.088 ms
8• Xe4-1-0-0-grtmiabr4.red.telefonica-wholesale.net (213.140.36.178) 43.701 ms
9• Xe5-0-1-0-grtmiabr3.red.telefonica-wholesale.net (84.16.14.41) 159.192 ms
10• Xe6-0-3-0-grtsaosi2.red.telefonica-wholesale.net.123.142.94.in-a (94.142.123.141) 152.044 ms
11• Xe1-2-0-0-grtmiabr4.red.telefonica-wholesale.net (84.16.14.13) 47.094 ms
MPLS Label=369680 CoS=5 TTL=1 S=0
12• Xe0-0-0-0-grtsaosi3.red.telefonica-wholesale.net (213.140.36.66) 154.041 ms
13• Xe10-0-0-0-grtmiabr6.red.telefonica-wholesale.net (84.16.14.6) 56.371 ms
14• Xe5-0-1-0-grtmiabr3.red.telefonica-wholesale.net (84.16.14.41) 205.575 ms
MPLS Label=332032 CoS=5 TTL=1 S=0
15• TEBRASIL-0-0-6-0-grtsaosi3.red.telefonica-wholesale.net (213.140.39.82) 152.986 ms
16• Xe1-1-2-0-grtsaosi2.red.telefonica-wholesale.net (213.140.36.14) 162.304 ms 160.029 ms
MPLS Label=305568 CoS=5 TTL=1 S=0
17• Xe1-0-2-0-grtsaosi3.red.telefonica-wholesale.net (213.140.49.98) 164.163 ms
18•  TE-Brasil-1-0-6-0-grtsaosi3.red.telefonica-wholesale.net (213.140.51.226) 152.337 ms 158.791 ms
19• TEBRASIL-0-0-6-0-grtsaosi3.red.telefonica-wholesale.net (213.140.39.82) 199.196 ms
20• 201-63-54-58.customer.tdatabrasil.net.br (201.63.54.58) 151.150 ms
21• 201-63-253-182.customer.tdatabrasil.net.br (201.63.253.182) 159.143 ms
22• h200-215-189-106.ipb.diveo.net.br (200.215.189.106) 153.563 ms
23• 201-63-54-58.customer.tdatabrasil.net.br (201.63.54.58) 157.762 ms
24• h200-215-189-106.ipb.diveo.net.br (200.215.189.106) 161.759 ms
25• * * *
26• h200-215-189-106.ipb.diveo.net.br (200.215.189.106) 161.114 ms 161.323 ms 161.195 ms
15• * * *
16• * * *
17• * * *
done ...

RE: What´s happening with www4 Server ?

Issues
No records in www4.
centrex.nexus.net.br
ser.sipcode.com.br

No records in www2.
voip510.com

Every hour adds to the list of logs off the server.
It worked all stopped suddenly
Please some solution before further increase the
list and get it all off




add


Tip ... At the time of registration of the trunk that create such an option to choose which server you want to register? Or something like that to release the use of two linked accounts or even something better why not add a server here or near here in Brazil is already time for new changes in Brazil do not have more clients because the server here in Brazil to do that and pbxes server with very expensive here would be a revolution. Please greater attention to our case the thing ta getting worse (sorry my bad english translated by google)

This post has been edited 1 time(s), it was last edited by dam on 02.11.2010 at 15:56.

RE: What´s happening with www4 Server ?

I have the same problem.

Please help us

RE: What´s happening with www4 Server ?

damape,

What exactly do you mean with the phrase "No records in www4"? Is it that trunks from these ITSPs can't register to the www4 & www2 servers? Can these trunks register on the european www1 & www3 servers? I know they are far from Brazil, but it's only a test.

We are here to help, but as I explained in my previous message, there is nothing for us to fix regarding this issue. It's not that we don't want to help, but that we cannot. This is a networking issue inside Brazil as far as the traceroutes allow us to see, for centrex.nexus.net.br. There seems to be a routing loop starting from hop 8 and continuing down. This should be affecting all the clients of the centrex.nexus.net.br service in North America. So the ITSP should be aware of this issue and ask its' upstream providers to fix it.

traceroute from www4(NY) to centrex.nexus.net.br (200.143.0.186), 30 hops max, 40 byte packets
01• 67-231-245-209.turnkeyinternet.net (67.231.245.209) 0.696 ms 0.692 ms 0.757 ms
02• c6509-ny1-i0ge11.turnkeyinternet.net (208.85.1.9) 0.546 ms 0.652 ms 0.636 ms
03• jm20-ny1-ge-0-1-0.turnkeyinternet.net (64.128.116.1) 0.562 ms 0.887 ms 0.568 ms
04• turnkey-ge-rtr1.alb.twtelcom.net (66.195.77.149) 0.568 ms 0.625 ms 0.996 ms
05• ash1-pr2-xe-1-2-0-0.us.twtelecom.net (66.192.245.102) 9.602 ms 9.647 ms 9.556 ms
06• Xe1-1-0-0-grtwaseq5.red.telefonica-wholesale.net.14.16.84.in-add (84.16.14.214) 43.865 ms 22.089 ms 43.735 ms
MPLS Label=510772 CoS=5 TTL=1 S=0
07• Xe1-0-0-0-grtsaosi3.red.telefonica-wholesale.net (213.140.36.70) 148.296 ms
08• Xe5-0-1-0-grtmiabr3.red.telefonica-wholesale.net (84.16.14.41) 158.911 ms
09• Xe2-0-0-0-grtmiabr5.red.telefonica-wholesale.net (84.16.14.198) 55.105 ms
10• Xe4-0-0-0-grtsaosi3.red.telefonica-wholesale.net (84.16.15.57) 148.003 ms
11• Xe5-0-1-0-grtmiabr3.red.telefonica-wholesale.net (84.16.14.41) 162.193 ms
12• Xe1-1-2-0-grtsaosi2.red.telefonica-wholesale.net (213.140.36.14) 151.016 ms
MPLS Label=305568 CoS=5 TTL=1 S=0
13• 201-63-253-182.customer.tdatabrasil.net.br (201.63.253.182) 148.581 ms
14• Xe2-3-0-0-grtsanem2.red.telefonica-wholesale.net (84.16.15.37) 153.302 ms 148.730 ms
MPLS Label=352784 CoS=5 TTL=1 S=0
15• Xe1-0-1-0-grtsaosi2.red.telefonica-wholesale.net (94.142.124.221) 162.522 ms
16• Xe0-0-4-0-grtsaosi3.red.telefonica-wholesale.net.118.142.94.in-a (94.142.118.85) 234.798 ms
17• 201-63-253-182.customer.tdatabrasil.net.br (201.63.253.182) 148.473 ms
18• Xe0-0-4-0-grtsaosi3.red.telefonica-wholesale.net.118.142.94.in-a (94.142.118.85) 162.158 ms
19• 201-63-54-58.customer.tdatabrasil.net.br (201.63.54.58) 150.162 ms 154.248 ms
20• 201-63-54-58.customer.tdatabrasil.net.br (201.63.54.58) 147.281 ms *
21• 201-63-253-182.customer.tdatabrasil.net.br (201.63.253.182) 151.103 ms
22• 201-63-253-182.customer.tdatabrasil.net.br (201.63.253.182) 154.752 ms *
23• 201-63-54-58.customer.tdatabrasil.net.br (201.63.54.58) 161.338 ms
24• 201-63-54-58.customer.tdatabrasil.net.br (201.63.54.58) 161.530 ms *
25 * * *
26 * * *

The traceroute to the ser.sipcode.com.br ITSP is short and does not point to any issues. But this does not mean there are no issues on this route, or the reverse route from ser.sipcode.com.br to the www4 server, which we cannot see.

traceroute from www4(NY) to ser.sipcode.com.br (200.152.125.221), 30 hops max, 40 byte packets
1• 67-231-245-209.turnkeyinternet.net (67.231.245.209) 1.726 ms 1.561 ms 5.566 ms
2• c6509-ny1-i0ge11.turnkeyinternet.net (208.85.1.9) 0.898 ms 0.676 ms 0.637 ms
3• jm20-ny1-ge-0-1-0.turnkeyinternet.net (64.128.116.1) 0.521 ms 0.570 ms 0.547 ms
4• so-5-1-2.ar4.JFK1.gblx.net (64.215.182.249) 3.795 ms 3.899 ms 3.855 ms
5• te3-3-10G.asr1.GIG1.gblx.net (67.17.71.134) 118.676 ms 118.746 ms 118.109 ms
6• MLS-Wireless.Po2.432.asr1.GIG1.gblx.net (64.208.222.222) 118.820 ms 119.177 ms 119.022 ms
7• mlsrj200152125p002.static.mls.com.br (200.152.125.2) 119.491 ms 119.599 ms 119.433 ms
8• mlsrj200152125p221.static.mls.com.br (200.152.125.221) 119.841 ms 119.788 ms 119.996 ms
done ...

The traceroute to voip510.com ITSP does not complete, but this might not be the cause of the SIP packets not reaching the www2 server. As I said previously, it is unfortunate that can't see the reverse path of packets from voip510.com to the www2 server. But your ITSPs can. So ask them to traceroute towards www4[.]pbxes.com and www2[.]pbxes.com (without the [] brackets) and to send you the results. At the same time ask them, how come you can't register to their server from these IPs. They should have an answer, or look into this issue and get back to you with the answer.

traceroute from www2(Seattle) to voip510.com (187.16.16.86), 30 hops max, 40 byte packets
01• 63.223.127.1 (63.223.127.1) 0.865 ms 1.159 ms 1.355 ms
02• agg1-sea-g1-33.bb.spectrumnet.us (208.76.184.209) 0.915 ms 1.084 ms 1.076 ms
03• cr2-sea-A-p10.bb.spectrumnet.us (208.76.153.41) 0.840 ms 0.885 ms 0.948 ms
04• 208.173.50.57 (208.173.50.57) 0.840 ms 0.991 ms 1.019 ms
05• cr1-pos-0-11-1-0.Seattle.savvis.net (204.70.198.121) 3.299 ms
06• cr1-pos-0-3-0-1.Seattle.savvis.net (208.172.83.62) 3.288 ms 3.275 ms
07• cr1-bundle-pos2.Washington.savvis.net (204.70.200.90) 68.646 ms 68.105 ms 68.339 ms
08• ber1-tengige-4-0-1.virginiaequinix.savvis.net (204.70.197.241) 69.144 ms 69.112 ms 69.736 ms
09• (213.140.55.153) 69.944 ms 69.932 ms 69.919 ms
10• Xe2-0-0-0-grtmiabr5.red.telefonica-wholesale.net (84.16.14.198) 97.406 ms 97.367 ms 97.370 ms
11• Xe5-0-1-0-grtmiabr3.red.telefonica-wholesale.net (84.16.14.41) 256.469 ms 256.471 ms 256.459 ms
12• Xe1-1-2-0-grtsaosi2.red.telefonica-wholesale.net (213.140.36.14) 230.851 ms 226.752 ms 226.733 ms
13• Xe0-0-4-0-grtsaosi3.red.telefonica-wholesale.net.118.142.94.in-addr.arpa (94.142.118.85) 227.518 ms 302.025 ms 302.012 ms
14• TEBRASIL-0-1-2-0-grtsaosi3.red.telefonica-wholesale.net (213.140.39.138) 225.293 ms 225.488 ms 225.460 ms
15• 201-0-5-190.dsl.telesp.net.br (201.0.5.190) 222.948 ms 223.239 ms 223.186 ms
16• 187-11-166-2.dsl.telesp.net.br (187.11.166.2) 217.309 ms 217.310 ms 217.305 ms
17• uol-core2-6.ixc.uol.com.br (200.221.30.238) 218.686 ms 218.960 ms 219.232 ms
18 * * *
19 * * *

RE: What´s happening with www4 Server ?

www3 WWW1 and works perfect.
In www4. of the problems with the accounts
talky: centrex.nexus.net.br
Sipcode: ser.sipcode.com.br
Does not work.

www2.
Everything works less
skyfone: voip510.com


Do what I am using that.
so far without a server solution in Brazil out of the question?

They could then release the use of two accounts pbxes together.
i take note of the problems with accounts in one place and into another account in the main www4. (Closer to Brazil)

Thanks.

This post has been edited 2 time(s), it was last edited by dam on 08.11.2010 at 16:11.

RE: What´s happening with www4 Server ?

To briefly answer the question of possibly locating a server in Brazil, or any other country in South America, we are currently exploring the possibility, but the cost of getting a reliable solution is a major concern.

In essence we are looking for a server, from a hosting company which has reliable interconnections with all the major ISPs in South America. So, if anyone can recommend reliable hosting providers, we would like to hear about them.

RE: What´s happening with www4 Server ?

Good news. Do you have any requirement something? Let's get good servants here.

RE: What´s happening with www4 Server ?

Really that`s a good news !

RE: What´s happening with www4 Server ?

I hate to put a damper on your enthusiasm, but it is not going to be good news, until we actually get the server(s) hosted in reliable data centers, which don't cost us an arm & a leg to mantain.

South America is a tough place to do business, with import duties ranging from 30% to 50%. Any kind of service in South America tends to be overpriced & underperforming, for the amount of money paid, in comparison to other countries. So until we find a reliable hosting provider who will let us use a decent server, with proper interconnections to a http://ptt.br IX, don't break open the Champaign bottle.

It will be like looking for a needle in the haystack, so start asking around about reliable hosting providers that rent decent servers on a monthly basis, anywhere there is good connectivity in Brazil or Argentina. The PBXes' requirements for servers & bandwidth are rather high, but the budget per server is rather limited.

So start inquiring, but don't get ready to celebrate, this is going to be an arduous process.

RE: What´s happening with www4 Server ?

understood, and as always good to dream it then we search for a server that is really good. we have to take into account that the U.S. dollar is worth more than the REAL .. So do not go out really so expensive. Yes it would be a very good server can try here? no expense!Yes it would be a very good server can try here? no expense!