Unsolved Changing extension mapping in Endpoint Manager Asterisk
-
Hello. I've been looking everywhere, but I haven't found a solution to my question yet. We use the Endpoint Manager module. In it, you can create mapping of an extension number from an asterisk with IP phones (Extension Mapping). Everything works in this part. But if it is necessary to change the extension number in the IP phone, difficulties begin. I did not find in the module how to do a simple change of extension numbers in the phone. So far, I am changing extensions as follows - I delete the existing mapping of the extension number with the phone. I add a new mapping of the extension number to the phone, and reboot the phone. But to restart the IP phone, you need to do a lot of actions. You need to go to the phone's web interface and reboot from there, you can reboot with a command from asterisk, you can also turn off the power and turn on the phone again. And if there are a lot of phones, how many extra actions will you have to do? Perhaps there is a correct way to change the old extension number mapping to a new number in the Endpoint Manager module, without unnecessary actions to manually restart the phone? IP phones Yealink
-
Endpoint Manager is available in many PBXs. Is there a specific one? Asterisk is the kernel of a PBX, but not a stand alone product.
My guess is you mean FreePBX, not Asterisk? FreePBX has an Endpoint Manager. But so does "every" PBX built off of Asterisk. So we'd need to know which one it is to know how to help.
-
@scottalanmiller Yes, FreePBX 15.0.23, EndPoint Manager15.0.48.1
-
Forgot to add. After adding a new extension mapping in the Endpoint Manager module and pressing send to phone, the phone does not receive a new extension. The phone remains with the old extension until the phone is rebooted, or you can manually download the configuration via autoprovision via the phone web interface
-
Your problem is a lack of understanding how EPM works.
When you use the update device button, a SIP NOTIFY message is sent to the extension.
Obviously, if you delete a mapping for Extension 123, but do not reset the phone itself, the phone will continue to be provisioned as extension 123.
When you reuse the MAC address for extension 124, which is not currently registered, there is no endpoint to send the SIP NOTIFY to.
Basically, EPM is using this asterisk command (assuming you have a Yealink phone) to tell extension 124 to check its config. But since 124 is not yet registered, nothing answers the message.
pjsip send notify reboot-yealink endpoint 124There are various contexts for different manufacturers
You can manually tell extension 123 to check it's config (which will make the device check, and pull the new config file with extension 124.
You can see it not work since I have no 124 on this PBX.
But for an extension that exists...
You can see the notify message in
sngrep
-
@JaredBusch Thanks for the help. Yes, I'm not quite familiar with the freepbx and endpoint manager settings yet. But I guessed that would be the result. It turns out I did everything right. It was only necessary to get a professional answer to make sure that I did not miss the right solution to my question. I found a solution to reboot phones via sip-notify earlier on this forum.
-
@JaredBusch Is it necessary to specify the [endpoint] command? It works for me even without specifying this command [endpoint]. For example, sip notify reboot-yealink 4287 or sip notify restart-yealink 4287 (depending on what I specified in the configuration file)
-
@goodtm said in Changing extension mapping in Endpoint Manager Asterisk:
@JaredBusch Is it necessary to specify the [endpoint] command? It works for me even without specifying this command [endpoint]. For example, sip notify reboot-yealink 4287 or sip notify restart-yealink 4287 (depending on what I specified in the configuration file)
You are using
sipnotpjsip. The commands are different.That said, the
chan_sipdriver is dead, and has been for years now. You need to switch to using thechan_pjsipdriver. -
Correct - you should be using PJsip. Also as far as changing extensions, you can run into the same issue even if you use the same extension number but you change the channel driver from SIP to PJSIP. This is how I've accomplished the task for remote phones that you can't touch. From your EPM, issue a reboot. Then real quick, you change the extension to use PJSIP, go to EPM, and then do a rebuild. If you do it properly, the phone will then grab the new settings and reconfigure itself and work just fine. You can of course do the same thing if you are changing the extension number on it.
