<![CDATA[Nice names vs secure names]]>In my Asterisk my SIP extensions are named things like SIP/101klcdkfiefnvjdfas and SIP/102klcdkfiefnvjdfas to make it difficult to hack. My extensions.conf handles turning a dialed 101 into SIP/101klcdkfiefnvjdfas. Is there any way in FOP2 to map a nice name to a complicated name? I looked but didn't see any way to do it. I've been going to install FOP for a long time and finally did today, but without something to allow this, it's really hard to remember the login codes and reading the screen is messy at best.

Ira

]]>https://forum.fop2.com/topic/1317/nice-names-vs-secure-namesRSS for NodeTue, 27 Oct 2026 17:44:17 GMTFri, 30 Nov 2012 02:52:51 GMT60<![CDATA[Reply to Nice names vs secure names on Sat, 01 Dec 2012 08:07:21 GMT]]>Ah, a bit more playing and now it all makes sense. Sorry for the confusion, it's all working now.

Ira

]]>https://forum.fop2.com/post/5844https://forum.fop2.com/post/5844Sat, 01 Dec 2012 08:07:21 GMT<![CDATA[Reply to Nice names vs secure names on Sat, 01 Dec 2012 05:23:02 GMT]]>So, I did that and it still shows the name in

[SIP/LongUglyName]

and not either of the ones in
extension=101
or
label=NiceName

The other concern is logging in. it looks like the login name must be the long ugly name which is more the problem from my perspective.

I did "service fop2 restart" which seemed to stop and then start fop2 but it still shows the long ugly name.

Thanks so much for your help.

Ira

]]>https://forum.fop2.com/post/5843https://forum.fop2.com/post/5843Sat, 01 Dec 2012 05:23:02 GMT<![CDATA[Reply to Nice names vs secure names on Fri, 30 Nov 2012 22:57:39 GMT]]>FOP2 does not care about nice or ugly names, it just needs a device name to monitor, you can have

[SIP/101uglystringlongsecurity]
type=extension
extension=101
context=some-context
label=Nice Name

As you see, you have your ugly device, and then a nice name for the button label.

Best regards,

]]>https://forum.fop2.com/post/5842https://forum.fop2.com/post/5842Fri, 30 Nov 2012 22:57:39 GMT