Skip to main content

Philippine telcos blocking entire SMS text with internet addresses in it

If you are sending SMS texts to your friends, family or colleagues and they contain internet or web address including IP and email addresses, and even a period or dot separating, regardless of, your words and numbers, they are automatically blocked and not going to be received by your waiting recipient. Cooler heads must prevail here especially if an important message is urgently being expected. IP version 6 address is fine. However, an IPv4 including localhost address (given automatically to every computers and network interfaces as their own alone designed for troubleshooting purposes), and your money in the billion figure using dot as separators would be blocked.  If you send "local.business, naman.naman etcetera" or any words that made you use dot in between them, as part of the text, they will be blocked. There are some, that isn't blocked in this category. Like check.iclassed, some.ent, whatever.local etcetera, that is because they do not form any domain name at all

8Ps preview

We've seen varying and elaborate ways to accomplish uncommon artifacts and rock solid business systems but still we had to create our own. For a simple reason, methodologies are not always full-clad, and practitioners concur on and adjust them, subsequently, overcoming problems and be able to pull through on agreements and goals. That's why we had to establish our own basic prerequisite for whatever job we should be in --
  • Purpose (Initiative, beginning of master plan) - does it solve issues for or augment the business?
  • People (Strategy and requiring correct Specifications) - who can deal with such assignment? Humans make everything and miss a lot!
  • Product (Architecture and Technology) - do we need it and how do we use it? However and whatsoever they are must not influence the major portion of the decision.
  • Policy (Practices, Standard, Rules, Regulations and Laws) - we need comprehensive and panoptic guidelines.
  • Process (Action guided by the purpose) - make sure we are consistent.
  • Procurement (Acquisition, reinforced by our AIM business lifecycle) - it must be competitive not corrupted. Where do you put major software development efforts? Pick one of the following facets: acquisitionimplementation or management?
  • Period (Time) - know it and save energy. Would you be able to calculate when may the complete delivery happen from the beginning? See purpose.
  • Produce (finished or set Goal achieved) - is it successful? If it really resolves the issue and augments the business. It satisfies the wants and everyone.
We need assurance that we will be able to commit and deliver on our accords. We find these 8Ps to be a good start in IT and contiguous facilities related work. It can be used to complement industry best practices, standards and regulatory compliance. They make matters explicit and kindred with each other. Failure to determine important components from the beginning will prolong engagement (that is considered wasteful for proponent companies themselves). Benefits and value must be realized from all phases of a particularly huge effort and concurrently acknowledged by parties involved.

Comments

Popular posts from this blog

[TW] IT documents, audit and leaders

IT documents comes with different names such as the following: - Manual or handbook, - Policies and procedures, - Management systems, - Project plans. In the real world we have various names with unique descriptions and purposes when in fact they could be made to do a uniform direction for which actions are based for the entire IT initiatives, probably the longest in IT lifecycle is operation. The problem is our inclination on something else which is wrong. IT remains an IT area. Business remains a business area. The same problem is carried out when we conduct IT audit. Most audit are missing the gists in which IT is being used by businesses. We once said that an effective IT audit is conducted by IT people themselves but there is something wrong with that even. Business and accounting people have been doing it with a different bias and preconceived notions which doesn't make the cut for IT direction and audit respectively. Leaders play the same game and so the problem continues an

[TW] Customers' trust and domains outside of internet's root

We all consider ourselves customers. Those who own businesses are customers even of their own. When we talk about the utility of technology, we often use customers to refer to our colleagues and some stakeholders that were provided access to our enterprise system. In business, customers are those who acquire and engage our products and services, respectively. Customers' trust is achieved and retained when we meet the expectations of our colleagues, stakeholders and the buyer of our products, services and ideas. Not only that we have assured them of those expectations in the contract or terms and conditions including some form of agreement but we attend to them sincerely when they need help. Giving them almost everything they need to form a decision. The experience must not be shallow and pretentious or they would notice whatever motive there is in between. Customers' trust is build not by the customers alone, just because we kept their experience up to their standards or we str