Recent content by ksstormmedia

  1. K

    Change Caller ID based on destination number

    Actually, I think I've found this solution...thanks again!
  2. K

    Change Caller ID based on destination number

    This is working great now, thank you! One other thing -- is it possible to set an extension to always use a specific outbound route? There is one extension on the system that should not ID as one of the virtual numbers, but as its own number regardless of destination area code.
  3. K

    Change Caller ID based on destination number

    You are correct, I asked this as a multiple routes/trunks question, and I apparently have something wrong from your example above because it didn't work. That's why I'm back. I'll take another go at it in the morning...would it be possible for you to cut/paste rather than screen shot? My best...
  4. K

    Change Caller ID based on destination number

    Setup: I have a single Vitelity outbound route. I have several Vitelity DIDs. Asterisk has the ability to rewirte the Caller ID based on the destination phone number. SO when I call a number in 316 area code, for instance, it used my 316 DID as the Caller ID. I can't seem to duplicate this in...
  5. K

    Sending Different Caller ID per outbound route

    I'm sorry, I was not clear. All outgoing calls use the same gateway (vitelity-outbound). The user at extension 102 may call a number in the 706 area code then turn around and call a number in the 316 area code. I want the caller ID to show correctly for each of those calls, but to show the...
  6. K

    Sending Different Caller ID per outbound route

    Hi, new FusionPBX user coming from PBX in a Flash. In the Asterisk-based systems there was an easy way to set Caller ID info so the call looked local. For example, if I were dialing a number local to 706NXX, it would give my DID 706NXXXXXX, while if I used the same trunk to dial a number local...