2023.10.05

 

 

 

 

 

 

 

Jun, 2023

 

Technical Note 

SIP Trunk IoT process

Whenever there is a need to have a new SIP trunk deployment, there must be a SIP IoT on the LAB platform first before the launch of a new SIP trunk on the commercial platform. 

 

What’s required?

  • SIP Trunk specification

-. The way of connection

    IP authentication or ID/PWD registration?

    In case of the IP authentication, if the iPECS Cloud sends OPTIONS to the carrier to check the Keep-alive, does  

    the carrier send 200OK for OPTIONS? Also the carrier sends OPTIONS to the iPECS Cloud?

   1 shared SBC based SIP connection or customer(tenant based) SIP connection?

   If it’s a customer based, SP needs to discuss it with TAM first.

-. Connection mode : TCP or UDP?

-. SIP trunk delivery : throughout the Internet or internal gateway?

-. Supported Codec list

-. DTMF mode : RFC2833 or INFO?

-. Carrier side proxy IP address and domain information, Port (e.g., 5060)

-. DDI digit format: E.164 (country code + digits, digits with or without a toll prefix?), 0NSN? Or NSN?

   e.g., Ericsson-LG Enterprise ER number : 02 480 7140

   1) E.164 (w/o toll prefix): 8224807140

   2) E.164 (w/ toll prefix): 82024807140

   3) 0NSN: 024807140

   4) NSN: 24807140

   What about the international call? e.g., international call prefix, SIP messages of an international incoming call

-. SIP Message Specification

   1) SIP message format, packet example and description required - for an incoming & outgoing call

        e.g., From field format specification, PAID field usage, A or B party presentation for call forward/transit

   2) anonymous call specification – outgoing call: From, Contact field format, Privacy header usage, PAID header usage

   3) Emergency number calling specification – packet example, what special headers required?

-. Test Requirement on the LAB

   1) contact TAM to proceed SIP Trunk IoT

   2) SIP connection instance

   3) 2 available DDI numbers

 

Please contact your TAM for detailed information with regard to the new SIP trunk IoT.   

If it requires anything to modify, enhance or develop the iPECS Cloud software, the schedule of new SIP trunk rollout needs to be setup carefully.

        

Tips

Save button in the Customer manager portal

-. There are menus of having multiple tab configuration in the customer manager portal, such as ‘Line Setting’, ‘User Setup’,

    ‘User Phone Configuration’, ‘Hunt Group’ and Auto Attendant – Scenario Define’.

-. When ‘Save’ button is located below the line, the changes of all table of that menu will be save at once with ‘Save’ button.

    e.g., ‘AA Scenario Define’ has 4 tabs and all changes of these tabs can be save at once using ‘Save’ button below the line.

-. But you need to press ‘Save’ button to apply change on every tabs if ‘Save’ button is located above the line.

    e.g., ‘Line settings’ menu has 4 tabs, you need to press ‘Save’ button of each tab for changes.

 

Have exciting news or questions to share, Submit it to here.

 

 

 

 

Tags
No added tags