[Asterisk-Users] asterisk behind cisco pix 506
Andreas Wilkens
wilkens_andreas at hotmail.com
Sun Jun 4 13:18:43 MST 2006
I use cleartext password. I double checked that is the right on several
times. When disbaling the fixup sip, the password is accepted.
>From: Jason Bachman <jason at bachman.cc>
>Reply-To: Asterisk Users Mailing List - Non-Commercial
>Discussion<asterisk-users at lists.digium.com>
>To: Asterisk Users Mailing List - Non-Commercial
>Discussion<asterisk-users at lists.digium.com>
>Subject: Re: [Asterisk-Users] asterisk behind cisco pix 506
>Date: Sun, 04 Jun 2006 15:55:15 -0400
>
>Debugs are showing that the request is getting there but the password is
>wrong. Are u using cleartext or md5 hash passwords? I would double check
>your secret= lines in sip.conf and make sure that the passwords in your
>clients match.
>
>Andreas Wilkens wrote:
>>Sorry, it´s not working. When enabling the fixup I got a "Wrong" password.
>>Asterisk has private IP 192.168.100.160 and an official IP. I set a static
>>fom the official IP to the internal private one and allowed UDP 5060 and
>>10000-20000 to everybody
>>
>>Attached the log:
>>
>>Jun 4 18:20:38 DEBUG[1951] chan_sip.c: Allocating new SIP dialog for
>>A2F6792434A79112299E0E6CA124D at 192.168.178.1 - REGISTER (No RTP)
>>Jun 4 18:20:38 DEBUG[1951] chan_sip.c: **** Received REGISTER (2) -
>>Command in SIP REGISTER
>>Jun 4 18:20:39 DEBUG[1951] chan_sip.c: **** Received REGISTER (2) -
>>Command in SIP REGISTER
>>Jun 4 18:20:39 DEBUG[1951] chan_sip.c: Ignoring SIP message because of
>>retransmit (REGISTER Seqno 1, ours 1)
>>Jun 4 18:20:39 DEBUG[1951] chan_sip.c: **** Received REGISTER (2) -
>>Command in SIP REGISTER
>>Jun 4 18:20:39 DEBUG[1951] chan_sip.c: SIP REGISTER attempt failed for
>>101 : Bad password
>>Jun 4 18:20:39 NOTICE[1951] chan_sip.c: Registration from
>>'<sip:101 at 192.168.100.160>' failed for '84.141.196.36' - Wrong password
>>Jun 4 18:20:39 DEBUG[1951] chan_sip.c: SIP message could not be handled,
>>bad request: A2F6792434A79112299E0E6CA124D at 192.168.178.1
>>Jun 4 18:20:39 DEBUG[1951] chan_sip.c: **** Received REGISTER (2) -
>>Command in SIP REGISTER
>>Jun 4 18:20:39 DEBUG[1951] chan_sip.c: SIP REGISTER attempt failed for
>>101 : Bad password
>>Jun 4 18:20:39 NOTICE[1951] chan_sip.c: Registration from
>>'<sip:101 at 192.168.100.160>' failed for '84.141.196.36' - Wrong password
>>Jun 4 18:20:39 DEBUG[1951] chan_sip.c: SIP message could not be handled,
>>bad request: A2F6792434A79112299E0E6CA124D at 192.168.178.1
>>Jun 4 18:20:50 DEBUG[1951] chan_sip.c: **** Received REGISTER (2) -
>>Command in SIP REGISTER
>>Jun 4 18:20:50 DEBUG[1951] chan_sip.c: SIP REGISTER attempt failed for
>>101 : Bad password
>>Jun 4 18:20:50 NOTICE[1951] chan_sip.c: Registration from
>>'<sip:101 at 192.168.100.160>' failed for '84.141.196.36' - Wrong password
>>Jun 4 18:20:50 DEBUG[1951] chan_sip.c: SIP message could not be handled,
>>bad request: A2F6792434A79112299E0E6CA124D at 192.168.178.1
>>Jun 4 18:20:50 DEBUG[1951] chan_sip.c: **** Received REGISTER (2) -
>>Command in SIP REGISTER
>>Jun 4 18:20:50 DEBUG[1951] chan_sip.c: SIP REGISTER attempt failed for
>>101 : Bad password
>>Jun 4 18:20:50 NOTICE[1951] chan_sip.c: Registration from
>>'<sip:101 at 192.168.100.160>' failed for '84.141.196.36' - Wrong password
>>Jun 4 18:20:50 DEBUG[1951] chan_sip.c: SIP message could not be handled,
>>bad request: A2F6792434A79112299E0E6CA124D at 192.168.178.1
>>Jun 4 18:21:05 DEBUG[1951] chan_sip.c: Auto destroying call
>>'A2F6792434A79112299E0E6CA124D at 192.168.178.1'
>>Jun 4 18:21:11 DEBUG[1951] chan_sip.c: Allocating new SIP dialog for
>>A2F6792434A79112299E0E6CA124D at 192.168.178.1 - REGISTER (No RTP)
>>Jun 4 18:21:11 DEBUG[1951] chan_sip.c: **** Received REGISTER (2) -
>>Command in SIP REGISTER
>>Jun 4 18:21:11 DEBUG[1951] chan_sip.c: **** Received REGISTER (2) -
>>Command in SIP REGISTER
>>Jun 4 18:21:11 DEBUG[1951] chan_sip.c: SIP REGISTER attempt failed for
>>101 : Bad password
>>Jun 4 18:21:11 NOTICE[1951] chan_sip.c: Registration from
>>'<sip:101 at 192.168.100.160>' failed for '84.141.196.36' - Wrong password
>>Jun 4 18:21:11 DEBUG[1951] chan_sip.c: SIP message could not be handled,
>>bad request: A2F6792434A79112299E0E6CA124D at 192.168.178.1
>>Jun 4 18:21:12 DEBUG[1951] chan_sip.c: **** Received REGISTER (2) -
>>Command in SIP REGISTER
>>Jun 4 18:21:12 DEBUG[1951] chan_sip.c: SIP REGISTER attempt failed for
>>101 : Bad password
>>Jun 4 18:21:12 NOTICE[1951] chan_sip.c: Registration from
>>'<sip:101 at 192.168.100.160>' failed for '84.141.196.36' - Wrong password
>>Jun 4 18:21:12 DEBUG[1951] chan_sip.c: SIP message could not be handled,
>>bad request: A2F6792434A79112299E0E6CA124D at 192.168.178.1
>>
>>
>>
>>>From: Jason Bachman <jason at bachman.cc>
>>>Reply-To: Asterisk Users Mailing List - Non-Commercial
>>>Discussion<asterisk-users at lists.digium.com>
>>>To: Asterisk Users Mailing List - Non-Commercial
>>>Discussion<asterisk-users at lists.digium.com>
>>>Subject: Re: [Asterisk-Users] asterisk behind cisco pix 506
>>>Date: Sun, 04 Jun 2006 10:21:23 -0400
>>>
>>>Enable the SIP fixup, and let the PIX handle the SIP/NAT issues. Do not
>>>use the nat features in asterisk
>>>forward all requests for UDP port 5060 to the asterisk box. also forward
>>>all requests for UDP 10000-20000 to the asterisk box. On asterisk
>>>rtp.conf file limit your RTP range 10000-20000. That should fix your
>>>problem.. Works here.
>>>
>>>Jason
>>>
>>>Andreas Wilkens wrote:
>>>>No, not working. Seems to be a prob w/ NAT
>>>>
>>>>
>>>>>From: "Woodoo People .pGa!" <wpeople at Shadow.microsystem.hu>
>>>>>Reply-To: Asterisk Users Mailing List - Non-Commercial
>>>>>Discussion<asterisk-users at lists.digium.com>
>>>>>To: Asterisk Users Mailing List - Non-Commercial
>>>>>Discussion<asterisk-users at lists.digium.com>
>>>>>Subject: Re: [Asterisk-Users] asterisk behind cisco pix 506
>>>>>Date: Sun, 4 Jun 2006 12:56:32 +0200
>>>>>
>>>>> > i try to make asterisk work behind a cisco pix 506. After
>>>>>deactivating the
>>>>> > sip fixup i´m able to register but I didn´t hear another party. It´s
>>>>> > dialing and connecting but silence. Does anybody has some tips or a
>>>>>sample
>>>>> > config for that issue ?
>>>>>allow any to asterisk?
>>>>>--
>>>>>WoodOO-[P]an[G]alaktikan[A]gent-People <][> http://shadow.pganet.com
>>>>>wpeople at shadow.pganet.com]iCQ#33118021[wpeople.on.iRCNet]wpeople at RedHat.users
>>>>>
>>>>>
>>>>>_______________________________________________
>>>>>--Bandwidth and Colocation provided by Easynews.com --
>>>>>
>>>>>Asterisk-Users mailing list
>>>>>To UNSUBSCRIBE or update options visit:
>>>>> http://lists.digium.com/mailman/listinfo/asterisk-users
>>>>
>>>>
>>>>_______________________________________________
>>>>--Bandwidth and Colocation provided by Easynews.com --
>>>>
>>>>Asterisk-Users mailing list
>>>>To UNSUBSCRIBE or update options visit:
>>>> http://lists.digium.com/mailman/listinfo/asterisk-users
>>>
>>>_______________________________________________
>>>--Bandwidth and Colocation provided by Easynews.com --
>>>
>>>Asterisk-Users mailing list
>>>To UNSUBSCRIBE or update options visit:
>>> http://lists.digium.com/mailman/listinfo/asterisk-users
>>
>>
>>_______________________________________________
>>--Bandwidth and Colocation provided by Easynews.com --
>>
>>Asterisk-Users mailing list
>>To UNSUBSCRIBE or update options visit:
>> http://lists.digium.com/mailman/listinfo/asterisk-users
>
>_______________________________________________
>--Bandwidth and Colocation provided by Easynews.com --
>
>Asterisk-Users mailing list
>To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
More information about the asterisk-users
mailing list