Summary:	ASTERISK-26741: PJSIP device state exchange does not work between Asterisk instances on different network subnets
Reporter:	Jason Shrack (jshrack)	Labels:
Date Opened:	2017-01-21 22:30:36.000-0600	Date Closed:	2020-01-14 11:13:43.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Resources/res_pjsip_outbound_publish
Versions:	13.13.1	Frequency of Occurrence	Constant
Related Issues:
Environment:	CentOS 6.5: 2.6.32-642.13.1.el6.x86_64 #1 SMP Wed Jan 11 20:56:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux	Attachments:	( 0) arch.txt ( 1) asterisk1-pjsip.conf.txt ( 2) asterisk2-pjsip.conf.txt ( 3) pjsip-debug-publish-not-working.txt ( 4) pjsip-debug-publish-working.txt
Description:	When configuring (per https://wiki.asterisk.org/wiki/display/AST/Exchanging+Device+and+Mailbox+State+Using+PJSIP) two Asterisk instances on different subnets to exchange device state information no PUBLISH events are generated. If you modify the server_uri attribute in pjsip.conf to a endpoint address on the same network as the source server PUBLISH event-devicestate are then generated. If you revert to a server_uri endpoint on a different network they are no longer generated and device state data is never received on the remote Asterisk server.
Comments:	By: Asterisk Team (asteriskteam) 2017-01-21 22:30:37.300-0600 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: Joshua C. Colp (jcolp) 2017-01-22 06:01:26.263-0600 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected and the location of documentation that led you to that expectation. 3. The behavior you actually encountered. To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines [2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Jason Shrack (jshrack) 2017-01-22 14:17:12.524-0600 1. Configure 'Asterisk 1' and 'Asterisk 2' for devicestate publish per https://wiki.asterisk.org/wiki/display/AST/Exchanging+Device+and+Mailbox+State+Using+PJSIP. Relevant pjsip.conf configuration is attached. 2. I should expect to see 'asterisk-devicestate' PUBLISH events in the pjsip debug log output (attached) per https://wiki.asterisk.org/wiki/display/AST/Exchanging+Device+and+Mailbox+State+Using+PJSIP. 3. No 'asterisk-devicestate' events occur when the devicestate publish server_uri target is set to the target IP address of the peer Asterisk instance that resides on a different subnet than the originating Asterisk instance. If you change the 'server_uri' target in pjsip.conf to a target IP address on the SAME subnet as the originating Asterisk instance you then see 'asterisk-devicestate' PUBLISH events in the pjsip debug output (attached). When you revert the configuration to the desired configuration (Asterisk peer target on a different subnet) no 'asterisk-devicestate' PUBLISH events are generated. Let me know if you need additional supporting information. By: Rusty Newton (rnewton) 2017-01-23 09:36:41.818-0600 Thanks for all the information so far. Can you gather additional SIP traces, but include all of the other Asterisk logging as well? https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information Specifically, warning,error,notice,verbose,debug and turn both verbose and debug up to level 5 each. Then turn on the pjsip logging as well. By: Asterisk Team (asteriskteam) 2017-02-06 12:00:02.058-0600 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines