Using different Extension Number & AUTH User ?

D

DOLMark

New Member
Feb 26, 2026
4
0
1
57
Hi All

(New to FusionPBX, so please forgive silly questions which I've not found answers to in docs yet :-)

I need to configure a system so that an extension number is not the same as the SIP User Auth. (Migrating over legacy SIP system and trying hard not to reconfigure everything). So ideally I'm after something like:

Extensions
User: 11
SIP Auth: ABC-XYZ-11
Pass: somepassword

So that the SIP account registers with the ABC-XYZ-11 credentials but rings when someone dials extension 11.

Is this doable in the standard extension config? I've seen mention of extension having an auth user but not sure if thats bad AI, old docs or people confused, as I cant find it :)

One possibility I was looking at creating the extensions as ABC-XYZ-11, with local CLI as 11. Then adding a dialplan / destination to catch 11 and send it to ABC-XYZ-11. Will that work?

Can this be done? If so what's the best way to do this?

Thanks
Mark
 
I'm not aware of any way to amend the authid for an extension, there doesn't appear to be anything in the database. Looking at a template the authid uses the same value as the extension number so it appears there's no separate value for an authid. I'd like to see this as it would make things more secure.
 
  • Like
Reactions: DOLMark
Can you explain how this would break BLF (Keys)?
You try and move everything you can to ext 11 (including BLF keys) but if anyone tries to traffic a call to the old extension it will still be forwarded to the new user so that the new extension will receive every incoming call. Also any BLF keys using the old extension should still arrive at ext 11 perfectly.

Let me know if I'm missing any context
 
Ah, sorry, context is; I'm trying not to change the configuration of the phones as remote access/provisioning is not easily available.

Existing system is set up for extension number (11) to be used for Calling or BLF, but Auth is the long ABC-XYZ-11 style. Once you're auth'd with ABC-XYZ-11 that effectively sets you domain/realm to ABC-XYZ for everything else to work in.

So if extension config is ABC-XYZ-11 with a redirect of 11 to it, a BLF for 11 misses the extension config.

... now if Fusion had a config box between Extension and Password of "SIP Username" I'm a happy man :-)
 
Let me get back to you in more detail later as I don't have the time at the moment.

What I am understanding from this is that if 'Jane' ext XYZ tries to call 'John' ext 11, it will fail because they are on different subdomains and therefore from the context of Jane, there is no valid extension 11

Let me know if this is not the issue
 
intimidatingtriangle2131 said:
Let me get back to you in more detail later as I don't have the time at the moment.

What I am understanding from this is that if 'Jane' ext XYZ tries to call 'John' ext 11, it will fail because they are on different subdomains and therefore from the context of Jane, there is no valid extension 11

Let me know if this is not the issue
Click to expand...
Not quite. Let me try and explain myself a bit clearer.

Everything is built to ignore the @domain in SIP. A users domain is determined by the first section of the username part of the sip authentication. SIP Auth ID are built as [domain]-[extension]@[dont care what domain is]

Most phones cope with this as they allow you to separate display/register/auth usernames.

SIP Auth abc-xyz-11@[dont care] is actually:
Extension: 11
Domain abc-xyz

So extension 11 can be dialled/used as BLF as you'd expect within that domain.

Multiple domains are implemented as part of the SIP Auth username:
SIP Auth freddie-11@[dont care]
Extension: 11
Domain freddie
 
You must log in or register to reply here.
Top Bottom