Jump to content

jf15219

S4GRU Premier Sponsor
  • Posts

    94
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by jf15219

  1. Tower is impaired. Hope it does't choose to drive...

     

    <response nebStatus="Success" serviceTrenderCode="333" serviceTrenderMessage="Sprint has a known issue impacting one of your most used towers. See the Service Alert Details section for more information on the known issue. If you have questions about the known issue or need further support, please call Customer Care for assistance (message 333)." serviceTrenderStatus="Success">

    <nebticket etr="2014-10-26T14:06:00-05:00" endDateTime="9999-12-31T17:59:59-06:00" servicesAffected="Voice" startDateTime="2014-10-23T14:06:00-05:00" statusUpdateDateTime="2014-10-26T05:26:50-05:00" statusUpdateNote="We are currently experiencing an outage across the market. Customers may experience increased dropped calls, blocked calls, no service, or roaming, until the impairment is resolved." ticketInformation="Thank you for your patience while we work to improve the performance on this tower. While we do not have a current estimated time of resolution for this issue, please rest assured that our Engineers are aware & fully engaged. While our Engineers work on a solution, you may experience intermittent service issues. You can continue to check Sprint Zone for the most recent status available." ticketLevel="CASCADE" ticketNumber="3669037" ticketStatus="O" ticketType="Other:"/>
    <nebticket etr="2014-10-23T00:00:00-05:00" endDateTime="2014-10-23T11:04:34-05:00" servicesAffected="Voice and Data" startDateTime="2014-10-22T19:00:00-05:00" statusUpdateDateTime="2014-10-23T10:45:29-05:00" statusUpdateNote="The tower is currently impaired. Customers may experience increased dropped calls, blocked calls, no service, roaming, loss of SDC, loss of 3G, EVDO, and LTE, or slow data connections until the impairment is resolved." ticketInformation="Thank you for your patience while we worked on this tower. Our Engineers have resolved the issue and your services should be back up & running. We value our customers and it is our top priority to deliver the best network experience. If we have not fully addressed your issue, please feel free to contact Customer Care."ticketLevel="MARKET" ticketNumber="3788591" ticketStatus="C" ticketType="Single Cellsite:"/>
    </response>
    • Like 2
  2. Plus the slightly overpriced accessories :P they make tons if money in accessories like any retail center.

     

    Money well spent; I've used their super liberal 1 year guarantee multiple times! (Most recently for my Dot View case which began to fall apart...)

     

    Ill let you in on a secret.....sprints wholesale price was $65

     

    So even when did the $100 bundle with the m8 hk and the current 150 promo they are making a killing.

     

     

    Curious, is Sprint's wholesale cheaper than others'?

  3. Downtown Pittsburgh had had plenty of work. They just couldn't bring things online until the entire cluster was complete.

     

    Sent from my Nexus 5

     

    I'm well aware of the cluster issues. I'm also aware that service was *emergency* bad. Until I got a spark phone, SMS wouldn't work and calls were sometimes not possible from PNC Park during games.... also problems driving through town without dropping calls at least twice...  

     

    Side question: the towers which cover the various tunnels. Are they not part of any cluster?

  4. Work is still on going in Vegas. Please give Sprint a chance as they are working hard to get things done. Vegas service has improved dramatically in the last two years, and if you have a triband phone, you probably will do better if you turn off LTE while you are at your hotel and the Strip if you keep losing signal.

     

     

    Sent from Josh's iPhone 5S using Tapatalk 2

     

    Baffled by the biggest problem areas being the last to get done. Same here, in Pittsburgh; downtown was untouched until mere days ago.

     

    As it is, so sad to read this. Flying to Vegas on Tuesday... Was hoping for my phone to not be a burning hot paperweight with rapidly draining battery as it has been for years when I vacation there...

    • Like 1
  5. <response serviceTrenderStatus="Success" serviceTrenderMessage="Sprint is seeing indications that your device could be impacting your voice experience. Please verify that your Software and PRL are both up to date by using the Voice Network Details section below. If additional support is needed, please visit your local Sprint store for assistance (message 213)." serviceTrenderCode="213" nebStatus="Success"/>

     

    Can someone help with what this means? Device in question is up to date with software and PRL...

  6. Service Alerts show up automatically only for numbers that are directly affected. I.E. the tower is a top 5 tower used by the number, or the issue is Market-wide. a Care or TS agent can look up other specific alerts opened, but the output Service Trender uses in Sprint Zone only automatically pulls up the ones directly affecting the top used towers.

    Ticket level is listed as "market" in this one though. I've seen this ticket before (it appears and disappears) and I'm exclusively in the Pittsburgh market...

  7. These things in Sprint Zone only show up intermittently, which is odd. For example the following, only shows up for a friend's number, although we are both in the same market and I'm definitely having the problem too: Also, statusUpdateDateTime

    remains the same even though there clearly has been a change...

     

    <response serviceTrenderStatus="Success" serviceTrenderMessage="Sprint has a known issue impacting one of your most used towers. See the Service Alert Details section for more information on the known issue. If you have questions about the known issue or need further support, please visit your local Sprint store for assistance (message 313)." serviceTrenderCode="313" nebStatus="Success">

    <nebticket ticketType="Other:Fast Busy/Reorder" ticketStatus="O" ticketNumber="69353" ticketLevel="MARKET" ticketInformation="Thank you for your patience while we work to improve the performance on this tower. Our records indicate the estimated time of resolution is Thu, 1 May 2014. While our Engineers work on a solution, you may experience intermittent service issues. You can continue to check Sprint Zone for the most recent status available." statusUpdateNote="Customers may hear DTMF tones (keypad sounds) such as a long sound as if someone is holding down a number, or minute beeps while on the phone. Customer may not be able to navigate a business?s menu system ( IVR) using the keyboard tones ( DTMF tones). The network is currently being investigated."statusUpdateDateTime="2014-02-21T13:50:53-06:00" startDateTime="2013-12-15T18:00:00-06:00" servicesAffected="Voice" endDateTime="9999-12-31T17:59:59-06:00" etr="2014-05-01T11:20:00-05:00"/>
    </response>

     

  8. Grumble. Snarl. Hiss. Promised March fix now listed for May? Can someone help me understand how this is other than incompetence? <response serviceTrenderStatus="Success" serviceTrenderMessage="Sprint has a known issue impacting one of your most used towers. See the Service Alert Details section for more information on the known issue. If you have questions about the known issue or need further support, please call Customer Care for assistance (message 333)." serviceTrenderCode="333" nebStatus="Success"><nebticket ticketType="Other:Fast Busy/Reorder" ticketStatus="O" ticketNumber="69353" ticketLevel="MARKET" ticketInformation="Thank you for your patience while we work to improve the performance on this tower. Our records indicate we will be completed during the month of May 2014. While our Engineers work on a solution, you may experience intermittent service issues. You can continue to check Sprint Zone for the most recent status available." statusUpdateNote="Customers may hear DTMF tones (keypad sounds) such as a long sound as if someone is holding down a number, or minute beeps while on the phone. The network is currently being investigated. " statusUpdateDateTime="2014-02-21T13:50:53-06:00" startDateTime="2013-12-15T18:00:00-06:00" servicesAffected="Voice" endDateTime="9999-12-31T17:59:59-06:00" etr="2014-05-01T11:20:00-05:00"/></response>

  9. Thanks for this, I called Care today and referenced that ticket number. They said the issue has also been reported in the Chicago market, and I let them know I've seen it in the East Texas and Louisiana markets and that Google Voice is not the cause. They opened additional tickets.

    I wonder what the common factor is? For reference, I'm in the Pittsburgh market...

×
×
  • Create New...