Forum

Unified Communications PBX System

Notifications
Clear all

[Solved] Since upgrade to 2.4.1-2, can't use trunk  

  RSS

tonywhelan
(@tonywhelan)
Estimable Member
Joined: 2 years ago
Posts: 110
28/03/2020 12:15 pm  

I have been happily using VitalPBX/Ombutel for a couple of years for a home PBX.

I have two SIP trunk providers and I route outbound calls to one or the other depending on dialplan.  I upgraded to VitalPNX v2.4.1-2 a few days ago.

Since then I realise that those calls that should go via my first trunk provider are failing over to my second trunk provider. When I force calls to only use the first trunk ("0918xxxx"), I get a message from the PBX saying "I'm sorry the number you dialed is disconnected or out of service". This happens to ALL outbound numbers. The trunk is SIP-registered ok but cannot make calls.

Extract from the log shows this: (numbers partly obscured with xxxx)

[2020-03-29 04:15:04] [12346][C-00000007] app_dial.c: Called SIP/0918xxxx/049009xxxx
[2020-03-29 04:15:04] [4904][C-00000007] chan_sip.c: Got SIP response 502 "Bad Gateway" back from 125.213.xxx.xx:5060
[2020-03-29 04:15:04] [12346][C-00000007] app_dial.c: SIP/0918xxxx-0000000b is circuit-busy
[2020-03-29 04:15:04] [12346][C-00000007] app_dial.c: Everyone is busy/congested at this time (1:0/1/0)

When I disable the trunk and connect a softphone directly to the same provider's sip server (not via the PBX), I can make calls from the softphone ok. But the PBX trunk no longer works.

I have switched my phones over to a backup arrangement, and rebuilt the PBX to test this, and the same problem happens on the newly built machine.

Full log available

 


Topic Tags
mrivera
(@ing-joserivera26)
Developer Admin
Joined: 2 years ago
Posts: 2355
29/03/2020 6:55 am  

You may use the sngrep tool to determine what is exactly sent and received on sip headers. 

Also, you must ask to your VoIP provider that help you out to debug the calls from VitalPBX in case that something is missing when sending calls to them.


tonywhelan
(@tonywhelan)
Estimable Member
Joined: 2 years ago
Posts: 110
29/03/2020 1:26 pm  

Thank you mrivera, I had not been aware of sngrep till now.

I've used sngrep just now and cannot see any clues as to why the provider is returning a 'bad gateway' message to the PBX yet a softphone works fine when configured to directly use the same account.

I'd like to try building an earlier version of VitalPBX on my test box to see if it does the same thing. Can you tell me where I can download an earlier version of VPBX?


tonywhelan
(@tonywhelan)
Estimable Member
Joined: 2 years ago
Posts: 110
29/03/2020 3:39 pm  

I just installed the ARM version 2.3.4-2armv7hl on a Raspeberry Pi test device as per https://vitalpbx.org/en/vitalpbx-in-raspberry-pi-3-b/

Set up an extension, a trunk for the 'problem' sip provider, and an outbound route. Calls are working OK. Yet my main machine with VitalPBX Community v2.4.1-2 refuses to work with the same provider.

I will play around some more with sngrep to see if I can work out what is going on.

This post was modified 2 months ago by tonywhelan

tonywhelan
(@tonywhelan)
Estimable Member
Joined: 2 years ago
Posts: 110
29/03/2020 4:24 pm  
Posted by: @tonywhelan

I just installed the ARM version 2.3.4-2armv7hl on a Raspeberry Pi test device as per https://vitalpbx.org/en/vitalpbx-in-raspberry-pi-3-b/

Set up an extension, a trunk for the 'problem' sip provider, and an outbound route. Calls are working OK. Yet my main machine with VitalPBX Community v2.4.1-2 refuses to work with the same provider.

I will play around some more with sngrep to see if I can work out what is going on.

Unfortunately sngrep is apparently not available for ARM devices.

I'd still like to build an earlier x86 version of VitalPBX if I can find where to download it - eg v2.4.0?


mrivera
(@ing-joserivera26)
Developer Admin
Joined: 2 years ago
Posts: 2355
30/03/2020 5:54 pm  

It could be something related to the SIP profiles, because, in the latest versions it is assigned by default the default SIP profile to the trunks.


tonywhelan
(@tonywhelan)
Estimable Member
Joined: 2 years ago
Posts: 110
30/03/2020 6:06 pm  

@ing-joserivera26

Thanks for that, will keep in mind. I will be doing some more testing today.

 


tonywhelan
(@tonywhelan)
Estimable Member
Joined: 2 years ago
Posts: 110
30/03/2020 6:21 pm  

Hmm. Had a look at the default SIP Profile, something I had not ever looked at or fiddled with before.

I noticed that "Send Remote Party ID" was set to Yes. Changed it to No and now the trunk is working.

I have no idea why this caused a problem but it looks like things are all OK now. Thanks for the help 🙂


Share: