sip-implementors  

Messages by Thread

• • Re: [Sip-implementors] sip conversation Paul Kyzivat
  • [Sip-implementors] sip conversation satya r
  • Re: [Sip-implementors] sip conversation satya r
  • [Sip-implementors] sip conversation satya r
  • Re: [Sip-implementors] sip conversation Iñaki Baz Castillo
• [Sip-implementors] Registrar / Presence Server receives SIP message without Max-Forwards Header Keerthi Srinivasan
  • Re: [Sip-implementors] Registrar / Presence Server receives SIP message without Max-Forwards Header Alok 2 Tiwari
  • Re: [Sip-implementors] Registrar / Presence Server receives SIP message without Max-Forwards Header Brett Tate
• [Sip-implementors] (no subject) satya r
  • [Sip-implementors] (no subject) satya r
  • Re: [Sip-implementors] (no subject) Sumit Jindal
  • Re: [Sip-implementors] (no subject) Iñaki Baz Castillo
  • [Sip-implementors] (no subject) satya r
  • Re: [Sip-implementors] (no subject) Mohit Soni
  • Re: [Sip-implementors] (no subject) Iñaki Baz Castillo
  • [Sip-implementors] (no subject) satya r
  • Re: [Sip-implementors] (no subject) Iñaki Baz Castillo
  • [Sip-implementors] (no subject) satya r
  • Re: [Sip-implementors] (no subject) Olle E. Johansson
  • [Sip-implementors] (no subject) Martin Wang
  • [Sip-implementors] (no subject) Nourhan Muhammed
• [Sip-implementors] sip refer - dialog reuse Mahudeswaran
• [Sip-implementors] Doubt in sip satya testing
  • Re: [Sip-implementors] Doubt in sip Joel Gerber
  • [Sip-implementors] Doubt in sip satya r
  • [Sip-implementors] Doubt in sip satya r
  • Re: [Sip-implementors] Doubt in sip Yaswanth Raparti
  • Re: [Sip-implementors] Doubt in sip Iñaki Baz Castillo
  • [Sip-implementors] Doubt in SIP voip tester
  • Re: [Sip-implementors] Doubt in SIP Tarun2 Gupta
  • [Sip-implementors] Question about proxy clustering SIP Learner
• [Sip-implementors] Is it MUST to have record-route in BYE, if Invite has it Vivek Singla
  • Re: [Sip-implementors] Is it MUST to have record-route in BYE, if Invite has it Theo Zourzouvillys
• [Sip-implementors] Is " <sip:anonymous.invalid; phone-context=+1...@domain.com:5060; maddr=10.10.10.10; transport=udp; user=phone>" a valid Contact Header? Adam Frankel
  • Re: [Sip-implementors] Is " <sip:anonymous.invalid; phone-context=+1...@domain.com:5060; maddr=10.10.10.10; transport=udp; user=phone>" a valid Contact Header? Paul Kyzivat
  • Re: [Sip-implementors] Is " <sip:anonymous.invalid; phone-context=+1...@domain.com:5060; maddr=10.10.10.10; transport=udp; user=phone>" a valid Contact Header? Adam Frankel
  • Re: [Sip-implementors] Is " <sip:anonymous.invalid; phone-context=+1...@domain.com:5060; maddr=10.10.10.10; transport=udp; user=phone>" a valid Contact Header? Paul Kyzivat
  • Re: [Sip-implementors] Is " <sip:anonymous.invalid; phone-context=+1...@domain.com:5060; maddr=10.10.10.10; transport=udp; user=phone>" a valid Contact Header? Theo Zourzouvillys
  • Re: [Sip-implementors] Is " <sip:anonymous.invalid; phone-context=+1...@domain.com:5060; maddr=10.10.10.10; transport=udp; user=phone>" a valid Contact Header? Paul Kyzivat
  • Re: [Sip-implementors] Is " <sip:anonymous.invalid; phone-context=+1...@domain.com:5060; maddr=10.10.10.10; transport=udp; user=phone>" a valid Contact Header? Brett Tate
  • [Sip-implementors] Appropriate, and inappropriate, use of user=phone. Paul Kyzivat
  • Re: [Sip-implementors] Is " <sip:anonymous.invalid; phone-context=+1...@domain.com:5060; maddr=10.10.10.10; transport=udp; user=phone>" a valid Contact Header? Brett Tate
  • Re: [Sip-implementors] Is " <sip:anonymous.invalid; phone-context=+1...@domain.com:5060; maddr=10.10.10.10; transport=udp; user=phone>" a valid Contact Header? Paul Kyzivat
