- Joined
- Nov 27, 2019
- Messages
- 9
- Reaction score
- 0
Hi
We will soon be porting our 20 numbers to a new SIP provider and they have provided us with a test number which was working when we tested it in July 2019. Due some issues we didn't move to the new provider but will be doing so next week.
We have applied all 3CX updates since July as they were released and are now on version Pro 16.0.461.
The test number was working fine in July but now there is an issue. We have an inbound rule setup so that calls to the test number go straight to my voicemail. The issue is that when calling the test number instead of following the inbound rule it is following the rule set in the SIP trunks settings (Route call to) which is set to end the call.
Why has it started doing this when we have made no changed since July apart from applying 3CX updates. I have attached images of the inbound rule and the SIP routing screen.
We will soon be porting our 20 numbers to a new SIP provider and they have provided us with a test number which was working when we tested it in July 2019. Due some issues we didn't move to the new provider but will be doing so next week.
We have applied all 3CX updates since July as they were released and are now on version Pro 16.0.461.
The test number was working fine in July but now there is an issue. We have an inbound rule setup so that calls to the test number go straight to my voicemail. The issue is that when calling the test number instead of following the inbound rule it is following the rule set in the SIP trunks settings (Route call to) which is set to end the call.
Why has it started doing this when we have made no changed since July apart from applying 3CX updates. I have attached images of the inbound rule and the SIP routing screen.