When NHS Grampian moved to Netcall Liberty Converse we also took the opportunity to migrate from DPNSS to SIP trunking between out Mitel 3300 controllers and the Netcall Servers.
The setup is as follows
We have two Mitel 3300 telephone system controllers and two Netcall telephony servers. We have 45 channels of SIP going from each controller to each server giving us a total of 180 channels. These are then split on the Netcall side to a 2:1 ratio (As requested by NHS Grampian). I.e. for each 45 channel sip peer profile (4) the calls are split to 30 inbound and 15 outbound. This gives us a total of 120 inbound and 60 outbound channels. This setup was agreed and minuted during project meetings. In addition we have 4 x 5 channels of SIP delivered from 2 x trunking gateways (2 x 5 channels to each Netcall server). This provides NHS Grampian with resilience should there be an issue with a single item of equipment.
What we expect to happen if 30 Inbound channels from one of our Mitel controllers are in use is to receive Busy from the Netcall Server which would prompt the Mitel controller to use its second choice route to the second Netcall Server using its second Peer Profile.
We have starting to experience “503 service unavailable” messages and reported the problem to Netcall. We have been advised that the above setup will not work. Netcall are set up to accept 68 Inbound calls before presenting Busy and cannot split the 45 SIP channels into 30 Inbound and 15 Outbound. This causes issues as we only have 45 SIP channels per Peer Profile so they continue to attempt to route calls back over the Peer Profile as they are happy to receive 68 calls.
Netcall will only use their second choice route in the event of a failure of our first SIP Peer Profile to our Mitel controller and not on Busy as they informed us during the Pre-Installation Meetings,
My questions are:
Is any other site experiencing this issue?
Will Netcall consider programming their servers so that they can route inbound and outbound calls as agreed in the project meetings? The Netcall servers don’t have the capability at present to define inbound and outbound calls for different SIP peer profiles. They can only accept inbound and outbound totals for that servers.