sip-implementors  

Messages by Thread

• [Sip-implementors] Handling 5XX that is not 503 Brian Rosen
• [Sip-implementors] RFC 7865 MATHEAU Franck (SNCF / DIR TECHNOLOGIES INNOVATION ET PROJETS GROUPE / DIN & RECH EUROPE)
  • Re: [Sip-implementors] RFC 7865 Paul Kyzivat
  • Re: [Sip-implementors] RFC 7865 Paul Kyzivat
• [Sip-implementors] retrieve IMEI of device Ranjit Avasarala
• [Sip-implementors] SRTP authentication issue Peter Schraffl
• [Sip-implementors] Transaction ACK route headers Filippos Vasilakis
  • Re: [Sip-implementors] Transaction ACK route headers Dale R. Worley
  • Re: [Sip-implementors] Transaction ACK route headers Ulrich Prakash
• [Sip-implementors] Call route advance standard Amanpreet Singh
  • Re: [Sip-implementors] Call route advance standard Govandcorp
  • Re: [Sip-implementors] Call route advance standard Dale R. Worley
  • Re: [Sip-implementors] Call route advance standard Govandcorp
  • Re: [Sip-implementors] Call route advance standard Amanpreet Singh
  • Re: [Sip-implementors] Call route advance standard Ranjit Avasarala
  • Re: [Sip-implementors] Call route advance standard Dale R. Worley
  • Re: [Sip-implementors] Call route advance standard Ranjit Avasarala
• [Sip-implementors] Call hold with a=inactive Sundbaum Per-Johan (Telenor Sverige AB)
  • Re: [Sip-implementors] Call hold with a=inactive Roman Shpount
  • Re: [Sip-implementors] Call hold with a=inactive Sundbaum Per-Johan (Telenor Sverige AB)
  • Re: [Sip-implementors] Call hold with a=inactive Roman Shpount
  • Re: [Sip-implementors] Call hold with a=inactive Sundbaum Per-Johan (Telenor Sverige AB)
  • Re: [Sip-implementors] Call hold with a=inactive Paul Kyzivat
  • Re: [Sip-implementors] Call hold with a=inactive Sundbaum Per-Johan (Telenor Sverige AB)
• [Sip-implementors] Authorization Header in the SIP Register. Zuñiga , Guillermo
• [Sip-implementors] Auto: Sip-implementors Digest, Vol 103, Issue 3 agnes . maurel
• [Sip-implementors] UAC sends ACK using transport UDP instead of TLS as specified in INVITE and Via sapellegrino
  • Re: [Sip-implementors] UAC sends ACK using transport UDP instead of TLS as specified in INVITE and Via Bartosz Baranowski
  • Re: [Sip-implementors] UAC sends ACK using transport UDP instead of TLS as specified in INVITE and Via Roman Shpount
• [Sip-implementors] Auto: Sip-implementors Digest, Vol 103, Issue 1 agnes . maurel
• [Sip-implementors] What is the rule for retransmitting the SIP packet Arun T
  • Re: [Sip-implementors] What is the rule for retransmitting the SIP packet Roman Shpount
  • Re: [Sip-implementors] What is the rule for retransmitting the SIP packet Arun T
  • Re: [Sip-implementors] What is the rule for retransmitting the SIP packet Roman Shpount
  • Re: [Sip-implementors] What is the rule for retransmitting the SIP packet Ranjit Avasarala
  • Re: [Sip-implementors] What is the rule for retransmitting the SIP packet Arun T
  • Re: [Sip-implementors] What is the rule for retransmitting the SIP packet Alex Balashov
• [Sip-implementors] 2 INVITE's: 491 answer -> 1 INVITE Alexandra Dias
  • Re: [Sip-implementors] 2 INVITE's: 491 answer -> 1 INVITE Dale R. Worley
