0

NSS SIP INVITE/302 Example

NSS supports standard SIP INVITE/302 redirect in addition to REST.  A 302 is provided to all STI-AS requests whether a call received a signature or not. A 302 is provided to all STI-VS requests.

STI-AS

INVITE sip:8587542211@nss-staging.sansay.com:5060 SIP/2.0
Via: SIP/2.0/UDP 54.177.185.224:5060;branch=z9hG4bK1sansay200rdb6
Record-Route: <sip:sansay200rdb6@54.177.185.224:5060;lr;transport=udp>
To: <sip:8587542211@nss-staging.sansay.com>
From: "Sansay Lab 1" <sip:8587542200@54.177.185.224;otg=000200;qtype=sti-as>;tag=sansay200rdb6
Call-ID: sti-as-41-0-356108330@172.31.23.116
CSeq: 1 INVITE
Contact: <sip:8587542200@54.177.185.224:5060>
Supported: replaces
Identity:
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, MESSAGE
Max-Forwards: 69
Content-Length: 0

The From otg and qtype are optional parameters. otg stands for Originating Trunk Group and it is used in NSS to apply attestation policies that involve a specific originating Trunk ID. qtype=sti-as is used for reporting purposes. You can also use qtype to more easily distinguish the type of transaction.

SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/UDP 54.177.185.224:5060;branch=z9hG4bK1sansay200rdb6
To: <sip:8587542211@nss-staging.sansay.com>
From: "Sansay Lab 1" <sip:8587542200@54.177.185.224;otg=000200;qtype=sti-as>;tag=sansay200rdb6
Call-ID: sti-as-41-0-356108330@172.31.23.116
CSeq: 1 INVITE
Contact: <sip:8587542211@54.177.185.224>
Identity: eyJhbGciOiJFUzI1NiIsInBwdCI6InNoYWtlbiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9jci5zYW5zYXkuY29tL1NhbnNheV85OTdUIn0.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyIxODU4NzU0MjIxMSJdfSwiaWF0IjoxNjE2NDU3MzA3LCJvcmlnIjp7InRuIjoiMTg1ODc1NDIyMDAifSwib3JpZ2lkIjoiMDc4ODJkYmEtOGI2YS0xMWViLWFlMDUtZGNiYmRiZGM4ODg4In0.CstFGUo9yAc_i4belI07rS-iYx4AtWPwlrL2R1Fb7knieyUvlRzO6X-eBYv5akAXcwVtP5PTEaBxJkp0bjZkxQ;info=<https://cr.sansay.com/Sansay_997T>;alg=ES256;ppt="shaken"
Content-Length: 0

STI-VS

INVITE sip:8587542211@nss-staging.sansay.com:5060 SIP/2.0
Via: SIP/2.0/UDP 54.177.185.224:5060;branch=z9hG4bK1sansay202rdb8
Record-Route: <sip:sansay202rdb8@54.177.185.224:5060;lr;transport=udp>
To: <sip:8587542211@nss-staging.sansay.com>
From: "Sansay Lab 1" <sip:8587542200@54.177.185.224;ttg=000201;qtype=sti-vs>;tag=sansay202rdb8
Call-ID: sti-vs-41-0-356108330@172.31.23.116
CSeq: 1 INVITE
Contact: <sip:8587542200@54.177.185.224:5060>
Supported: replaces
Identity: eyJhbGciOiJFUzI1NiIsInBwdCI6InNoYWtlbiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9jci5zYW5zYXkuY29tL1NhbnNheV85OTdUIn0.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyIxODU4NzU0MjIxMSJdfSwiaWF0IjoxNjE2NDU3MzA3LCJvcmlnIjp7InRuIjoiMTg1ODc1NDIyMDAifSwib3JpZ2lkIjoiMDc4ODJkYmEtOGI2YS0xMWViLWFlMDUtZGNiYmRiZGM4ODg4In0.CstFGUo9yAc_i4belI07rS-iYx4AtWPwlrL2R1Fb7knieyUvlRzO6X-eBYv5akAXcwVtP5PTEaBxJkp0bjZkxQ;info=<https://cr.sansay.com/Sansay_997T>;alg=ES256;ppt="shaken"
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, MESSAGE
Max-Forwards: 69
Content-Length: 0

For STI-VS, From ttg stands for terminating trunk group. This parameter along with qtype are used only for reporting and are considered optional.

SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/UDP 54.177.185.224:5060;branch=z9hG4bK1sansay202rdb8
To: <sip:8587542211@nss-staging.sansay.com>
From: "Sansay Lab 1" <sip:8587542200;verstat=TN-Validation-Passed@54.177.185.224;ttg=000201;qtype=sti-vs>;tag=sansay202rdb8
Call-ID: sti-vs-41-0-356108330@172.31.23.116
CSeq: 1 INVITE
Contact: <sip:8587542211@54.177.185.224>
Reason: SIP;cause=302;text="no-fraud-detected"
Content-Length: 0

SIP Message Conversion

NSS SIP Message Conversion engine can be used to modify the INVITE or 302 response for interoperability or special cases. In addition to standard SIP (e.g. manipulate response code, response text, SIP header parameters), NSS' SMC can:

  • Insert a Date header with the request's associated timestamp.
  • Return the Attestation Level (A,C,B) and/or Reason Text in a proprietary header (e.g. X-Attest, X-Reason).
  • Request a specific level of attestation.

3 replies

null
    • moises_amiga
    • 2 yrs ago
    • Reported - view

    Hi

    How its possible to add a date with the SMC?

      • cperez
      • 2 yrs ago
      • Reported - view

      Moy Amiga yes, that is available in our latest release. We will share the SMC with you.

      • Carlos_Tena
      • 2 yrs ago
      • Reported - view

      Moy Amiga 

      You can use the attached SMC profile as an example to insert the Date header. You need the VSXi code 10.5.1.354R12 or the NSS code 5.1.581.11R71 to be able to use the new SMC variable for the date.