Re: [reSIProcate] add transport with ip address
It seemed the appropriate way to react when being warned (with a 499,
whatever that means) about steven...
For you actual problem - the message you paste below is is emitted
into the logs before the message gets sent
to the transport selector. Along that path, based on the actual
transport that gets used (based on following 3263's
rules on figuring out where to send the message), the rest of that
Via will get populated correctly.
The most likely thing causing you to get this error is that you
haven't given your stack any transports (look at the addTransport
method).
RjS
On Feb 5, 2007, at 10:16 AM, maodonghu wrote:
Hi, Robert Sparks
what you say?
Oh NO!
Steven!
RjS
On Feb 5, 2007, at 4:20 AM, maodonghu wrote:
resip
I wrote like:
resip::Data IpIntf(SIPBindIP);
mDum.addTransport(resip::UDP, ListenPort, V4, IpIntf);
if the SIPBindIP is empty then register ok, but if I set SIPBindIP
to "192.168.101.28"(my local ip), then register failure:
SIP/2.0 503 No matching transport found
Via: SIP/2.0/ ;branch=z9hG4bK-d8754z-49416417b6096007-1---
d8754z-;rport
To: "maodonghu"<sip:114@xxxxxxxxxxxxxx>;tag=b703282c
From: "maodonghu"<sip:114@xxxxxxxxxxxxxx>;tag=c1586a1c
Call-ID: MGI3ZWFjZTllMGZkMjcyYmJhMWJlMmVlMmYyNzdlZmM.
CSeq: 1 REGISTER
Warning: 499 steven ""
Content-Length: 0
seems Via: lack of something, I am using revision 6897
maodonghu
hhmmdd@xxxxxxx
2007-02-05
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
maodonghu
hhmmdd@xxxxxxx
2007-02-06