• [Sip-implementors] Unsubscribe from Mail list Sunil hegde
• Re: [Sip-implementors] Sip-implementors Digest, Vol 98, Issue 11 PT.Pertamina Pertamina
• Re: [Sip-implementors] Sip-implementors Digest, Vol 98, Issue 9 PT.Pertamina Pertamina
  • Re: [Sip-implementors] Sip-implementors Digest, Vol 98, Issue 9 Info Skymem
• [Sip-implementors] How to differentiate Hold RTP and voice RTP Arun Tagare
  • Re: [Sip-implementors] How to differentiate Hold RTP and voice RTP Amanpreet Singh
  • Re: [Sip-implementors] How to differentiate Hold RTP and voice RTP Arun Tagare
  • Re: [Sip-implementors] How to differentiate Hold RTP and voice RTP Amanpreet Singh
  • Re: [Sip-implementors] How to differentiate Hold RTP and voice RTP Ranjit Avasarala
  • Re: [Sip-implementors] How to differentiate Hold RTP and voice RTP Arun Tagare
  • Re: [Sip-implementors] How to differentiate Hold RTP and voice RTP Ranjit Avasarala
  • Re: [Sip-implementors] How to differentiate Hold RTP and voice RTP Roman Shpount
  • Re: [Sip-implementors] How to differentiate Hold RTP and voice RTP Arun Tagare
  • Re: [Sip-implementors] How to differentiate Hold RTP and voice RTP Paul Kyzivat
  • Re: [Sip-implementors] How to differentiate Hold RTP and voice RTP Dale R. Worley
  • Re: [Sip-implementors] How to differentiate Hold RTP and voice RTP Roman Shpount
• [Sip-implementors] RTP packet loss tolerance/ timers Amanpreet Singh
  • Re: [Sip-implementors] RTP packet loss tolerance/ timers Basu Chikkalli
  • Re: [Sip-implementors] [SIPForum-discussion] RTP packet loss tolerance/ timers Dale R. Worley
  • Re: [Sip-implementors] [SIPForum-discussion] RTP packet loss tolerance/ timers Amanpreet Singh
  • Re: [Sip-implementors] [SIPForum-discussion] RTP packet loss tolerance/ timers Ranjit Avasarala
  • Re: [Sip-implementors] [SIPForum-discussion] RTP packet loss tolerance/ timers James Bress
  • Re: [Sip-implementors] [SIPForum-discussion] RTP packet loss tolerance/ timers Dale R. Worley
  • Re: [Sip-implementors] [SIPForum-discussion] RTP packet loss tolerance/ timers Info Skymem
  • Re: [Sip-implementors] [SIPForum-discussion] RTP packet loss tolerance/ timers Amanpreet Singh
• Re: [Sip-implementors] Where in the SDP RFC I could find why rtpmap is not define when we have just one payload like g711 and just another dynamic payload Jānis Rukšāns
• Re: [Sip-implementors] question about RFC 8866 SDP Dale R. Worley
  • Re: [Sip-implementors] question about RFC 8866 SDP Filippos Vasilakis
• [Sip-implementors] Sip From header without user part Rakesh
  • Re: [Sip-implementors] Sip From header without user part Paul Kyzivat
  • Re: [Sip-implementors] Sip From header without user part Rakesh
  • Re: [Sip-implementors] Sip From header without user part Paul Kyzivat
  • Re: [Sip-implementors] Sip From header without user part Rakesh
  • Re: [Sip-implementors] Sip From header without user part Dale R. Worley
• [Sip-implementors] SIP over QUIC Filippos Vasilakis
  • Re: [Sip-implementors] SIP over QUIC Ranjit Avasarala
• [Sip-implementors] CSeq in subsequent Register messages Gilson Urbano Ferreira Dias
  • Re: [Sip-implementors] CSeq in subsequent Register messages Filippos Vasilakis
  • Re: [Sip-implementors] CSeq in subsequent Register messages Gilson Urbano Ferreira Dias
  • Re: [Sip-implementors] CSeq in subsequent Register messages Dale R. Worley
  • Re: [Sip-implementors] CSeq in subsequent Register messages Gilson Urbano Ferreira Dias
  • Re: [Sip-implementors] CSeq in subsequent Register messages Paul Kyzivat
