Re: [Asterisk-Users] Broadvoice problems again Attn: James
I can attest that my SUPPORTED device never lost service. This was a Cisco 7960 configured with their TFTP config file (although from my tftp server, I intercepted the file before allowing the phone to use it, but didn't make any changes). It uses the sip server sip.broadvoice.com via the SRV records for the outbound sip proxy listed as as proxy.broadvoice.com So, I chalked it up to confusion, they changed the rules and prevented direct connections to their sip server. Their supported devices worked fine using their configuration because they the outbound proxy. I will also admit that using a single phone on their system is totally useless, but I plugged it in to try and narrow down the problem, within hours of the outage start on Sunday evening. Charlie Hedlin Brian McManus wrote: I do have a few questions about the broadvoice outage: 1) Did supported devices ever loose service? 2) IDo supported devices use the same SIP server, aka, the SIP SRV entries in sip.broadvoice.com, as asterisk would have if configured properly? 3) Would the asterisk SIP SRVLOOKUP entry prevent non-supported devices from loosing service during that outage? I'm only curious because I may be giving them service, as they are the only VoIP provider with number portability that will allow asterisk, and third party SIP devices. However, long outages are of course unacceptable If there supported devices never lost service, i'm willing to chalk it up to a little confusion, and assume that properly configuring DNS SRV Lookups is how I will prevent such an outage in the future. Brian James Jones wrote: not sure I know is pinging does not work. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wolfgang S. Rupprecht Sent: Monday, July 26, 2004 5:00 PM To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] Broadvoice problems again Attn: James [EMAIL PROTECTED] (James Jones) writes: you can not ping that address because ICMP is turned off. Do you mean *all* ICMP is turned off or just icmp-echo-request / icmp-echo-reply? -wolfgang ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Broadvoice problems again Attn: James
not sure I know is pinging does not work. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wolfgang S. Rupprecht Sent: Monday, July 26, 2004 5:00 PM To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] Broadvoice problems again Attn: James [EMAIL PROTECTED] (James Jones) writes: you can not ping that address because ICMP is turned off. Do you mean *all* ICMP is turned off or just icmp-echo-request / icmp-echo-reply? -wolfgang -- Wolfgang S. Rupprechthttp://www.wsrcc.com/wolfgang/ openbsd amd64 http://www.wsrcc.com/wolfgang/ftp/asterisk-openbsd35.patch ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.726 / Virus Database: 481 - Release Date: 7/22/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.726 / Virus Database: 481 - Release Date: 7/22/2004 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Broadvoice problems again Attn: James
I do have a few questions about the broadvoice outage: 1) Did supported devices ever loose service? 2) IDo supported devices use the same SIP server, aka, the SIP SRV entries in sip.broadvoice.com, as asterisk would have if configured properly? 3) Would the asterisk SIP SRVLOOKUP entry prevent non-supported devices from loosing service during that outage? I'm only curious because I may be giving them service, as they are the only VoIP provider with number portability that will allow asterisk, and third party SIP devices. However, long outages are of course unacceptable If there supported devices never lost service, i'm willing to chalk it up to a little confusion, and assume that properly configuring DNS SRV Lookups is how I will prevent such an outage in the future. Brian James Jones wrote: not sure I know is pinging does not work. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wolfgang S. Rupprecht Sent: Monday, July 26, 2004 5:00 PM To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] Broadvoice problems again Attn: James [EMAIL PROTECTED] (James Jones) writes: you can not ping that address because ICMP is turned off. Do you mean *all* ICMP is turned off or just icmp-echo-request / icmp-echo-reply? -wolfgang ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Broadvoice problems again Attn: James
Greetings, C:\ping 147.135.8.129 Pinging 147.135.8.129 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 147.135.8.129: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\ping 147.135.0.129 Pinging 147.135.0.129 with 32 bytes of data: Reply from 147.135.3.6: Destination host unreachable. Reply from 147.135.3.6: Destination host unreachable. Reply from 147.135.3.6: Destination host unreachable. Reply from 147.135.3.6: Destination host unreachable. Ping statistics for 147.135.0.129: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\ The first one is probably a firewall, but the 147.135.0.129 indicates a larger problem. P.S - Can phones that do not support outbound proxy also register at 147.135.8.128 (not just Asterisk?) - Original Message - From: Wolfgang S. Rupprecht [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 26, 2004 1:57 PM Subject: Re: [Asterisk-Users] Broadvoice problems again [EMAIL PROTECTED] (Olle E. Johansson) writes: The easiest first-level hack would be to randomly choose on of the SRV records provided they have the same weight. One of the other posts mentioned their ATA that simply registered with all the addresses. I don't think it would be a big or difficult change to have asterisk register with all the addresses also. I'm not sure what the right thing for outgoing is, or if it is even possible to have asterisk try all the sip servers in parallel, and then blow off the ones that are late in replying. That sounds like a much more involved hack. (I'll try to hack the registration issue here and post some GPL-ed patches if I get it working.) -wolfgang -- Wolfgang S. Rupprechthttp://www.wsrcc.com/wolfgang/ openbsd amd64 http://www.wsrcc.com/wolfgang/ftp/asterisk-openbsd35.patch ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Broadvoice problems again Attn: James
Both the ping timeouts are normal responses. Don't worry. The hosts are there, and functioning. I promise. As far as the outbound proxy question... The key seems to be keeping @sip.broadvoice.com included in the URI while sending the request to the proxy (a .128 address). The only way I've been able to accomplish this is with a hosts file. I'm not quite sure how you'd accomplish this in a phone flying solo. In other words, register [EMAIL PROTECTED], but send the request to proxy.broadvoice.com. It also seems that if a proper SRV record were set up for sip.broadvoice.com, this would work semi-automagically. Assuming the phone supported SRV in DNS. Hope that helps. - Jeff Greetings, C:\ping 147.135.8.129 Pinging 147.135.8.129 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 147.135.8.129: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\ping 147.135.0.129 Pinging 147.135.0.129 with 32 bytes of data: Reply from 147.135.3.6: Destination host unreachable. Reply from 147.135.3.6: Destination host unreachable. Reply from 147.135.3.6: Destination host unreachable. Reply from 147.135.3.6: Destination host unreachable. Ping statistics for 147.135.0.129: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\ The first one is probably a firewall, but the 147.135.0.129 indicates a larger problem. P.S - Can phones that do not support outbound proxy also register at 147.135.8.128 (not just Asterisk?) ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Broadvoice problems again Attn: James
you can not ping that address because ICMP is turned off. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Deon Rodden Sent: Monday, July 26, 2004 2:22 PM To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] Broadvoice problems again Attn: James Greetings, C:\ping 147.135.8.129 Pinging 147.135.8.129 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 147.135.8.129: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\ping 147.135.0.129 Pinging 147.135.0.129 with 32 bytes of data: Reply from 147.135.3.6: Destination host unreachable. Reply from 147.135.3.6: Destination host unreachable. Reply from 147.135.3.6: Destination host unreachable. Reply from 147.135.3.6: Destination host unreachable. Ping statistics for 147.135.0.129: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\ The first one is probably a firewall, but the 147.135.0.129 indicates a larger problem. P.S - Can phones that do not support outbound proxy also register at 147.135.8.128 (not just Asterisk?) - Original Message - From: Wolfgang S. Rupprecht [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 26, 2004 1:57 PM Subject: Re: [Asterisk-Users] Broadvoice problems again [EMAIL PROTECTED] (Olle E. Johansson) writes: The easiest first-level hack would be to randomly choose on of the SRV records provided they have the same weight. One of the other posts mentioned their ATA that simply registered with all the addresses. I don't think it would be a big or difficult change to have asterisk register with all the addresses also. I'm not sure what the right thing for outgoing is, or if it is even possible to have asterisk try all the sip servers in parallel, and then blow off the ones that are late in replying. That sounds like a much more involved hack. (I'll try to hack the registration issue here and post some GPL-ed patches if I get it working.) -wolfgang -- Wolfgang S. Rupprechthttp://www.wsrcc.com/wolfgang/ openbsd amd64 http://www.wsrcc.com/wolfgang/ftp/asterisk-openbsd35.patch ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.726 / Virus Database: 481 - Release Date: 7/22/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.726 / Virus Database: 481 - Release Date: 7/22/2004 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Broadvoice problems again Attn: James
[EMAIL PROTECTED] (James Jones) writes: you can not ping that address because ICMP is turned off. Do you mean *all* ICMP is turned off or just icmp-echo-request / icmp-echo-reply? -wolfgang -- Wolfgang S. Rupprechthttp://www.wsrcc.com/wolfgang/ openbsd amd64 http://www.wsrcc.com/wolfgang/ftp/asterisk-openbsd35.patch ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
