csh
/
y.st.
フォーク元 y.st./y.st.


			
				
					
						
						
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146
							<?xml version="1.0" encoding="utf-8"?>
<!--
                                                                                     
 h       t     t                ::       /     /                     t             / 
 h       t     t                ::      //    //                     t            // 
 h     ttttt ttttt ppppp sssss         //    //  y   y       sssss ttttt         //  
 hhhh    t     t   p   p s            //    //   y   y       s       t          //   
 h  hh   t     t   ppppp sssss       //    //    yyyyy       sssss   t         //    
 h   h   t     t   p         s  ::   /     /         y  ..       s   t    ..   /     
 h   h   t     t   p     sssss  ::   /     /     yyyyy  ..   sssss   t    ..   /     
                                                                                     
	<https://y.st./>
	Copyright © 2016 Alex Yst <mailto:copyright@y.st>

	This program is free software: you can redistribute it and/or modify
	it under the terms of the GNU General Public License as published by
	the Free Software Foundation, either version 3 of the License, or
	(at your option) any later version.

	This program is distributed in the hope that it will be useful,
	but WITHOUT ANY WARRANTY; without even the implied warranty of
	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
	GNU General Public License for more details.

	You should have received a copy of the GNU General Public License
	along with this program. If not, see <https://www.gnu.org./licenses/>.
-->
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<base href="https://y.st./en/weblog/2016/08-August/24.xhtml" />
		<title>Telephone troubles all around &lt;https://y.st./en/weblog/2016/08-August/24.xhtml&gt;</title>
		<link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
		<link rel="stylesheet" type="text/css" href="/link/basic.css" />
		<link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
		<script type="text/javascript" src="/script/javascript.js" />
		<meta name="viewport" content="width=device-width" />
	</head>
	<body>
		<nav>
			<p>
				<a href="/en/">Home</a> |
				<a href="/en/a/about.xhtml">About</a> |
				<a href="/en/a/contact.xhtml">Contact</a> |
				<a href="/a/canary.txt">Canary</a> |
				<a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
				<a href="/en/opinion/">Opinions</a> |
				<a href="/en/coursework/">Coursework</a> |
				<a href="/en/law/">Law</a> |
				<a href="/en/a/links.xhtml">Links</a> |
				<a href="/en/weblog/2016/08-August/24.xhtml.asc">{this page}.asc</a>
			</p>
			<hr/>
			<p>
				Weblog index:
				<a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
				<a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
				<a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
			</p>
			<hr/>
			<p>
				Jump to entry:
				<a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
				<a rel="prev" href="/en/weblog/2016/08-August/23.xhtml">&lt;Previous</a>
				<a rel="next" href="/en/weblog/2016/08-August/25.xhtml">Next&gt;</a>
				<a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
			</p>
			<hr/>
		</nav>
		<header>
			<h1>Telephone troubles all around</h1>
			<p>Day 00536: Wednesday, 2016 August 24</p>
		</header>
<p>
	Alyssa&apos;s new carrier sent them a message saying that the service setup had been finished, but we found that it really hadn&apos;t.
	The new TracFone device wasn&apos;t able to make or receive calls while the old Verizon device was still able to.
	My mother telephoned the TracFone people, but when they asked for my mother&apos;s Verizon account information to use it to port the telephone number properly, my mother rejected that idea.
	I agreed that this was necessary, as Verizon isn&apos;t going to give up the telephone number to random people that ask for it.
	They instead need to be sure that the paying customer actually wants their telephone number ported away, but my mother wanted them to somehow authorize the port without that information.
	My mother also supposedly gave them that information through the Web last night, but they said that Verizon said that it was incorrect.
	Furthermore, my mother doesn&apos;t even seem to know what their account <abbr title="personal identification number">PIN</abbr> is, so my guess is that they did in fact supply invalid information.
	Either my mother is going to have to supply this account information eventually, Alyssa is going to have to stay on my mother&apos;s Verizon plan, or Alyssa is going to switch telephone numbers.
	Porting the telephone number without proper authorization using information from the Verizon account doesn&apos;t sound like an actual possibility.
