Summary: | ASTERISK-26026: res_pjsip: Error on configuring PJSIP multi domain | ||||
Reporter: | Andrea Sannucci (voztovoice) | Labels: | |||
Date Opened: | 2016-05-16 15:53:40 | Date Closed: | 2018-08-15 07:59:40 | ||
Priority: | Minor | Regression? | |||
Status: | Closed/Complete | Components: | Resources/res_pjsip | ||
Versions: | 13.9.0 13.9.1 | Frequency of Occurrence | Constant | ||
Related Issues: |
| ||||
Environment: | CentOS 7.X VPS - Digital Ocean | Attachments: | ( 0) debug_log_pjsip.txt ( 1) debug_log_pjsip.txt | ||
Description: | I'm Trying to configure PJSIP in a multi domain escenario. My Endpoint configuration is:
{noformat} [1000@sip.domain.com] type=endpoint context=externas-pjsip disallow=all allow=ulaw,g722 accountcode=1000 language=es mailboxes=1000@default dtmf_mode=rfc4733 callerid=Fulano <1000> direct_media=no force_rport=yes rtp_symmetric=yes rewrite_contact=yes call_group=1 pickup_group=1 transport=no-nat auth=aut1000 aors=1000 [aut1000] type=auth auth_type=userpass password=password username=1000 [1000] type=aor max_contacts=1 remove_existing=yes qualify_frequency=30 {noformat} When I register a Softphone (XLITE) on the Asterisk console i can see: {noformat} ERROR[11156]: res_pjsip.c:2946 create_out_of_dialog_request: Unable to create outbound OPTIONS request to endpoint 1000@sip.domain.com ERROR[11156]: res_pjsip/pjsip_options.c:350 qualify_contact: Unable to create request to qualify contact sip:1000@95.250.29.3:55448;rinstance=ae1fb142f87db1a2 ERROR[11156]: res_pjsip.c:2946 create_out_of_dialog_request: Unable to create outbound NOTIFY request to endpoint 1000@sip.domain.com WARNING[11156]: res_pjsip_mwi.c:379 send_unsolicited_mwi_notify_to_contact: Unable to create unsolicited NOTIFY request to endpoint 1000@sip1.voztovoice.net URI sip:1000@95.250.29.3:55448;rinstance=ae1fb142f87db1a2 {noformat} The Endpoint appear registered but can't receive calls because qualify don't work. | ||||
Comments: | By: Asterisk Team (asteriskteam) 2016-05-16 15:53:41.031-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Rusty Newton (rnewton) 2016-05-17 18:34:30.128-0500 We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Rusty Newton (rnewton) 2016-05-17 18:36:35.400-0500 Please follow the debug instructions precisely and verify that your logs contain verbose,warning,error,notice,debug messages before attaching to the issue. Make sure the log includes the registration of the endpoint as well as the "unable to create OPTIONS" messages as well. In addition - include the output of "pjsip show endpoint <endpoint name>" for the endpoint in question. By: Andrea Sannucci (voztovoice) 2016-05-18 08:49:41.137-0500 Helo, the debug file required Regards By: Andrea Sannucci (voztovoice) 2016-05-18 08:50:23.946-0500 The debug file By: Andrea Sannucci (voztovoice) 2017-01-28 10:14:20.389-0600 Any News? By: Joshua C. Colp (jcolp) 2017-01-28 11:30:11.940-0600 If there is anything it will be posted on this issue. By: Andrea Sannucci (voztovoice) 2018-08-15 05:50:40.156-0500 Hello, I think the last changes to PJSIP qualify support have fixed this issue. After some tests MultiDomain work correctly on Asterisk 13.22 Maybe you can try too to close this report. Regards By: Richard Mudgett (rmudgett) 2018-08-15 07:59:40.342-0500 Closing per reporter. ASTERISK-26806 apparently fixed this issue too. By: Andrea Sannucci (voztovoice) 2019-04-19 11:50:40.709-0500 asterisk 13.26.0 and Asterisk 16.3.0 reintroduce the issue... I have to open a new report? Regards By: Asterisk Team (asteriskteam) 2019-04-19 11:50:41.173-0500 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Kevin Harwell (kharwell) 2019-04-22 12:09:38.135-0500 [~voztovoice], yes please create a new issue, provide the steps to reproduce, and attach the appropriate debug logs along with relevant configuration to it. Thanks! |