John, tafas might be a mitel term too, but definitely is a Meridian term. Some people might call it night pickup, but on nortel you dial spre+4 to pick up a call ringing at the night DN
We are experiencing that tafas (trunk answer from any station) works when an external call is ringing at the night service number, but not when an internal call is ringing. We have multi-tenant enabled and are trying this feature within the tenant. Any ideas?
Hard to explain. We are using the scripts to perform some call control functions, not related to a call center. We need real-time response from the scripts.
As we all are aware of, it is not possible to edit the scripts in SECC. What we have found is that when you use the wizard to create a script, a two second pause is added to the beginning of each script. We REALLY need to lose that. Anyone have any idea how to get rid of that? Or does any one...
Thaks for responses so far guys. I know my pbx is on NS (no consoles) but I do not understand why the DID trunk is in NS.
CDB:
REQ: prt
TYPE: cdb
CUST 0
TYPE CDB
CUST 00
AML_DATA
OPT DNX
VSID
GP02
GP03
GP04
GP05
GP06
GP07
GP08
GP09
GP10
GP11
GP12
GP13
GP14
GP15...
That is fair enough, but my incoming calls have always gone to where they are supposed to, now they do not reach the phone configured in IDC. I understand the PBX as such is in NS, but why all DID calls go to the DID NITe number, I do not understand.
Since the PBX has no attendants (never has), obviously the trunks are not supposed to be in NS. Like I said, I have been playing around with a multi-tenant, other than that I have no idea why suddenly no calls arrive at the phones. They actualy go to a NITE number defined on channel 1 on the DID...
My RDB does say I am in NS, NDNO 1 *. But I have no idea why the whole PBX is in NS. I have no attendants configured, I have one ACD q which has one agent logged in, yet the PBX is in night service.
I have just found out that my DID trunk is in constant night service. This is a test PBX, so I have obviously done something to cause this. I have been playing around with multi-tenant and ACD queues, so I am investigating that.
All our incoming calls to our Meridian fail now. D-channel trace shows :
DCH 15 UIPE_IMSG CC_SETUP_IND REF 00000080 CH 1 1 TOD 15:03:00
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:1372220710 NUM PLAN: E164
CALLED #:220711 NUM PLAN: E164
DCH 15 UIPE_IMSG CC_DISC_IND REF 0000003F CH 1 8...
We have a CTI application which we want to log in an ACD agent. The command setAgentStatus works fine on the Meridian in our lab, but fails at the customer. The customer has ACD-C and ACD-D packages which require that you go off-hook before you login. Any ideas how this can be accomplished since...
We have just installed CCM 4.0(2) and there is now some setting which makes calls to the PSTN look like internal calls. We se this from our app which uses JTAPI, the remote connection (PSTN) gets address type INTERNAL, the connection goes to the wrong state OFFERED, and subsequent events are...
Just for the record, I was finally able to define what I needed. I defined a set of cti ports (no users) and when my jtapi app connected to CM, I registered the cti ports as CiscoMerdiaTerminals. Now I can receive and place calls at the virtual stations.
Sven
Do you know how to make a phone active with out having a IP phone or softphone register to it. We would like to define a pool of say 50 virtual stations which we can use to originate or terminate calls.
Sven
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.