• [Sip-implementors] simultaneous use of UDP and TCP Arun kalia
  • Re: [Sip-implementors] simultaneous use of UDP and TCP Brett Tate
  • [Sip-implementors] Content header : application/isup Vivek Singla
  • Re: [Sip-implementors] Content header : application/isup Paul Kyzivat
  • Re: [Sip-implementors] Content header : application/isup Joel Gerber
  • Re: [Sip-implementors] Content header : application/isup Vivek Singla
  • Re: [Sip-implementors] Content header : application/isup Joel Gerber
  • Re: [Sip-implementors] Content header : application/isup Vivek Singla
  • Re: [Sip-implementors] Content header : application/isup Harsha. R
• Re: [Sip-implementors] Route Set creation from response Kamini Gangwani
  • Re: [Sip-implementors] Route Set creation from response Kumar, Puneet (Puneet)
  • Re: [Sip-implementors] Route Set creation from response Gaurav Khare
  • Re: [Sip-implementors] Route Set creation from response Kamini Gangwani
• [Sip-implementors] Route Set creation from response. Kumar, Puneet (Puneet)
  • Re: [Sip-implementors] Route Set creation from response. Olle E. Johansson
  • Re: [Sip-implementors] Route Set creation from response. Brett Tate
• [Sip-implementors] Request-URI Vs to URI ikuzar RABE
  • Re: [Sip-implementors] Request-URI Vs to URI Olle E. Johansson
  • Re: [Sip-implementors] Request-URI Vs to URI Dean Willis
• [Sip-implementors] Regarding Expires values in SUBSCRIBE Santhana Krishnan
  • Re: [Sip-implementors] Regarding Expires values in SUBSCRIBE Paul Kyzivat
• [Sip-implementors] branch length in Via field Aro RANAIVONDRAMBOLA
  • Re: [Sip-implementors] branch length in Via field Brett Tate
  • Re: [Sip-implementors] branch length in Via field Paul Kyzivat
• [Sip-implementors] FQDN length ? Aro RANAIVONDRAMBOLA
  • Re: [Sip-implementors] FQDN length ? Brett Tate
  • Re: [Sip-implementors] FQDN length ? Joel Gerber
• [Sip-implementors] SIP outbound and contacts Olle E. Johansson
• [Sip-implementors] Query a SIP user Antonio Spirandelli
• [Sip-implementors] Registration for SIPit 30 is open Robert Sparks
  • [Sip-implementors] Deadline approaching (was: Registration for SIPit 30 is open) Robert Sparks
  • Re: [Sip-implementors] Deadline approaching Robert Sparks
• [Sip-implementors] FOSDEM 2013 Telephony/Communications Devroom Call for Presenters Matthew Jordan
• [Sip-implementors] Transaction Stateful Proxy Keerthi Srinivasan
• [Sip-implementors] SIP Forking Vivek Gupta
  • Re: [Sip-implementors] SIP Forking Brett Tate
• [Sip-implementors] What will be set in Request-URI with respect to loose and strict routing Vivek Batra
  • Re: [Sip-implementors] What will be set in Request-URI with respect to loose and strict routing Alok 2 Tiwari
  • Re: [Sip-implementors] What will be set in Request-URI with respect to loose and strict routing Pranab Bohra
  • Re: [Sip-implementors] What will be set in Request-URI with respect to loose and strict routing Vivek Gupta
  • Re: [Sip-implementors] What will be set in Request-URI with respect to loose and strict routing Alok 2 Tiwari
  • Re: [Sip-implementors] What will be set in Request-URI with respect to loose and strict routing Pranab Bohra
  • Re: [Sip-implementors] What will be set in Request-URI with respect to loose and strict routing Nataraju A.B
  • Re: [Sip-implementors] What will be set in Request-URI with respect to loose and strict routing Brett Tate
• [Sip-implementors] Looking for a Server (Open Source) which supports Instant Message Store and forward Premalatha Rajasekaran
• [Sip-implementors] SUBSCRIBE request having multiple contact header Keerthi Srinivasan
  • Re: [Sip-implementors] SUBSCRIBE request having multiple contact header Preksha .
  • Re: [Sip-implementors] SUBSCRIBE request having multiple contact header Brett Tate
  • Re: [Sip-implementors] SUBSCRIBE request having multiple contact header Jānis Rukšāns
  • Re: [Sip-implementors] SUBSCRIBE request having multiple contact header Paul Kyzivat
  • Re: [Sip-implementors] SUBSCRIBE request having multiple contact header Brett Tate
  • Re: [Sip-implementors] SUBSCRIBE request having multiple contact header Jānis Rukšāns
