Difference between revisions of "H323 pass-through test"

From Kolmisoft Wiki
Jump to navigationJump to search
Line 8: Line 8:
* Protocol: H323
* Protocol: H323
* Codec G711
* Codec G711
* The NuFone Network's OpenH323 Channel Driver
* openh323_v1_18_0
* pwlib_v1_10_0


* Test schema: originator(playback) ---> Our test server ---> terminator(playback)
* Test schema: originator(playback) ---> Our test server ---> terminator(playback)

Revision as of 15:29, 6 February 2009

Server

  • Intel® Xeon® Processor 5030 (4M Cache, 2.66 GHz, 667 MHz FSB)
  • 4 gb ram
  • Hardware RAID 10 128 MB cash SATA 4 x 250 GB 7200 RPM
  • Asterisk 1.4.18.1
  • MOR 0.8 pre17
  • Protocol: H323
  • Codec G711
  • The NuFone Network's OpenH323 Channel Driver
  • openh323_v1_18_0
  • pwlib_v1_10_0
  • Test schema: originator(playback) ---> Our test server ---> terminator(playback)

Call file used

  • Channel:Local/99555272804@mor
  • MaxRetries:1
  • RetryTime:60
  • WaitTime:30
  • Account:2823
  • Context:test
  • Extension:111
  • Priority:1


Conclusion

We reached 120 sim. calls because our originator could not make more calls. (Later will try with more powerful server).

Tests shown that 1 H323 pass-through call takes ~1% of CPU power of this server.

Theoretically ~350 calls can be reached on this server.


H323test chart.png


Screenshots

  • top, 10 calls H323test top10calls.png
  • top, 20 calls H323test top20calls.png
  • top, 30 calls H323test top30calls.png
  • top, 40 calls H323test top40calls.png
  • top, 50 calls H323test top50calls.png
  • top, 60 calls H323test top60calls.png
  • top, 70 calls H323test top70calls.png
  • top, 80 calls H323test top80calls.png
  • top, 90 calls H323test top90calls.png
  • top, 100 calls H323test top100calls.png
  • asterisk, 100 calls H323test asterisk100calls.png
  • top, 110 calls H323test top110calls.png
  • top, 120 calls H323test top120calls.png
  • asterisk, 120 calls H323test asterisk120calls.png