David Robinson | Hello all, I came across an issue recently concerning the addition of translation patterns and existing DNs. The situation is as follows: We have a v8 PBX and CUCM system set up. We retrieve various data from this configuration via AXL requests. We also occassionaly add translation patterns as well. When adding a translation via the addTransPattern AXL request we are seeing some strange behavior. If the new translation pattern has a pattern value that matches an existing 10-digit DN (I think it only affects DNs on the same route partition), the existing DN (in our case, the DN is on some phone that is already provisioned) is removed from the system. Then the translation pattern is added successfully. If you attempt to add the translation pattern via the CUCM UI, you get an error that tells you that the DN already exists and the translation pattern is not added. Why the different behavior? Is the AXL behavior by design? Is this a known issue? If more info of any kind is needed, please let me know. Thanks, David |
| Please sign in to flag this as inappropriate. |