|
|
**Please read this post before asking questions on the [mailing list](MailingList).**
|
|
|
## Mailing list usage
|
|
|
1. openair5g-user: Mailing list to post questions on the usage of oenairinterface5g repository. This mailing list must not contain questions related to development of OAI. This mailing list is meant for users of OAI.
|
|
|
1. openair5g-devel: Mailing list to post questions on the development of oenairinterface5g repository. This mailing list is meant only for developers of openairinterface.
|
|
|
1. openaircn-user: Mailing list to post questions on the usage of openair-cn repository. This mailing list must not contain questions related to development of OAI. This mailing list is meant only for users of openair-cn repository
|
|
|
1. openaircn-devel: Mailing list to post questions on the development of openair-cn repository. This mailing list is meant only for developers of openair-cn.
|
|
|
|
|
|
## General
|
|
|
1. Search the [Mailing List Archives](http://lists.eurecom.fr/sympa/arc/openair4g-devel) if the problem was not already treated.
|
|
|
1. Please understand that community has limited time/resources to help you. So, please read this carefully to ensure you get the correct response.
|
|
|
1. Search the [Mailing List Archives](https://gitlab.eurecom.fr/oai/openairinterface5g/wikis/MailingList) if the problem was not already treated. Try to look at the linux installation, kernel logs to find out the problem. If you describe the *problem clearly*, then someone can answer you with a *clear* solution.
|
|
|
1. Try to locate whether the problem is within openairinterface5g or openair-cn repository. Please avoid sending email to multiple mailing lists and spamming the community.
|
|
|
1. In some cases, it might be that problem of usage is related to both openairinterface5g and openair-CN. Only in these exceptional cases, you should send email to both the mailing lists.
|
|
|
1. Please make sure the subject describes the problems clearly. And avoid sending new/different problems on the old thread.
|
|
|
1. Please do not post questions on usage of OAI in developer mailing list or vice versa.
|
|
|
1. Look in the list of [know bugs](OpenAirCriticalIssues) and at the [issues on gitlab](https://gitlab.eurecom.fr/oai/openairinterface5g/issues)
|
|
|
|
|
|
## Questions related to basic installation of OAI (core + optional packages)
|
... | ... | @@ -9,7 +19,7 @@ |
|
|
1. Send these log files along with information on your machine (VM, Ubuntu 14.04?) and x86 CPU type
|
|
|
|
|
|
## Questions related to compilation of OAI (oaisim + lte-softmodem)
|
|
|
1. Look at the logfiles that are generated after installation for errors
|
|
|
1. Look at the logfiles that are generated after installation for errors. In most cases, it is related to Linux issues.
|
|
|
1. What command did you use for compilation?
|
|
|
1. Send these log files along with information on your machine (VM, Ubuntu 14.04?) and x86 CPU type
|
|
|
|
... | ... | @@ -21,3 +31,6 @@ |
|
|
1. Send the config files which were changed for your setup
|
|
|
1. If HSS database was changed, send the image of the database
|
|
|
1. Upload the wireshark trace (eNB and EPC) on a dropbox/google drive capturing the traffic on ALL interfaces. Please do not send wireshark trace as an attachment to the mailing list. **If these files are too big (which should not be the case), please do not send them on the mailing list**, but upload them on google drive/dropbox folder and send everyone the link. Please refrain from sending huge attachments to the mailing list.
|
|
|
|
|
|
## Questions related to openair-cn
|
|
|
1. Please follow the guidelines above to post questions on the usage of openair-cn |