TRUNK OUTBOUND CALLS not working after 30 minutes

[sccwirelessinc]

Hi,

I use DIDWW trunk service provider and i used the ip address for new york and it was working to make outgoing calls for about 30 minutes at 3 differents canadian and toll free numbers. But after 30 minutes that stopped working and my 3cx app on iphone 6 said that temporary unavailable and when i push line 1 for example. It doesn't work. there is no tonality anymore.

 

[NickD_3CX]

First things first, I have to ask, do you have a supported provider with the same issue? At least this would tell us if it is something specific to this provider or not.

So, just so we can better understand, the call is dropping after ~30 minutes phone call? What happens after, can you call again?

Also what version of the PBX are you using?

 

[sccwirelessinc]

First things first, I have to ask, do you have a supported provider with the same issue? At least this would tell us if it is something specific to this provider or not.

So, just so we can better understand, the call is dropping after ~30 minutes phone call? What happens after, can you call again?

Also what version of the PBX are you using?

The calls worked only one time during 30 minutes i make 3 phone calls in canada. but now its no longer working. no tonality on the line 1 and top right on 3cx app it say tempooary available. Is it something to do with outbound rules? I tries with one trunk for outbound and inbound and i tried two seperate trunk and it si the same problem. when i delete the outbound rules. It is always uptodate the 3cx cloud based. the temporary unavailable message not appear but so not found or something like that. what can be the cause?

 

[NickD_3CX]

"Temporarily Unavailable" sounds like something your provider could be responding when you try to make a call.
I would suggest enabling Verbose Logging, try to make a call, then check the Activity Log for clues if the provider is sending an SIP error message.

You didn't mention though, which provider is this?

 

[sccwirelessinc]

"Temporarily Unavailable" sounds like something your provider could be responding when you try to make a call.
I would suggest enabling Verbose Logging, try to make a call, then check the Activity Log for clues if the provider is sending an SIP error message.

You didn't mention though, which provider is this?

Yes I use DIDWW service provider. They have local IP addresses in the STATES, NY and MIAMI which i am near there.

 

[NickD_3CX]

As it's not a supported provider, your next best bet is the Activity Log then to try and figure out what is going on.

 

[sccwirelessinc]

As it's not a supported provider, your next best bet is the Activity Log then to try and figure out what is going on.

01/14/2021 8:54:22 AM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 84.17.57.120:54975 tid=183749544 Call-ID=1068776436-984904803-231315074: REGISTER sip:34.70.241.0 SIP/2.0 Via: SIP/2.0/UDP 10.119.50.50:54975;branch=z9hG4bK183749544;received=84.17.57.120 Max-Forwards: 70 Contact: <sip:[email protected]:54975> To: <sip:[email protected]> From: <sip:[email protected]>;tag=156502262 Call-ID: 1068776436-984904803-231315074 CSeq: 2 REGISTER Proxy-Authorization: Digest username="829",uri="sip:34.70.241.0",algorithm=MD5,realm="3CXPhoneSystem",nonce="414d535960004d0d80:cf6905ebcd6ec07ecb12c2550b581ae4",response="c2fdd853333bfe4da0ee9d063c934917" User-Agent: Asterisk PBX Content-Length: 0 ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

01/14/2021 8:53:16 AM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 84.17.57.120:59055 tid=542671197 Call-ID=1591778582-1437249554-1215988774: REGISTER sip:34.70.241.0 SIP/2.0 Via: SIP/2.0/UDP 10.119.50.50:59055;branch=z9hG4bK542671197;received=84.17.57.120 Max-Forwards: 70 Contact: <sip:[email protected]:59055> To: <sip:[email protected]> From: <sip:[email protected]>;tag=1647569079 Call-ID: 1591778582-1437249554-1215988774 CSeq: 2 REGISTER Proxy-Authorization: Digest username="928",uri="sip:34.70.241.0",algorithm=MD5,realm="3CXPhoneSystem",nonce="414d535960004ccc11:e7a37f4b2817d737acbfcd53d628fcd8",response="f999fdf301506821a851d136315b647b" User-Agent: Avaya IP Phone 1120E Content-Length: 0 ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

01/14/2021 8:53:12 AM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 84.17.57.120:58747 tid=1851250004 Call-ID=1001754782-791955453-1229785321: REGISTER sip:34.70.241.0 SIP/2.0 Via: SIP/2.0/UDP 10.119.50.50:58747;branch=z9hG4bK1851250004;received=84.17.57.120 Max-Forwards: 70 Contact: <sip:[email protected]:58747> To: <sip:[email protected]> From: <sip:[email protected]>;tag=1571727217 Call-ID: 1001754782-791955453-1229785321 CSeq: 2 REGISTER Proxy-Authorization: Digest username="729",uri="sip:34.70.241.0",algorithm=MD5,realm="3CXPhoneSystem",nonce="414d535960004cc890:e9ac8e3ea18de63984a300b71399d832",response="a4ab3ac89a3572f17fc314c0d018b038" User-Agent: Auerswald COMpact VoIP sofia-sip1.12.11 Content-Length: 0 ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

