Hi Folks,
This will be my first week in Telco vendor Mediation Multi National company. Wish me luck allz!!
I wish to gain my experience and knowledge here and succeed in company.
Faizal
20121217, Monday
Wednesday, December 19, 2012
Wednesday, July 25, 2012
International Numbering Plan
Hi Again,
On top of the Malaysian MNP number verification, I would also like to share the International Numbering Plan where you can look at your mobile number and the Original Network provider that you currently using.
Here are the snapshot of the web-page and you can see there has a lot of options that you can look around. Please give a try and enjoy!
One of the menu in there.
Some sample using the Malaysian MSISDN.
Malaysia MCMC MNP
Hi Folks,
Please refer to below web-page if you would like to check which Telco Operator that your family member, buddy, colleague tied to. This would be easy for you to check whether you are calling on-net or off-network. Enjoy!
http://mnpcheck.skmm.gov.my/MNPQuery.aspx
MTN Nigeria employs Ericcson SSR 8020
Please refer below link for article details:
http://telecommunicationnews.net/2012/07/25/mtn-nigeria-employs-ericssons-ssr-8020-to-build-ip-network-of-future/
http://telecommunicationnews.net/2012/07/25/mtn-nigeria-employs-ericssons-ssr-8020-to-build-ip-network-of-future/
Wednesday, July 4, 2012
SMPP Error code
| Error Number | Error Name | Error Description |
|---|---|---|
| 0x00000000 | ESME_ROK | No Error |
| 0x00000001 | ESME_RINVMSGLEN | Message too long |
| 0x00000002 | ESME_RINVCMDLEN | Command length is invalid |
| 0x00000003 | ESME_RINVCMDID | Command ID is invalid or not supported |
| 0x00000004 | ESME_RINVBNDSTS | Incorrect bind status for given command |
| 0x00000005 | ESME_RALYBND | Already bound |
| 0x00000006 | ESME_RINVPRTFLG | Invalid Priority Flag |
| 0x00000007 | ESME_RINVREGDLVFLG | Invalid registered delivery flag |
| 0x00000008 | ESME_RSYSERR | System error |
| 0x0000000A | ESME_RINVSRCADR | Invalid source address |
| 0x0000000B | ESME_RINVDSTADR | Invalid destination address |
| 0x0000000C | ESME_RINVMSGID | Message ID is invalid |
| 0x0000000D | ESME_RBINDFAIL | Bind failed |
| 0x0000000E | ESME_RINVPASWD | Invalid password |
| 0x0000000F | ESME_RINVSYSID | Invalid System ID |
| 0x00000011 | ESME_RCANCELFAIL | Cancelling message failed |
| 0x00000013 | ESME_RREPLACEFAIL | Message recplacement failed |
| 0x00000014 | ESME_RMSSQFUL | Message queue full |
| 0x00000015 | ESME_RINVSERTYP | Invalid service type |
| 0x00000033 | ESME_RINVNUMDESTS | Invalid number of destinations |
| 0x00000034 | ESME_RINVDLNAME | Invalid distribution list name |
| 0x00000040 | ESME_RINVDESTFLAG | Invalid destination flag |
| 0x00000042 | ESME_RINVSUBREP | Invalid submit with replace request |
| 0x00000043 | ESME_RINVESMCLASS | Invalid esm class set |
| 0x00000044 | ESME_RCNTSUBDL | Invalid submit to ditribution list |
| 0x00000045 | ESME_RSUBMITFAIL | Submitting message has failed |
| 0x00000048 | ESME_RINVSRCTON | Invalid source address type of number ( TON ) |
| 0x00000049 | ESME_RINVSRCNPI | Invalid source address numbering plan ( NPI ) |
| 0x00000050 | ESME_RINVDSTTON | Invalid destination address type of number ( TON ) |
| 0x00000051 | ESME_RINVDSTNPI | Invalid destination address numbering plan ( NPI ) |
| 0x00000053 | ESME_RINVSYSTYP | Invalid system type |
| 0x00000054 | ESME_RINVREPFLAG | Invalid replace_if_present flag |
| 0x00000055 | ESME_RINVNUMMSGS | Invalid number of messages |
| 0x00000058 | ESME_RTHROTTLED | Throttling error |
| 0x00000061 | ESME_RINVSCHED | Invalid scheduled delivery time |
| 0x00000062 | ESME_RINVEXPIRY | Invalid Validty Period value |
| 0x00000063 | ESME_RINVDFTMSGID | Predefined message not found |
| 0x00000064 | ESME_RX_T_APPN | ESME Receiver temporary error |
| 0x00000065 | ESME_RX_P_APPN | ESME Receiver permanent error |
| 0x00000066 | ESME_RX_R_APPN | ESME Receiver reject message error |
| 0x00000067 | ESME_RQUERYFAIL | Message query request failed |
| 0x000000C0 | ESME_RINVTLVSTREAM | Error in the optional part of the PDU body |
| 0x000000C1 | ESME_RTLVNOTALLWD | TLV not allowed |
| 0x000000C2 | ESME_RINVTLVLEN | Invalid parameter length |
| 0x000000C3 | ESME_RMISSINGTLV | Expected TLV missing |
| 0x000000C4 | ESME_RINVTLVVAL | Invalid TLV value |
| 0x000000FE | ESME_RDELIVERYFAILURE | Transaction delivery failure |
| 0x000000FF | ESME_RUNKNOWNERR | Unknown error |
| 0x00000100 | ESME_RSERTYPUNAUTH | ESME not authorised to use specified servicetype |
| 0x00000101 | ESME_RPROHIBITED | ESME prohibited from using specified operation |
| 0x00000102 | ESME_RSERTYPUNAVAIL | Specified servicetype is unavailable |
| 0x00000103 | ESME_RSERTYPDENIED | Specified servicetype is denied |
| 0x00000104 | ESME_RINVDCS | Invalid data coding scheme |
| 0x00000105 | ESME_RINVSRCADDRSUBUNIT | Invalid source address subunit |
| 0x00000106 | ESME_RINVSTDADDRSUBUNIR | Invalid destination address subunit |
| 0x0000040B | ESME_RINVBALANCE | Insufficient credits to send message |
| 0x0000040C | ESME_RUNESME_SPRTDDESTADDR | Destination address blocked by the ActiveXperts SMPP Demo Server |
Friday, June 22, 2012
How do I configure SMPP?
The short message peer-to-peer protocol (SMPP) is a telecommunications
industry protocol for exchanging SMS messages between SMS peer entities such as
short message service centers. It is often used to allow third parties (for
example, value-added service providers like news organizations) to submit
messages, sometimes in bulk.
The protocol is based on pairs of request/response PDUs (protocol data units,
or packets) exchanged over OSI layer 4 (TCP/IP session or X.25 SVC3)
connections. PDUs are binary encoded for efficiency.
The most commonly used versions of SMPP are v3.3 (the most widely supported
standard) and v3.4, which adds transceiver support (single connections that can
send and receive messages). Data exchange can be synchronous, (each peer waits
for a response for each PDU being sent) or asynchronous (messages are received
and transmitted in independent threads with the use of buffers and timers). The
latest version of SMPP is v5.0.
to know details about SMPP; please refer https://www.watchguard.com/help/docs/ssl/2/en-US/Content/FAQs/configure_smpp_faq.html
Monday, June 18, 2012
How the Intelligent Network works?
In telecommunication company, telecommunications services that provided to their customer is very important. Company will get revenue by providing value-added service to their customer. One of value-added service enabler for telecommunication company is Intelligent Network or known as IN. IN can provide and differentiate their product between their competitor. IN mainly used for Prepaid Charging, in Prepaid Charging system IN hold configuration about charging matrix, discount, bonus and many other prepaid charging service can provided by IN.
Beside used for prepaid charging, IN also can provide another telecommunication service, such as Friend and Family Promo, Corporate User Group, Single IMSI multiple MMDN and many other
Beside used for prepaid charging, IN also can provide another telecommunication service, such as Friend and Family Promo, Corporate User Group, Single IMSI multiple MMDN and many other
 telecommunication service can be provided. IN consist of some network element such as: SCP(service control point), SMP(service management point), SDP(service data point) and RBI. Lets give a brief overview of IN network element:
- SCP : SCP mainly used for call control that communicate to MSC or STP. SCP usually also act as the charging and rating application.
- SMP: SMP used for management of IN. It interact with person or application to make modification of all network element in IN.
- SDP: SDP used for data management, it will used for manipulating and querying data in realtime. All deduction of prepaid subscriber will be done by SDP in realtime
- RBI: RBI used for hold Call Data Record. It will be used by another party to calculate revenue from Intelligent Network. Usually Datawarehouse will used data on RBI.
All of this network element communicate in SS7 and IP based. With the integration of all network element in IN Telecommunications Services will be provided to the customer and revenue will come to the telecommunication company.
Subscribe to:
Posts (Atom)