The order procedure -the cycle of port hell

Let's take a look at the ordering procedure when your in port hell (example is my 45th application with Internode):

First you hit the resubmit button (or place a new order) and wait a few hours and get the following:

Overall Status Provisioning is in progress Detailed Status: Confirmed: Carrier has confirmed service as deliverable, provisioning work is now being undertaken Carrier Advice ADSL New Request In Progress (ETA: 18-01-2008)

First time I got this I was thinking: "YAY! I'm getting my ADSL back" not the case at all. At this stage this is the the first check for ADSL which is basically a check of your local main exchange which may have few ports.

Wait a few more hours and then it will show:

Overall Status Provisioning is in progress Detailed Status: Held: Service Held - Delay in provisioning encountered Carrier Advice ADSL New Request Held Carrier for ADSL Port Telstra

This will happen AFTER Telstra check their backend database. This is when they see your on a CMUX/RIM without ports and place your order into HELD status. This status can last a few days to a week. If you get an ETA next to this HELD status you might be in luck.

When the final rejection comes (45th application hasn't failed yet so this example is from my 43rd attempt) you will see this:

Overall Status Service Retired Detailed Status: Cancelled: Service order rejected by Carrier Carrier Advice ADSL New Request Rejected - Alternative path currently not available Carrier for ADSL Port Telstra

That's a rejection! So at this point you have to resubmit your application again.

Notes:

1) You can only ever have one application in the orders system
2) You have to ring the ISP on occasions to check if the issue is still the same eg "no ports on CMUX"; etc
3) There are no waiting lists for ports on CMUX/RIM so your only recourse is to resubmit - if you don't and a port becomes available you might miss out.
4) You can not find out if ports are pending for release, if ports are in the 180-182 hold status and you can't find out (you can if you research enough) how many ports your local CMUX/RIM has.