[reSIProcate] custom transport that does not use stack
Hi
I'm trying to implement our own transport that inherits from the
Transport class. I have implemented the transport and I add it to
the SipStack object using addTransport().
Since we have our own threads that wait for messages on the socket, I
assume that shareStackProcessAndSelect() should return false.
However, I am not clear on how messages generated by the SIP stack are
handed through to the Transport itself to be sent out by our
transport.
A breakpoint on Transport::send() is never being hit, but I do see
this in the resiprocate log. It appears that the message ends up in
the TransactionController::mStateMacFifo, but I am not doing something
to be able to grab messages from that queue into my transport.
DEBUG | 20070131-095046.742 | | RESIP:DUM | 1228 | DialogSet.cxx:52 |
************* Created DialogSet(UAC) --
NDQzYTMyMzdmY2QxOTUwZDY2MzliYTc3OGJlMjViZTE.-897f673c
*************
DEBUG | 20070131-095046.742 | | RESIP:DUM | 1228 |
DialogUsageManager.cxx:800 | SEND: REGISTER sip:iptel.org SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-d87543-5a3de22bed13ae1b-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:nealsid;rinstance=0b050256c417201b>
To: "nealsid"<sip:nealsid@xxxxxxxxx>
From: "nealsid"<sip:nealsid@xxxxxxxxx>;tag=897f673c
Call-ID: NDQzYTMyMzdmY2QxOTUwZDY2MzliYTc3OGJlMjViZTE.
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, MESSAGE, SUBSCRIBE, NOTIFY, REGISTER
Supported: timer
Content-Length: 0
DEBUG | 20070131-095046.758 | | RESIP:DUM | 1228 | DialogId.cxx:50 |
DialogId::DialogId:
NDQzYTMyMzdmY2QxOTUwZDY2MzliYTc3OGJlMjViZTE.-897f673c-
DEBUG | 20070131-095046.758 | | RESIP:DUM | 1228 |
DialogUsageManager.cxx:912 | Using outbound proxy:
sip:nealsid@xxxxxxxxx;lr -> SipReq: REGISTER iptel.org tid=5a3
de22bed13ae1b cseq=REGISTER contact=nealsid / 1 from(tu)
Thanks!
Neal