• [Sip-implementors] Help understanding trace Antonio Spirandelli
  • Re: [Sip-implementors] Help understanding trace Alok 2 Tiwari
  • Re: [Sip-implementors] Help understanding trace Antonio Spirandelli
• [Sip-implementors] Is contact header mandatory for each sip messages? Tamjid Ali
  • Re: [Sip-implementors] Is contact header mandatory for each sip messages? Yaswanth Raparti
  • Re: [Sip-implementors] Is contact header mandatory for each sip messages? Alok 2 Tiwari
  • Re: [Sip-implementors] Is contact header mandatory for each sip messages? Pranab Bohra
• [Sip-implementors] To-Tag in REGISTER message Keerthi Srinivasan
  • Re: [Sip-implementors] To-Tag in REGISTER message Vivek Talwar
  • Re: [Sip-implementors] To-Tag in REGISTER message Paul Kyzivat
  • Re: [Sip-implementors] [SIPForum-discussion] To-Tag in REGISTER message Santosh Iyer
  • Re: [Sip-implementors] [SIPForum-discussion] To-Tag in REGISTER message Partha Ray
  • Re: [Sip-implementors] [SIPForum-discussion] To-Tag in REGISTER message Vijay Badola
  • Re: [Sip-implementors] [SIPForum-discussion] To-Tag in REGISTER message Pranav Damele
  • Re: [Sip-implementors] [SIPForum-discussion] To-Tag in REGISTER message Vijay Badola
• [Sip-implementors] SIP server intergration with Windows Application Ritwick
• [Sip-implementors] Payload type change "on the fly" kumar.ramadoss
  • Re: [Sip-implementors] Payload type change "on the fly" Paul Kyzivat
• [Sip-implementors] sip source code venkateswarlu Nidamanuri
• [Sip-implementors] PRACK Response Time from UAS NK
  • Re: [Sip-implementors] PRACK Response Time from UAS Brett Tate
  • Re: [Sip-implementors] PRACK Response Time from UAS NK
  • Re: [Sip-implementors] PRACK Response Time from UAS Brett Tate
  • Re: [Sip-implementors] PRACK Response Time from UAS Kumar Verma, Sunil (Sunil)
• [Sip-implementors] Codec Negotiation Frank S.
  • Re: [Sip-implementors] Codec Negotiation Paul Kyzivat
  • Re: [Sip-implementors] Codec Negotiation Brett Tate
  • Re: [Sip-implementors] Codec Negotiation Aman
  • Re: [Sip-implementors] Codec Negotiation Ashwin Kumar
  • Re: [Sip-implementors] Codec Negotiation Kumar Verma, Sunil (Sunil)
• [Sip-implementors] 403 forbidden response Lohith HS
  • Re: [Sip-implementors] 403 forbidden response Manivannan S
• [Sip-implementors] BFCP query for content channel Gaurav Kumar
  • Re: [Sip-implementors] BFCP query for content channel Charles Eckel (eckelcu)
  • [Sip-implementors] different SDPs in 18x and 200 OK sam.jeyaseelan
  • Re: [Sip-implementors] different SDPs in 18x and 200 OK Paul Kyzivat
  • Re: [Sip-implementors] different SDPs in 18x and 200 OK sam.jeyaseelan
  • Re: [Sip-implementors] different SDPs in 18x and 200 OK Paul Kyzivat
  • Re: [Sip-implementors] different SDPs in 18x and 200 OK Olle E. Johansson
  • Re: [Sip-implementors] different SDPs in 18x and 200 OK Brett Tate
  • Re: [Sip-implementors] different SDPs in 18x and 200 OK Paul Kyzivat
• [Sip-implementors] Calling NUMBER display p...@codetech.net
• [Sip-implementors] Same dynamic payload numbers in rtpmap and fmtp line in SDP for different video codecs Gaurav Kumar
  • Re: [Sip-implementors] Same dynamic payload numbers in rtpmap and fmtp line in SDP for different video codecs Kashif Husain
• [Sip-implementors] A questions a bout the requirements to adapt the SIP client to a device Amir Amininejad
• [Sip-implementors] Doubt regarding privacy header Yaswanth Raparti
  • [Sip-implementors] doubt regarding privacy header bumble omap
• [Sip-implementors] Reminder: Regarding SIP Outbound feature implementation manju nath
  • Re: [Sip-implementors] Reminder: Regarding SIP Outbound feature implementation Ozdogru, Kutay
  • Re: [Sip-implementors] Reminder: Regarding SIP Outbound feature implementation manju nath
  • Re: [Sip-implementors] Reminder: Regarding SIP Outbound feature implementation Brez Borland
  • Re: [Sip-implementors] Reminder: Regarding SIP Outbound feature implementation manju nath
  • Re: [Sip-implementors] Reminder: Regarding SIP Outbound feature implementation Brez Borland
