BBZA API 2011.322

Rating: No reviews yet
Downloads: 213
Change Set: 11063
Released: Nov 20, 2011
Updated: Nov 21, 2011 by IanSaunders
Dev status: Beta Help Icon

Recommended Download

Application BBZA DLL 2011.322
application, 17K, uploaded Nov 20, 2011 - 180 downloads

Other Available Downloads

Application BBZA Docs 2011.322
application, 959K, uploaded Nov 21, 2011 - 33 downloads

Release Notes

The following additions were added in the 2011.322 Release:
  1. Additional data returned in phone/exchange query
    1. Parent Exchange Code
      1. This is the exchange code for the parent exchange (interconnect) of this exchange. If this value matches the exchanges name this exchange has no parent
    2. Parent Exchange Type
      1. This is the type of the parent exchange. Either DPSU or DSSU (see page 14 of https://secure1.telkom.co.za/apps_static/ir/pdf/financial/docs/Technology-DB-2305.pdf for more details)
    3. Child Exchanges
      1. This is the list of exchanges which are connected to this exchange. These may be DSSU or DLU exchanges.
      2. Note: To reduce output returned only key data is returned in this list.
    4. Grouped Exchanges
      1. This is the list of exchanges which are grouped to this exchange. For example the NNWC exchange contains the following physical exchanges NNWC03, NNWC97, NNWC98.
      2. Note: To reduce output returned only key data is returned in this list.
    5. Precision when doing a phone query
      1. When only a single exchange matches the phone query the ‘exact_phone’ property will be set to 1 if more than a single exchange matches this number 0 will be returned.
      2. When multiple exchanges are found the exactphonematch_list field will be populated with the list of matching exchanges.
      3. Note:
        1. Multiple exchanges may exist in the same physical location.
        2. VSAT exchanges are associated with phone number (DN) matches.
    6. Geographic search API added (NEW)
      1. New query to search for exchanges based on longitude and latitude. Please see below API documentation for usage.
    7. Output type shortcuts. When querying the API for test purposes it is no possible to append /xml or /json to the query to change the output format. This option is for debugging purposes only and may be removed without warning. Please use the appropriate POST variable to set output type when doing critical queries.
    8. New error code ‘5’ for geographic queries
    9. Note: There are no breaking API changes in 2011.322 with regards to 2011.203

Reviews for this release

No reviews yet for this release.