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.5 years ago 4 Answers

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.7 years ago 14 Answers

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.7 years ago 4 Answers

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.7 years ago 0 Answers

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.7 years ago 7 Answers

instead of username

Report
Question

Hello,
Asterisk seems to try to authenticate incoming INVITE based on the [section]
in sip.conf and not the username specified. I just removed the "insecure" option from my sip.conf requesting every
connection to be authenticated. I added the match_auth_username=yes in the
[general] section for extra security. To make it work, I have to use the
same [section] identifier as username. This is really bad because if
multiple provider are giving me the same username, it doesn't work. If I put the following data in sip.conf, it doesn't work. Asterisk return
the following error:…

Asterisk Users 4.2 years ago 0 Answers

username mismatch

Report
Question

"Dan Journo" wrote:
>> I've got a Polycom 501 that I just can't seem to get lines 2 and 3 to
work on.
>> Line 1 works fine.
>
> Last time I had that issue, it resolved itself when i restarted Asterisk. Any ideas as to what causes it, though? > Are you able to do that? I'm scheduling a SIP reload tonight. Might as well do an Asterisk restart
instead.

Asterisk Users 4.2 years ago 0 Answers

Issue with Asterisk & Aastra 57i at v3.2

Report
Question

2011/5/5 Richard Kenner > I recently tried to update my Aastra 57i to version 3.2 and ran into
> a problem. It won't properly register and says "contact mismatch".
> I added "sip contact matching: 2" to aastra.cfg, but that didn't help.
>
> When I look at the SIP trace, but I see is the Aastra sending a
> REGISTER and Asterisk replying with the 401. The phone then sends
> the REGISTER again, this time with the hash. Asterisk now replies OK,
> but sends an OPTION packet FIRST…

Asterisk Users 4.4 years ago 0 Answers

username mismatch on calls from client

Report
Question

I have my asterisk Server A registered as a client with another asterisk
Server B. When I place a call from Server A to B I get the following: WARNING[834]: chan_sip.c:12673 check_auth: username mismatch, have ,
digest has NOTICE[834]: chan_sip.c:19961 handle_request_invite: Failed to authenticate
device "0014734068436" ;tag=as0b50a2f9 I can call from server A to Server B with no problem
My sip.conf (asterisk client A) register => openbts1:openbts12@x.x.x.x:5060
[SS72]
type=peer
canreinvite=no
secret=openbts12
username=openbts1
host=x.x.x.x
context=openbts
fromuser=openbts1
dtmfmode=info
fromdomain=x.x.x.x
insecure=port,invite
qualify=yes
disallow=all

Asterisk Users 4.8 years ago 0 Answers