Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  • Users: kfife
  • Order by date
  1. kfife

    CCR external Transfer Points work, but discard CallerID

    I see. When you say 'hard forwarding', do you mean Telco forwarding? Thanks for your helpful feedback -K
  2. kfife

    CCR external Transfer Points work, but discard CallerID

    Good idea. So would that mean everyone calling out from voicemail (and CCR transfers) would show the same CallerID? If so, is there a way to make it match the inbound CLID from the originating channel or the OLI of the mailbox subscriber? Thanks! -Karl
  3. kfife

    CCR external Transfer Points work, but discard CallerID

    We're using a new callpilot system for Voicemail and CCR on a PRI. We have external transfer points in our CCR tree, but when calls go out (transferred out), they have NO CallerID info. Shouldn't the outbound call leg (of the transfer) carry the CallerID of the inbound call? I'm snooping in...
  4. kfife

    MICS 7.1 Software Upgrade Questions

    read the 'Second call doesn't ring the prime set, WTF" thread going on right now. I'm having trouble with 7.1. It's possible that my specific problem started with changes made somewhere between 4.1 and 7.1. -Karl
  5. kfife

    2nd call DOESN'T ring to prime set? WTF?

    Those are all really clever ideas. Do you have any idea why it is doing this? Is this the new 'normal' behavior ever since some specific software release? If this is the 'new way' it works, I can see an argument being made for its superiority as it relates specifically to line appearances...
  6. kfife

    2nd call DOESN'T ring to prime set? WTF?

    When you say to assign the Target to ring only, do you mean that I should remove set 2's answer key for set 1 and instead assign the Target line for set 1 directly onto set 2, configured for ring only? Two appearances seemed like a good idea at first, but the problem is that only EASES the...
  7. kfife

    2nd call DOESN'T ring to prime set? WTF?

    >>Put an Answer key on Mr Important Guys set for blondie. Thanks, I needed that. I did LOL Your summary is perfect. To answer your questions: 1. Fwd on busy: None 2. Set A has exactly one target line appearance. 3. There are 'none' line appearances of A's DID on B 4. There are two intercoms...
  8. kfife

    2nd call DOESN'T ring to prime set? WTF?

    To answer cook1082, yes, I've tried playing with "Answer Key" all three options, basic, enhanced, extended and doesn't 'fix' anything. If any setting should 'work' it seems that it would be 'basic'. What I'm observing is maybe something like being 'stuck' on 'extended' (which enables prime...
  9. kfife

    2nd call DOESN'T ring to prime set? WTF?

    Anyone who can answer this question gets the official "Smartest guy in the room" award. "Mr-Important-Guy" (The president of the company) is the prime set for his target line, so the SECOND call to his target line rings through intercom. HOWEVER things get WEIRD and SURPRISING now that the...
  10. kfife

    Target line PRIME SET behavior changed between MICS v 4.1 & 7.1??

    I might also add that it was configured exactly the same way on the 4.1 & 7.1 system. That's probably obvious but I thought I'd say it anyway.
  11. kfife

    Target line PRIME SET behavior changed between MICS v 4.1 & 7.1??

    We have just one appearance of target line Y on each of the two phones. In this example there are no other appearances of that target line anywhere else on the system. -K
  12. kfife

    Target line PRIME SET behavior changed between MICS v 4.1 & 7.1??

    Not long ago When we were running Version 4.1 of MICS software we were in the practice of putting additional target line appearances on certain phones to cover the target line's main DN. This worked fine & users of covering extensions liked the ability to see which DID was dialed by observing...
  13. kfife

    Norstar "Dial plan" -- Pattern matching (PRI)

    It works for vertical service codes! Problem solved. However, I wasn't thinking about it properly as it relates to ISN dialing. Obviously that wouldn't work because ISN numbers don't BEGIN with *. I need to drink more coffee before posting my bright ideas :-).
  14. kfife

    Norstar "Dial plan" -- Pattern matching (PRI)

    If it works, this will also neatly enable me to capture and route ISN numbers over the internet for SIP URI dialing! For example I could dial an ITAD Subscriber Numbers such as 1234*256 ISN is kinda new, so if you're curious about it, or would like to register an ITAD for your organization, go...
  15. kfife

    Norstar "Dial plan" -- Pattern matching (PRI)

    Brainstorm: I could maybe accomplish it by EXCLUSION Default: collect 19 for numbers beginning with: 2, collect 7 3, collect 7 4, collect 7 5, collect 7 6, collect 7 7, collect 7 8, collect 7 9, collect 7 neatly leaving * to collect 19. This just might work. IT's a bit ugly but it just...
  16. kfife

    Norstar "Dial plan" -- Pattern matching (PRI)

    curlycord: I think you're suggesting making a routing code (for example 8) which the user would substitute for the *? In other words *70 would be substituted by 870? Something like that?
  17. kfife

    Norstar "Dial plan" -- Pattern matching (PRI)

    Pls correct me if I'm wrong, but if I change the default from 7, wouldn't that make it so that users dialing 7 digit numbers would have to wait until timout before the number would 'send' (unless they explicitly hit #)?
  18. kfife

    Norstar "Dial plan" -- Pattern matching (PRI)

    YEP, there it is! However, it appears as though I can't enter the '*' key as the prefix. This is unfortunate because *XX is the pattern I want to match. Vertical service codes always start with *, so I have a strong preference against doing something 'hacky' by making my VSC's start with...
  19. kfife

    Door Opening Controller - behaving like an M7208

    Got it. We had incomplete programming the door phone itself, as discreet from the door opening controller. Thanks! -K
  20. kfife

    Door Opening Controller - behaving like an M7208

    I have a door opening controller that I've moved from our OLD MICS (4.0) to our NEW MICS (7.1). Both systems are running in parallel to prevent any downtime. It's the darnedest thing, but everything works perfectly on the new system (hunt group etc) except that system behaves as though the...

Part and Inventory Search

Back
Top