Sip Insecure

Report
Question

Hi, How to allow registered sip users to call without re-authentication insecure =yes/very are deprecated in 1.8 I want to avoid fromuser= in peer configuration. When I add this in peer asterisk, my asterisk accepts call otherwise it says username mismatch. Please help Regards, Zohair Raza

Asterisk Users 3.3 years ago 4 Answer

asterisk 1.8.8 - caller ID not working.

Report
Question

On 01/05/12 16:42, Joseph wrote:
>I just noticed after upgrade from Asterisk 1.4.39 to 1.8.8
>my caller ID is not working
>
>WARNING[1671]: chan_sip.c:13956 check_auth: username mismatch, have <11>, digest has
>NOTICE[1671]: chan_sip.c:22048 handle_request_invite: Failed to authenticate device "KMIEC Z" ;tag=1c976040515
>
>--
>Joseph
>
>-- I had this problem before and was able to solve it:

Asterisk Users 3.5 years ago 14 Answer

Asterisk fail2ban filters - show us yours

Report
Question

Hi, In the thread "Interesting attack tonight & fail2ban them" Bruce B
mentioned it would be nice to have input from the Community to come up
with the best set of fail2ban filters. That's a great idea. So let's
start with Bruce's filters (thanks!) and take it from there. Anyone have
any improvements and/or additions? Apologies for the line wrap. No idea
how to prevent that in Thunderbird. The filters are also at
http://pastebin.com/6T9M1W3F Not sure but it may be possible that logging has changed between
Asterisk 1.4, 1.6, 1.8 and…

Asterisk Users 3.6 years ago 4 Answer

Interesting attack tonight & fail2ban them

Report
Question

You mentioned the IP, 208.122.57.58, where did you get that from? Following are the default for Asterisk 1.8 (It would be great to have
others input on this to strengthen this part of the filter): failregex = Registration from '.*' failed for '(:[0-9]{1,5})?' -
Wrong password
Registration from '.*' failed for '
(:[0-9]{1,5})?' - No
matching peer found
Registration from '.*' failed for '
(:[0-9]{1,5})?' -
Device does not match ACL
Registration from '.*' failed for '
(:[0-9]{1,5})?' -
Username/auth name mismatch
Registration from '.*' failed for '
(:[0-9]{1,5})?' - Peer
is not supposed…

Asterisk Users 3.6 years ago 0 Answer

Codec warnings after upgrade to 1.8

Report
Question

I'm getting various codec related warnings after upgrading to 1.8. Did I miss something in the UPGRADE file? Does Asterisk no longer transcode 8-)? WARNING[11123]: channel.c:4909 ast_write: Codec mismatch on channel DAHDI/i1/12124221200-74 setting write format to g722 from ulaw native formats 0x4 (ulaw) And WARNING[11120]: channel.c:4909 ast_write: Codec mismatch on channel SIP/interglobe-sip-000001e6 setting write format to g722 from ulaw native formats 0x4 (ulaw)

Asterisk Users 3.6 years ago 7 Answer