</p>
<p>
	The other day, Verizon told us that <a href="/en/weblog/2016/08-August/22.xhtml">only an Apple store could unlock their iPhone</a>, so we headed to one on our way home.
	They took over an hour to even start helping us! This is the kind of customer support that Apple customers pay through the nose to get? Wow.
	Just wow.
	Not only that, but the representative that helped us seemed slightly incompetent.
	They weren&apos;t connecting simple dots, and I was the one having to bring up simple possibilities such as that the account email address might have changed (instead of there being a second Apple account).
	Add that to the fact that my mother couldn&apos;t even remember their account password, and it took a while to get us serviced and out of there.
	They managed to wipe the device, and now it should be usable, or at least as usable as before it locked up.
	Strangely, the device couldn&apos;t even function without a <abbr title="subscriber identity module">SIM</abbr> card! If you take the <abbr title="subscriber identity module">SIM</abbr> card out of an Android/Replicant device, you lose cell tower connectivity, but you keep all other functionality.
	However, we couldn&apos;t even get through the iPhone setup without a <abbr title="subscriber identity module">SIM</abbr> card present in the device (the device complained, not the Apple representative), so the Apple representative gave us a gratis, unactivated, Verizon <abbr title="subscriber identity module">SIM</abbr> card.
</p>
<p>
	We were going to go hassle Verizon about the failed telephone number port out, but we needed to get back to Springfield on the double to check into a new storage unit before our reservation was dropped.
	As it turned out, the plan made yesterday wasn&apos;t to look for a storage unit, but rather to claim the unit that my mother was informed about yesterday.
	I&apos;m never kept fully in the loop on these things.
	Cyrus (who came with us) wanted to joke around, and ended up bringing up the fact that my mobile device has an active telephone line now instead of just a data line.
	My mother was steamed! Somehow, despite the fact that I&apos;d already told them that I was adding a voice/<abbr title="Short Message Service">SMS</abbr> line after my device was stolen, they still didn&apos;t know and blamed me for withholding this information.
	Why does it even matter though? They aren&apos;t going to like my telephone number because it&apos;s going to change, and I always try to get them to contact me via email instead of anything that involves telephone numbers.
	My having telephone service is completely irrelevant to anything, even though I <strong>*did*</strong> tell them about it.
	By the time we arrived home, the post office was already closed, so that errand will have to wait.
	Likewise, we&apos;re leaving early in the morning to move stuff to the storage unit, so I can&apos;t head to  the post office right away.
	My guess is that I won&apos;t make it to the post office at all tomorrow.
</p>
<p>
	Once home where they were able to connect to our father&apos;s Wi-Fi router, Vanessa successfully activated the proprietary pedometer and synchronized it with the proprietary pedometer server.
</p>
<p>
	I borrowed Vanessa&apos;s telephone number <a href="/en/weblog/2016/08-August/21.xhtml">as planned</a>, and set up a new Google account to use when dealing with my mother.
	This should provide a permanent telephone number at which they can reach me without requiring that I actually keep the same telephone number when I switch providers.
	I used Vanessa&apos;s telephone number to get past the <abbr title="Short Message Service">SMS</abbr> verification, but then tried to use my own temporary telephone number as the number to forward to.
	That didn&apos;t work.
	Google disallowed the setup of a Google Voice telephone number if I used the same telephone number as the destination number that I did last time.
	I had to set Vanessa&apos;s telephone number as the forwarding number, then correct it to point to my telephone number instead.
	Google is such a stupid pain in the neck.
	At least I have the account set up and working now though.
	Hopefully, Google won&apos;t lock this account up as well.
	Last time, the account got locked up soon after I disabled &quot;less secure application&quot; access, but this time, that was disabled by default.
	I had to actively enable it to allow <a href="apt:icedove">Icedove</a> to retrieve mail from the account.
	Strangely, disabling call forwarding doesn&apos;t function as it should.
	Even if I disable all forwarding numbers, Google still stupidly forwards all calls to my telephone number but not Vanessa&apos;s telephone number.
	However, activating &quot;do not disturb&quot; mode seems to prevent call forwarding as I want it to.
	With that active, all calls are sent to voicemail.
	Voicemail messages are transcribed and sent to my email inbox, making this probably about as decent telephone-to-email functionality as currently exists.
	The one thing that would make it better would be not requiring active telephone service and a telephone number to set it up.
</p>
		<hr/>
		<p>
			Copyright © 2016 Alex Yst;
			You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
			If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
			My address is in the source comments near the top of this document.
			This license also applies to embedded content such as images.
			For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
		</p>
		<p>
			<abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
			This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F08-August%2F24.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F08-August%2F24.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
		</p>
	</body>
</html>