| |||||||||
 |
| ||||||||
| |||||||||||||||
| |||||||||||||||
| 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: dchannel, isdnquot, messages, quotnot |
  |
| | LinkBack | Thread Tools | Display Modes |
 11-15-2004, 10:58 AM | #1 (permalink) |
| Junior Member | Turning up a PRI from a new carrier and inbound calls are not coming through. It appears that the carrier's switch isn't even attempting to send the call through because I get no D-channel messaging at all when I make inbound calls (an 800# the carrier translates to the new PRI). Outbound calls, however, work fine but I get "ORIGINATING/TERMINATING END IS NOT ISDN" within some of the D-channel messages. I don't understand why this message is being generated. Both the carrier's end and my end are configured as NI2 and the carrier is certain the 800# is routed correctly. Any ideas on why I'm getting these "...IS NOT ISDN" messages? CH 3 UIPE_OMSG CC_SETUP_REQ REF 00000017 CH 18 23 TOD 9:38:52 PROGRESS: ORIGINATING END IS NOT ISDN CALLING #:6023456789 NUM PLAN: E164 CALLED #:3212345678 NUM PLAN: E164 DCH 3 UIPE_IMSG CC_PROCEED_IND REF 00000017 CH 18 23 TOD 9:38:52 DCH 3 UIPE_IMSG CC_ALERT_IND REF 00000017 CH 18 23 TOD 9:38:54 PROGRESS: TERMINATING END IS NOT ISDN DCH 3 UIPE_IMSG CC_SETUP_CONF REF 00000017 CH 18 23 TOD 9:38:58 PROGRESS: TERMINATING END IS NOT ISDN DCH 3 UIPE_OMSG CC_DISC_REQ REF 00000017 CH 18 23 TOD 9:39:26 CAUSE: #16 - NORMAL CALL CLEARING DCH 3 UIPE_IMSG CC_RELEASE_IND REF 00000017 CH 18 23 TOD 9:39:26 CAUSE: #16 - NORMAL CALL CLEARING |
 |   |
| 11-15-2004, 11:22 AM | #2 (permalink) | |||||||||
| Senior Member 
Location: 3498.51 miles from Tiverton, Ontario (CANADA) Rep Power: 16  | Orignally posted by Fletch in a different thread... Quote:
| |||||||||
| | |
| 11-15-2004, 11:26 AM | #3 (permalink) | ||||||||
| Guest
| Who the Heck did the walk through? Incoming not working ? Is this the 1st implementaion of PRI in the switch ? It may be something as simple as checking the LDN in the CDB. How many digits is the CO sending ? There must a LDN, the same dn length as your extensions, defined in the CDB for PRI inbound. | ||||||||
| |
| 11-15-2004, 12:56 PM | #4 (permalink) |
| Junior Member | RE: Not the first implementation of PRI on the switch. I currently have two other inbound/outbound PRIs working on my 61C. I don't get "...IS NOT ISDN" on the D-channel messaging on those PRIs, which are configured as interface type DMS100 as opposed to the new one which is NI2. |
| | |
| 11-15-2004, 02:06 PM | #5 (permalink) | |||||||||
| Senior Member
Location: 3498.51 miles from Tiverton, Ontario (CANADA) Rep Power: 16 | Quote:
| |||||||||
| | |
| 11-15-2004, 03:29 PM | #6 (permalink) | ||||||||
| Senior Member 
Location: Chicago -- CENTER OF THE UNIVERSE Rep Power: 10 | FD, What is carrier seeing as far as reject msg's from you? Are you using DNIS? Are you using IDC on the 800 numbers? Most carriers provide a test number on PRI Spans, after you have defined the "ext." of the test number does call complete? Is the 800 number provided by same carrier as the PRI? Jack | ||||||||
| | |
| 11-15-2004, 04:40 PM | #7 (permalink) |
| Junior Member | jack- The carrier folks I dealt with were only able to get a hold of someone to check the 800# translation. I had asked about getting a test DID but they seemed to balk at that, preferring instead to set up an 800#. They're sending 4 digit DNIS. I tried assigning the digits as an ext on my phone and tried using IDC as well but neither worked. We though we found the problem when the carrier discovered that they were sending 0001 instead of the last four digits of the 800#, but routing 0001 to an ext via IDC didn't work. Monitoring STAT in LD 60, TRAC / TRAD in LD 80, as well as D-channel messaging, showed nothing coming in from their end at all. When a call is made to the 800#, you receive a "I'm sorry, all circuits are currently busy..." message. All B-channels show idle, however, and, outbound calls go through fine-- complete with the normal assortment of back and fourth D-channel messaging between the 61C and their switch. My current theory is that the carrier either does not have the 800# routed correctly or there is some mismatch in hunt method. |
| | |
| 11-15-2004, 04:48 PM | #8 (permalink) | ||||||||
| Senior Member
Location: Chicago -- CENTER OF THE UNIVERSE Rep Power: 10 | Polycom feature codes hmm.... Mismatch on what they are sending -- 0001 vs DNIS + No d-channel msg + No b channel being used + Network override/intercept message DOES NOT EQUAL your equipment. Jack | ||||||||
| | |
| |
| 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 |
| decoding BUG and ERR messages | Panchanka | Meridian Systems | 3 | 07-02-2003 03:29 PM |
| Building D Channel on Dual PRI w/DDCH | aldon | Meridian Systems | 2 | 06-17-2003 03:10 PM |
| Voicemail messages cut off | sjm | BCM and Norstar | 4 | 05-01-2003 07:02 PM |
| Intercept Messages and Codes | twscrb | Technology Chat | 2 | 12-12-2002 07:50 PM |
Linear Mode