• [Sip-implementors] Inputs required on Memory leak in RADV code Rakesh Rajkumar
  • Re: [Sip-implementors] Inputs required on Memory leak in RADV code Ozdogru, Kutay
  • Re: [Sip-implementors] Inputs required on Memory leak in RADV code berat çağlar er
  • Re: [Sip-implementors] Inputs required on Memory leak in RADV code Rakesh Rajkumar
  • Re: [Sip-implementors] Inputs required on Memory leak in RADV code Brez Borland
• [Sip-implementors] need help pranab sahoo
  • [Sip-implementors] need help Pranab Sahoo
• [Sip-implementors] Call escalation and de-escalation between audio call and video call Xu, Fangpo
  • Re: [Sip-implementors] Call escalation and de-escalation between audio call and video call Ashwin Kumar
  • Re: [Sip-implementors] Call escalation and de-escalation between audio call and video call Balint Menyhart
• [Sip-implementors] Regarding SIP Outbound feature implementation manju nath
• [Sip-implementors] ask for PRACK omitting Require:100rel Manolis Katsidoniotis
  • Re: [Sip-implementors] ask for PRACK omitting Require:100rel Alok 2 Tiwari
• [Sip-implementors] regarding user behaviour in REGISTRATION request with contact header having no value pranab sahoo
  • Re: [Sip-implementors] regarding user behaviour in REGISTRATION request with contact header having no value Tarun2 Gupta
  • Re: [Sip-implementors] regarding user behaviour in REGISTRATION request with contact header having no value pranab sahoo
  • Re: [Sip-implementors] regarding user behaviour in REGISTRATION request with contact header having no value Tarun2 Gupta
• [Sip-implementors] How to a server is redirect or not. kiran kumar
  • Re: [Sip-implementors] How to a server is redirect or not. Brett Tate
  • Re: [Sip-implementors] How to a server is redirect or not. kiran kumar
  • Re: [Sip-implementors] How to a server is redirect or not. Paul Kyzivat
• [Sip-implementors] Race between re-registration and registration expiration Michael Schwarz
  • Re: [Sip-implementors] Race between re-registration and registration expiration Brett Tate
  • Re: [Sip-implementors] Race between re-registration and registration expiration Neel Neelakantan
• [Sip-implementors] Query on Transport parameter in Contact header kumar.ramadoss
  • Re: [Sip-implementors] Query on Transport parameter in Contact header Brett Tate
  • Re: [Sip-implementors] Query on Transport parameter in Contact header kumar.ramadoss
  • Re: [Sip-implementors] Query on Transport parameter in Contact header Brett Tate
• [Sip-implementors] query regarding RTP and RTCP pranab sahoo
  • Re: [Sip-implementors] query regarding RTP and RTCP Charles Eckel (eckelcu)
• [Sip-implementors] Reject CANCEL with 481 or statelessly forward? Clayton Hawbaker
  • Re: [Sip-implementors] Reject CANCEL with 481 or statelessly forward? Worley, Dale R (Dale)
  • Re: [Sip-implementors] Reject CANCEL with 481 or statelessly forward? Clayton Hawbaker
• Re: [Sip-implementors] Mime parser for ISUP message in SIP body Srivastava, Gaurav
  • Re: [Sip-implementors] Mime parser for ISUP message in SIP body satish agrawal
• [Sip-implementors] Should a proxy relay a second 200 for a SUBSCRIBE? Iñaki Baz Castillo
  • Re: [Sip-implementors] Should a proxy relay a second 200 for a SUBSCRIBE? Neel Neelakantan
  • Re: [Sip-implementors] Should a proxy relay a second 200 for a SUBSCRIBE? Brett Tate
  • Re: [Sip-implementors] Should a proxy relay a second 200 for a SUBSCRIBE? Iñaki Baz Castillo
  • Re: [Sip-implementors] Should a proxy relay a second 200 for a SUBSCRIBE? Olle E. Johansson
  • Re: [Sip-implementors] Should a proxy relay a second 200 for a SUBSCRIBE? Iñaki Baz Castillo
  • Re: [Sip-implementors] Should a proxy relay a second 200 for a SUBSCRIBE? Worley, Dale R (Dale)
• [Sip-implementors] Behavior for ACK on local transport errors Brez Borland
  • Re: [Sip-implementors] Behavior for ACK on local transport errors Brett Tate
• [Sip-implementors] Can BYE be sent by UAC just after receiving 18x Response Pratishtha Pandey
  • Re: [Sip-implementors] Can BYE be sent by UAC just after receiving 18x Response Brett Tate

• Later messages