Welcome to Tell-A-Tek

{All-You-Can-Eat Telecom and IT Buffet!}

Returning users can log in to your account or if you are a new user you can create an account!

Simple!

It's so easy, give it a try.

Member Login

Lost your password?

Not a member yet? Sign Up!

Home » 2000 IPS, Call Center and Voicemail, NEC, Phone Systems, Zeacom

714 Area code change effects a few things

24 September 2008 View Comments

You can click the following link to enhance the reading of this article: Reading Blinds.

On August 23, 2008 the local Southern Ca area code 714 users were required to now dial 1+714 for local calls. This had a few setbacks.

See 714-area-code-change-effects-a-few-things

I had a trouble ticket open yesterday regarding a particular client that could not use the call forward all feature without receiving the recording “You must first dial one plus seven one four…”. The client presumed that the access code was being sent twice resulting in 9,91714…

He was kind of on the right track.

The client has an NEC 2000IPS with a Zeacom Call Center application server installed and the call forward all feature is monitored and controlled via the OAI connection. Apparently the guys at Zeacom had setup a little rule where the system would strip off the local area code when it was unnecessary. For example, if I reside in 714 and forward my phone to 17145551212 the system actual hijacks what is sent to the actual carrier and only sends the 5551212 part.

The fix is simple.

    1. 1. Remote into the Server
      2. Open Control Panel
      3. Double click on phone and modems options
      4. Dialing Rules
      5. Click on Edit
      6. Click on Area Code Rules
      7. Click on New
      8. and enter 714 under Area code
      9. Check Dial 1
      10. Check Include the area code
      11. Click OK
714 area code change

714 area code change

That should do it!

If you enjoyed this post, make sure you subscribe to my RSS feed! You can also subscribe by Email and have new posts sent directly to your inbox. When you feel bored, follow me on Twitter.

blog comments powered by Disqus