by Date

2005-11-10

• Re: [reSIProcate] dum - sip stack many-to-one relation question
  • From: Jason Fischl
• Re: [reSIProcate] Problem designing a B2BUA with DUM
  • From: Jason Fischl
• RE: [reSIProcate] dum - sip stack many-to-one relation question
  • From: Micky Kaufmann
• [reSIProcate] Problem designing a B2BUA with DUM
  • From: Micky Kaufmann
• Re: [reSIProcate] dum - sip stack many-to-one relation question
  • From: Jason Fischl
• Re: [reSIProcate] How can I catch the interface that received a SipMessage
  • From: Jason Fischl
• [reSIProcate] How can I catch the interface that received a SipMessage
  • From: Lorenzo
• Re: [reSIProcate] dum - sip stack many-to-one relation question
  • From: Meir Elberg
• [reSIProcate] Fwd: Using syslog
  • From: Boris Rozinov
• RE: [reSIProcate] How can one deal with 200 OK with incorrect SDP ?
  • From: Scott Godin
• RE: [reSIProcate] PRACK is not completely supported on the sever side?
  • From: Scott Godin
• [reSIProcate] How can convert a InviteSessionHandle to ServerInviteSessionHandle?
  • From: frank zhao
• [reSIProcate] PRACK is not completely supported on the sever side?
  • From: frank zhao
• RE: [reSIProcate] onSuccess for registration is called only ones
  • From: Scott Godin
• Re: [reSIProcate] onSuccess for registration is called only ones
  • From: Gianluca Martiniello
• RE: [reSIProcate] onSuccess for registration is called only ones
  • From: Asheesh Joshi
• [reSIProcate] onSuccess for registration is called only ones
  • From: Sasha Youkhananov
• [reSIProcate] How can one deal with 200 OK with incorrect SDP ?
  • From: Asheesh Joshi

2005-11-09

• Re: [reSIProcate] generate a 183 with SDP on the server side
  • From: Jason Fischl
• Re: [reSIProcate] MessageWaitingContexts: a bit wrong encoding
  • From: Jason Fischl
• Re: [reSIProcate] dum - sip stack many-to-one relation question
  • From: Jason Fischl
• RE: [reSIProcate] dum - sip stack many-to-one relation question
  • From: Micky Kaufmann
• RE: [reSIProcate] ServerInviteSession Bug on provisional
  • From: Scott Godin
• RE: [reSIProcate] dum - sip stack many-to-one relation question
  • From: Scott Godin
• [reSIProcate] ServerInviteSession Bug on provisional
  • From: Micky Kaufmann
• RE: [reSIProcate] MessageWaitingContexts: a bit wrong encoding
  • From: Scott Godin
• [reSIProcate] registration refresh with dum
  • From: Gianluca Martiniello
• RE: [reSIProcate] dum - sip stack many-to-one relation question
  • From: Scott Godin
• RE: [reSIProcate] generate a 183 with SDP on the server side
  • From: Scott Godin
• Re: [reSIProcate] generate a 183 with SDP on the server side
  • From: frank zhao
• [reSIProcate] MessageWaitingContexts: a bit wrong encoding
  • From: Sasha Youkhananov
• RE: [reSIProcate] dum - sip stack many-to-one relation question
  • From: Micky Kaufmann
• [reSIProcate] dum - sip stack many-to-one relation question
  • From: Meir Elberg
• Re: [reSIProcate] Mime.cxx compile error under Linux using gcc(hash_mapproblem)
  • From: Jinke Jiang
• Re: [reSIProcate] TLS Client Connect Inefficiency
  • From: Noiile

2005-11-08

• RE: [reSIProcate] Memory leaks because ofstd::auto_ptr<>::release()misuse
  • From: Scott Godin
• RE: [reSIProcate] visual studio 2005 build issue & fix
  • From: Scott Godin
• [reSIProcate] visual studio 2005 build issue & fix
  • From: Justin Matthews
• RE: [reSIProcate] Memory leaks because ofstd::auto_ptr<>::release()misuse
  • From: Justin Matthews
• RE: [reSIProcate] NameAddr::parse() bug?
  • From: Scott Godin
• Re: [reSIProcate] NameAddr::parse() bug?
  • From: Robert Sparks
• RE: [reSIProcate] NameAddr::parse() bug?
  • From: Scott Godin
• RE: [reSIProcate] NameAddr::parse() bug?
  • From: Scott Lawrence
• RE: [reSIProcate] NameAddr::parse() bug?
  • From: Scott Godin
• Re: [reSIProcate] NameAddr::parse() bug?
  • From: Francesco Fondelli
• [reSIProcate] TLS Client Connect Inefficiency
  • From: Scott Godin
• Re: [reSIProcate] SipFrag parsing leads to heap corruption
  • From: Alan Hawrylyshen
• RE: [reSIProcate] Mime.cxx compile error under Linux using gcc(hash_mapproblem)
  • From: Scott Godin
• RE: [reSIProcate] New DUM Invite Session State Diagrams
  • From: Scott Godin
