Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current Restore this Version View Page History

« Previous Version 3 Next »

Target release
Epic
Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Feature Request Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Document statusDRAFT
Document owner

John Shaheen

Designer
Developers
QA

Goals

  • Implement support for SIP over TLS on the SR140

Information from Pablo DePaulis (Deactivated)

\\pysnas01.dialogic.com\Infofactory\MCPD Export Data\MCPD Program Information\HMP Generic\Planning\FRs\FRRDs\HMP TLS Requirements Document.doc

\\pysnas01\Infofactory\MCPD Export Data\MCPD Program Information\Protocols\Design Docs\SIP TLS.doc

\\pysnas01\Infofactory\MCPD Export Data\MCPD Program Information\Protocols\Design Docs\API Committee Proposal - SIP TLS.doc

The sources are more likely portable to any other RV implementation relatively easily… In fact it’s very clear we took the RV TLS examples and augmented them as required. The HMP interface resembles the RV interface a lot as you will see from the API committee document at a quick glance.

If you have CC access to our database (otherwise Brian O. will be able to provide), this is the subsystem build that contains it: \\pysnas02\INT_BLD\scm\subsystem_builds\iphost\5.0.1

Developer’s Config spec should be there…

I can walk you or anyone else thru the sources, to take you specifically where the files are (SIP Sigal subcomponent).

It might also be of interest in having a quick overview of the high-level components of the Iphost subsystem: \\pysnas01\Infofactory\MCPD Export Data\MCPD Program Information\Protocols\Training Docs\NJ

The IP CCLIB Overview is relatively short, and though very old it’s still relevant.

 

TLS requirements indicates TLS 1.0, i.e. RFC 2246 compliance:

\\pysnas01.dialogic.com\Infofactory\MCPD Export Data\MCPD Program Information\HMP Generic\Planning\FRs\FRRDs\HMP TLS Requirements Document.doc

That said the TLS support comes from RV stack… they support TLS v1.2 options, but it doesn’t look we have taken advantage of them. In fact:

http://www.dialogic.com/~/media/manuals/docs/globalcall_for_ip_hmp_v12.pdf

sip_tls_method indicates the version of SSL to use. Defined enumerations are: Dialogic® Global Call IP Technology Guide 679 TLS engine configuration information — SIP_TLS_ENGINE • ENUM_TLS_METHOD_TLS_V1 – use TLS ver. 1 (Default value)

  if (ENUM_TLS_METHOD_TLS_V1 != pEngine->E_sip_tls_method)

   {

      pDbg->print (Dbg::M_SHM,Dbg::LEVEL_ERROR,0,__FILE__,__LINE__,

         "<< checkTLSEngineParams: invalid TLS method %d\n",pEngine->E_sip_tls_method);

      return IPERR_INVALID_TLS_PARAM;

   }

Information from Dan LoPresti (Deactivated)

 

I did find a few useful general topics on the links.

In our docs, we do also provide an overview and then get into the weeds on using it with out API

-          Page 335 - http://www.dialogic.com/~/media/manuals/docs/globalcall_for_ip_hmp_v12.pdf

Background and strategic fit

Assumptions

Requirements

#TitleUser StoryImportanceNotes
1
     

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Not Doing