Ports_Super LTE PORT-IN Errors

Saad Akhtar Updated by Saad Akhtar Permissioned article This article is internal and cannot be seen by public viewers.

Super LTE PORT-IN Errors:

Whenever the status of a Super LTE Port in request is on hold, a PSS should always write the carrier name in the comments and then resubmit the PORT-IN request in order to view the actual error due to which the Port request is not being submitted.
  • E-1094 Device is active on another line error:

Please make a Dummy IMEI when you see this error and resubmit the port request with it to get it submitted.

  •  E0104-Invalid Billing Street Address ERROR:

The address that the customer has entered in their port request seems to be invalid and does not reflect the information in the database of their previous carrier. Please ask the customer to provide their valid address so that the port request can get submitted successfully.

  • E1029-Requested Port In number 1234567890 is currently in VZW inventory and cannot be ported in ERROR

When you see this error continue to cancel and resubmit the port request, except if response type is C. If you are still getting an error please ask the porting team to escalate the port request to VZW.

  • E2231-Pending transaction exists for the requested ESN/MEID 123456789012345 ERROR

Please make a Dummy IMEI when you see this error and resubmit the port request with it to get it submitted.

  • E2239-MDN IS AGING - ACTIVATE OR RELEASE FROM AGING - SEE M AND P ERROR

The error message indicates the line is not currently active with the previous carrier. Please advise the customer to reach back to their carrier and try getting their line active to continue porting the line with us.

  • E2239-MDN IS RESERVED - CHECK FOR PENDING ORDER - SEE M AND P ERROR

This error means that the previous carrier has placed a restriction on the porting the line out of their system, or the port is not possible since the line with the previous carrier is no longer active. Please advise customer to reach out to their carrier to sort this out in order to continue porting with us.

  • E2239-MDN NOT FOUND IN VZW OR INDUSTRY TNI DATABASE ERROR

This error means that the number provided by the customer might be an incorrect number or it might not be a US number. Kindly ask the customer to verify their number and then amend it in their port request.

  • E2239-PORT RESTRICTED BY LNP OPERATIONS - NOT PORTABLE TO VZW ERROR

This error means that there are some restrictions and this line number can not be ported over to our Super LTE Network. Solution can be to cancel the port request and activate a new number for the customer on the Super LTE Network or port in their number on to the GSM LTE Network if they agree.

  • E2239-VZW DOES NOT HAVE A LICENSE TO OPERATE IN THIS RATE CENTER ERROR
    This error means that the Verizon network cannot support porting of numbers in their area at this moment and this line number can not be ported over to our Super LTE Network. Solution can be to cancel the port request and activate a new number for the customer on the Super LTE Network or port in their number on to the GSM LTE Network if they agree.
  • E2239-VZW NETWORK IS NOT CONFIGURED TO SUPPORT PORTING AT THIS TIME ERROR

This error means that the Verizon network cannot support porting of numbers in their area at this moment and this line number can not be ported over to our Super LTE Network. Solution can be to cancel the port request and activate a new number for the customer on the Super LTE Network or port in their number on to the GSM LTE Network if they agree.

  • E3748-Activation Or Port-In not allowed on CDMA or 4G Non HD Voice Device ERROR

This error shows up if the device is compatible but does not have VoLTE/HD Voice feature. Solution can be to either ask for any other Super LTE compatible device IMEI from the customer and resubmit the port request with it or advise them to port their number on the GSM LTE Network after checking the compatibility and coverage.

  • E2217-A port in request for XXXXXXXXXX was submitted today. Although it was cancelled, another port in request cannot be issued until tomorrow. ERROR

On Super LTE, a port request can be cancelled and re-submitted only once within a 24 hour period. Attempting to do so again would return the above error.

  • Could not cancel port request: E2237-Transaction not allowed for the order already closed or successful in RSS ERROR

Sometimes comes up on attempts to cancel a port request. Been known to happen when a port request has been cancelled on Verizon’s end, but still shows up as Submitted in Admin. Needs to be escalated to Michael by the porting team.

  • E1008-Schema validation failed:cvc-maxLength-valid: Value 'gbttfsahsnafa@3io' with length = '17' is not facet-valid with respect to maxLength '15' for type '#AnonType_pinType'.,cvc-complex-type.2.2: Element 'pin' must have no element [children], and the value must be valid. ERROR

Shows up on querying a port request that was not submitted correctly, due to one or more of the entries being in an unsupported format or if there are any spaces in the customer account details.

  • E1034-Reference number: USMOBILELLC_1540838265787604646 pending on ICCID: 89148000004582714997 ERROR

Is seen when the phone number on a port request is modified without first cancelling the port request. The solution is to enter the provided order reference number under Admin > Verizon > Order Inquiry, copying the phone number mentioned therein > modify port request > then cancel > modify with correct number > then resubmit > Query.

  • E1096-Device not eligible for ResellerAddSubscriberPortIn ERROR
    The device is not eligible for use with re-seller. Please request the customer to contact the carrier it is locked with to get it released to use with re-seller. If not, may need to get another Verizon compatible device to use with service. Usually this error occurs on Palm devices and LIGHT Phones in which using a dummy IMEI of an android CDMALess device fixes the error on resubmitting.

If there is NO RESPONSE found on a Super LTE Port In request, please ask the porting team to check for the correct response on Syniverse.

How did we do?

Ports_Port Out: Issues

Troubleshooting Guide

Contact