Goodmorning,
Ive encountered a problem that anonymous calls are stuck in a queue. the phones keep replying busy.
it describes the problem below:
Anonymous calls not getting through
https://www.3cx.com/community/threads/anonymous-calls-not-getting-through.87322/
My setup:
3CX: 16.0.8.16
Server: Windows Server 2019 Standard
Phones in queue:
701 Yealink SIP-T58 (58.86.0.20)
842 Yealink SIP-T46S (66.86.0.5)
843 Yealink SIP-T46S (66.86.0.5)
Phones are available and loggedin in the queue.
A inbound rule directly to the extension gives the same message.
tried different setups for the inboud rules.
*xxxxxx > extension
0xxxxxxxx > extension
+31xxxxxxxxx > extension
All give the same output.
We have several 3CX systems. it looks like it is in v16.
v15.5 and v18 works with the anonymous calls. All systems also have the same sip trunk provider with the same settings. (tested the anonymous inbound call with *xxxxxx works fine)
Ive encountered a problem that anonymous calls are stuck in a queue. the phones keep replying busy.
it describes the problem below:
Anonymous calls not getting through
https://www.3cx.com/community/threads/anonymous-calls-not-getting-through.87322/
My setup:
3CX: 16.0.8.16
Server: Windows Server 2019 Standard
Phones in queue:
701 Yealink SIP-T58 (58.86.0.20)
842 Yealink SIP-T46S (66.86.0.5)
843 Yealink SIP-T46S (66.86.0.5)
Phones are available and loggedin in the queue.
A inbound rule directly to the extension gives the same message.
tried different setups for the inboud rules.
*xxxxxx > extension
0xxxxxxxx > extension
+31xxxxxxxxx > extension
All give the same output.
We have several 3CX systems. it looks like it is in v16.
v15.5 and v18 works with the anonymous calls. All systems also have the same sip trunk provider with the same settings. (tested the anonymous inbound call with *xxxxxx works fine)
