Unable to Increase Simultaneous Calls on SIP Trunk

[Senõr Engineer]

Have customer that has a Pro license with 24 sim calls. The SIP trunk on the PBX (currently v18 build 31), is showing the sim calls value at 6, but won't allow me to change this to anything else. If I create a new SIP trunk, it defaults to 10 and again does not allow me to change this.

Have numerous other customers where I can happily change the SIP trunk sim calls value.

Why would this be the case?

 

[Evolute IT]

The SIM Calls is modifiable for sure. Shouldn't be locked.

 

[Senõr Engineer]

The SIM Calls is modifiable for sure. Shouldn't be locked.

Yup! But in this instance this does seem to be case. So the question is, why?

 

[Evolute IT]

Yup!

Screenshot, as it's not normal.

 

[AWS2P]

Is it a trunk SIP with a supported Provider?

If I create a new SIP trunk, it defaults to 10 and again does not allow me to change this.

is it same provider or another one just randomly chosen to test with ?

 

[Senõr Engineer]

Not sure how a screen shot is gonna help, but this is what's there currently. I can delete the value, but cannot put anything back in.

 

[Senõr Engineer]

Is it a trunk SIP with a supported Provider?


is it same provider or another one just randomly chosen to test with ?

Same provider. Other PBXs on same provider too and these I can change no problem.

 

[Evolute IT]

Clear your browser cache and make sure to disable adblockers. Maybe something is conflicting as the field is definitely not disabled there.

 

[Senõr Engineer]

Browser cleared. No change. PBX hosted on a 3rd party cloud provider so don't have direct access or ability to check/disable AV or ad blockers etc. Seems odd only this field appears locked/unable to change.

 

[Senõr Engineer]

Update! These instances are being accessed via an RDweb service and a random selection of these showed the same issue. I then arranged with the customer to access the PBX via a TeamViewer session on their PC and could update fine. So looks like either something in the RDweb or on the virtual server is preventing this. Have also fed this back to customer.