search

dOpensource / dsiprouter

UI Interface for implementing Kamailio to provide PBX Hosting and SIP Trunking Services
https://dsiprouter.org
Apache License 2.0
198 stars 105 forks source link

Endpoint/PBX's with a different port must be entered twice once for inbound and again for outbound #218

Open jbarfield opened 4 years ago

jbarfield commented 4 years ago

As the subject is written: "Endpoint/PBX's with a different port must be entered twice once for inbound and again for outbound".

I believe that this report should be considered a bug but I would also call it a feature request.

Example: Freeswitch endpoint sitting behind dSIProuter using the default external profile utilizes port 5080 for public call routing. If I add a freeswitch endpoint using IP:PORT inbound routing works as expected. However, entering the port for inbound calls breaks the outbound IP authentication requiring me to enter the same endpoint again without the port. If you do not enter the IP again without a port 407 errors will be displayed in a packet capture.

Expected behavior: entering the endpoint connection information once should be sufficient for IP authentication both inbound and outbound.

Potential fix or Feature request: Add fields for SIP port/Protocol separate from the IP field so that the AUTHDB can authenticate by the IP field and the routing modules can utilize the IP/SIP_PORT/PROTO fields.

cruzer45 commented 1 year ago

Hi @jbarfield

Do you know if this is still an issue in recent dSIPRouter releases?

mackhendricks commented 1 year ago

@cruzer45 I think the implementation would consists of adding the ip address to the dr_routing Carrier group when the IP is added to the PBX group. An IP is added to the PBX group whenever a user adds an Endpoint to an Endpoint Group. Please validate this.

So, basically, whenever a user adds an Endpoint to an Endpoint Group we will allow dSIPRouter to automatically receive calls from this Endpoint as well without the end user having to add the ip to the Carrier Group. Perhaps, we automatically create a Carrier Group for each Endpoint group if they click it as an option.

devopsec commented 10 months ago

I have experienced this same issue in a few builds.
Adding "needs-planned".
This could be a minor release, maybe v0.76.

jbarfield commented 10 months ago

@cruzer45 I haven't used it in a while to TBH. Once I made the work around it just seems to work. I set my routes and haven't many changes in the last few years.