405 Method Not Allowed

[lazedo]

Hi,
i have 3cx voip for windows connected to a freeswitch/asterix/other IP/PBX.
mwi is not working.
the SUBSCRIBE message after login works ok, but when the IP/PBX sends a NOTIFY message with content-type "application/simple-message-summary", 3cx replies with "405 Method Not Allowed".

any hints ?

 

[leejor]

405 Method Not Allowed
The method specified in the Request-Line is understood, but not allowed for the address identified by the Request-URI.

So, it may not be that the messaging is incorrect, as far as 3Cx is concerned, it may be that the extension number is not valid (as sent) on the PBX, or possibly a problem with the IP.

 

[lazedo]

Hi,

the problem maybe with message content.
what are the values we should send ?

Exension : 995551077
ID : 995551077 (should be [email protected] ? )

here is the trace, it gets to part where it reads the message content.

thank you

NOTIFY sip:[email protected]:51988;rinstance=f0b80a4089095896 SIP/2.0
Via: SIP/2.0/UDP y.y.y.y:49154;rport=49154;branch=z9hG4bKpUHaa9vmX5prD
Max-Forwards: 70
Contact: <sip:[email protected]:49154>
To: <sip:[email protected]:51988>;rinstance=f0b80a4089095896
From: <sip:[email protected]>;tag=jKc68prDF8ypK
Call-ID: 72bd6777-778b-1231-37a2-0800277cd41b
CSeq: 47468273 NOTIFY
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Content-Type: application/simple-message-summary
Supported: precondition, path, replaces
User-Agent: Voip
Subscription-State: terminated;reason=noresource
Event: message-summary
Allow-Events: talk, hold, conference, presence, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer
Content-Length: 103

Messages-Waiting: yes
Message-Account: sip:[email protected]
Voice-Message: 37/0 (0/0)


(4972)8000110|TransactionUser.cxx(74):Match!
(4972)8000110|Helper.cxx(375):Helper::makeResponse(SipReq: NOTIFY [email protected]:51988 tid=pUHaa9vmX5prD cseq=NOTIFY [email protected]:49154 / 47468273 from(wire) code=100 reason=
(4972)8000110|TimerQueue.cxx(85):Adding timer: Timer Trying tid=pUHaa9vmX5prD ms=3500
(4972)8000110|TransactionState.cxx(2112):Send to TU: TU: DialogUsageManager size=0


NOTIFY sip:[email protected]:51988;rinstance=f0b80a4089095896 SIP/2.0
Via: SIP/2.0/UDP y.y.y.y:49154;rport=49154;branch=z9hG4bKpUHaa9vmX5prD
Max-Forwards: 70
Contact: <sip:[email protected]:49154>
To: <sip:[email protected]:51988>;rinstance=f0b80a4089095896
From: <sip:[email protected]>;tag=jKc68prDF8ypK
Call-ID: 72bd6777-778b-1231-37a2-0800277cd41b
CSeq: 47468273 NOTIFY
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Content-Type: application/simple-message-summary
Supported: precondition, path, replaces
User-Agent: Voip
Subscription-State: terminated;reason=noresource
Event: message-summary
Allow-Events: talk, hold, conference, presence, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer
Content-Length: 103

Messages-Waiting: yes
Message-Account: sip:[email protected]
Voice-Message: 37/0 (0/0)

(3708)8000108|DialogUsageManager.cxx(1333):Got: SipReq: NOTIFY [email protected]:51988 tid=pUHaa9vmX5prD cseq=NOTIFY [email protected]:49154 / 47468273 from(wire)
(3708)8000110|DialogUsageManager.cxx(1651)ialogUsageManager:rocessRequest: SipReq: NOTIFY [email protected]:51988 tid=pUHaa9vmX5prD cseq=NOTIFY [email protected]:49154 / 47468273 from(wire)
(3708)8000110|DialogSetId.cxx(34):********** Generated Local Tag ***********
(3708)8000110|DialogSetId.cxx(34):********** Generated Local Tag ***********
(3708)8000110|DialogSetId.cxx(34):********** Generated Local Tag ***********
(3708)8000110|DialogSet.cxx(85): ************* Created DialogSet(UAS) -- 72bd6777-778b-1231-37a2-0800277cd41b-3f798f23*************
(3708)8000110|DialogSetId.cxx(34):********** Generated Local Tag ***********
(3708)8000110|DialogId.cxx(50)ialogId:ialogId: 72bd6777-778b-1231-37a2-0800277cd41b-464db141-jKc68prDF8ypK
(3708)8000110|DialogSetId.cxx(34):********** Generated Local Tag ***********
(3708)8000110|DialogId.cxx(50)ialogId:ialogId: 72bd6777-778b-1231-37a2-0800277cd41b-0c5f7677-jKc68prDF8ypK
(3708)8000110|ServerOutOfDialogReq.cxx(52):ServerOutOfDialogReq::dispatch - handler found for NOTIFY method.
(3708)8000110|SipMessage.cxx(986):SipMessage::getContents: application/simple-message-summary
(3708)8000110|Helper.cxx(375):Helper::makeResponse(SipReq: NOTIFY [email protected]:51988 tid=pUHaa9vmX5prD cseq=NOTIFY [email protected]:49154 / 47468273 from(wire) code=405 reason=
(3708)8000110|DialogUsageManager.cxx(866):SEND:

SIP/2.0 405 Method Not Allowed

 

[leejor]

These appear to be the key logs...

(3708)8000110|DialogUsageManager.cxx(1651)ialogUsageManager:rocessRequest: SipReq: NOTIFY [email protected]:51988 tid=pUHaa9vmX5prD cseq=NOTIFY [email protected]:49154 / 47468273 from(wire)

And then...

(3708)8000110|ServerOutOfDialogReq.cxx(52):ServerOutOfDialogReq::dispatch - handler found for NOTIFY method.

So it seems to know what to do with it, but does not allow it, thus...

SIP/2.0 405 Method Not Allowed

 

[lazedo]

can someone tell what validations are made on the message content ?