[asterisk-users] Problematic Trunk SIP: Got SIP response 405 "Method not allowed"

Tue Sep 2 14:04:18 CDT 2008

On Mon, Sep 1, 2008 at 5:57 AM, daniele visaggio
<visaggio.daniele at gmail.com> wrote:
>
>
> 2008/9/1 Steven Howes <steve at geekinter.net>
>>
>> Sip debug please.
>>
>>
>>
>
> ---
> Sep 1 11:53:42 VERBOSE[3599] logger.c:
> <-- SIP read from 10.1.1.11:5060:
> SIP/2.0 405 Method not allowed
> From: ;tag=as411269a4
> To: ;tag=a01010b-13c4-64622-1881f814-4122656d
> Call-ID: 011058b75aafa1c1530f1a0600fae548 at 127.0.0.1
> CSeq: 146 REGISTER
> Via: SIP/2.0/UDP 10.1.1.36:5060;rport=5060;branch=z9hG4bK01f3b5c6
> Supported: 100rel,replaces
> Content-Length: 0
>
>
> Sep 1 11:53:42 VERBOSE[3599] logger.c: --- (8 headers 0 lines) ---
> Sep 1 11:53:42 DEBUG[3599] chan_sip.c: Stopping retransmission on
> '011058b75aafa1c1530f1a0600fae548 at 127.0.0.1' of Request 146: Match Found
> Sep 1 11:53:42 VERBOSE[3599] logger.c: -- Got SIP response 405 "Method not
> allowed" back from 10.1.1.11
> Sep 1 11:53:42 VERBOSE[3599] logger.c: Destroying call
> '011058b75aafa1c1530f1a0600fae548 at 127.0.0.1'
> Sep 1 11:53:45 DEBUG[10671] manager.c: Manager received command 'login'
> Sep 1 11:53:45 VERBOSE[10671] logger.c: == Parsing
> '/etc/asterisk/manager.conf': Sep 1 11:53:45 VERBOSE[10671] logger.c: ==
> Parsing '/etc/asterisk/manager.conf': Found
> Sep 1 11:53:45 VERBOSE[10671] logger.c: == Parsing
> '/etc/asterisk/manager_additional.conf': Sep 1 11:53:45 VERBOSE[10671]
> logger.c: == Parsing '/etc/asterisk/manager_additional.conf': Found
> Sep 1 11:53:45 VERBOSE[10671] logger.c: == Parsing
> '/etc/asterisk/manager_custom.conf': Sep 1 11:53:45 VERBOSE[10671] logger.c:
> == Parsing '/etc/asterisk/manager_custom.conf': Found
> Sep 1 11:53:45 DEBUG[10671] acl.c: 0.0.0.0/0.0.0.0/0.0.0.0 appended to acl
> for peer
> Sep 1 11:53:45 DEBUG[10671] acl.c: 127.0.0.1/255.255.255.0/255.255.255.0
> appended to acl for peer
> Sep 1 11:53:45 DEBUG[10671] acl.c: ##### Testing 127.0.0.1 with 0.0.0.0
> Sep 1 11:53:45 DEBUG[10671] acl.c: ##### Testing 127.0.0.1 with 127.0.0.0
> Sep 1 11:53:45 VERBOSE[10671] logger.c: == Manager 'admin' logged on from
> 127.0.0.1
> Sep 1 11:53:47 DEBUG[10671] manager.c: Manager received command 'Command'
> Sep 1 11:53:47 DEBUG[10671] manager.c: Manager received command 'Command'
> Sep 1 11:53:47 DEBUG[10671] manager.c: Manager received command 'Command'
> Sep 1 11:53:47 DEBUG[10671] manager.c: Manager received command 'Command'
> Sep 1 11:53:47 DEBUG[10671] manager.c: Manager received command 'Command'
> Sep 1 11:53:47 VERBOSE[10671] logger.c: == Manager 'admin' logged off from
> 127.0.0.1
> Sep 1 11:53:47 DEBUG[10679] manager.c: Manager received command 'login'
> Sep 1 11:53:47 VERBOSE[10679] logger.c: == Parsing
> '/etc/asterisk/manager.conf': Sep 1 11:53:47 VERBOSE[10679] logger.c: ==
> Parsing '/etc/asterisk/manager.conf': Found
> Sep 1 11:53:47 VERBOSE[10679] logger.c: == Parsing
> '/etc/asterisk/manager_additional.conf': Sep 1 11:53:47 VERBOSE[10679]
> logger.c: == Parsing '/etc/asterisk/manager_additional.conf': Found
> Sep 1 11:53:47 VERBOSE[10679] logger.c: == Parsing
> '/etc/asterisk/manager_custom.conf': Sep 1 11:53:47 VERBOSE[10679] logger.c:
> == Parsing '/etc/asterisk/manager_custom.conf': Found
> Sep 1 11:53:47 DEBUG[10679] acl.c: 0.0.0.0/0.0.0.0/0.0.0.0 appended to acl
> for peer
> Sep 1 11:53:47 DEBUG[10679] acl.c: 127.0.0.1/255.255.255.0/255.255.255.0
> appended to acl for peer
> Sep 1 11:53:47 DEBUG[10679] acl.c: ##### Testing 127.0.0.1 with 0.0.0.0
> Sep 1 11:53:47 DEBUG[10679] acl.c: ##### Testing 127.0.0.1 with 127.0.0.0
> Sep 1 11:53:47 VERBOSE[10679] logger.c: == Manager 'admin' logged on from
> 127.0.0.1
> Sep 1 11:53:47 VERBOSE[10679] logger.c: == Manager 'admin' logged off from
> 127.0.0.1
> Sep 1 11:53:49 DEBUG[10681] manager.c: Manager received command 'login'
> Sep 1 11:53:49 VERBOSE[10681] logger.c: == Parsing
> '/etc/asterisk/manager.conf': Sep 1 11:53:49 VERBOSE[10681] logger.c: ==
> Parsing '/etc/asterisk/manager.conf': Found
> Sep 1 11:53:49 VERBOSE[10681] logger.c: == Parsing
> '/etc/asterisk/manager_additional.conf': Sep 1 11:53:49 VERBOSE[10681]
> logger.c: == Parsing '/etc/asterisk/manager_additional.conf': Found
> Sep 1 11:53:49 VERBOSE[10681] logger.c: == Parsing
> '/etc/asterisk/manager_custom.conf': Sep 1 11:53:49 VERBOSE[10681] logger.c:
> == Parsing '/etc/asterisk/manager_custom.conf': Found
> Sep 1 11:53:49 DEBUG[10681] acl.c: 0.0.0.0/0.0.0.0/0.0.0.0 appended to acl
> for peer
> Sep 1 11:53:49 DEBUG[10681] acl.c: 127.0.0.1/255.255.255.0/255.255.255.0
> appended to acl for peer
> Sep 1 11:53:49 DEBUG[10681] acl.c: ##### Testing 127.0.0.1 with 0.0.0.0
> Sep 1 11:53:49 DEBUG[10681] acl.c: ##### Testing 127.0.0.1 with 127.0.0.0
> Sep 1 11:53:49 VERBOSE[10681] logger.c: == Manager 'admin' logged on from
> 127.0.0.1
> Sep 1 11:53:49 VERBOSE[10681] logger.c: == Manager 'admin' logged on from
> 127.0.0.1
>
> Thanks for your prompt reply
>

You have Asterisk configured to register to your PBX.  The Samsung
doesn't support REGISTER.  Remove the relevant register => line from
sip.conf.

I should point out that REGISTER failures would not necessarily
prevent a successful call setup but because it does not support
REGISTER you will have to create a trunk (or whatever their
terminology is) on the Samsung to point to your Asterisk system's IP
address.

-- 
Kristian Kielhofner
http://blog.krisk.org