Outgoing CID

Tim....

What a great comprehensive explanation..

Thanks..

how would one find out whether he/she has a ELS or LI number?

Quote:

---

Originally Posted by voxabox

how would one find out whether he/she has a ELS or LI number?

---

If there's a name on the outgoing CID, it's LI.

If it was issued through the automated ordering, it is always LI. We only issue ELS manually.

Tim, I have a number ported in from verizon. Will that work? If so, by design? By luck?

Quote:

---

Originally Posted by VOIPoTim

If there's a name on the outgoing CID, it's LI.

If it was issued through the automated ordering, it is always LI. We only issue ELS manually.

---

I'm not sure what it is. For my out of state parent, I elected to keep the same beta number (703.651.32xx).
AFIK, our home number was ported in from VT; hopefully, it maintains its prior CNAM and directory listing status

Ported numbers are ported in as ELS except in rare cases. As an example, Level3 won't issue ELS numbers (or port them) in areas where they don't provide E911 (based on service address).

Since we do E911 separately and don't use their service for that, we have seen some cases where we had 911 coverage but Level3 did not and did those as LI.

99% of the time ported will be ELS anyway.

Tim; my outbound caller ID WAS working fine for the longest time. Since the number was ported. I noticed after changing to the 502 adapter; (I don't believe the adapter is the issue, just that I never called myself to check until I was experimenting with the new adapter); but I no longer see an outgoing caller ID on the receiving line. I have a trouble ticket in on it. The response was they thought it got messed up when they put in to FIX the spelling of my name being wrong. However, the spelling got corrected and I remember numerous times seeing the outbound caller ID working fine. Most times I would check by calling my other voipo line. However now, it's just showing my number in place of my name. Being it WAS working, should it be fixable? Or am I out of luck? thanks... mike....

Quote:

---

Originally Posted by christcorp

Tim; my outbound caller ID WAS working fine for the longest time. Since the number was ported. I noticed after changing to the 502 adapter; (I don't believe the adapter is the issue, just that I never called myself to check until I was experimenting with the new adapter); but I no longer see an outgoing caller ID on the receiving line. I have a trouble ticket in on it. The response was they thought it got messed up when they put in to FIX the spelling of my name being wrong. However, the spelling got corrected and I remember numerous times seeing the outbound caller ID working fine. Most times I would check by calling my other voipo line. However now, it's just showing my number in place of my name. Being it WAS working, should it be fixable? Or am I out of luck? thanks... mike....

---

Your number is ELS and supports it. I looked at this earlier today actually and there's still a Level3 ticket open about it.

I still don't know how they misspelled it since it was submitted correctly on our end (I figured that was our issue). It looks like once they corrected it, they deleted it or something this time. So we're waiting to hear back from them unfortunately. It will get fixed though.

Wouldn't be device related.

This is another good example of why so many people are getting more and more irritated with Level3. It's virtually impossible to get anything done/fixed without it going through 4 or 5 levels of people. Literally. :)