| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications |
| Tags: connection, trunk, woes |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Junior Member
Rep Power: 6 ![]() | Assorted Laws Hey guys, Im not sure if this is even a trunk to trunk issue but it seems that way. We have 3 systems 81C and 2 11Cs. PRI TIEs exist between the each 11C and the 81C. Voicemail is at the 81C and all DIDs are CDPed to the 11Cs. When a user at one of the 11Cs makes an outgoing call they cannot transfer the call to any extensions mainly voicemail (express messaging) to the 81C. They have to use conference for the time being but once that user who initated the conference drops the off the entire call is dropped. Anyone know of a workaround? | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Junior Member
Location: Florida, Where old phonemen go to die Rep Power: 6 ![]() | Option 11C Wouldn't allow all of this because of size limitation, try this URL below for rest. http://www142.nortelnetworks.com/bvd...x/P094398C.pdf Features and Services Trunk to Trunk Connection Contents The following are the topics in this section: Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3097 Operating parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3100 Feature interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3100 Feature packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3102 Feature implementation . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3102 Task summary list . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3102 Feature operation . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3103 Feature description The Trunk to Trunk Connection feature introduces the following capabilities: transfer on ringing of external trunk across the network, transfer of one supervised outgoing external trunk to another, conference of external trunks and outgoing trunk to trunk charging. These capabilities are available on an analog (500/2500 type) set, Meridian 1 proprietary set or an Attendant Console. Transfer on Ringing of External Trunk over Network Allows the transfer on ringing of an established external trunk call over a supervised analog network TIE trunk. If the called party does not answer within a specified time, the call will slow answer recall to the attendant on the transferring node. This capability ensures that available network resources are not occupied indefinitely. Page 3098 of 3156 Trunk to Trunk Connection 553-3001-306 Standard 10.00 January 2002 Transfer of External Trunks Allows the transfer of one outgoing external trunk to another trunk provided both calls are answered and both trunks have answer supervision. As illustrated in Figure 97, Set A is on an incoming/outgoing call with Set X, an external trunk. Set A initiates a call transfer of Set X to Set B. With the Trunk to Trunk Connection feature, Set A can transfer on ringing without waiting for Set B to answer. If Set B does not answer the transferred call, the external trunk will slow answer recalls to the attendant on the transferring node. Figure 97 Transfer on ringing of external call 553-7662.EPS Meridian 1 Meridian 1 • Set A is on an active incoming/outgoing call with Set X, an external party • Set A transfers on ringing Set X to Set B on another node Supervised TIE trunk Set X Set B Set A Trunk to Trunk Connection Page 3099 of 3156 Features and Services Conference of External Trunks Allows external trunks to remain established in a conference call in circumstances when all external trunks involved in the call offer disconnect supervision. Figure 98 illustrates the Conference of External Trunk capabilities of this feature. Set A is on an established conference call with two or more external trunks, Set X and Set Y. When Set A disconnects during the conference, Set X and Set Y continue in the established call. Figure 98 Conference of external trunks Outgoing Trunk to Trunk Charging Ensures that outstanding charging information, relevant to both outgoing calls, is contained in relevant Call Detail Recording records. Set X Set Y Set A Set A 1 2 Set A hangs up Set X Set Y 553-7660.EPS Sets X and Y remain connected Page 3100 of 3156 Trunk to Trunk Connection 553-3001-306 Standard 10.00 January 2002 Operating parameters Slow answer recall occurs when an external trunk is transferred on ringing across an answer supervised network TIE trunk to a set that does not answer. However, the resulting recall will be to an attendant on the transferring node and not to the original set which transferred the call. When transferring one outgoing trunk to another, it is required that the two external calls involved are both answered prior to completing the transfer. Both external trunks involved must have both answer and disconnect supervision. When the last internal party disconnects from a conference call, involving two or more external trunks, all external trunks must have disconnect supervision for the call to remain established. If any one of the remaining external trunks does not have disconnect supervision, all external trunks will be dropped. No change is made to existing VNS operation. Feature interactions Busy Tone Detection for Japan Busy Tone Detection for Japan does not impact Trunk to Trunk Connection. However, whichever occurs first, prevails. Call Transfer To transfer an external trunk on ringing across a supervised analog network TIE trunk, the external trunk and internal TIE line must have both answer and disconnect supervision, and the external call must be established. To transfer one outgoing external trunk to another, both external trunks must have answer and disconnect supervision, and both external calls must be established. Centralized Answering Position The Option 11C system may not have an actual attendant console. Instead, the Option 11C will use Centralized Answering Position (CAP). The CAP Directory Number (DN) is the customer Night DN. Since no attendant is configured, the customer is viewed to be in Night Service and any calls for the attendant are directed to the CAP. Slow Answer Recall may be presented to a CAP when no attendant console is configured for the customer. Trunk to Trunk Connection Page 3101 of 3156 Features and Services Conference Trunk to Trunk Connection allows external trunks to remain established in a call, provided that all external trunks involved have disconnect supervision. With respect to charging costs associated with a conference call, once the last set involved in the conference call disconnects, a search is made of all remaining trunks in the call to determine which call is established in the call for the longest period of time. This trunk is the chargeable Terminal Number (TN). This process is repeated to find the next chargeable TN. Multi-Party Operations - Ringing No Answer In a standalone environment, the RGNA prompt in the Customer Data Block will be used when an external trunk is transferred on ringing and the called party does not answer. In a network environment, the RTIM timer value in the Customer Data Block will be used for slow answer recall. Message Registration The last party releasing the call collects the total value of outstanding Periodic Pulse Metering (PPM) generated on outgoing trunks. If the last party is an internal set, the outstanding PPM is stored against the meter of the set. If the last party is an internal TIE trunk, the outstanding PPM is stored against the meter associated with the internal TIE trunk access code. If the last party is an outgoing external trunk, the outstanding PPM is stored against the meter associated with the external trunk access code. Night Service If an attendant is placed in Night Service, calls to the attendant are directed to a station with the Night DN. Recalls are not directed to the Night DN. Recalls are put in the attendant call waiting queue when in Night Service. Night Service Enhancement Recalls made while the attendant is in Night Service are routed to the Night DN, if the original call is an external call. In such a case, the destination party is disconnected, the internal network trunk is released and the original extended call is presented to the Night DN. If the original call is internal, recalls are put in the attendant call waiting queue when in Night Service. Trunk Barring Trunk Group Access Restriction Trunk Barring and Trunk Group Access Restriction takes precedence over the Trunk to Trunk Connection feature. Page 3102 of 3156 Trunk to Trunk Connection 553-3001-306 Standard 10.00 January 2002 Feature packaging This feature is included in base X11 System Software. Note: DID to TIE (DTOT) for Japan package 176 must be restricted to enable this feature. Feature implementation Task summary list The following is a summary of the tasks in this section: 1 LD 15 – Modifications to Customer Data Block. 2 LD 15 – Modifications to Customer Data Block. LD 15 – Modifications to Customer Data Block. Prompt Response Description REQ: CHG Change. TYPE: ATT Attendant console prompts. CUST xx Customer number. RTIM xxx yyy zzz Enter defined value for the Slow Answer Recall timer where: xxx = 0-(30)-378 Slow Answer Recall yy y= 0-(30)-510 Camp On Recall zzz = 0-(30)-510 Call Waiting Recall Trunk to Trunk Connection Page 3103 of 3156 LD 15 – Modifications to Customer Data Block. Feature operation No specific operating procedures are required to use this feature. Prompt Response Description REQ: CHG Change TYPE NET Trunk and network options. CUST xx Customer number. ... ISDN YES Change the Integrated Services Digital Network options. - PSTN NO Public Switched Telephone Network. Limit the number of PSTNs allowed in a network connection to one PSTN. NO= Puts no limit on the number of PSTN connections. YES = Limits the number of PSTN connections. ... DITI YES Allow Direct Inward Dialing to TIE connections for customer. TRNX YES YES = Allows transfer on ringing of an external trunk over a supervised analog network TIE trunk across private network. NO= Prevents transfer on ringing of an external trunk over a supervised analog network TIE trunk across private network. EXTT YES YES = Allows connection of supervised external trunks. NO = Prevents connection of supervised external trunks. | ||||||||
| | |
![]() |
| 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 |
| Trunk measurements | Switchtek | Definity Support | 7 | 01-02-2006 10:25 AM |
| CHage UNR for all sets | Meridian Systems | 7 | 03-02-2004 12:59 PM | |
| trunk to trunk connection | aoxie | Meridian Systems | 2 | 09-10-2003 04:19 AM |
| Option 11C | telcotech1 | Meridian Systems | 2 | 02-05-2003 07:34 PM |