01/14/2021 8:51:00 AM - [CM306002]: There is no valid STUN server specified! External IP can not be resolved.

01/14/2021 8:41:18 AM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 141.98.103.28:56491 tid=1071665808 Call-ID=1903237644-1545231293-379348719: REGISTER sip:34.70.241.0 SIP/2.0 Via: SIP/2.0/UDP 10.118.102.26:56491;branch=z9hG4bK1071665808;received=141.98.103.28 Max-Forwards: 70 Contact: <sip:[email protected]:56491> To: <sip:[email protected]> From: <sip:[email protected]>;tag=1852570446 Call-ID: 1903237644-1545231293-379348719 CSeq: 2 REGISTER Proxy-Authorization: Digest username="627",uri="sip:34.70.241.0",algorithm=MD5,realm="3CXPhoneSystem",nonce="414d5359600049fd97:af7ceace1041275126a5ae73bf5e4bac",response="8a12e3d09346065b1b2640d539bba3f7" User-Agent: PolycomVVX-VVX_300-UA/4.1.6.4835 Content-Length: 0 ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

01/14/2021 8:41:15 AM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 141.98.103.28:56259 tid=1130392911 Call-ID=1225637003-1665086852-651326471: REGISTER sip:34.70.241.0 SIP/2.0 Via: SIP/2.0/UDP 10.118.102.26:56259;branch=z9hG4bK1130392911;received=141.98.103.28 Max-Forwards: 70 Contact: <sip:[email protected]:56259> To: <sip:[email protected]> From: <sip:[email protected]>;tag=517700589 Call-ID: 1225637003-1665086852-651326471 CSeq: 2 REGISTER Proxy-Authorization: Digest username="527",uri="sip:34.70.241.0",algorithm=MD5,realm="3CXPhoneSystem",nonce="414d5359600049fa44:4226257a1892c779442135a52654d73b",response="39144cdf026b846e3cf7b3cb583a730f" User-Agent: PolycomVVX-VVX_300-UA/4.1.6.4835 Content-Length: 0

 

[NickD_3CX]

No, these are not what you are looking for. a good starting point would be to search for the IP of your Provider.
also please make sure the Outbound rules are correct and that they will actually allow the call to go out through the right provider, and that the provider is registered.

 

[sccwirelessinc]

No, these are not what you are looking for. a good starting point would be to search for the IP of your Provider.
also please make sure the Outbound rules are correct and that they will actually allow the call to go out through the right provider, and that the provider is registered.

That is the point I mentionned in my post earlier. I want to know what to put in Outbound Rules. I think that is the issue. Please advise

 

[NickD_3CX]

Ok, I would suggest going over some of the Academy Material we have, specifically this one:
https://www.3cx.com/3cxacademy/videos/basic/configuring-voip-providers/

It explains some basics about Inbound and Outbound Rules, it also shows you an exmaple of an Outbound rule you can use.

 

[FridayIT]

@sccwirelessinc Nick is absolutely correct, run the activity log to see the exact SIP information. When I had originally setup our system there were a few things I had to do to get calls to work.

We had issues with a unsupported provider as well, in our case, we had to ensure "support re-invites" and "replaces" was disabled on the trunk to prevent the 30 minute disconnect issue from happening.

If you can, switch to a supported provider as things should "just work" but if you like us had a previous agreement then the activity log is your best friend.

The outbound rules that Nick posted is very helpful as well. if you have time, watch the video they have. it really helps to make the process easier to understand

 

[sccwirelessinc]

@sccwirelessinc Nick is absolutely correct, run the activity log to see the exact SIP information. When I had originally setup our system there were a few things I had to do to get calls to work.

We had issues with a unsupported provider as well, in our case, we had to ensure "support re-invites" and "replaces" was disabled on the trunk to prevent the 30 minute disconnect issue from happening.

If you can, switch to a supported provider as things should "just work" but if you like us had a previous agreement then the activity log is your best friend.

The outbound rules that Nick posted is very helpful as well. if you have time, watch the video they have. it really helps to make the process easier to understand

its not the issue. they are already disabled the "support re-invites" and "replaces" but thank you to try to help me.

 

[leejor]

But after 30 minutes that stopped working and my 3cx app on iphone 6 said that temporary unavailable and when i push line 1 for example. It doesn't work. there is no tonality anymore.

Is this happening on more that one device, or just the iPhone?
Are you able to call another extension?

I tries with one trunk for outbound and inbound and i tried two seperate trunk and it si the same problem.

This is happening when using more than one provider? If so, and calls do work to begin with, then it may be a problem between the device and 3CX. You'd have to look at the Activity Log to confirm.