Discussion:
[asterisk-dev] Question regarding SIP MESSAGE log verbosity in chan_pjsip
Floimair Florian
2018-07-03 12:18:17 UTC
Permalink
I’m not exactly sure if the current implementation (tested with 15.4.1) of SIP MESSAGE in chan_pjsip is logging with the correct loglevel.

E.g.: If a SIP MESSAGE is sent to an endpoint (in my case via ARI) where there is currently no registered contact (the phone is offline), Asterisk throws an ERROR message:

["2018-07-03 14:13:09.9130"] ERROR[18893]: res_pjsip.c:3538 create_out_of_dialog_request: Unable to retrieve contact for endpoint xxxxxxxx
["2018-07-03 14:13:09.9130"] ERROR[18893]: res_pjsip_messaging.c:630 msg_send: PJSIP MESSAGE - Could not create request

To my understanding this should be a WARNING or maybe even just INFO as there is nothing wrong in this situation.
It’s the counterpart to dialing a phone that isn’t currently registered in which case the call will fail but Asterisk does not throw an error.

Any other thoughts about this or is there something that I’m missing?


With best regards

Florian Floimair
Innovation - Software-Development

COMMEND INTERNATIONAL GMBH
A-5020 Salzburg, Saalachstraße 51
http://www.commend.com<http://www.commend.com/>

Security and Communication by Commend

FN 178618z | LG Salzburg
Matt Fredrickson
2018-07-05 19:10:11 UTC
Permalink
I’m not exactly sure if the current implementation (tested with 15.4.1) of
SIP MESSAGE in chan_pjsip is logging with the correct loglevel.
E.g.: If a SIP MESSAGE is sent to an endpoint (in my case via ARI) where
there is currently no registered contact (the phone is offline), Asterisk
["2018-07-03 14:13:09.9130"] ERROR[18893]: res_pjsip.c:3538
create_out_of_dialog_request: Unable to retrieve contact for endpoint
xxxxxxxx
["2018-07-03 14:13:09.9130"] ERROR[18893]: res_pjsip_messaging.c:630
msg_send: PJSIP MESSAGE - Could not create request
To my understanding this should be a WARNING or maybe even just INFO as
there is nothing wrong in this situation.
It’s the counterpart to dialing a phone that isn’t currently registered in
which case the call will fail but Asterisk does not throw an error.
Any other thoughts about this or is there something that I’m missing?
I don't think that I disagree with your thoughts on it. I'd be ok
with a patch to change it to a WARNING. I wonder if INFO is too
benign for this situation. Anybody else have any thoughts?
--
Matthew Fredrickson
Digium, Inc. | Engineering Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/
Floimair Florian
2018-07-24 09:52:22 UTC
Permalink
Hi Matt!



Thanks for clarification and sorry for the late answer (I was on vacation).

I will create a patch for this today.







With best regards



Florian Floimair

Innovation - Software-Development



COMMEND INTERNATIONAL GMBH

A-5020 Salzburg, Saalachstraße 51

http://www.commend.com <http://www.commend.com/>



Security and Communication by Commend



FN 178618z | LG Salzburg
I’m not exactly sure if the current implementation (tested with 15.4.1) of
SIP MESSAGE in chan_pjsip is logging with the correct loglevel.
E.g.: If a SIP MESSAGE is sent to an endpoint (in my case via ARI) where
there is currently no registered contact (the phone is offline), Asterisk
["2018-07-03 14:13:09.9130"] ERROR[18893]: res_pjsip.c:3538
create_out_of_dialog_request: Unable to retrieve contact for endpoint
xxxxxxxx
["2018-07-03 14:13:09.9130"] ERROR[18893]: res_pjsip_messaging.c:630
msg_send: PJSIP MESSAGE - Could not create request
To my understanding this should be a WARNING or maybe even just INFO as
there is nothing wrong in this situation.
It’s the counterpart to dialing a phone that isn’t currently registered in
which case the call will fail but Asterisk does not throw an error.
Any other thoughts about this or is there something that I’m missing?
I don't think that I disagree with your thoughts on it. I'd be ok

with a patch to change it to a WARNING. I wonder if INFO is too

benign for this situation. Anybody else have any thoughts?



--

Matthew Fredrickson

Digium, Inc. | Engineering Manager

445 Jan Davis Drive NW - Huntsville, AL 35806 - USA



--

_____________________________________________________________________

-- Bandwidth and Colocation Provided by http://www.api-digital.com --



asterisk-dev mailing list

To UNSUBSCRIBE or update options visit:

http://lists.digium.com/mailman/listinfo/asterisk-dev
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/l
Loading...