dSIP Hardware Specifications

[David Trad]

Hi Community,

Looking for some advice as to the best hardware configuration for dSIP.

I am thinking of the following, and would love community feedback/input.

• Dell R720 Gen 8/9 series
  - Dual Xeon processors (Not sure which revision they will be would like the E5-2690 v2 3.0GHz/10Core version)
  - 256GB-512GB Of memory
  - SSD Hard Drives, either the Intel or Samsung Enterprise drives
• HP ProLiant DL-380P Gen 8/9 series
  - Dual Xeon processors (Not sure which revision they will be would like the E5-2690 v2 3.0GHz/10Core version)
  - 256GB-512GB Of memory
  - SSD Hard Drives, either the Intel or Samsung Enterprise drives

I am looking for dSIP to do trunking capabilities and aiming for about 5000-10000 concurrent calls, not sure if dSIP can handle that or not.

I am not sure how distributed dSIP is and how it would work on that basis, but from what I have read it is quite scalable.

We will also look to support them taking out commercial licensing as the project looks amazingly solid.

Again thank you for your support and advice in advance.

Cheers,

David.

[Mack Hendricks]

Hey David,

dSIPRouter is based on Kamailio which is really a performant SIP engine.  So, you could get away with much less memory.  Are you going to be anchoring audio through dSIPRouter or are you going to let the carrier pass-thru audio directly with your customers? Also, are you planning to support transcoding from one codec to another?

[David Trad]

Hey Mack,

Thanks for responding mate :) 

Not sure what you mean by anchoring the Audio, I am not familiar with that term so forgive me for not getting that.

I have attached a very basic diagram, which I hope will give a very basic explanation as to what I am trying to achieve, happy for the feedback so I can get this POC up and running, with the intent that before we go into production on this system we will have our support contracts with dSIP and Fusion place as well. 

I will assume that Fusion at this stage will do the Transcoding, and dSIP will just do passthrough of the negotiated CODEC by the end carrier.

Please hit me up with what ever questions you have, no matter how thought provoking it is as I want to make sure I am able to resolve the topology in my mind correctly.

Cheers,

David.

[Mack Hendricks]

Looks good.  The LCR is not that complex.  But, everything else looks good.  Are you planning to use a central database for dSIPRouter or replicating the database between the instances?

On Oct 5, 2021, at 10:15 PM, David Trad <davidtrad...@gmail.com> wrote:

Hey Mack,

--
You received this message because you are subscribed to a topic in the Google Groups "dSIPRouter" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dSIPRouter/XcnjXWadDYc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dSIPRouter+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dSIPRouter/d7d8ea6b-6d7a-43b9-858e-ea0ca549754en%40googlegroups.com.

<TELAIR-VOICE-TOPOLOGY-EXT-REV1.pdf>

[David Trad]

Hi Mack,

Thanks for the quick response!

At this stage I am not looking at running a centralized DB as I am not confident that we will get a net benefit out of doing that, instead keeping it distributed (On the local machine) might have better gains right now... Unless you convince me otherwise as I am totally open to ideas.

We will be booking a day session, however I want to give it a crack with getting the initial setup done.

Are there any videos that are not listed up on YouTube that show a basic configuration that might be similar to what I have outlined in the Document? I do love the videos up on YouTube but they dont quite fit what I am trying to achieve and I think they have confused me more than assisted at this stage.

Again thank you in advance for your help :) 

Cheers,

David.