Hey David have you tested the following scenarios: 1) Out of area Cell phone roams into the affected market(s) 2) Assigning a Wash DC DID to a phone in your PDX market and testing with a PDX cell phone. In the first case the out of area phone will use a TLDN that is typically a non-cellular DID (it is typically part of the wireline network for the wireless carrier). The second scenario should remove the local market handoff between the cell carriers and level3. You might also try a Wash DC assigned cell phone used in PDX to the Wash DC DID. We had a similar problem with Nextel phones to Level3 DID's which turned out to be a SIP trunk issue between Sprint and Level3 (it was on Sprint's side). We had to get Level3 to open a ticket with Sprint for testing. Since this is all carriers, it points to a Level3 issue (if they are L3 DID's on your VOIP phones) Jon Schnelz -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of voiceops-request at voiceops.org Sent: Thursday, October 06, 2011 6:31 AM To: voiceops at voiceops.org Subject: VoiceOps Digest, Vol 28, Issue 4 Send VoiceOps mailing list submissions to voiceops at voiceops.org To subscribe or unsubscribe via the World Wide Web, visit https://puck.nether.net/mailman/listinfo/voiceops or, via email, send a message with subject or body 'help' to voiceops-request at voiceops.org You can reach the person managing the list at voiceops-owner at voiceops.org When replying, please edit your Subject line so it is more specific than "Re: Contents of VoiceOps digest..." Today's Topics: 1. AT&T Right of Ways (Carlos Alcantar) 2. Re: AT&T Right of Ways (Paul Timmins) 3. Re: AT&T Right of Ways (Carlos Alcantar) 4. Audio latency in DC area, Part 2 (David Hiers) ---------------------------------------------------------------------- Message: 1 Date: Wed, 5 Oct 2011 20:17:11 +0000 From: Carlos Alcantar <carlos at race.com> To: VoiceOps <voiceops at voiceops.org> Subject: [VoiceOps] AT&T Right of Ways Message-ID: <CAB20AED.474CC%carlos at race.com> Content-Type: text/plain; charset="us-ascii" Anyone familiar with doing all the paper work and design work for using the right of ways in the AT&T states? We have the row in our ICA amendments and looking for the first time to possibly use them. Carlos Alcantar Race Communications / Race Team Member 101 Haskins Way, So. San Francisco, CA. 94080 Phone: +1 415 376 3314 Fax: +1 650 246 8901 / carlos at race.com / www.race.com<http://www.race.com/>
Thanks for the feedback!!! David On Thu, Oct 6, 2011 at 6:54 AM, Jon Schnelz <jschnelz at enterprisepcs.com> wrote:
Hey David have you tested the following scenarios:
1) Out of area Cell phone roams into the affected market(s) 2) Assigning a Wash DC DID to a phone in your PDX market and testing with a PDX cell phone.
In the first case the out of area phone will use a TLDN that is typically a non-cellular DID (it is typically part of the wireline network for the wireless carrier).
The second scenario should remove the local market handoff between the cell carriers and level3. You might also try a Wash DC assigned cell phone used in PDX to the Wash DC DID.
We had a similar problem with Nextel phones to Level3 DID's which turned out to be a SIP trunk issue between Sprint and Level3 (it was on Sprint's side). We had to get Level3 to open a ticket with Sprint for testing. Since this is all carriers, it points to a Level3 issue (if they are L3 DID's on your VOIP phones)
Jon Schnelz
Message: 4 Date: Thu, 6 Oct 2011 06:30:32 -0700 From: David Hiers <hiersd at gmail.com> To: VoiceOps at voiceops.org Subject: [VoiceOps] Audio latency in DC area, Part 2 Message-ID: ? ? ? ?<CANpkwCZ2ZxzLVmN4aOhW2pr4Rf403KpHoKxtB7KgUD3_gvVadg at mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1
Hi folks,
I want to send out another shout regarding an on-going issue in the DC area. We've got excessive audio delay between our voip phones and cell phones. Packet specs (loss, jitter, etc) are fine, ping times for everything rock.
Specifically, these rate centers are involved:
DALE CITY HERNDON MANASSAS WSNGTNZN08 WSNGTNZN17
but NOT this nearby one:
TRIANGLE
Here are some of the voip NPA/NXXs involved:
703647 703880 703508 703647 240283
The issue affects any cell in the area. ?All our test calls are local; the cell phone is in the same building as the voip phone. The cell phone has and has strong signal.
We've measured audio latency of up to 550ms; it is just impossible to hold a conversation.
In all cases:
1. VOIP-to-CELL calls are slower than CELL-to-VOIP 2. 3G is slower than GSM 3. PSTN-VOIP calls are good 4. PSTN-CELL calls are good 5 ?Only VOIP-CELL calls are bad
Anyone got any issues in the DC area? ?Would your users report this kind of problem? ?The DC area comes in near the bottom of the list on most of the "bad cell phone area" studies, so most cell users there have had tolerance of this sort of thing beat into them over the years.
Thanks,
David
------------------------------
Hi David, I just performed a test from my Sprint phone in DC to a Herndon rate center Level3 DID. Audio was not delayed. The RTP stream came from a Washington, DC Originated IP on Level3's network as well. Contact me directly if you'd like me to place any test calls to your numbers. Regards, Jared Geiger On Thu, Oct 6, 2011 at 10:13 AM, David Hiers <hiersd at gmail.com> wrote:
Thanks for the feedback!!!
David
On Thu, Oct 6, 2011 at 6:54 AM, Jon Schnelz <jschnelz at enterprisepcs.com> wrote:
Hey David have you tested the following scenarios:
1) Out of area Cell phone roams into the affected market(s) 2) Assigning a Wash DC DID to a phone in your PDX market and testing with a PDX cell phone.
In the first case the out of area phone will use a TLDN that is typically a non-cellular DID (it is typically part of the wireline network for the wireless carrier).
The second scenario should remove the local market handoff between the cell carriers and level3. You might also try a Wash DC assigned cell phone used in PDX to the Wash DC DID.
We had a similar problem with Nextel phones to Level3 DID's which turned out to be a SIP trunk issue between Sprint and Level3 (it was on Sprint's side). We had to get Level3 to open a ticket with Sprint for testing. Since this is all carriers, it points to a Level3 issue (if they are L3 DID's on your VOIP phones)
Jon Schnelz
Message: 4 Date: Thu, 6 Oct 2011 06:30:32 -0700 From: David Hiers <hiersd at gmail.com> To: VoiceOps at voiceops.org Subject: [VoiceOps] Audio latency in DC area, Part 2 Message-ID: < CANpkwCZ2ZxzLVmN4aOhW2pr4Rf403KpHoKxtB7KgUD3_gvVadg at mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1
Hi folks,
I want to send out another shout regarding an on-going issue in the DC area. We've got excessive audio delay between our voip phones and cell phones. Packet specs (loss, jitter, etc) are fine, ping times for everything rock.
Specifically, these rate centers are involved:
DALE CITY HERNDON MANASSAS WSNGTNZN08 WSNGTNZN17
but NOT this nearby one:
TRIANGLE
Here are some of the voip NPA/NXXs involved:
703647 703880 703508 703647 240283
The issue affects any cell in the area. All our test calls are local; the cell phone is in the same building as the voip phone. The cell phone has and has strong signal.
We've measured audio latency of up to 550ms; it is just impossible to hold a conversation.
In all cases:
1. VOIP-to-CELL calls are slower than CELL-to-VOIP 2. 3G is slower than GSM 3. PSTN-VOIP calls are good 4. PSTN-CELL calls are good 5 Only VOIP-CELL calls are bad
Anyone got any issues in the DC area? Would your users report this kind of problem? The DC area comes in near the bottom of the list on most of the "bad cell phone area" studies, so most cell users there have had tolerance of this sort of thing beat into them over the years.
Thanks,
David
------------------------------
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
participants (3)
-
hiersd＠gmail.com -
jared＠compuwizz.net -
jschnelz＠enterprisepcs.com