Quote:
| Originally Posted by Rachelle
Should there not be something in the RLS and RCAP prompts?
Would this configuration cause calls to drop or not connect during a transfer off switch?
recommendations are more than welcome.
|
I believe the RLS ID is only used in environments where you are sending application messages between the switches, i.e. network ring again, NACD, MWI and so on. Since this looks like an interface to the public network I don't see why any application messaging would be required. All of my public network PRIs interface to a 5E switch and have nothing programmed in the RLS ID field however all of my SL100 PRIs have an entry since we use MWI across the network.
The RCAP (remote capabilities) is something you would have to take up with your provider. Most of my public network PRIs have little to nothing for RCAP but my SL100 PRIs have things like ND (name display) TAT (trunk anti tromboning) and so on to match what is programmed at the SL100. Your provider should be able to provide you with a D-channel 'cut sheet' that shows how they have things configured on their end, most are difficult to read at best and some of the terms don't match up but with the NTP one can usually figure it out.
I don't see anything in your programming that would be causing a problem, as stated above I interface mostly with SL100s and 5E systems so I can't say for sure that it's not causing a problem for you. Are you getting any weird error codes related to PRIs, trunks, force disconnects or timeslots? Sometimes we get conditioned to seeing a certain code and ignore it when it really is causing a problem. Any customer complaints?