Wow! never thought of using regex :<

nice

viewing solutions is depressing....

i absolutly agree with you , in fact they should accept all forms of data types for a more realistic and complete training ...

The reason why you should never do str == str in solutions is:
The answer: Phone => 1-908-512-2222, Name => Peter O'Brien, Address => High Street CC-47209
My answer: Phone => 1-908-512-2222, Name => Peter O'Brien, Address => High Street CC-47209

The difference is one space. Stop comparing str == str in solutions where there is no reason for it.
This kata could have it's solutions as a dict which is not just more readable but this is what we would do in real life:

{
  "phone": ...,
  "name": ...,
  "address": ...
}

There is no reason here for using strings like this.

Does this have random tests?

range('a', 'z') is ok. Have a look at array_search()

Still not working since '2' and '8' is 3 so the solution is 45 not 47.

It is not an issue.

The MORSE_CODE "code table" contains a key for '...---...' which has a value of 'SOS'.

Just an advice ...

Using a loop for creating abc is unnecessary, use ord() and chr() next time.

PHP translation added.

Same with me.