I didn’t know there was a limitation on that. It really is too bad. Imagine a corp user who needs to use a UDP SIP softphone when at work and a webrtc client when teleworking. The user should still have the same extension regardless of the transport type.
Anyway, let’s see if I can work around this. I can use alphanumerical values for the extensions ,right?
For instance, does the following look sane?
Yes, that would work. The reason that you can’t use the same extension is that the media configuration between WebRTC and normal SIP is vastly different, so one doesn’t work for the other. Noone has done work on figuring out a way to make things work in that scenario using a single configuration.
Also, you can have the same extension; what you are referring to are not extensions, in Asterisk terminology.
There is no requirement that the device name match the extension number in extensions.conf, and there are security advantages if it does not. You can have:
WebRTC media configuration doesn’t work like that, because you can’t send a call to a WebRTC endpoint with optional SRTP. It’s mandatory and the SDP has to state it as such. As a result you’d then have to send another INVITE to fallback to different behavior, which is something noone has coded.