486 Busy Here

[Luke Cage]

Had a power outage and my trusty Patton SN4970 never came back to life. Replaced it with a Patton Trinity SN4171, downloaded and installed the new templates from Patton, created a config file with the Patton Wizard, and go the system running.

Problem is we keep getting 486 Busy Here messages on some outbound calls. Been working with Patton support and through some routing changes and other config modifications the problem is reduced, but it still happens multiple times daily.

My 3CX v20 is running virtually in house connected to the Patton 4171, which is then connected to a Comcast / Xfinity AdTran gateway. Basically it's a PRI T-1 over fiber connection.

Log entry:

09/23/2024 2:35:22 PM - Call to T:Line:10002>>9719006933@[Dev:sip:[email protected]:5060;transport=udp] from L:1903.1[Extn:234] failed, cause: Cause: 486 Busy Here/INVITE from 192.168.1.105:5060

Patton support doesn't think there is much more they can do on their end, so I'm not sure where to look to resolve this issue.

I can upload log files, Wireshark captures, Patton debug logs whatever it takes to resolve this.

Any ideas are appreciated.

 

[Guillaume Bourgeois]

According to the logs you shared, the 486 Busy issue originates from either your Patton or your Comcast / Xfinity AdTran gateway.
In any case, the 3CX forum focuses on 3CX solutions and supported services.

3CX does not directly support VoIP gateways.
3CX is not at fault; your investigation should be directed towards Comcast / Xfinity AdTran and Patton.

 

[Luke Cage]

That was a little harsh.
I never said 3CX was the issue, but I love the usual telco blame game that it's someone else's problem

This being a user forum, in my experience being a part of many forums, there are folks out there who have used and possibly worked for other companies i.e. Patton / Adtran that have seen this issue before and may have some insight on it.

As mentioned I do have support tickets open with Patton (which btw didn't cost anything and is much more helpful than spending $75 for a 3CX ticket) and not once have they blamed 3CX.

All I'm trying to do is resolve an issue. For all I know I may have an Outbound Rule issue in 3CX that doesn't like the Patton device.

Sorry, just frustrated.

 

[Guillaume Bourgeois]

09/23/2024 2:35:22 PM - Call to T:Line:10002>>9719006933@[Dev:sip:[email protected]:5060;transport=udp] from L:1903.1[Extn:234] failed, cause: Cause: 486 Busy Here/INVITE from 192.168.1.105:5060

My diagnosis was not made blindly. Unless you tell me that 3CX has the IP address 192.168.1.105, the "486 busy" response is coming from that IP. Your log copy-paste clearly indicates this.

Cause: 486 Busy Here/INVITE from 192.168.1.105:5060

And if your PBX does have the IP 192.168.1.105, it would mean that you're trying to call from 3CX to your own 3CX, which wouldn't make sense. If there were an issue with the Outbound Rules, the 192.168.1.105 would not have responded with a 486 Busy. In fact, it wouldn't have responded at all since it wouldn’t have received any request.

You asked a question, and I answered it.

3CX is receiving a "Busy" response from 192.168.1.105, but it's also possible that 192.168.1.105 is receiving a "Busy" signal from an upstream device, which is why I mentioned your Adtran.

So, you might feel frustrated, and you may say you enjoy the "game" of passing the blame, but as far as I know, we are not an Adtran or Patton support forum. The issue clearly lies at that level.

This being a user forum, in my experience being a part of many forums, there are folks out there who have used and possibly worked for other companies i.e. Patton / Adtran that have seen this issue before and may have some insight on it.

It's like having problems with my car—if I mention the make and model, maybe some people on this forum also use the same car. Can I ask my car-related question here?

Engage in discussions on their forums...

As mentioned I do have support tickets open with Patton (which btw didn't cost anything and is much more helpful than spending $75 for a 3CX ticket) and not once have they blamed 3CX.

" which btw didn't cost anything and is much more helpful than spending $75 " ... Oh, I thought Patton hadn't been able to resolve your issue. That indeed sounds very helpful to me.

I apologize, but if you insult 3CX on the 3CX forum, you should expect a response.

If Patton is telling you that the problem doesn't lie with them, they should be able to provide you with a PCAP (Wireshark capture) showing that the 486 Busy error isn't originating from their side.

This trace would help you pinpoint exactly where the issue is occurring.

Regardless, even if you choose not to believe it, I’ve pointed you in the right direction—between your Patton and your Adtran. If you don’t want to believe me, that’s your choice.

Based on your reaction, you should consider hiring a VOIP technician who specializes in SIP in general. Yes, it will cost you, but you’ll receive the service that comes with it.