• RE: [reSIProcate] generate a 183 with SDP on the server side
  • From: Scott Godin
• Re: [reSIProcate] generate a 183 with SDP on the server side
  • From: frank zhao
• Re: [reSIProcate] generate a 183 with SDP on the server side
  • From: frank zhao
• [reSIProcate] generate a 183 with SDP on the server side
  • From: zhao hongbin
• [reSIProcate] SipFrag parsing leads to heap corruption
  • From: Sasha Youkhananov
• [reSIProcate] Mime.cxx compile error under Linux using gcc(hash_map problem)
  • From: Jinke Jiang
• [reSIProcate] duplicate AbstractFifo::getNext(int ms) definition in SVN HEAD
  • From: Jinke Jiang
• Re: [reSIProcate] New DUM Invite Session State Diagrams
  • From: Alan Hawrylyshen
• Re: [reSIProcate] New DUM Invite Session State Diagrams
  • From: Alan Hawrylyshen
• Re: [reSIProcate] New DUM Invite Session State Diagrams
  • From: Alan Hawrylyshen
• RE: [reSIProcate] NameAddr::parse() bug?
  • From: Scott Lawrence

2005-11-07

• Re: [reSIProcate] New DUM Invite Session State Diagrams
  • From: John Draper
• Re: [reSIProcate] (no subject)
  • From: John Draper
• RE: [reSIProcate] NameAddr::parse() bug?
  • From: Scott Godin
• [reSIProcate] IntegerParameter and IntegerCategory
  • From: Derek MacDonald
• [reSIProcate] Problem with Boston Bridge
  • From: Scott Godin
• Re: [reSIProcate] whether NOTIFY message must have the event header
  • From: Jason Fischl
• [reSIProcate] librutil.so: undefined reference to...
  • From: Gianluca Martiniello
• [reSIProcate] NameAddr::parse() bug?
  • From: Francesco Fondelli
• [reSIProcate] New DUM Invite Session State Diagrams
  • From: Scott Godin
• RE: [reSIProcate] error compiling SVN HEAD by VC++7.1
  • From: Scott Godin
• RE: [reSIProcate] whether NOTIFY message must have the event header
  • From: Bayart, Frederik
• [reSIProcate] whether NOTIFY message must have the event header
  • From: 贾军营
• [reSIProcate] error compiling SVN HEAD by VC++7.1
  • From: stensil
• [reSIProcate] Can't complie 5606 version
  • From: resiprocate
• Re: [reSIProcate] Open source UA based on resiprocate
  • From: Jason Fischl

2005-11-06

• [reSIProcate] Open source UA based on resiprocate
  • From: Livio Torrero

2005-11-05

• RE: [reSIProcate] 1.0 Release Candidate?
  • From: Scott Godin

2005-11-04

• [reSIProcate] 1.0 Release Candidate?
  • From: Jason Fischl
• [reSIProcate] Re: [sipX-dev] reciprocate externals issues when checking out sipX main
  • From: Scott Lawrence
• [reSIProcate] 200 Ok retransmission issue
  • From: Rajat Lala
• [reSIProcate]support outbound proxy in dum test program(basicRegister.cxx)
  • From: jiangjinke
• [reSIProcate] Enabled stdext::hash_map for VS.NET 2003 Builds
  • From: Scott Godin

2005-11-03

• [reSIProcate] 200/ACK retransmission Question
  • From: Scott Godin
• RE: [reSIProcate] using only TCP transport
  • From: Scott Godin
• [reSIProcate] RE: exception thrown in lock.cxx line 28
  • From: Scott Godin
• [reSIProcate] RE: OnOffer callback for 200 OK !
  • From: Scott Godin
• RE: [reSIProcate] resiprocate 0.9.0 - UAC problem
  • From: Scott Godin
• [reSIProcate] exception in sample basicMessage
  • From: 大笨熊
• [reSIProcate] On Tarball release 0.5.0
  • From: Asheesh Joshi
• [reSIProcate] resiprocate 0.9.0 - UAC problem
  • From: Clemens Fischer (VI/SEA)
• [reSIProcate] using only TCP transport
  • From: Amit Rastogi
• [reSIProcate] OnOffer callback for 200 OK !
  • From: Asheesh Joshi
• RE: [reSIProcate] How to handle retransmission of 200 OK for anINVITE ?
  • From: Scott Godin
• [reSIProcate] exception thrown in lock.cxx line 28
  • From: maodonghu
• RE: [reSIProcate] How to handle retransmission of 200 OK for anINVITE ?
  • From: Asheesh Joshi
• RE: [reSIProcate] How to handle retransmission of 200 OK for an INVITE ?
  • From: Asheesh Joshi
• RE: [reSIProcate] How to handle retransmission of 200 OK for anINVITE ?
  • From: Scott Godin
• RE: [reSIProcate] (no subject)
  • From: Scott Godin
• RE: [reSIProcate] How to handle retransmission of 200 OK for an INVITE ?
  • From: Scott Godin
• [reSIProcate] How to handle retransmission of 200 OK for an INVITE ?
  • From: Asheesh Joshi