- Joined
- May 25, 2022
- Messages
- 9
- Reaction score
- 1
Hi all!
We have a problem with receiving calls via SIP trunk
We use a Standard license (free)
A week ago, we updated the PBX from the 16th version to the 18th.
We have 1 trunk with 3 voice channels.
Registration by IP address.
Sometimes, when an incoming call, the subscriber hears a message from his operator that the number is not in serviced.
The same message can be heard if the incoming call is not directed anywhere - do not do DID.
But our incoming calls fall on:
1. Voice menu.
2. Then to a group of calls.
3. Then, if there is no response, to voicemail.
If there are more than 3 incoming calls - the subscriber receives a busy signal from our operator.
But the problem is that sometimes the subscriber hears a message that the number is not serviced.
That is, it seems that the PBX cannot route the incoming call and gives a rebound to the line.
The problem is not permanent.
The operator sent a dump in which it is clear that our PBX gives him a signal SIP 600 Busy everywhere (apparently this message is perceived as unavailability of the number).
He asks to reconfigure our PBX so that it sends SIP 486 Busy Here
Is there any way to reconfigure this behavior of the PBX to send a 486 Busy Here message?
Apparently, at some point we reach the limits on the number of calls (just it is not clear on what, on the trunk, on the IVR on the incoming group).
Where and how to see it?
We have a problem with receiving calls via SIP trunk
We use a Standard license (free)
A week ago, we updated the PBX from the 16th version to the 18th.
We have 1 trunk with 3 voice channels.
Registration by IP address.
Sometimes, when an incoming call, the subscriber hears a message from his operator that the number is not in serviced.
The same message can be heard if the incoming call is not directed anywhere - do not do DID.
But our incoming calls fall on:
1. Voice menu.
2. Then to a group of calls.
3. Then, if there is no response, to voicemail.
If there are more than 3 incoming calls - the subscriber receives a busy signal from our operator.
But the problem is that sometimes the subscriber hears a message that the number is not serviced.
That is, it seems that the PBX cannot route the incoming call and gives a rebound to the line.
The problem is not permanent.
The operator sent a dump in which it is clear that our PBX gives him a signal SIP 600 Busy everywhere (apparently this message is perceived as unavailability of the number).
He asks to reconfigure our PBX so that it sends SIP 486 Busy Here
Is there any way to reconfigure this behavior of the PBX to send a 486 Busy Here message?
Apparently, at some point we reach the limits on the number of calls (just it is not clear on what, on the trunk, on the IVR on the incoming group).
Where and how to see it?

