AAPT National Wholesale Broadband L3 - Revision history

Scarpenter: /* API Integration */

2016-03-18T06:39:52Z

‎API Integration

Scarpenter at 06:39, 18 March 2016

2016-03-18T06:39:10Z

Scarpenter: /* Daily Usage Collection & Processing */

2016-01-27T03:00:05Z

‎Daily Usage Collection & Processing

Scarpenter: Created page with "== AAPT National Wholesale Broadband L3 == AAPT National Wholesale Broadband L3 (also known as Broadband Connect Layer 3) is a fully automated service type in Emersion. In o..."

2015-07-06T01:39:47Z

Created page with "== AAPT National Wholesale Broadband L3 == AAPT National Wholesale Broadband L3 (also known as Broadband Connect Layer 3) is a fully automated service type in Emersion. In o..."

New page

== AAPT National Wholesale Broadband L3 ==
AAPT National Wholesale Broadband L3 (also known as Broadband Connect Layer 3) is a fully automated service type in Emersion.

In order for service providers to provision services and process usage, Emersion requires the following from you:

# AAPT FTP log in credentials.
# AAPT Account number
# Your AAPT provisioning certificate and certificate password.
# Your FrontierLink connection service ID

If you currently have multiple accounts from AAPT, one will need to be selected for provisioning. AAPT issue a single provisioning certificate and passoword for each account.

== Daily Usage Collection & Processing ==

