| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| Definity Support Definity Servers Support |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Junior Member ![]()
Location: Hong Kong Rep Power: 0 ![]() | Digits translation for incoming call We have 2 Avaya PBX tie together and the trunk type of trunk group is "TIE". In the near-end PBX, it will receive 7 digits (e.g. 9995XXX), then it will delete first 3 digits and terminate the call to extension 5XXX Avaya phones. Now, the extension need to change into 65XXX. So, is there any way to translate incoming digits 9995XXX into 65XXX (i.e. delete first 3 digits and insert 6). I know for trunk type "TIE", it cannot do digits delete and insert at the same time. So, is there any solution? | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Moderator ![]() MSYoung is meddling with dragons
Location: San Diego, CA Rep Power: 6 ![]() | I am not quite clear on what you are trying to do. Is station 5xxx trying to call station 65xxx? Are you changing from a four digit dial plan to a five digit dial plan? Are you changing station 5xxx to station 65xxx? __________________ Do not meddle in the affairs of dragons for you are crunchy and taste good with ketchup. Marty | ||||||||
| | |
| | #4 (permalink) | ||||||||
| Junior Member ![]()
Location: Hong Kong Rep Power: 0 ![]() | yes, extension range changed from 5XXX to 65XXX. if we don't want to change the dialing method, i.e. users still dial 9995XXX, and let the near-end PABX to do digit translation, then is there any solution. I'm thinking whether the following solution is work or not. - Insert aar access code (e.g. 7) in incoming trunk group to become 79995XXX. - create aar digit conversion table - in Matching pattern column, input 9995XXX - in Del column, input 3 - in Replacement String column, input 6 - in Net column, input ext | ||||||||
| | |
| | #5 (permalink) | ||||||||
| Moderator ![]() MSYoung is meddling with dragons
Location: San Diego, CA Rep Power: 6 ![]() | AAR is used for calling out not for handling incoming calls. You have a couple of issues to resolve. Your calls on the inter PBX tie trunk can be resolved in the route pattern assuming the switch that is calling a 5xxx number does not have any 5xxx stations of its' own. Just insert a 6 for those calls. If that switch has 5xxx numbers of its' own, then that machine will need to allow five digit dialing and you will need to handle the calls in your UDP tables. If your DID's are coming in on an ISDN trunk group you can insert a 6 on the third page of the trunk group. If it is not ISDN then you will need to contact the vendor and have them do the digit manipulation in the CO before you get the call. You will have to change your dial plan to permit five digit station numbers because other people in that switch are going to have to dial 65xxx to reach those phones. __________________ Do not meddle in the affairs of dragons for you are crunchy and taste good with ketchup. Marty | ||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| stripping of leading digits on incoming CS1K calls... | pbx_dancer | Meridian Systems | 3 | 10-17-2007 01:35 PM |
| Using OABS in a RDB to remove incoming digits? | mmanrqz | Meridian Systems | 6 | 03-16-2007 05:49 PM |
| Siemens Call Logging Data Translation | Eager Beaver | Hicom/HiPath | 10 | 01-18-2007 03:56 PM |
| MIPCD passing Incoming Digits | PBXChick | NORTEL | 3 | 11-07-2006 10:37 AM |
| Specifying Call Forward Digits on 500 Set from Terminal | Archibald J. Cox | Meridian Systems | 4 | 02-18-2005 12:39 PM |