Dmitriy Serov
2015-Sep-07 08:24 UTC
[asterisk-users] res_pjsip. Turn off the authorization request for an incoming MESSAGE
Hello. Continuea months-longstrugglethat is associatedwith the transfer from chan_sip to res_pjsip. Where are many gates (GSM gate) that do not supportauthentication whensendingMESSAGE. For example, 4goip when relay incoming SMS. Using chan_sip it was not a problem. Using res_pjsip is the problem :( Is any way to turn off the authorization request for an incoming MESSAGE using res_pjsip? Or any workaround? [2015-09-07 06:01:14] DEBUG[12947] pjsip: sip_endpoint.c Processing incoming message: Request msg MESSAGE/cseq=542 (rdata0x7f88642fdc28) [2015-09-07 06:01:14] VERBOSE[12947] res_pjsip_logger.c: <--- Received SIP request (447 bytes) from UDP:109.165.111.xx:5807 ---> MESSAGE sip:smsin at 85.142.148.xx SIP/2.0 Via: SIP/2.0/UDP 109.165.111.xx:5807;branch=z9hG4bK837973400 Route: <sip:85.142.148.xx;lr> From: <sip:srv_918588xxxx at 85.142.148.xx>;tag=284759743 To: <sip:smsin at 85.142.148.xx> Call-ID: 76603xxxx at 192.168.1.100 CSeq: 542 MESSAGE Contact: <sip:srv_918588xxxx at 109.165.111.xx:5807> Max-Forwards: 30 User-Agent: dble Content-Type: text/plain Content-Length: 35 111 ??? ?????? 68,08 rub. [2015-09-07 06:01:14] DEBUG[23059] pjsip: sip_endpoint.c Distributing rdata to modules: Request msg MESSAGE/cseq=542 (rdata0x7f88640a9288) [2015-09-07 06:01:14] DEBUG[23059] res_pjsip_endpoint_identifier_ip.c: No identify sections to match against [2015-09-07 06:01:14] DEBUG[23059] res_pjsip_endpoint_identifier_user.c: Retrieved endpoint srv_9185880046 [2015-09-07 06:01:14] DEBUG[23059] pjsip: endpoint .Response msg 401/MESSAGE/cseq=542 (tdta0x7f88717063b0) created [2015-09-07 06:01:14] VERBOSE[23059] res_pjsip_logger.c: <--- Transmitting SIP response (479 bytes) to UDP:109.165.111.xx:5807 ---> SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 109.165.111.xx:5807;rport=5807;received=109.165.111.xx;branch=z9hG4bK837973400 Call-ID: 76603xxxx at 192.168.1.100 From: <sip:srv_918588xxxx at 85.142.148.xx>;tag=284759743 To: <sip:smsin at 85.142.148.xx>;tag=z9hG4bK837973400 CSeq: 542 MESSAGE WWW-Authenticate: Digest realm="ruvoip.net",nonce="1441594874/5741fb37496404a4aa5cf0e53a129867",opaque="7441b8c64eddc67a",algorithm=md5,qop="auth" Server: ruVoIP.net PBX Content-Length: 0 Dmitriy Serov. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20150907/79b82fe7/attachment.html>
Matthew Jordan
2015-Sep-07 14:10 UTC
[asterisk-users] res_pjsip. Turn off the authorization request for an incoming MESSAGE
On Mon, Sep 7, 2015 at 3:24 AM, Dmitriy Serov <serov.d.p at gmail.com> wrote:> > Hello. > Continue a months-long struggle that is associated with the transfer from chan_sip to res_pjsi p. Where are many gates (GSM gate) that do not support authentication when sending MESSAGE. For example, 4goip when relay incoming SMS. Using chan_sip it was not a problem. Using res_pjsip is the problem :( Is any way to turn off the authorization request for an incoming MESSAGE using res_pjsip? Or any workaround? [2015-09-07 06:01:14] DEBUG[12947] pjsip: sip_endpoint.c Processing incoming message: Request msg MESSAGE/cseq=542 (rdata0x7f88642fdc28) [2015-09-07 06:01:14] VERBOSE[12947] res_pjsip_logger.c: <--- Received SIP request (447 bytes) from UDP:109.165.111.xx:5807 ---> MESSAGE sip:smsin at 85.142.148.xx SIP/2.0 Via: SIP/2.0/UDP 109.165.111.xx:5807;branch=z9hG4bK837973400 Route: <sip:85.142.148.xx;lr> From: <sip:srv_918588xxxx at 85.142.148.xx>;tag=284759743 To: <sip:smsin at 85.142.148.xx> Call-ID: 76603xxxx at 192.168.1.100 CSeq: 542 MESSAGE Contact: <sip:srv_918588xxxx at 109.165.111.xx:5807> Max-Forwards: 30 User-Agent: dble Content-Type: text/plain Content-Length: 35 111 ??? ?????? 68,08 rub. [2015-09-07 06:01:14] DEBUG[23059] pjsip: sip_endpoint.c Distributing rdata to modules: Request msg MESSAGE/cseq=542 (rdata0x7f88640a9288) [2015-09-07 06:01:14] DEBUG[23059] res_pjsip_endpoint_identifier_ip.c: No identify sections to match against [2015-09-07 06:01:14] DEBUG[23059] res_pjsip_endpoint_identifier_user.c: Retrieved endpoint srv_9185880046 [2015-09-07 06:01:14] DEBUG[23059] pjsip: endpoint .Response msg 401/MESSAGE/cseq=542 (tdta0x7f88717063b0) created [2015-09-07 06:01:14] VERBOSE[23059] res_pjsip_logger.c: <--- Transmitting SIP response (479 bytes) to UDP:109.165.111.xx:5807 ---> SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 109.165.111.xx:5807;rport=5807;received=109.165.111.xx;branch=z9hG4bK837973400 Call-ID: 76603xxxx at 192.168.1.100 From: <sip:srv_918588xxxx at 85.142.148.xx>;tag=284759743 To: <sip:smsin at 85.142.148.xx>;tag=z9hG4bK837973400 CSeq: 542 MESSAGE WWW-Authenticate: Digest realm="ruvoip.net",nonce="1441594874/5741fb37496404a4aa5cf0e53a129867",opaque="7441b8c64eddc67a",algorithm=md5,qop="auth" Server: ruVoIP.net PBX Content-Length: 0Your endpoint, ' srv_9185880046', most like has an auth object specified for it. If it did not, then the MESSAGE request would not be challenged. If you know that requests for that endpoint should not be authenticated, then you can remove the auth option from the endpoint and it should allow the request to proceed without a 401 challenge response. If you need to authenticate certain requests while allowing others through, then today, there is no way to accomplish that in the PJSIP stack. As an open source project, someone could certainly propose that functionality if they wanted. -- Matthew Jordan Digium, Inc. | Director of Technology 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org