• [Sip-implementors] send multiple VIA header through sipp Anjan Naik
• [Sip-implementors] fmtp is missing in the retransmitted 200ok Anusha Muralidhara
  • Re: [Sip-implementors] fmtp is missing in the retransmitted 200ok Ranjit Avasarala
  • Re: [Sip-implementors] fmtp is missing in the retransmitted 200ok Dale R. Worley
• [Sip-implementors] [Extended CFP] 4th International workshop in Artificial Intelligence and Industrial Internet-of-Things Security (AIoTS) Sergio González Muriel
  • [Sip-implementors] [Extended CFP] 4th International workshop in Artificial Intelligence and Industrial Internet-of-Things Security (AIoTS) Sergio González Muriel
  • [Sip-implementors] [Extended CFP] 4th International workshop in Artificial Intelligence and Industrial Internet-of-Things Security (AIoTS) Sergio González Muriel
  • [Sip-implementors] [Extended CFP] 4th International workshop in Artificial Intelligence and Industrial Internet-of-Things Security (AIoTS) Sergio González Muriel
• [Sip-implementors] [CFP] 4th International workshop in Artificial Intelligence and Industrial Internet-of-Things Security (AIoTS) Sergio González Muriel
  • [Sip-implementors] [CFP] 4th International workshop in Artificial Intelligence and Industrial Internet-of-Things Security (AIoTS) Sergio González Muriel
  • [Sip-implementors] [CFP] 4th International workshop in Artificial Intelligence and Industrial Internet-of-Things Security (AIoTS) Sergio González Muriel
  • [Sip-implementors] [CFP] 4th International workshop in Artificial Intelligence and Industrial Internet-of-Things Security (AIoTS) Sergio González Muriel
  • [Sip-implementors] [CFP] 4th International workshop in Artificial Intelligence and Industrial Internet-of-Things Security (AIoTS) Sergio González Muriel
  • [Sip-implementors] [CFP] 4th International workshop in Artificial Intelligence and Industrial Internet-of-Things Security (AIoTS) Sergio González Muriel
  • [Sip-implementors] [CFP] 4th International workshop in Artificial Intelligence and Industrial Internet-of-Things Security (AIoTS) Sergio González Muriel
  • [Sip-implementors] [CFP] 4th International workshop in Artificial Intelligence and Industrial Internet-of-Things Security (AIoTS) Sergio González Muriel
• [Sip-implementors] SIP REGISTER MESSAGE flow Arun Tagare
  • Re: [Sip-implementors] SIP REGISTER MESSAGE flow Paul Kyzivat
  • Re: [Sip-implementors] SIP REGISTER MESSAGE flow Ranjit Avasarala
  • Re: [Sip-implementors] SIP REGISTER MESSAGE flow Arun Tagare
  • Re: [Sip-implementors] SIP REGISTER MESSAGE flow ankur bansal
  • Re: [Sip-implementors] SIP REGISTER MESSAGE flow Arun Tagare
• [Sip-implementors] SIPit 33 Robert Sparks
• [Sip-implementors] One Month Till SIPit 33 - Focused on STIR/SHAKEN Interop Testing Marc Robins
• [Sip-implementors] SIP Forum Announces SIPit 33 - Focused on STIR/SHAKEN Interop Testing Marc Robins
• [Sip-implementors] Troubleshooting an ACK onewhoknows
  • Re: [Sip-implementors] Troubleshooting an ACK Dale R. Worley
  • Re: [Sip-implementors] Troubleshooting an ACK Ranjit Avasarala
  • Re: [Sip-implementors] Troubleshooting an ACK Arsen Semenov
