Jump to content

Service Alerts in Sprint Zone


Recommended Posts

<nebticket ticketType="Other:Blocked calls" ticketStatus="C" ticketNumber="2027892" ticketLevel="NATIONAL" ticketInformation="Thank you for your patience while our Engineers worked to resolve this issue. Our records indicated that the issue has been resolved and your services should be back up and 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." statusUpdateNote="At 2013/11/25 01:03:40 we experienced the following Problem(s) in the Kansas : Kansas City Market: Voice (Blocked calls) FSM Alarm raised Application not reachable . Under investigation by NGVN VoIP NOC, NTAC, Vendor" statusUpdateDateTime="2013-11-24T19:55:45-06:00"startDateTime="2013-11-24T19:03:00-06:00" servicesAffected="Voice" endDateTime="2013-11-24T20:47:02-06:00" etr="2013-11-25T03:56:02-06:00"/>

Link to comment
Share on other sites

ticketType="Other:Blocked calls" ticketStatus="C" ticketNumber="2027892" ticketLevel="NATIONAL" ticketInformation="Thank you for your patience while our Engineers worked to resolve this issue. Our records indicated that the issue has been resolved and your services should be back up and 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." statusUpdateNote="At 2013/11/25 01:03:40 we experienced the following Problem(s) in the Kansas : Kansas City Market: Voice (Blocked calls) FSM Alarm raised Application not reachable . Under investigation by NGVN VoIP NOC, NTAC, Vendor" statusUpdateDateTime="2013-11-24T19:55:45-06:00"startDateTime="2013-11-24T19:03:00-06:00" servicesAffected="Voice" endDateTime="2013-11-24T20:47:02-06:00" etr="2013-11-25T03:56:02-06:00"/>

Yep. I saw that too. Odd alert.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

Link to comment
Share on other sites

On the app you wouldn't know it was for Kansas though. Nice to see the full text.

Yeah, for sure. Thanks for reverse engineering the alerts so I could see local alerts for my area. I finally have an update on the Visalia area. They said that etr is scheduled for 2-22-14 for at least 2 sites in Visalia. The excitement is brewing. :)

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

Link to comment
Share on other sites

I uninstalled the app and tried this only to get a blank page. Before I uninstalled the app there was a closed ticket

 

Sent from Evo

Interesting.  I can confirm it works without the app though.  No app on the Nexus 5 and it works for me.

Link to comment
Share on other sites

On the app you wouldn't know it was for Kansas though. Nice to see the full text.

 

Except that I see that exact same message when I punch in my very-much-not-Kansas number..? Even though it is listed as a "Kansas City market" outage, does that "ticketLevel=NATIONAL" flag attach it to everyone? I don't think a KC tower is my most used tower, since I've never been there..  :)

 

-Mike

Link to comment
Share on other sites

Except that I see that exact same message when I punch in my very-much-not-Kansas number..? Even though it is listed as a "Kansas City market" outage, does that "ticketLevel=NATIONAL" flag attach it to everyone? I don't think a KC tower is my most used tower, since I've never been there.. :)

 

-Mike

Same here. I see it on the app as well. It doesn't show the Kansas part though but the ticket number is the same.

Link to comment
Share on other sites

wow, a useful purpose for Sprint Zone who knew. I restored my bacup from TI backup, my eta of completion says Feb 2014. My tower has been borked Since July. Would be nice if it showed the actual tower but this is a good start.

Link to comment
Share on other sites

 

<nebticket ticketType="Single Cellsite:Intermittent service" ticketStatus="C" ticketNumber="1804750" ticketLevel="CASCADE" 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." statusUpdateNote="At 2013/11/26 05:20:01 we experienced the following Problem(s) in the Pittsburgh : Pittsburgh Market: Single Cellsite (Intermittent service) The tower is currently impaired. The customer may experience increased dropped calls, blocked calls, roaming, or no service, until the impairment is resolved. Advise the customer of the expected experience, the ETR, and that network has been notified that they are impacted by this impairment, the customer will not receive a call with an update on this notification." statusUpdateDateTime="2013-11-26T23:15:00-06:00" startDateTime="2013-11-25T23:20:00-06:00" servicesAffected="Voice and Data" endDateTime="2013-11-27T15:27:40-06:00"etr="2013-11-28T23:15:01-06:00"/>

 

Link to comment
Share on other sites

Anyone notice the following added feature in Sprint Zone?

I see they are using Network Vision as an excuse for this outage. How do we know the Network Vision buildout caused the problem? I have been told that disclaimer for the past two years. Every time a tower goes down and we still don't have Network Vision in New York's Hudson Valley. Can you believe 2014 will be here in just three weeks and guess what? STILL NO NETWORK VISION!!! SHAKING  MY HEAD...

 

attachicon.gifScreenshot_2013-11-21-23-22-59.png

 

attachicon.gifScreenshot_2013-11-21-23-14-07.png

Link to comment
Share on other sites

I am guess they blocked the requests by agents such as IE, Mozilla, etc. Or was there an update recently to the app? If so could some snag the apk? I haven't tried to sideload it on the N5 yet.

 

I was able to deodex the version in the LG G2 system dump (4.5.31) and load it onto my Nexus S. ADB log shows "connection refused" when the app itself attempts to contact zone.sprint.com, so it looks like the user agent doesn't make a difference.

