 03-21-2007, 06:33 PM | #1 (permalink) |
| Junior Member | Nec Ipk11 Inmail Caller Id Hi Guys, I have a NEC IPK11 system with inmail. With the inmail answering the lines in night mode,all I see on the display is "transfer inmail#1". When the system in day mode, the caller ID shows fine. I checked and re-checked all my programming. Any ideas? Thank you Jagie |
 |   |
| 03-21-2007, 08:33 PM | #2 (permalink) | ||||||||
| Moderator 
Rep Power: 3  | Typically the caller ID data packet shows up between the 1st & 2nd ring. If the inmail is answering on the 1st ring it is probably not getting the caller id. Set the inmail ports to answer on the 2nd ring and see if that works??? I've only installed a few inmails, and unfortunately I've replaced every one of them with an elitemail because of their limited functionality. D __________________ NEC NTAC 1 800 852 4632 http://www.necntac.com http://www.2000stuff.com http://ipk2stuff.com/ | ||||||||
| | |
| 03-21-2007, 09:06 PM | #3 (permalink) |
| Junior Member | Hi, thank you for your reply. After I left the customer this morning, I was thinking the same thing. It seems that auto attendant is picking up on the first ring. I tested the lines for caller id packets. The cid packets was sent after the first ring. I don't know in which memory block to set the rings to 2 rings instead of the first. This is what I found so far, memory block 15-03-14 (single line). Since the voicemail ports are assigned as single line ports, it looks like I have to enable 15-03-14 to forward the cid instead of the name of the station. In this case,inmail port name. I will try this in the morning. I will post the results. Best Regards |
| | |
| 03-22-2007, 11:39 AM | #4 (permalink) |
| Junior Member | Hi Guys, here is an update. I spoke to NEC this morning and they told me that MB 15-03-14 will not fix my problem and to Call TAC. I still think that if I can get the inmail to answer on the second ring, then the caller ID info will be captured. Right now it answers on the first ring. Now where is that setting?? Best Regards Jagie |
| | |
| 03-26-2007, 10:28 PM | #5 (permalink) | ||||||||
| Moderator
Rep Power: 3 | Any update? Were you able to find a solution? D __________________ NEC NTAC 1 800 852 4632 http://www.necntac.com http://www.2000stuff.com http://ipk2stuff.com/ | ||||||||
| | |
| 03-28-2007, 08:21 PM | #6 (permalink) |
| Junior Member | Hi Guys,Yes I was able to fix this problem. First I had to remove the trunks assignment from 22-05-01 Mode 2 (enter 0 in Mode 2). Once that was done,I assigned the trunks as DIL trunks in 22-02-1 (change to type 4) in Mode 2. Then the trunks were DIL to the INMAIL pilot number(200). Once that was done the INMAIL waited for the caller ID packet. So all is well and the caller ID is working fine. Thank you all for your input. Best Regards Jagie |
| | |
  |
| 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 |
| Caller ID | pwalters | Meridian Systems | 4 | 02-10-2006 10:26 AM |
| Caller ID | pwalters | Meridian Systems | 1 | 02-10-2006 08:22 AM |
| ID A CALLER ON A PBX SYS | decambralock | Security | 1 | 08-03-2005 09:25 AM |
| Caller ID | cma14 | BCM and Norstar | 3 | 01-10-2005 10:08 PM |
| PRI Caller ID help | Lm_man | Meridian Systems | 20 | 12-06-2004 08:55 AM |
Linear Mode