• [Sip-implementors] [LAST DAY - SECOND SUBMISSION]: 2nd Joint Workshop on CPS&IoT Security and Privacy (CPSIoTSec 2021) - for papers rejected from ACM CCS 2021 [FIRM DEADLINE: JULY 30th, 2021] Call For Papers CPSIOTSEC21
• [Sip-implementors] [3 DAYS - SECOND SUBMISSION]: 2nd Joint Workshop on CPS&IoT Security and Privacy (CPSIoTSec 2021) - for papers rejected from ACM CCS 2021 [FIRM DEADLINE: JULY 30th, 2021] Call For Papers CPSIOTSEC21
• [Sip-implementors] [5 DAYS - SECOND SUBMISSION]: 2nd Joint Workshop on CPS&IoT Security and Privacy (CPSIoTSec 2021) - for papers rejected from ACM CCS 2021 [FIRM DEADLINE: JULY 30th, 2021] Call For Papers CPSIOTSEC21
• [Sip-implementors] [8 DAYS - SECOND SUBMISSION]: 2nd Joint Workshop on CPS&IoT Security and Privacy (CPSIoTSec 2021) - for papers rejected from ACM CCS 2021 [FIRM DEADLINE: JULY 30th, 2021] Call For Papers CPSIOTSEC21
• [Sip-implementors] [10 DAYS - SECOND SUBMISSION]: 2nd Joint Workshop on CPS&IoT Security and Privacy (CPSIoTSec 2021) - for papers rejected from ACM CCS 2021 [FIRM DEADLINE: JULY 30th, 2021] Call For Papers CPSIOTSEC21
• [Sip-implementors] response context association on stateful proxies Filippos Vasilakis
• [Sip-implementors] [DEADLINE APPROACHING LAST DAY - CFP]: 2nd Joint Workshop on CPS&IoT Security and Privacy (CPSIoTSec 2021) - [FIRM DEADLINE: JULY 13th, 2021] Call For Papers CPSIOTSEC21
• [Sip-implementors] [CFP] [DEADLINE APPROACHING - 1 DAY REMAINING] 2nd Joint Workshop on CPS&IoT Security and Privacy (CPSIoTSec 2021) Call For Papers CPSIOTSEC21
• [Sip-implementors] [CFP] [DEADLINE APPROACHING - 2 DAYS REMAINING] 2nd Joint Workshop on CPS&IoT Security and Privacy (CPSIoTSec 2021) Sergio González Muriel
• [Sip-implementors] Timer Sundbaum Per-Johan (Telenor Sverige AB)
• Re: [Sip-implementors] Sip-implementors Digest, Vol 85, Issue 3 7076373110
• Re: [Sip-implementors] Sip-implementors Digest, Vol 85, Issue 2 7076373110
• Re: [Sip-implementors] [sipcore] RFC 4028 UAS behavior requirement of Require header Ranjit Avasarala
  • Re: [Sip-implementors] [sipcore] RFC 4028 UAS behavior requirement of Require header Hoil Choi
  • Re: [Sip-implementors] [sipcore] RFC 4028 UAS behavior requirement of Require header Ranjit Avasarala
  • Re: [Sip-implementors] [sipcore] RFC 4028 UAS behavior requirement of Require header Paul Kyzivat
  • Re: [Sip-implementors] RFC 4028 UAS behavior requirement of Require header Paul Kyzivat
  • Re: [Sip-implementors] [sipcore] RFC 4028 UAS behavior requirement of Require header Hoil Choi
• [Sip-implementors] SDES-sRTP: When not the same Crypto Context? Alexander Traud
• [Sip-implementors] 400 BadRequest Sundbaum Per-Johan (Telenor Sverige AB)
  • [Sip-implementors] 400 BadRequest Sundbaum Per-Johan (Telenor Sverige AB)
  • Re: [Sip-implementors] 400 BadRequest Paul Kyzivat
  • Re: [Sip-implementors] 400 BadRequest Sundbaum Per-Johan (Telenor Sverige AB)
  • Re: [Sip-implementors] 400 BadRequest Paul Kyzivat
  • Re: [Sip-implementors] 400 BadRequest Sundbaum Per-Johan (Telenor Sverige AB)
