Implemented Able to Set Mobile Number as "SP1"/2/3/4

chris.eakland

Platinum Partner
Advanced Certified
Joined
Jul 24, 2012
Messages
15
Reaction score
6
With Version 14 and under i was able to create a dummy extensions, lets call them 401/402/403/404. Then i would set the mobile number to be "SP1"/"SP2"/"SP3"/"SP4" and configure it so that when the extension was not registered it would forward to the mobile number. I would be then able to Dial 401 to pull a call out of SP1 or blind transfer a call to 401 to put the call into SP1. This was great for Yealink W52/56 phones and other phones that do not have the buttons to be able to configure a BLF key for Shared Park lines. this functionality was removed with V15 and i get an error saying that SP1 is not a supported Mobile Number format. Please bring this functionality back as it is very useful.
 
Upvote 10
Actually, I was doing a bit of testing with this and I still see a problem.
I see that if I add a BLF to the 3CX softphone for Windows and a Fanvil X5S I am testing with, the SP1 BLF does not light up when a call is parked there. This is not at all helpful. Is this normal behavior?

Roy
 
I'm sure others have seen this but if not I discovered that if you import your SPn numbers into the directory that you can avoid the invalid input errors and users can transfer in and out of Shared Parks without worrying about typing uppercase. I added "_" to the name so they are displayed at the top of contacts for quick access.

To Park to SP1 from Android is: Trans/Contacts/_SP1/Call (no typing just clicks)
To Pickup SP1 from Android is: Contacts/_SP1/Call (no typing just clicks)


Example csv

FirstName,LastName,Company,Mobile,Mobile2,Home,Home2,Business,Business2,Email,Other,BusinessFax,HomeFax,Pager
_SP 1,,,SP1,,,,,,,,,,
_SP 2,,,SP2,,,,,,,,,,
_SP 3,,,SP3,,,,,,,,,,
_SP 4,,,SP4,,,,,,,,,,
 
Still doesn't help with cordless phones, JMK. But now we can add SPx as an external number again when setting up routing on an extension.
So I used 77x && for S & P as alpha. 771,772,773, etc.
Works like a charm.
 
I'm sure others have seen this but if not I discovered that if you import your SPn numbers into the directory that you can avoid the invalid input errors and users can transfer in and out of Shared Parks without worrying about typing uppercase. I added "_" to the name so they are displayed at the top of contacts for quick access.

To Park to SP1 from Android is: Trans/Contacts/_SP1/Call (no typing just clicks)
To Pickup SP1 from Android is: Contacts/_SP1/Call (no typing just clicks)


Example csv

FirstName,LastName,Company,Mobile,Mobile2,Home,Home2,Business,Business2,Email,Other,BusinessFax,HomeFax,Pager
_SP 1,,,SP1,,,,,,,,,,
_SP 2,,,SP2,,,,,,,,,,
_SP 3,,,SP3,,,,,,,,,,
_SP 4,,,SP4,,,,,,,,,,

We've been doing this for some time now in v15x for our clients to be able to quickly Park and Pickup using there mobile phones. I just noticed that v16 is now error checking importing of the phone number and won't allow SPx as a valid entry. How can I get this feature/workaround back?