Has anyone experienced problems with PRI's out of a Siemens EWSD C.O. switch?
Background: 2-way NFAS trunk group w/ DID, 3 PRI's, 1 primary and 1 backup D-channel. D-channel releases, B-channels of course go into lockout. What then happens is: the D-channel will eventually establish, but B channels will not. Sorry I don't have a capture from the D-channel messaging, but basically what happens is that I can see OMSG's and IMSG's establishing the D-channel and then trying to establish B channels, but the PBX times out after failing to receive a final IMSG on the B channel establish. Then the whole IMSG/OMSG process repeats ad infinitum.
The only fix the carrier (MCI) has found is "reloading the controllers" in the C.O., a procedure that--as I understand it--resets every customer on the Siemens switch.
Sorry for being long winded, but this is a wierd one. Doesn't happen at our sites served by a DMS or 5E, etc. Both of our offices served by the Siemens have experienced this problem. MCI can't find any documentation on the Siemens to suggest interoperability problems.
FYI bouncing the trunk group just makes things worse!
Anyone seen this or have a setting that may help? I've tried increasing the T200 timer, didn't help.
Thanks!
Background: 2-way NFAS trunk group w/ DID, 3 PRI's, 1 primary and 1 backup D-channel. D-channel releases, B-channels of course go into lockout. What then happens is: the D-channel will eventually establish, but B channels will not. Sorry I don't have a capture from the D-channel messaging, but basically what happens is that I can see OMSG's and IMSG's establishing the D-channel and then trying to establish B channels, but the PBX times out after failing to receive a final IMSG on the B channel establish. Then the whole IMSG/OMSG process repeats ad infinitum.
The only fix the carrier (MCI) has found is "reloading the controllers" in the C.O., a procedure that--as I understand it--resets every customer on the Siemens switch.
Sorry for being long winded, but this is a wierd one. Doesn't happen at our sites served by a DMS or 5E, etc. Both of our offices served by the Siemens have experienced this problem. MCI can't find any documentation on the Siemens to suggest interoperability problems.
FYI bouncing the trunk group just makes things worse!
Anyone seen this or have a setting that may help? I've tried increasing the T200 timer, didn't help.
Thanks!