• [Sip-implementors] reuse of payload type Sundbaum Per-Johan (Telenor Sverige AB)
  • Re: [Sip-implementors] reuse of payload type Ranjit Avasarala
  • Re: [Sip-implementors] reuse of payload type Sundbaum Per-Johan (Telenor Sverige AB)
  • Re: [Sip-implementors] reuse of payload type Paul Kyzivat
  • Re: [Sip-implementors] reuse of payload type Sundbaum Per-Johan (Telenor Sverige AB)
  • Re: [Sip-implementors] reuse of payload type Ranjit Avasarala
  • Re: [Sip-implementors] reuse of payload type Sundbaum Per-Johan (Telenor Sverige AB)
  • Re: [Sip-implementors] reuse of payload type Paul Kyzivat
  • Re: [Sip-implementors] reuse of payload type Sundbaum Per-Johan (Telenor Sverige AB)
  • Re: [Sip-implementors] reuse of payload type Sundbaum Per-Johan (Telenor Sverige AB)
  • Re: [Sip-implementors] reuse of payload type Arun Tagare
  • Re: [Sip-implementors] reuse of payload type Ranjit Avasarala
  • Re: [Sip-implementors] reuse of payload type Sundbaum Per-Johan (Telenor Sverige AB)
  • Re: [Sip-implementors] reuse of payload type Sundbaum Per-Johan (Telenor Sverige AB)
• Re: [Sip-implementors] Sip-implementors Digest, Vol 81, Issue 4 supp...@advisory24.vip
  • Re: [Sip-implementors] Sip-implementors Digest, Vol 81, Issue 4 supp...@advisory24.vip
  • Re: [Sip-implementors] Sip-implementors Digest, Vol 81, Issue 4 Alex Balashov
  • Re: [Sip-implementors] Sip-implementors Digest, Vol 81, Issue 4 Brian Rosen
  • Re: [Sip-implementors] Sip-implementors Digest, Vol 81, Issue 4 Jonathan Lennox
  • Re: [Sip-implementors] Sip-implementors Digest, Vol 81, Issue 4 Ranjit Avasarala
• Re: [Sip-implementors] Sip-implementors Digest, Vol 81, Issue 3 supp...@advisory24.vip
• Re: [Sip-implementors] Sip-implementors Digest, Vol 81, Issue 2 supp...@advisory24.vip
• Re: [Sip-implementors] Sip-implementors Digest, Vol 81, Issue 1 supp...@advisory24.vip
• Re: [Sip-implementors] [SIPForum-discussion] RTP Volume Values wodb0116
  • Re: [Sip-implementors] RTP Volume Values James Bress
• [Sip-implementors] RFC 4028: SessionTimer negotiation using Early Update akashdeep vishnoi
  • Re: [Sip-implementors] RFC 4028: SessionTimer negotiation using Early Update Ranjit Avasarala
  • Re: [Sip-implementors] RFC 4028: SessionTimer negotiation using Early Update ankur bansal
• [Sip-implementors] Errata ID: 4744 for RFC 4028: Session Expire timer value can be changed? akashdeep vishnoi
  • Re: [Sip-implementors] Errata ID: 4744 for RFC 4028: Session Expire timer value can be changed? Ranjit Avasarala
  • Re: [Sip-implementors] Errata ID: 4744 for RFC 4028: Session Expire timer value can be changed? akashdeep vishnoi
  • Re: [Sip-implementors] Errata ID: 4744 for RFC 4028: Session Expire timer value can be changed? Ranjit Avasarala
  • Re: [Sip-implementors] Errata ID: 4744 for RFC 4028: Session Expire timer value can be changed? akashdeep vishnoi
  • Re: [Sip-implementors] Errata ID: 4744 for RFC 4028: Session Expire timer value can be changed? Ranjit Avasarala
  • Re: [Sip-implementors] Errata ID: 4744 for RFC 4028: Session Expire timer value can be changed? akashdeep vishnoi
  • Re: [Sip-implementors] Errata ID: 4744 for RFC 4028: Session Expire timer value can be changed? OKUMURA Shinji
