Has anyone seen on a forwarded 1-8xx call with a cause code ISDN error 127?
The customer has a CS1000E and CS1000M's release 4.5.88. The "E" is an older release "E" that does not have the capability to have it's own PRI's so a 1000T PRI PBX was installed between the LEC and the "E" and some of the "M"'s also use a virtual "D" channel for their DID/ DOD and network calling.
The sites that have their own PRI's work fine in regards to 1-8xx forwarding. Again it is just the 1-8xx forwarding off the sites that utilize a virtual "D" channel for all types of calls that fail and get this cause code of 127. We have TRO set to yes and if we change it to no the 1-8xx forwarding works but there are other issues so leaving this as no is not an option.
Again I am just wondering if anyone has had this issue and what was done to resolve? Was the resolution on the LEC side or the PBX such as a patch?
I had changed other parameters within the PBX's in regards to RDB and "D" channel modifications and nothing worked other than changing the TRO parameter in the RDB for the virtual route.
Thank you..
The customer has a CS1000E and CS1000M's release 4.5.88. The "E" is an older release "E" that does not have the capability to have it's own PRI's so a 1000T PRI PBX was installed between the LEC and the "E" and some of the "M"'s also use a virtual "D" channel for their DID/ DOD and network calling.
The sites that have their own PRI's work fine in regards to 1-8xx forwarding. Again it is just the 1-8xx forwarding off the sites that utilize a virtual "D" channel for all types of calls that fail and get this cause code of 127. We have TRO set to yes and if we change it to no the 1-8xx forwarding works but there are other issues so leaving this as no is not an option.
Again I am just wondering if anyone has had this issue and what was done to resolve? Was the resolution on the LEC side or the PBX such as a patch?
I had changed other parameters within the PBX's in regards to RDB and "D" channel modifications and nothing worked other than changing the TRO parameter in the RDB for the virtual route.
Thank you..