CS_Default_System_Transfer issue

Answered Question

Hi,

Every couple of days, the Call Patterns within the default_system_transfer 'fail'. We use Unity (4) to front a DDI range and prompts the caller to enter the required extension number and everythings fine, however the patterns such as 35???, 24???, 23??? 'randomly' fail. When the caller tried to get to one of the extensions Unity tells them that this number cannot be reached. The solution is to simply remove the affected Call Pattern from the dial string list and re-enter it. It works fine again (you dont have to restart any services etc - it works straight away).

I'd like to know if anyone else has encountered this and if so, is there a workaround as it happens too frequently.

Thanks,

Mark.

I have this problem too.
0 votes
Correct Answer by rob.huffman about 9 years 2 months ago

Hi Mark,

Does this sound like it could be the Bug?

CSCsh02771 Bug Details

10 entries in CS_Default* restriction table will break table.

Symptom:

Cannot transfer to allowed restriction table entries past entry 0,1. This is using the CS_DEFAULT_SYSTEM_TRANSFER table.

Conditions:

This will happen if you add more than 10 entries in this restriction table. I was able to reproduce this on the customer site, and in my lab 4.2.1 lab environment.

Workaround:

You have to delete all the rules out and then start re-adding them in, making sure not to add more than 9 rules. Once you add the 10th rule it breaks the table and only the first 2 rules in the table will be followed.

Rob

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
rob.huffman Fri, 09/14/2007 - 05:31

Hi Mark,

This really sounds like a bug. What exact version of Unity are you running?

Rob

Correct Answer
rob.huffman Mon, 09/17/2007 - 05:44

Hi Mark,

Does this sound like it could be the Bug?

CSCsh02771 Bug Details

10 entries in CS_Default* restriction table will break table.

Symptom:

Cannot transfer to allowed restriction table entries past entry 0,1. This is using the CS_DEFAULT_SYSTEM_TRANSFER table.

Conditions:

This will happen if you add more than 10 entries in this restriction table. I was able to reproduce this on the customer site, and in my lab 4.2.1 lab environment.

Workaround:

You have to delete all the rules out and then start re-adding them in, making sure not to add more than 9 rules. Once you add the 10th rule it breaks the table and only the first 2 rules in the table will be followed.

Rob

rob.huffman Mon, 09/17/2007 - 08:08

Hi Mark,

Good stuff! These bugs can really play havoc can't they :(

Take care,

Rob

Actions

This Discussion