call queue problem, ring group working, call queue drop call 481.

[iulik]

Hi,

i have a 3cx installed from about 3 year without problems, my voice provider is iristel.

i was forced to upgrade internet line and change the IP.

after change the ip, the 3cx can't make outbound call anymore. iristel change my ip, i didn't change something in my 3cx config, only the ip. after 2 weeks, scratching my head, learn 3cx, learn wireshark, with support from iristel i make some changes to outbound rules and i can make outbound call.

in this time i update 3cx from 16 to 16 not a major upgrade and my call queue was screwed, when i receive an incoming call, i try to answer, te internal line drop, the caller remain in call, not in my 3cx, call disappear from manager.

when i switch to ring group, i can make and receive calls.

the problem is in call queue, the iristel server response is the call i try to take is not exist. error message 481.


how 3cx response is different from call queue and ring group? i think is something messed with 3cx.


i make another 3cx server, win2019, i installed 3cx, restore a backup, same problem.


on older 3cx server i have win2012, i can't install 3cx v16, i can install only v15, i try to put an older config, i can't because license is wrong version.


so i'm stuck.

in ring group i can't make transfer call, which is my main problem now.

 

[leejor]

There are some suggestions in this, that you might try...
https://www.3cx.com/community/threads/all-inbound-calls-droping-when-answered.57135/

Do internal calls, to the queue work? The fact that you had to change your outbound rules, to accommodate a public IP change while remaining with the same VoIP provider, has me perplexed. That should not normally be required.

 

[iulik]

Hi,

i look in that thread, save xml config of the trunk, erase trunk and import xml config.

It's working.

Thank you.

So i think this is a bug of the 3cx.

The linux version is more stable?

 

[JohnS_3CX]

As this this is not a supported provider and we do not know what your setup was, it is hard to say what the issue was.

However, deleting the trunk will erase its internal trunk number (usually starts from 10000, 10001 etc) and re-importing it will allocate the next valid internal number. If this was modified in the previous installation it may justify the issues.

PS: a backup containing a bad configuration would behave the same whether windows or Linux