0
Votes

2 Digit Phone Numbers in Omada VOIP configuration

 
0
Votes

2 Digit Phone Numbers in Omada VOIP configuration

2 Digit Phone Numbers in Omada VOIP configuration
2 Digit Phone Numbers in Omada VOIP configuration
a week ago
Tags: #3cx
Model: EAP650-Desktop  
Hardware Version: V1
Firmware Version: 1.1.0 Build 20251105 Rel. 50852

We run a 3CX Phone system, which has been configured for 2 digit extensions.

We have rolled out a number of EAP650-Desktop's as they have a FXS port, which we intended to connect some older POTS based cordless phones and ringers.

Unfortunately, the Omada > Network Config > VoIP > VoIP Phone Number > "Add" function limits the phone number (extension number) to either a single digit or 3-32 digits.

We have created a provider using "Other Provider".

 

We are unable to authenticate our EAP-650 Desktop units because we are unable to enter our 2 digit extensions, as they are considered invalid.

 

Does anyone have a suitable workaround, or can TP-Link implement an override to this behaviour so we can connect using the correct extension number our system requires.

 

Switching the 3CX Phone system to use 3 digit extensions would work, however given the amount of existing extensions on this system, in this case that solution would not be suitable.

 

Running Omada Controller 6.2.0.17.

 

Thanks in advanced,

Scott. 

 

 

#1
2 Reply
Re:2 Digit Phone Numbers in Omada VOIP configuration
Friday

  @Scott-G Can you try placing a 0 in front of the extension in the Omada Controller to turn the two digit extension into a three digit one for provisioning? (ex: 12 -> 012)



 

Check out our subreddit, r/Omada_Networks! Want to help test and give feedback on new products? Sign up for the US Enterprise Beta Program here! Need a ticket? Contact Technical Support
#2
Re:2 Digit Phone Numbers in Omada VOIP configuration
Monday - last edited Monday

  @NeilR_M thanks for the follow up.

 

Yes we have tried every possible combination we could think of to trick either system into allowing this to authenticate, but in all cases, the TP-Link SIP stack sent through the Phone/Extension number as typed, and the 3CX system rejected the authentication attempt - noting that 2 digit extensions could not be saved via the form, nor when submitted via a modified HTTP POST payload, both throwing errors.

 

Cheers,

Scott. 

#3