Frequently Asked Questions
      Back to home
      1. Help Centre
      2. Frequently Asked Questions

      What Telephone Number Formats are supported by SecureCo?

      Learn what Telephone Numbering Formats are supported by SecureCo Voice Services

      Overview

      The Intelligent Voice Platform (IVP) is designed to operate globally and manage phone numbers in multiple countries, requiring it to store and process phone numbers in International E.164 format (including the leading + sign).

      Example:

      SecureCo's Australian Telephone Number 1300731158 in Australian "National" Format would be shown as +611300731158 in E.164 format.

      This prevents overlaps between numbers that are similar or the same in different countries, including allowing customers to associate numbers from multiple countries with the same service where they are operating in multiple regions.

      What Voice Services does this apply to?

      SIP Trunks

      For incoming calls to SIP Trunk services, the IVP sends E.164 Format (including the leading +) within any SIP headers that may contain telephone numbers, including but not limited to:

      • SIP Request URI - Often Used to Indicate Called Number (DNIS) 
      • SIP From Header - Caller ID Name (where available) and Number (CLI or ANI)
      • SIP To Header - Called Number (DNIS)
      • SIP Diversion Indications:
        • SIP Remote-Party-ID Header (RFC3323)
        • SIP Diversion Header

      Example Incoming Call SIP INVITE from IVP to Customer:

      INVITE sip:+612725774XX@sip.pstnhub.microsoft.com:5061;transport=TLS SIP/2.0
      Via:  SIP/2.0/TLS XXX.XXX.XXX.XXX:5061;branch=z9hG4bKZZZZZZ
      Max-Forwards:  32
      From:  "+614XXXXXXXXX" <sip:+614XXXXXXXX@XXXX.pstn.ivp.secureco.co>;tag=YYYYYYY
      To:  <sip:+612725774XX@sip.pstnhub.microsoft.com:5061>
      Call-ID: YYYYYYYYYYYYYY
      CSeq:  71138125 INVITE
      Contact:  <sip:XXX:5061;transport=tls>
      Supported:  timer, path, replaces
      Allow-Events:  talk, hold, conference, refer
      Session-Expires:  3600;refresher=uac
      Min-SE:  3600
      Privacy:  none
      Content-Type:  application/sdp
      Content-Disposition:  session
      Content-Length:  1499
      X-SecureCo-Correlation-ID:  XXXXXXXXXXXXXXXXXXXXX
      P-Asserted-Identity:  "+614XXXXXXXXX" <sip:+614XXXXXXXXX@XXXX.pstn.ivp.secureco.co>
      Record-Route:  <sip:XXXX.pstn.ivp.secureco.co:5061;transport=tls;r2=on;lr;ftag=WWWWWW>
      Allow:  INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
      User-Agent:  Intelligent Voice Platform

      For outgoing calls made by customers via SIP Trunk services, the IVP requires that the customer ensures that any SIP Headers containing telephone numbers are sent to SecureCo in E.164 Format (including the leading +) including but not limited to:

      • SIP Request URI - Number being Called
      • SIP From Header - Number to Present as Caller ID to the Called Party
        Note: IVP will Screen the CLI and behave as per the 
      • SIP To Header - Number being Called
      • SIP P-Asserted-Identity Header - 
      • SIP Diversion Indications (if applicable due to a diversion / call forward on customer equipment):
        • SIP Remote-Party-ID Header (RFC3323)
        • SIP Diversion Header

      Warning: While in some cases calls using number formats other than E.164 including E.164 missing the leading + may work, it may lead to unexpected behaviours and is not a configuration supported by SecureCo if a ticket is raised for failed calls.

      Example Outgoing Call SIP INVITE from Customer to IVP:

      INVITE sip:+614XXXXXXXX@XXX.pstn.ivp.secureco.co:5061;user=phone;transport=tls SIP/2.0
      FROM:  "Teams User"<sip:+612725774XX@sip.pstnhub.microsoft.com:5061;user=phone>;tag=YYYYYY
      TO:  <sip:+614XXXXXXXX@XXX.pstn.ivp.secureco.co:5061;user=phone>
      CSEQ:  1 INVITE
      CALL-ID:  YYYYYYYY
      MAX-FORWARDS:  69
      VIA:  SIP/2.0/TLS 52.114.16.74:5061;branch=z9hG4bKZZZZZZ
      RECORD-ROUTE:  <sip:sip-du-a-au.pstnhub.microsoft.com:5061;transport=tls;lr>
      CONTACT:  <sip:api-du-c-auea.pstnhub.microsoft.com:443;x-i=XXXXXX>
      CONTENT-LENGTH:  1106
      MIN-SE:  300
      SUPPORTED:  histinfo,timer
      USER-AGENT:  Microsoft.PSTNHub.SIPProxy v.2023.6.29.3 i.AUEA.0
      CONTENT-TYPE:  application/sdp
      ALLOW:  INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
      SESSION-EXPIRES:  3600

      Emergency Calls: Because of the E.164 requirement on SecureCo services, it is recommended that customers ensure their equipment sends any emergency calls in E.164 format, especially where the service has numbers from multiple countries associated with it.

      For Example: Australian Emergency Services 000 would be sent as +61000 and North American 911 would be +1911 with the correct Caller ID for the caller's location sent in the From and optional P-Asserted-Identity or Remote Party-ID  headers.

      Voice Gateway

      For incoming calls to Voice Gateway, the IVP sends E.164 Format (including the leading +) within any metadata sent to the Bot including but not limited to:

      • Called Number
      • Calling Number
      • Redirecting Number

      For Transfers or outgoing calls from Voice Gateway, the IVP requires telephone numbers to be specified in E.164 format (including the leading +) including but not limited to:

      • Transfer Destination Number (Transfers Only)
      • Called Number (Outgoing Calls Only)
      • Calling Number (Outgoing Calls Only)

      Warning: While in some cases Voice Gateway transfers or outgoing calls using number formats other than E.164 including E.164 missing the leading + may work, it may lead to unexpected behaviours and is not a configuration supported by SecureCo if a ticket is raised for failed calls.

      Need More Information?

      Please refer to the SIP Trunking and Voice Gateway documentation for further information.