starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add FXS Interface Type #8833

New Issue
Closed
opened 2025-12-29 20:41:51 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:41:51 +01:00
Owner
Copy Link

Originally created by @nick-bogle on GitHub (Nov 10, 2023).

NetBox version

v3.6.5

Feature type

Data model extension

Proposed functionality

I propose adding a new interface group of Analog, and a new interface type of FXO/FXS.

Use case

This would be a useful interface type to use on ATA devices, widely used in Enterprises and Service Providers. This would also be useful on any device that has a phone line interface of any kind (e.g. dial up modems for OOB, access control panels, fire alarm stations, etc).

Database changes

N/A

External dependencies

N/A

Originally created by @nick-bogle on GitHub (Nov 10, 2023). ### NetBox version v3.6.5 ### Feature type Data model extension ### Proposed functionality I propose adding a new interface group of Analog, and a new interface type of FXO/FXS. ### Use case This would be a useful interface type to use on ATA devices, widely used in Enterprises and Service Providers. This would also be useful on any device that has a phone line interface of any kind (e.g. dial up modems for OOB, access control panels, fire alarm stations, etc). ### Database changes N/A ### External dependencies N/A
adam added the type: featurepending closure labels 2025-12-29 20:41:51 +01:00
adam closed this issue 2025-12-29 20:41:52 +01:00
adam commented 2025-12-29 20:41:52 +01:00
Author
Owner
Copy Link

@apellini commented on GitHub (Dec 4, 2023):

if @jeremystretch approve I could do that.

@apellini commented on GitHub (Dec 4, 2023): if @jeremystretch approve I could do that.
adam commented 2025-12-29 20:41:53 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 4, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 4, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:41:53 +01:00
Author
Owner
Copy Link

@nick-bogle commented on GitHub (May 21, 2024):

@jeremystretch Why was this closed? I don't quite understand why voice ports would be ignored in this project, they're quite common in almost every enterprise, education, and service provider network. Analog Telephone Adapters still have a huge presence and would be very useful to document in Netbox.

@nick-bogle commented on GitHub (May 21, 2024): @jeremystretch Why was this closed? I don't quite understand why voice ports would be ignored in this project, they're quite common in almost every enterprise, education, and service provider network. Analog Telephone Adapters still have a huge presence and would be very useful to document in Netbox.
adam commented 2025-12-29 20:41:53 +01:00
Author
Owner
Copy Link

@mhansen453 commented on GitHub (Jul 31, 2024):

I missed this feature request so I just created a new one asking for almost the exact same thing.

@mhansen453 commented on GitHub (Jul 31, 2024): I missed this feature request so I just created a new one asking for almost the exact same thing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pending closure type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8833
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?