[asterisk-bugs] [JIRA] (ASTERISK-30400) Asterisk 16.28.0 Wireguard
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Fri Jan 20 11:05:03 CST 2023
[ https://issues.asterisk.org/jira/browse/ASTERISK-30400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261219#comment-261219 ]
Asterisk Team commented on ASTERISK-30400:
------------------------------------------
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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.
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].
Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.
Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].
> Asterisk 16.28.0 Wireguard
> --------------------------
>
> Key: ASTERISK-30400
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-30400
> Project: Asterisk
> Issue Type: Information Request
> Security Level: None
> Components: pjproject/pjsip
> Affects Versions: 16.28.0
> Environment: Raspberry PI3 Debian Bullseye latest Version of OS and Asterisk
> Reporter: Hans-Peter Mauderer
>
> Hello Asterisk Team,
> My setup is :
> External SIP Trunk Provider in Germany (Vodafone)
> AVM Fritzbox 7530AX as Internet Router
> internal Network with Raspbery PI (Asterisk hostet 16.28.0, pjsip-channel) and Glinet AX1800
> Wireguard Client. (192.168.1.0/24)
> Wireguard works for complete Network (Laptops, IoT, ...) without any issue
> All internal Devices sent/receive their data to Glinet AX1800, the Glinet uses the Fritzbox as Internet Gatewway.
> Asterisk can connect to external SIP-Trunk provider if Wirgaurd is switched off in Glinet Router. If Wireguard is switched on no connection is possible -> we receive no packets from SIP-Trunk provider, even we do ncot know if Packets are received by SIP-Trunk provider.
> We did many measurements with wireshark, but we are running out of ideas.
> According to some google searches the "Requirement of SIP Port 5060" could be a issue?
> My question: is it technical wise possible to tunnel SIP traffic via Wireshark protocoll ?
> Are there some tutorials covering this issue (Asterisk/Wireguard/pjsip) ?
> I'm mot an SIP expert, any help would be highly appreciated :)
> br hpm
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list