NOTIFY and Method Not Allowed

[lamsoft]

Hi, all.
I have a VOIP Gateway (Linksys SPA-3102) on my network, after I configured other clients can successfully call out or in.

But my VOIP Gateway consistently send a command and the server keep replies method not allowed, what does it mean?

NOTIFY sip:192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.250:5060;branch=z9hG4bK-7c9fc838;rport=5060
Max-Forwards: 70
To: <sip:192.168.0.1>
From: SPA-3102 <sip:[email protected]>;tag=25fe529612d612cao0
Call-ID: [email protected]
CSeq: 45316 NOTIFY
User-Agent: Linksys/SPA3102-5.1.7(GW)
Event: keep-alive
Content-Length: 0


15:38:40.155|.\DialogUsageManager.cxx(1299)|Trace5|Resip|::ResipLogger:Got: SipReq:  NOTIFY 192.168.0.1 tid=-7c9fc838 cseq=NOTIFY / 45316 from(wire)
15:38:40.155|.\DialogUsageManager.cxx(1617)|Debug8|Resip|::ResipLogger:DialogUsageManager::processRequest: SipReq:  NOTIFY 192.168.0.1 tid=-7c9fc838 cseq=NOTIFY / 45316 from(wire)
15:38:40.155|.\DialogSetId.cxx(34)|Debug8|Resip|::ResipLogger:********** Generated Local Tag *********** 
15:38:40.155|.\DialogSetId.cxx(34)|Debug8|Resip|::ResipLogger:********** Generated Local Tag *********** 
15:38:40.155|.\DialogSetId.cxx(34)|Debug8|Resip|::ResipLogger:********** Generated Local Tag *********** 
15:38:40.155|.\DialogSet.cxx(84)|Debug8|Resip|::ResipLogger: ************* Created DialogSet(UAS)  -- [email protected]*************
15:38:40.155|.\DialogSetId.cxx(34)|Debug8|Resip|::ResipLogger:********** Generated Local Tag *********** 
15:38:40.155|.\DialogId.cxx(50)|Debug8|Resip|::ResipLogger:DialogId::DialogId: [email protected]
15:38:40.155|.\DialogSetId.cxx(34)|Debug8|Resip|::ResipLogger:********** Generated Local Tag *********** 
15:38:40.155|.\DialogId.cxx(50)|Debug8|Resip|::ResipLogger:DialogId::DialogId: [email protected]
15:38:40.155|.\ServerOutOfDialogReq.cxx(67)|Debug8|Resip|::ResipLogger:ServerOutOfDialogReq::dispatch - handler not found for NOTIFY method - sending 405.
15:38:40.155|.\Helper.cxx(372)|Debug8|Resip|::ResipLogger:Helper::makeResponse(SipReq:  NOTIFY 192.168.0.1 tid=-7c9fc838 cseq=NOTIFY / 45316 from(wire) code=405 reason=
15:38:40.155|.\DialogUsageManager.cxx(832)|Debug8|Resip|::ResipLogger:SEND: 

SIP/2.0 405 Method Not Allowed
Via: SIP/2.0/UDP 192.168.0.250:5060;branch=z9hG4bK-7c9fc838;rport=5060
To: <sip:192.168.0.1>;tag=0a73d257
From: "SPA-3102"<sip:[email protected]>;tag=25fe529612d612cao0
Call-ID: [email protected]
CSeq: 45316 NOTIFY
User-Agent: 3CXPhoneSystem 7.0.4708.0
Content-Length: 0

Thanks

 

[William400]

Hi

The Linksys is sending a keep-alive to the PABX.

This is not normally required and you can turn off the feature in the Linksys.

 

[Kevin Attard Compagno]

Hi there

William is correct: it's a keep-alive being sent from the phone to the proxy.

A little clarification here: It can be safely be turned off in a LAN environment, but if the phone is connecting to the PBX from outside the PBX's LAN, it may assist the NAT device between the phone and the internet to keep the dynamic port mapping on the NAT device for SIP open, ensuring that the phone continues to receive to send and receive calls correctly. This will depend somewhat on the NAT implementation on the device.

Regards

Kevin

 

[lamsoft]

Then I disable the NAT keep alive setting.
Thank you very much.