| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| 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: blocking, caller, incoming |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #2 (permalink) | ||||||||
| Senior Member Fletch is Nortel E911 PLM
Location: NORTEL - NJ Rep Power: 7 ![]() | Re: Ok, now this is just doggone stupid! Try using an IDC (Incoming Digit Conversion) Table in LD 49 to throw that DN to another destination, or an invalid one to block the inbound call. __________________ Fletch Nortel Emergency Services PLM For more on Nortel E911 Solutions on the web: http://nortel.com/e911 Check out this month's E911 Talk podcast at Nortel E911 Talk Podcasts | ||||||||
| | |
| | #5 (permalink) | ||||||||
| Junior Member ![]()
Rep Power: 6 ![]() | OTM HELP Well, I don't really understand the difference between ANI and DNIS. A certain person is calling from xxx-xxxx to yyy-yyyy (a DN off our switch). I need to stop x's calls from getting to y. I looked at the IDC table, but am confused about what to do--I am guessing that I'd put the incoming digits under Deny--but wouldn't that deny them coming in at all? Thanks! | ||||||||
| | |
| | #6 (permalink) | ||||||||
| Senior Member ![]() ![]() jack has no status.
Location: Chicago -- CENTER OF THE UNIVERSE Rep Power: 12 ![]() | Think of ANI as Caller ID. DNIS on the other hand is what the carrier sends you, typically the last four or five digits of what the caller dialed but NOT always. I don't belive that IDC will work for you as an IDC entry will affect all calls, not just the ones from ANI XXX-XXX-XXXX. Now if you have something like Symposium that can route via ANI then you are all set. If this involves harrasement you should get your local Police department involved, ONLY if you or the person being harrased are willing to pursue the issue up to and including court appearances. Jack | ||||||||
| | |
| | #7 (permalink) | ||||||||
| Senior Member Fletch is Nortel E911 PLM
Location: NORTEL - NJ Rep Power: 7 ![]() | Jack is correct. IDC's will only let you manage DNIS destinations, they will not allow you to control what ANI can call. You will need Symposium or the Meridian Integrated Personal Call Director for what you want to do.. __________________ Fletch Nortel Emergency Services PLM For more on Nortel E911 Solutions on the web: http://nortel.com/e911 Check out this month's E911 Talk podcast at Nortel E911 Talk Podcasts | ||||||||
| | |
| | #8 (permalink) | ||||||||
| Junior Member ![]()
Rep Power: 6 ![]() | I have Personal call director. How can I forward all calls coming to yyyy to the MIPCD without doing it on the phone? If I CFW it to MIPCD, then set all calls (but the offensive caller) to ring her desk, it will just be CFWed back to the MIPCD. Also...It would be best if things didn't change too much for the user. Thanks, guys. | ||||||||
| | |
| | #9 (permalink) | ||||||||
| Junior Member ![]() Panchanka has no status.
Location: Ottawa Rep Power: 6 ![]() | Perhaps Slags Next Avatar? I'm trying to block a number xxx-xxxx from the PBX ld 49 REQ "NEW" TYPE "FCR" CRNO "0" INIT "DENY" ALOW DENY xxxxxxx I get a sch0136 "More general condition exists for NFCR" What is this refering to? How can I deny xxx-xxxx. Thanks in advance. | ||||||||
| | |
![]() |
| 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 input - Dial by Name | TelecomDude | Definity Support | 3 | 12-04-2003 02:44 PM |
| Blocking caller ID from a Davox Dialer | mmtech | Meridian Systems | 6 | 08-07-2003 12:44 PM |
| AUDIX could not capture the external caller ID | waynelin | Merlin | 2 | 08-07-2003 01:45 AM |
| Caller ID name on SBC PRIs | jheath | Meridian Systems | 1 | 07-20-2003 10:59 PM |
| Block Caller ID? | Wildman | Meridian Systems | 6 | 03-10-2003 04:26 PM |