" /> PBX simulator problem with type 1 scenario - Genesys CTI User Forum

Author Topic: PBX simulator problem with type 1 scenario  (Read 5251 times)

This topic contains a post which is marked as Best Answer. Press here if you would like to see it.

kamesh

  • Guest
PBX simulator problem with type 1 scenario
« on: May 21, 2008, 05:37:47 AM »
Advertisement
Hi,

New to genesys Switch Simulation environment.

We are trying to have the switch simulator generate calls that we can monitor via the Tlib.

1. Configuration of the switch simulator with the DNs, Queues, routepoints is completed.
2. Connection with the TServer is up ( CTI link is up)
3. We are able to run the CCA sim with a type 2 scenario (ringingwait-answer-talk-release-aftercallwork-ready) scenario set up and working. ( when the scenario is run, the test simulator interface shows the devices under the appropriate queues)
4. To generate calls to these agents, understand that there are two ways,
                          a. Create a Type1 Scenario in the test simulator and run it
                          b. From the Test simulator interface, in the pbx summary tab, use the interface to generate a specific number of calls.

When we execute option a) above, the test simulator starts Dialing and remains so (no calls are generated)

  When we execute option b) nothing happens (ofcourse the Go is displayed in the window )

Any help in getting this righ is appreciate.

Thanks in advance,
Kamesh



Kamesh_s

  • Guest
Re: PBX simulator problem with type 1 scenario
« Reply #1 on: May 25, 2008, 11:25:54 AM »
Interesting, is this so mundane a setup that i can't get it right and no body ventured to answer?
??? ??? ??? ???

Offline cwmunn

  • Newbie
  • *
  • Posts: 6
  • Karma: 0
Re: PBX simulator problem with type 1 scenario
« Reply #2 on: May 26, 2008, 10:03:01 PM »
I do not have experience with a) however, when b) is not working for me it is usually because I forgot to define an entry point in the annex of the switch

ex: Annex -> section 'Simulator'

option name:
entry-point5557000

option value:
5557000, 18883695555, 1.0

'1888...' should come through as DNIS and 1.0 is the rate of calls / sec.

5557000 is defined as a RP on which I have my main strategy.

There may be some sparse bits on this is the 6.5 Simulator Test Toolkit document as well.

~S

kamesh_s

  • Guest
Re: PBX simulator problem with type 1 scenario
« Reply #3 on: May 29, 2008, 07:24:51 PM »
Thanks!! but this does not seem to solve the problem. is there something else that i should look out for.

1. I have tried making calls through the Test Simulator Interface and am able to make individual calls, however, i am unable to make the CCAsim work though!!!.

I do have the simulator user guide. Is there anyother manual that i should be referring to inorder to configure the same?

Thanks
Kamesh




kamesh_s

  • Guest
Re: PBX simulator problem with type 1 scenario
« Reply #4 on: June 02, 2008, 04:36:53 PM »
Can you please let me know what a strategy is ? and how does it help inbound call generation. I tried your post verbatim but did not understand what this 'strategy' is ?

Pardon my ignorance.




Marked as best answer by on Today at 06:25:07 PM

Offline rbeard

  • Newbie
  • *
  • Posts: 2
  • Karma: 0
Re: PBX simulator problem with type 1 scenario
« Reply #5 on: December 08, 2008, 06:32:15 AM »
  • Undo Best Answer
  • Hello-

    It's been a long time since you posted your question, so probably you got this working. I struggled with it today and saw your post while I was looking for a solution.

    To enable automatically launching calls, I configured Switch Annex Simulator q1 and r1 like this:

    Option Name: q1-6601  Option Value: 6001-6008
    Option Name: r1-6660  Option Value: 6601,0,0.25

    The first line sets up an ACD queue with a range of extensions. After the extension range, two additional parameters can be set: autoanswer (or noautoanswer) and postready (or nopostready). You can omit the parameters and the noautoanswer and nopostready states will be the default.

    The second line associates the queue with a routing point, puts in a 0 as a DNIS placeholder, and sets the speed at which calls are launched.

    Hope this helps.