ira

Member

Last active 11 years ago

  1. 11 years ago
    Sat Dec 1 08:07:21 2012
    ira posted in Nice names vs secure names.

    Ah, a bit more playing and now it all makes sense. Sorry for the confusion, it's all working now.

    Ira

  2. Sat Dec 1 05:23:02 2012
    ira posted in Nice names vs secure names.

    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

  3. 12 years ago
    Fri Nov 30 02:52:51 2012
    ira started the conversation 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