403 Forbidden (R403_REUSE_OF_OUTGOING_TRANSPORT)

[Quandredrick]

Good Morning,

My client is recieving this message when attemping to call-out just about every morning.

403 Forbidden (R403_REUSE_OF_OUTGOING_TRANSPORT);

After a restart of the SIP server, the services are available again.

3cx details:
Debain
version: 15.5 sp6
telekom sip provider

--Any idea whats going on here?

Thanks,

Quandredrick

 

[AWS2P]

Hi,
can you please provide more details answering this:
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[Quandredrick]

Hey! Thanks for the reply.

• 3CX Version 15.5 sp6
• Server OS, Debian 9
• Is the 3CX Server Hosted and where? NO
• IP Phone Make/Model/Firmware: Yealink T46S
• Provisioning Method: Local
• Trunk Provider: telekom
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

 

[AWS2P]

is this message has happening recently,or ever got it?
When problem occurs, you can't call out? is it working for incoming calls? sip trunk is unregistred?
Did you do some PBX config change or sip provider has done any change ?
Do you see in log some interresting info? are the logs on verbose?

You said pbx is local, is it running on dedicated computer? in VM ?

 

[StefanW]

Hi,

we have an increase in cases reported by customers in relation to the german Telekom trunk (NGN).
It seems for the moment a change on the destination is causing the reject messages as it affects different versions of 3CX. The reason is unknown for now.

 

[Quandredrick]

is this message has happening recently,or ever got it?
When problem occurs, you can't call out? is it working for incoming calls? sip trunk is unregistred?
Did you do some PBX config change or sip provider has done any change ?
Do you see in log some interresting info? are the logs on verbose?

You said pbx is local, is it running on dedicated computer? in VM ?

1. We have been having the problem reoccuring for the past week.
2. Outgoing calls cannot be made, I was able to make an incoming call this morning.. then recieved a mail from my client saying they are unable to make an outgoing call.

--> During that time the SIP trunk is showing registered.

1. No changes done on our side. and telekom was contacted and also have no solution.
2. The only thing in the logs is the error message i have posted

 

[AWS2P]

As said by StefanW , for now they didn't know what's the reason of this behaviour. So in waiting time may be another trunk sip provider could be a good way to workaround and retablish working PBX

 

[StefanW]

We got further on the matter but we have no conclusive idea why.
This message means you are registered to server A but we send a call to server B.
The team tries to break our implementation currently without luck to find the source.
Since V16, it implies that calls are made to the entity we are registered to.

If you have not opened a support case I advise to do so.
Set logging to verbose and start a Wireshark capture (unfo. unfiltered) and then restart 3CX services to have a start point.