search for: foobar1

..., I'm trying to build two differents PJSIP trunks between two Asterisk 13.8.0enabled boxes. I thought I could set up both trunks like this: Box A/port 5060 <------ Trunk1 -----> Box B/port 5060 Box A/port 5062 <------ Trunk2 -----> Box B/port 5062 and declare trunks like this: [foobar1] type=endpoint transport=simpletrans context=from-customer aors=foobar1 allow=!all,alaw [foobar1] type=identify endpoint=foobar1 match=100.66.1.104:5060 [foobar1] type=aor contact=sip:100.66.1.104:5060 (In my above example,simpletrans is one of the two configured UDP transports). When giving t...

...Log on to: Old password: New password: Confirm new password: 2. The password requirements set forth by ppolicy (such as length, strength, and recently used passwords) don't seem to be adhered to. I can put in 'foobar' as the new password, change it to 'foobar1', change it back to 'foobar', and Samba will happily change the passwords. While the change does take, and I can log in to the domain with 'foobar' or 'foobar1' as the password, it's certainly not what I want. Conversely, I get this desired results when invoking ...

Is there something strange about using regular expressions in the context to which incoming Skype calls go? If I set up accounts, foobar1, foobar2, etc, it doesn't seem to work to have: exten => _foobarX,1,... should it?