dan
Registration Date: 01.01.1970
Posts:
|
|
|
19.10.2010 01:54 |
|
tij
Grünschnabel
Registration Date: 28.10.2007
Posts: 137
|
|
|
19.10.2010 15:25 |
|
req
Registration Date: 01.01.1970
Posts:
|
|
|
20.10.2010 23:42 |
|
dam
Grünschnabel
Registration Date: 30.04.2009
Posts: 17
|
|
|
21.10.2010 20:56 |
|
dan
Registration Date: 01.01.1970
Posts:
|
|
|
28.10.2010 02:44 |
|
mar
Registration Date: 01.01.1970
Posts:
|
|
|
29.10.2010 16:11 |
|
tij
Grünschnabel
Registration Date: 28.10.2007
Posts: 137
|
|
|
29.10.2010 16:22 |
|
dam
Grünschnabel
Registration Date: 30.04.2009
Posts: 17
|
|
|
29.10.2010 17:13 |
|
mar
Registration Date: 01.01.1970
Posts:
|
|
|
29.10.2010 17:30 |
|
tij
Grünschnabel
Registration Date: 28.10.2007
Posts: 137
|
|
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.
|
|
29.10.2010 18:49 |
|
Dia
Premium Account
Registration Date: 03.03.2006
Posts: 1443
|
|
|
30.10.2010 10:27 |
|
dam
Grünschnabel
Registration Date: 30.04.2009
Posts: 17
|
|
|
01.11.2010 16:53 |
|
tij
Grünschnabel
Registration Date: 28.10.2007
Posts: 137
|
|
|
02.11.2010 23:17 |
|
Dia
Premium Account
Registration Date: 03.03.2006
Posts: 1443
|
|
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 * * *
|
|
03.11.2010 13:20 |
|
dam
Grünschnabel
Registration Date: 30.04.2009
Posts: 17
|
|
|
08.11.2010 16:05 |
|
Dia
Premium Account
Registration Date: 03.03.2006
Posts: 1443
|
|
|
10.11.2010 16:44 |
|
dam
Grünschnabel
Registration Date: 30.04.2009
Posts: 17
|
|
|
12.11.2010 13:57 |
|
tij
Grünschnabel
Registration Date: 28.10.2007
Posts: 137
|
|
|
12.11.2010 20:56 |
|
Dia
Premium Account
Registration Date: 03.03.2006
Posts: 1443
|
|
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.
|
|
14.11.2010 02:59 |
|
dam
Grünschnabel
Registration Date: 30.04.2009
Posts: 17
|
|
|
14.11.2010 23:48 |
|
|
|
|
|
|
|