Howto:NL - oneCentral - SIP Trunk TLS SIP-Provider (2020)

WARNING: WIKI Hints required (in Howto:NL_-_oneCentral_-_SIP_Trunk_TCP_SIP-Provider_(2020))!! You must note the following issues in the wiki article!

  do not forget to mention the following specials:
  - If you intend to use SIPS (SIP/TLS) registration, you need to add the ' sip.onecentral.net' certificate to the trust list of your SBC
  - Dialling of subscriber numbers not possible, 'Dialing Location' must be configured without 'Area Code'

Various manual steps are required. So now...

- from the 9.00 repository, get the latest version of $/13r1/ip6010 (best using your vault client)

- with Visual Studio (currently 2013) open ip6010.sln

Firmware V12r2 Vault todos

- add/checkin NL-oneCentral-SIP_Trunk_TCP.xsl to $/12r2/ip6010/relay/products/

- checkout/edit $/12r2/ip6010/relay/relay.mak
  - add the following line to the rule for obj/relay_httpdata.h: 
    	products/NL-oneCentral-SIP_Trunk_TCP.xsl \ (note that the line MUST start with a tab and end with a backslash!)

- checkout/edit $/12r2/ip6010/relay/relay_ifs.xsl
  - locate the '<select name="profile">' line
  - add the following line to the list of providers
    <option value="NL-oneCentral-SIP_Trunk_TCP">NL-oneCentral-SIP_Trunk_TCP</option>
  - make sure the line is inserted in the correct alphabetic order!
- proceed with "final steps" below

Firmware 13r1 Vault todos

- add/checkin NL-oneCentral-SIP_Trunk_TCP.xsl to $/13r1/ip6010/relay/products/
- add/checkin sip_product_NL-oneCentral-SIP_Trunk_TCP.js to $/13r1/ip6010/relay/products/

- checkout/edit $/13r1/ip6010/relay/products/sip_products.js
  - add the following line to the correct country property "NL": 
    { name: "oneCentral-SIP Trunk TCP", js: "NL-oneCentral-SIP_Trunk_TCP" }, (note that the line MUST ends with a comma!)
  - make sure the line is inserted in the correct alphabetic order!

- checkout/edit $/13r1/ip6010/relay/relay.mak
  - add the following lines to the rule for obj/relay_httpdata.h: 
    	products/NL-oneCentral-SIP_Trunk_TCP.xsl \ (note that the line MUST start with a tab and end with a backslash!)
    	products/sip_product_NL-oneCentral-SIP_Trunk_TCP.js,SERVLET_STATIC,HTTP_CACHE+HTTP_NOPWD \ (note that the line MUST start with a tab and end with a backslash!)

- checkout/edit $/13r1/ip6010/relay/relay_ifs.xsl
  - locate the '<select name="profile">' line
  - add the following line to the list of providers
    <option value="NL-oneCentral-SIP_Trunk_TCP">NL-oneCentral-SIP_Trunk_TCP</option>
  - make sure the line is inserted in the correct alphabetic order!
- proceed with "final steps" below

=Final steps=
- create a project task and add it to suggested fixes
 - Fix: [Add/Update] oneCentral-SIP Trunk TCP
 - Bereich: Fixes
 - Release: _Fixes - Suggested Fixes
 - Status: Beendet

- save all changes you have done so far

- create an IP6010 build (either locally [preferred, call make Firmware_Build] or using the builder [do not forget to check-in before in this case])
- DRAM this build to Ohm (from C:/sources/builder/src/13r1/ip6010/bin) and test the provider profile (V12 AND V13!)
- if the build is good, check-in all files to vault

- from the test repository, get the latest version of $/test/13r1/relay/sip-profiles/Makefile (best using your vault client)

- checkout/edit Makefile in $/test/13r1/relay/sip-profiles/
  - locate the 'TESTEDPROVIDER=line' line 
  - add the following line to the list of tested providers:
    	NL-oneCentral-SIP_Trunk_TCP \ (note that the line MUST start with a tab!)

- make sure all your changes are checked in if satisfied

- create the service release documentation
  see http://wiki-intern.innovaphone.com/index.php?title=Entwicklung#Service_Release_Dokumentation for details on the development process for service release documentation
  - login to the project tool (use myApps for that)
  - select 'Area' 'Fixes'
  - in the left pane ('Releases') select and open 'Current Releases'
  - select the current Firmware Version (currently this is 'Firmware 13r1')
    you should now be in  "Fixes" Releases/Current Releases/Firmware 13r1
  - navigate to the next Service Release (e.g. '13r1 Service Release 2')
  - Check if there already is a fix 'SIP-Provider Profile NL-oneCentral-SIP_Trunk_TCP'
  - if so, open it.  if not, create a new fix by clicking on the '+ Fix' button
    in the form, fill in: 
    - Fix: 'SIP-Provider Profile NL-oneCentral-SIP_Trunk_TCP'
    - Release: select the next 13r1 service release
    - Status: 'Aktuell'
    - Beschreibung: 
      if this is a new profile, then add the words 'New SIP Provider Profile'
      if this is an updated profile, then add the words 'Updated SIP Provider Profile' plus an explanation why it has been updated (in English)
    - Add 2 Document Links: 
      - http://mantis.innovaphone.com/view.php?id=237667
      - http://wiki.innovaphone.com/index.php?title=Howto%3ANL_-_oneCentral_-_SIP_Trunk_TCP_SIP-Provider_%282020%29
  - Save the new fix
  - navigate to the 'Aktuelle Fixe' section and click on the symbol for 'Fix in Communote posten' 
     in the communote-form, add 'Techserv/Sip-Provider' in 'Themen' 
  - navigate to 'Aktuelle Fixes' section of your fix and click on the symbol for 'Fix erledigt' 

- create/update the wiki article (Howto:NL_-_oneCentral_-_SIP_Trunk_TCP_SIP-Provider_(2020)) in http://wiki.innovaphone.com/index.php?title=Howto:NL_-_oneCentral_-_SIP_Trunk_TCP_SIP-Provider_(2020)&action=edit
  use content of '<profilename>.wiki.txt' to start with
  do not forget to mention the wiki specials mentioned above
- send email to the provider from Mantis and summarize all the test findings
  do not forget to attach ProviderProfile.png and all relevant traces!
  Here is an email template: 

---

Provider Email ------------------------------

We have concluded our tests. Outcome so far is documented in http://wiki.innovaphone.com/index.php?title=Howto:NL_-_oneCentral_-_SIP_Trunk_TCP_SIP-Provider_(2020):

Issues you may want to look into (we refer to the traces found in attached zip):

 - <explain issues here, mention traces if any>

We have created a special configuration form four your product (screenshot ProviderProfile.png attached). Would you please have a look at it and especially review and check the terms we are using in the form? We can change all the terms used in this form to reflect the terms you are using in your communication between you and your customers.

Hope to hear from you soon so we can finish the process.

---

Provider Email ------------------------------

• • • Do not forget to attach ProviderProfile.png as well es all relevant traces.