Feature: Redirecting Number Information Element (RNIE) Feature Description: When optioned, Shoreware will provide the Caller ID of the caller when placing outbound calls. This feature was helpful to the recipient of the call for they would know who the caller was by looking at the Caller ID on their display. The callers could be a local or remote Shoreware User or in the case of a transferred call via "External Assignment" or "Find-Me", the Caller ID could be a number external to the Shoreware system. Situation: An issue arose some time ago with some carriers where they would reject calls if the Caller ID was not within the DID range configuration of the specific trunk selected. In rare cases some carriers would reject calls even if the Caller ID was missing. As a short term work around for this issue a Custom Dial Plan was used to spoof the original Caller ID to a static Caller ID that the carrier would consider valid. Unfortunately with work around the recipient of the call would never know who the original caller was. With ShoreTel Release 11.2 and 12.1 comes the introduction of ISDN Redirecting Number Information Element (RNIE). As long as the carrier has provisioned their equipment for RNIE, Shoreware can now provide the carrier with both the Billing Telephone Number (BTN) as well as the original Caller ID, the carrier would accept the call due to the BTN and the recipient of the call would once again know who the caller was by looking at the Caller ID on their display. Of course the spoofing workaround will interfere with RNIE so should be removed. The Administrator would need to MANUALLY remove the workaround from the Custom Dial Plan or call TAC for assistance.
Configuration: In Shoreware you will need to configure options in the: ISDN Profiles Trunk Group Sometimes declaring the Number Type to the carrier is also required which requires an entry in the Custom Dialing Rules. ISDN Profiles The Director Contents Pane you will find ISDN Profiles under Trunks Select ISDN Profiles and Director will navigate to the list of all ISDN Profiles. With the different carriers requiring different call parameters it is recommended that when an ISDN Profile is needed that you create a new Profile for each carrier or carrier region by clicking the new button.
The ISDN Profile Parameters for Feature RNIE are: SEND_BTN_AS_RNIE=<Yes No> Default: SEND_BTN_AS_RNIE=No SEND_BTN_AS_RNIE=No Calling party number is presented with Billing Telephone Number (BTN). The caller ID is sent as redirecting number (if Enable Original Caller Information is checked.) SEND_BTN_AS_RNIE=Yes Calling party number is presented with caller ID. The Billing Telephone Number (BTN) is sent as redirecting number (if Enable Original Caller Information is checked.) Note: If Enable Original Caller Information is not checked, the ISDN parameter setting for SEND_BTN_AS_RNIE is ignored.
Trunk Group In the Trunk Group page the Profile must be selected. The option Enable Original Called Information must be checked before you can enter the Billing Telephone Number. The last option to check is the Caller ID not blocked by default. Note: The option Enable Original Called Information is also how to Enable or Disable the RNIE feature. Number Plan Identification: In the ISDN Setup message there is the Called Party Number, Calling Party Number and Redirecting Number Information Elements all have Number Plan Identification. By default the Number Plan Identification used in the Shoreware ISDN is set to unknown. More and more carriers are no longer accepting unknown for the Number Plan Identification. In the US the common setting is ;2E which will sets the PRI to no international numbers, except national (& subscriber) numbers represented as E.164 national.
Logs and Services: There are no logs that can be reviewed or services that need to be manipulated to troubleshoot this feature. Verifying the proper options have been set through Director and a telnet session with debugs are all that is needed. Log and Debug Review: To troubleshoot this feature a telnet session is needed to the Shoregear Trunk Switch. Refer to the Maintenance Guide for instructions on how to telnet to a Shoregear switch. To verify what the current setting on the Shoregear Trunk Switch enter: cfg_opt_flip_rnie This command can also change the setting for testing by entering: cfg_opt_flip_rnie=0 SEND_BTN_AS_RNIE=Yes Calling party number is presented with caller ID. The Billing Telephone Number (BTN) is sent as redirecting number cfg_opt_flip_rnie=1 SEND_BTN_AS_RNIE=No Calling party number is presented with Billing Telephone Number (BTN). The caller ID is sent as redirecting number To observe the ISDN Setup Message two debug commands must be used: pri_log=2 pri_trace=2 Note: Be sure to set both debug commands back to 0 (zero) before logging off the Shoregear switch.
Diagnosing the debug output: In the following examples were for a Find-Me call where the inbound call is shaded in blue and the outgoing call is in green. Below each call example is a table of the ID fields for that call. Example 1: In this example all settings are at the default (SEND_BTN_AS_RNIE=No). Incoming: L2 -> L3 00 DL_DATA_IND 000 0001 0373 SETUP 20a 300 00 241 00 00 00 03 08 02 03 73 05 04 03 80 90 a2 18 03 a1 83 81 1c 19 9f 8b 01 00 a1 13 02 01 01 02 01 00 80 0b 55 6e 61 76 61 69 6c 61 62 6c 65 6c 0c 00 80 34 30 38 35 35 35 31 32 33 34 70 05 80 39 30 32 34 Caller ID 6c 0c 00 80 34 30 38 35 35 35 31 32 33 34 408.555.1234 Called # 70 05 80 39 30 32 34 9024 Outgoing: L3 -> L2 00 DL_DATA_REQ 001 8335 0335 SETUP 300 20a 00 240 00 00 00 00 08 02 03 35 05 04 03 80 90 a2 18 03 a9 83 97 6c 0d 00 80 31 36 33 30 35 34 34 34 30 30 30 70 0c 80 31 36 33 30 35 35 35 36 37 38 39 74 0d 00 00 80 34 30 38 35 35 35 31 32 33 34 Caller ID 6c 0d 00 80 31 36 33 30 35 34 34 34 30 30 30 1.630.544.4000 Called # 70 0c 80 31 36 33 30 35 35 35 36 37 38 39 1.630.555.6789 RN 74 0d 00 00 80 34 30 38 35 35 35 31 32 33 34 408.555.1234
Example 2: In this example the outgoing numbers in the Caller ID and RN Information Elements are flipped (SEND_BTN_AS_RNIE=Yes). Incoming: L2 -> L3 00 DL_DATA_IND 000 0001 0374 SETUP 20a 300 00 241 00 00 00 03 08 02 03 74 05 04 03 80 90 a2 18 03 a1 83 81 1c 19 9f 8b 01 00 a1 13 02 01 01 02 01 00 80 0b 55 6e 61 76 61 69 6c 61 62 6c 65 6c 0c 00 80 34 30 38 35 35 35 31 32 33 34 70 05 80 39 30 32 34 Caller ID 6c 0c 00 80 34 30 38 35 35 35 31 32 33 34 408.555.1234 Called # 70 05 80 39 30 32 34 9024 Outgoing: L3 -> L2 00 DL_DATA_REQ 001 8336 0336 SETUP 300 20a 00 240 00 00 00 00 08 02 03 36 05 04 03 80 90 a2 18 03 a9 83 97 6c 0c 00 80 34 30 38 35 35 35 31 32 33 34 70 0c 80 31 36 33 30 35 35 35 36 37 38 39 74 0f 00 00 80 2b 31 36 33 30 35 34 34 34 30 30 30 Caller ID 6c 0c 00 80 34 30 38 35 35 35 31 32 33 34 408.555.1234 Called # 70 0c 80 31 36 33 30 35 35 35 36 37 38 39 1.630.555.6789 RN 74 0f 00 00 80 2b 31 36 33 30 35 34 34 34 30 30 30 1.630.544.4000
Example 3: In this example the outgoing numbers in the Caller ID and RN Information Elements are flipped (SEND_BTN_AS_RNIE=Yes) and the Number Plan Identification was set to #################################### << ;2E [National # and strip 1] >> Number Plan Identification Incoming: L2 -> L3 00 DL_DATA_IND 000 0001 0376 SETUP 20a 300 00 241 00 00 00 03 08 02 03 76 05 04 03 80 90 a2 18 03 a1 83 81 1c 19 9f 8b 01 00 a1 13 02 01 01 02 01 00 80 0b 55 6e 61 76 61 69 6c 61 62 6c 65 6c 0c 00 80 34 30 38 35 35 35 31 32 33 34 70 05 80 39 30 32 34 Caller ID 6c 0c 00 80 34 30 38 35 35 35 31 32 33 34 408.555.1234 Called # 70 05 80 39 30 32 34 9024 Outgoing: L3 -> L2 00 DL_DATA_REQ 001 8337 0337 SETUP 300 20a 00 240 00 00 00 00 08 02 03 37 05 04 03 80 90 a2 18 03 a9 83 97 6c 0c 21 80 34 30 38 35 35 35 31 32 33 34 70 0c 80 31 36 33 30 35 35 35 36 37 38 39 74 0d 21 00 80 36 33 30 35 34 34 34 30 30 30 Caller ID 6c 0c 21 80 34 30 38 35 35 35 31 32 33 34 408.555.1234 Called # 70 0c 80 31 36 33 30 35 35 35 36 37 38 39 1.630.555.6789 RN 74 0d 21 00 80 36 33 30 35 34 34 34 30 30 30 630.544.4000 Note: The Number Plan Identification set to??? removed the leading 1 from the BTN in the RNIE.