Announcement

Collapse

Welcome to ShoreTelForums.com

Welcome to ShoreTelForums.com!

This site was created as a place to share stories, tips, and troubleshooting help with ShoreTel/Mitel systems. ShoreTel/Mitel is obviously the MOST exciting VoiP platform on the market right now, and we realized there was no centralized place to discuss this platform, but now there is. Please feel free to join and share your experiences.

Please Note: This site IS NOT owned, funded, or managed by ShoreTel/Mitel, Inc. although you may find ShoreTel/Mitel employees sharing there experiences and expertise. If you would like more information on ShoreTel/Mitel systems, contact BTX at [email protected]

As always please support the advertisers that help support our site.

Thank You,
BTX
See more
See less
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • caller id unavailable

    I've just noticed that regardless of what is entered into the caller ID field for a given user, the caller ID comes up as unavailable on the receiving phone.
    This was not always the case- it used to work just fine.
    Ideas?

  • #2
    Originally posted by sgr60 View Post
    I've just noticed that regardless of what is entered into the caller ID field for a given user, the caller ID comes up as unavailable on the receiving phone.
    This was not always the case- it used to work just fine.
    Ideas?
    Make sure "Make Private" checkbox isn't checked.

    If that doesn't work, check which trunk the user is making calls from. 24 line T1's don't pass the caller id over, but 23 channel PRI's do if it is configured properly at the carrier.

    Comment


    • #3
      some carriers require the Calling Party IE for ISDN to set for National/E.164.. ShoreTel by default sends this out unknown/unknown. You will need to add ;2E in the custom tab of the trunk-group to set the above. You will need to login in the support mode.

      Comment

      Working...
      X
      😀
      🥰
      🤢
      😎
      😡
      👍
      👎