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 support for phone patch panels #2645

New Issue
Closed
opened 2025-12-29 18:20:47 +01:00 by adam · 3 comments
adam commented 2025-12-29 18:20:47 +01:00
Owner
Copy Link

Originally created by @Hossy on GitHub (Jun 3, 2019).

Environment

  • Python version:
  • NetBox version: 2.5.12

Proposed Functionality

Add ability to add telephone patch panels and specify that all ports are connected to each other.

Use Case

To extend https://github.com/digitalocean/netbox/issues/20, I would like to track telephone wiring and how it connects to network devices (like VoIP devices and servers/PCs).

Originally created by @Hossy on GitHub (Jun 3, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: <!-- Example: 3.5.4 --> * NetBox version: 2.5.12 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Add ability to add telephone patch panels and specify that all ports are connected to each other. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case To extend https://github.com/digitalocean/netbox/issues/20, I would like to track telephone wiring and how it connects to network devices (like VoIP devices and servers/PCs).
adam closed this issue 2025-12-29 18:20:48 +01:00
adam commented 2025-12-29 18:20:48 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jun 3, 2019):

There is nothing fundamentally different between patch panels for network devices or telephone devices. VoIP devices, servers, PCs will all use the same connectors. If you need a new connector (6P2C, 6P4C, 6P6C) that is something that can be looked at and see if the need is there.

Is there something specific that is missing?

In the meantime, the issue request doesn't provide enough information to be actionable so it is going to be closed.

@DanSheps commented on GitHub (Jun 3, 2019): There is nothing fundamentally different between patch panels for network devices or telephone devices. VoIP devices, servers, PCs will all use the same connectors. If you need a new connector (6P2C, 6P4C, 6P6C) that is something that can be looked at and see if the need is there. Is there something specific that is missing? In the meantime, the issue request doesn't provide enough information to be actionable so it is going to be closed.
adam commented 2025-12-29 18:20:48 +01:00
Author
Owner
Copy Link

@Hossy commented on GitHub (Jun 3, 2019):

The issue with the current system is that I can only map a single front
port to a single rear port. That is how a network patch panel works.
However, with a phone patch panel, all ports are connected to each other.
I'm not sure how to represent this is.

On Jun 3, 2019 at 9:06 AM, <Daniel Sheppard notifications@github.com>
wrote:

There is nothing fundamentally different between patch panels for network
devices or telephone devices. VoIP devices, servers, PCs will all use the
same connectors. If you need a new connector (6P2C, 6P4C, 6P6C) that is
something that can be looked at and see if the need is there.

Is there something specific that is missing?

In the meantime, the issue request doesn't provide enough information to be
actionable so it is going to be closed.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/3234?email_source=notifications&email_token=AANM5LUZAXEN5UJQX5AOQXLPYUQNXA5CNFSM4HSD5PHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWZQHLQ#issuecomment-498271150,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANM5LXL3WUXOHXUQN3FUP3PYUQNXANCNFSM4HSD5PHA
.

@Hossy commented on GitHub (Jun 3, 2019): The issue with the current system is that I can only map a single front port to a single rear port. That is how a network patch panel works. However, with a phone patch panel, all ports are connected to each other. I'm not sure how to represent this is. On Jun 3, 2019 at 9:06 AM, <Daniel Sheppard <notifications@github.com>> wrote: There is nothing fundamentally different between patch panels for network devices or telephone devices. VoIP devices, servers, PCs will all use the same connectors. If you need a new connector (6P2C, 6P4C, 6P6C) that is something that can be looked at and see if the need is there. Is there something specific that is missing? In the meantime, the issue request doesn't provide enough information to be actionable so it is going to be closed. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/digitalocean/netbox/issues/3234?email_source=notifications&email_token=AANM5LUZAXEN5UJQX5AOQXLPYUQNXA5CNFSM4HSD5PHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWZQHLQ#issuecomment-498271150>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AANM5LXL3WUXOHXUQN3FUP3PYUQNXANCNFSM4HSD5PHA> .
adam commented 2025-12-29 18:20:48 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jun 3, 2019):

Netbox isn't meant to model anything beyond network infrastructure.

You may want to take this to the mailing list to see if there is a way to properly model this.

@DanSheps commented on GitHub (Jun 3, 2019): Netbox isn't meant to model anything beyond network infrastructure. You may want to take this to the mailing list to see if there is a way to properly model this.
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
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#2645
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?