January 04, 2022, 09:16:25 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Revised digitmap for Callcentric  (Read 2687 times)
carl
Sr. Member
****
Posts: 453


« on: September 30, 2012, 08:41:43 pm »

I was not able to use Callcentric star code features except voice mail.
Callcentric's customer service made suggestions to alter the pre configured digitmap for Callcentric we have on Obi.
This suggestion works for me:
(*xx.|*123|**275*x.|[3469]11|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
 Cool
Logged
Billt928
Jr. Member
**
Posts: 39


Business Network Doctors


« Reply #1 on: October 01, 2012, 10:12:30 am »

I too have already made this change. I was having issues with obi and callcentric star codes interfering with each other.
Logged
SDilley
Newbie
*
Posts: 1


« Reply #2 on: October 06, 2012, 10:15:57 am »

WOW! Am I a Newbie or what. I have been in Network programming for nearly 40 years, but that line, "(*xx.|*123|**275*x.|[3469]11|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)". means nothing to me. (Well, I do recognize the "*123".

Can someone be more explicit? I have the Callcentric lock-out problem. Embarrassed
Logged
carl
Sr. Member
****
Posts: 453


« Reply #3 on: October 06, 2012, 07:11:55 pm »

This has nothing to do with the problems Callcentric( and the customers) recently experienced. The pre configured digitmap Obi provides for Callcentric will not allow to use the star code features, e.g. *67 . The new digitmap corrects the problem.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC

Advertisement
Advertisement