• Re: [Sip-implementors] Sip-implementors Digest, Vol 79, Issue 1 supp...@advisory24.vip
• [Sip-implementors] SIP TLS client cert Olle E. Johansson
• [Sip-implementors] The SIP Forum Announces Dates for SIPNOC 2020 Marc Robins
• [Sip-implementors] B2BUA Session refresh Basu Chikkalli
  • Re: [Sip-implementors] B2BUA Session refresh OKUMURA Shinji
• [Sip-implementors] RFC8760: Using different nonces for alternative algorithms [Was: [sipcore] I-D Action: draft-ietf-sipcore-digest-scheme-14.txt] Maxim Sobolev
  • Re: [Sip-implementors] RFC8760: Using different nonces for alternative algorithms [Was: [sipcore] I-D Action: draft-ietf-sipcore-digest-scheme-14.txt] Maxim Sobolev
• Re: [Sip-implementors] Sip-implementors Digest, Vol 77, Issue 2 supp...@advisory24.vip
• [Sip-implementors] RFC 3261 section 14.2 - "brand new call" does not specify whether the SDP should modify media attributes of an existing session containing a=sendonly or a=recvonly Shaun Stokes
  • Re: [Sip-implementors] RFC 3261 section 14.2 - "brand new call" does not specify whether the SDP should modify media attributes of an existing session containing a=sendonly or a=recvonly Roman Shpount
  • Re: [Sip-implementors] RFC 3261 section 14.2 - "brand new call" does not specify whether the SDP should modify media attributes of an existing session containing a=sendonly or a=recvonly Shaun Stokes
  • Re: [Sip-implementors] RFC 3261 section 14.2 - "brand new call" does not specify whether the SDP should modify media attributes of an existing session containing a=sendonly or a=recvonly Dale R. Worley
  • Re: [Sip-implementors] RFC 3261 section 14.2 - "brand new call" does not specify whether the SDP should modify media attributes of an existing session containing a=sendonly or a=recvonly Raymond Peita
• Re: [Sip-implementors] [External]Sip-implementors Digest, Vol 76, Issue 14 info
• Re: [Sip-implementors] [External]Sip-implementors Digest, Vol 76, Issue 13 info
• Re: [Sip-implementors] [External]Sip-implementors Digest, Vol 76, Issue 12 info
• [Sip-implementors] Sip-implementors Digest, Vol 76, Issue 8 Support Team
• [Sip-implementors] Sip-implementors Digest, Vol 76, Issue 10 Support Team
• [Sip-implementors] Sip-implementors Digest, Vol 76, Issue 6 Support Team
• [Sip-implementors] Sip-implementors Digest, Vol 76, Issue 7 Support Team
• [Sip-implementors] Sip-implementors Digest, Vol 76, Issue 5 Support Team
• [Sip-implementors] Sip-implementors Digest, Vol 76, Issue 4 Support Team
• Re: [Sip-implementors] [External]Sip-implementors Digest, Vol 76, Issue 11 info
• Re: [Sip-implementors] [External]Sip-implementors Digest, Vol 76, Issue 10 info
• Re: [Sip-implementors] Sip-implementors Digest, Vol 76, Issue 9 Filip Testowy
  • [Sip-implementors] Sip-implementors Digest, Vol 76, Issue 9 Support Team
• Re: [Sip-implementors] [External]Sip-implementors Digest, Vol 76, Issue 9 info
• Re: [Sip-implementors] [External]Sip-implementors Digest, Vol 76, Issue 8 info
• [Sip-implementors] Multiple Colon (:) as Header delimiter of name-value Gaurav Khare

• Earlier messages