Link to comment
Share on other sites

I am guess they blocked the requests by agents such as IE, Mozilla, etc. Or was there an update recently to the app? If so could some snag the apk? I haven't tried to sideload it on the N5 yet.

 

Never mind, figured it out. They're actually limiting connections to zone.sprint.com by IP address now. Once I disabled Wi-Fi on my Nexus S, the Sprint Zone app was able to successfully refresh. So I tethered my laptop to my phone, and I was able to pull up zone.sprint.com with Google Chrome.

 

They must have freaked out when their server logs showed all of our connections from various IP addresses before, since they're leaking account-specific information if you just type in any phone number.

Link to comment
Share on other sites

Never mind, figured it out. They're actually limiting connections to zone.sprint.com by IP address now. Once I disabled Wi-Fi on my Nexus S, the Sprint Zone app was able to successfully refresh. So I tethered my laptop to my phone, and I was able to pull up zone.sprint.com with Google Chrome.

 

They must have freaked out when their server logs showed all of our connections from various IP addresses before, since they're leaking account-specific information if you just type in any phone number.

 

Nice work..  looks like their app won't work on wifi now though.

Link to comment
Share on other sites

Never mind, figured it out. They're actually limiting connections to zone.sprint.com by IP address now. Once I disabled Wi-Fi on my Nexus S, the Sprint Zone app was able to successfully refresh. So I tethered my laptop to my phone, and I was able to pull up zone.sprint.com with Google Chrome.

 

They must have freaked out when their server logs showed all of our connections from various IP addresses before, since they're leaking account-specific information if you just type in any phone number.

 

It's working again, regardless of the means of access.

 

<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="Single Cellsite:Intermittent service" ticketStatus="O" ticketNumber="2159123" ticketLevel="CASCADE" 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, 12 Dec 2013. 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="At 2013/12/09 18:08:18 we experienced the following Problem(s) in the Pittsburgh : Pittsburgh Market: Single Cellsite (Intermittent service) The tower is currently impaired. The customer may experience increased dropped calls, blocked calls, roaming, or no service, until the impairment is resolved." statusUpdateDateTime="2013-12-10T12:28:51-06:00" startDateTime="2013-12-09T12:08:00-06:00" servicesAffected="Voice and Data" endDateTime="9999-12-31T17:59:59-06:00" etr="2013-12-12T12:29:15-06:00"/>
<nebticket ticketType="Other:Blocked calls" ticketStatus="C" ticketNumber="2097549" ticketLevel="MARKET" 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." statusUpdateNote="At 2013/12/09 10:53:46 we experienced the following Problem(s) in the Pittsburgh : Pittsburgh Market: Voice (Blocked calls) ." statusUpdateDateTime="2013-12-09T05:34:29-06:00" startDateTime="2013-12-09T04:53:00-06:00" servicesAffected="Voice" endDateTime="2013-12-09T07:18:10-06:00" etr="2013-12-09T13:34:47-06:00"/>
</response>

 

Link to comment
Share on other sites

Nice work..  looks like their app won't work on wifi now though.

 

Not sure if you'll have to do this on Nexus 5, but I had to explicitly specify my device info to get Sprint Zone fully working on my Nexus S.

 

In the following file...

/data/data/com.sprint.zome/shared_preferences/com.sprint.zone_preferences.xml

...I added the following lines...

<string name="funnyPref1">%NAI%</string>
<string name="funnyPref2">%MEID-HEX%</string>
<string name="funnyPref3">%RESELLER-ID%</string>
<string name="funnyPref4">%MSID%</string>
<string name="funnyPref5">%PRL-VERSION%</string>
<string name="funnyPref6">%MDN%</string>
<string name="funnyPref7">%MAKE%</string>
<string name="funnyPref8">%MODEL%</string>

...with my actual device data, of course. It looked something like this:

<string name="funnyPref1">jason****@sprintpcs.com</string>
<string name="funnyPref2">A00000**********</string>
<string name="funnyPref3">Sprint</string>
<string name="funnyPref4">504*******</string>
<string name="funnyPref5">60798</string>
<string name="funnyPref6">504*******</string>
<string name="funnyPref7">Samsung</string>
<string name="funnyPref8">Nexus S 4G</string>

Prior to doing that, tapping Refresh would spit an error into the device log stating "mdn is a required parameter," which is what the server responds when it doesn't receive a valid MDN. After making the modification, account auto-login worked correctly, I could see all my devices and billing data, and service trender alerts appeared.

 

This seems to be an issue because my device doesn't system properties for MDN, NAI, and PRL that Sprint Zone is looking for. I've been attempting to reverse-engineer the specific properties with no success. I'll post them here if I can find them, since using setprop is a lot easier than modifying shared preferences.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
    • T-Mobile owns the PCS G-block across the contiguous U.S. so they can just use that spectrum to broadcast direct to cell. Ideally your phone would only connect to it in areas where there isn't any terrestrial service available.
    • So how does this whole direct to satellite thing fit in with the way it works now? Carriers spend billions for licenses for specific areas. So now T-Mobile can offer service direct to customers without having a Terrestrial license first?
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...