Usage is collected and processed once the usage files (known as CTOP files) are delivered daily by AAPT to the Service Providers FTP directory. Service Providers selling SSaaS need to supply Emerson with their AAPT FTP log in credentials in order for Emerson to collect these files and process the usage. Service Providers also need to request AAPT add [[Main_Page/Provisioning|Emersion's IP addresses]] through the firewall so that we can access the FTP directories.

@@ Line 20: / Line 20: @@
 REQUEST - PERFORMED@ 2016-01-01T11:38:03+11:00
-=======================================
 <?xml version="1.0" encoding="UTF-8"?>
 <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.aapt.com.au/FrontierLink/xsd">
@@ Line 70: / Line 70: @@
 RESPONSE - RECEIVED@ 2016-01-01T11:38:19+11:00
-=======================================
 <?xml version="1.0" encoding="UTF-8"?>
 <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

← Older revision		Revision as of 06:39, 18 March 2016
Line 14:		Line 14:

	Usage is collected and processed once the usage files (known as CTOP files) are delivered daily by AAPT to the Service Providers FTP directory. Service Providers selling AAPT NWB need to supply Emerson with their AAPT FTP log in credentials in order for Emerson to collect these files and process the usage. Service Providers also need to request AAPT add [[Main_Page/Provisioning\|Emersion's IP addresses]] through the firewall so that we can access the FTP directories.		Usage is collected and processed once the usage files (known as CTOP files) are delivered daily by AAPT to the Service Providers FTP directory. Service Providers selling AAPT NWB need to supply Emerson with their AAPT FTP log in credentials in order for Emerson to collect these files and process the usage. Service Providers also need to request AAPT add [[Main_Page/Provisioning\|Emersion's IP addresses]] through the firewall so that we can access the FTP directories.
		+
		+	== API Integration ==
		+
		+	When Emersion's system performs an API call to order or provision some data services, the request includes your AAPT account number and the connection service ID. This information is mandatory for all L2 and L3 services. See an example of the API call Emersion's system sends to AAPT during such requests. Feedback from our customers who have requested the connection service ID from AAPT has resulted in confusion by AAPT staff who are not technical. If AAPT advise you they do not know what the connection service id is, sending them this API example wiht the connection service id highlighted should give them clarity.
		+
		+	REQUEST - PERFORMED@ 2016-01-01T11:38:03+11:00
		+	=======================================
		+	<?xml version="1.0" encoding="UTF-8"?>
		+	<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.aapt.com.au/FrontierLink/xsd">
		+	<SOAP-ENV:Body>
		+	<ns1:NewServiceRequest>
		+	<ns1:orderContact>
		+	<ns1:individual>
		+	<ns1:salutation>MR</ns1:salutation>
		+	<ns1:firstName>xxxxxxx</ns1:firstName>
		+	<ns1:lastName>xxxxxx</ns1:lastName>
		+	</ns1:individual>
		+	<ns1:phone>xxxxxx</ns1:phone>
		+	<ns1:email>xxxx@xxxxx.com.au</ns1:email>
		+	</ns1:orderContact>
		+	<ns1:installationContact>
		+	<ns1:individual>
		+	<ns1:salutation>MR</ns1:salutation>
		+	<ns1:firstName>Jimmy</ns1:firstName>
		+	<ns1:lastName>Jackson</ns1:lastName>
		+	</ns1:individual>
		+	<ns1:phone>03545xxxxx</ns1:phone>
		+	<ns1:email>jimmy@jackson.com</ns1:email>
		+	</ns1:installationContact>
		+	<ns1:customerReference>698557</ns1:customerReference>
		+	<ns1:serviceDetailsList>
		+	<ns1:serviceDetails>
		+	<ns1:nationalWholesaleBroadbandService>
		+	<ns1:accountNumber>200002xxxx</ns1:accountNumber>
		+	<ns1:qualificationID>4526244</ns1:qualificationID>
		+	<ns1:nbnLocationID>LOC000131391726</ns1:nbnLocationID>
		+	<ns1:accessMethod>NBN</ns1:accessMethod>
		+	<ns1:accessType>NWAS</ns1:accessType>
		+	<ns1:serviceSpeed>25Mbps/5Mbps</ns1:serviceSpeed>
		+	<ns1:networkConnectionServiceId>8103xxx</ns1:networkConnectionServiceId>
		+	<ns1:contractTerm>24</ns1:contractTerm>
		+	<ns1:radiusEntry>
		+	<ns1:radiusUserName>1584xxxx</ns1:radiusUserName>
		+	<ns1:radiusDomain>au.xxxxx</ns1:radiusDomain>
		+	<ns1:password>qxxxxxxx</ns1:password>
		+	</ns1:radiusEntry>
		+	<ns1:batteryBackupService>true</ns1:batteryBackupService>
		+	</ns1:nationalWholesaleBroadbandService>
		+	</ns1:serviceDetails>
		+	</ns1:serviceDetailsList>
		+	</ns1:NewServiceRequest>
		+	</SOAP-ENV:Body>
		+	</SOAP-ENV:Envelope>
		+
		+
		+	RESPONSE - RECEIVED@ 2016-01-01T11:38:19+11:00
		+	=======================================
		+	<?xml version="1.0" encoding="UTF-8"?>
		+	<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
		+	<soapenv:Body>
		+	<NewServiceResponse xmlns="http://www.aapt.com.au/FrontierLink/xsd">
		+	<salesOrder>
		+	<salesOrderID>CA3322xxxx</salesOrderID>
		+	<productOrders>
		+	<productOrderID>8584xxx</productOrderID>
		+	<serviceOrders>
		+	<serviceOrderID>1352xxx</serviceOrderID>
		+	<serviceOrderType>Standard Access</serviceOrderType>
		+	</serviceOrders>
		+	<serviceOrders>
		+	<serviceOrderID>526xxx</serviceOrderID>
		+	<serviceOrderType>NWB Link</serviceOrderType>
		+	</serviceOrders>
		+	</productOrders>
		+	</salesOrder>
		+	</NewServiceResponse>
		+	</soapenv:Body>
		+	</soapenv:Envelope>

← Older revision		Revision as of 03:00, 27 January 2016
Line 13:		Line 13:
	== Daily Usage Collection & Processing ==		== Daily Usage Collection & Processing ==

−	Usage is collected and processed once the usage files (known as CTOP files) are delivered daily by AAPT to the Service Providers FTP directory. Service Providers selling ~~SSaaS~~ need to supply Emerson with their AAPT FTP log in credentials in order for Emerson to collect these files and process the usage. Service Providers also need to request AAPT add [[Main_Page/Provisioning\|Emersion's IP addresses]] through the firewall so that we can access the FTP directories.	+	Usage is collected and processed once the usage files (known as CTOP files) are delivered daily by AAPT to the Service Providers FTP directory. Service Providers selling AAPT NWB need to supply Emerson with their AAPT FTP log in credentials in order for Emerson to collect these files and process the usage. Service Providers also need to request AAPT add [[Main_Page/Provisioning\|Emersion's IP addresses]] through the firewall so that we can access the FTP directories.