[reSIProcate] Contact missing in 180 response...

John Draper lists at webcrunchers.com
Wed Dec 21 12:54:18 CST 2005


frank zhao wrote:

>hi,
> 1.The client's Dialog is created after the client received a "180
>message" from the Proxy. So I think it is correct for the client that
>it failed when calling findDialog method after receiving "180 Ring".
>  
>
I'll check and see if my message has a "Contact" field just after I get
the 180 Ring.   So in my 180 Ring callback,  is that a good place to add
the contact?   Or do I have to do it before?

>2.For the "100 trying " reponse, Contact is not necessary. But for
>"180 Ring" message, I think the Contact header is mandatory. So you
>should check your proxy.
>  
>
But my "Initial Invite" message HAS the Contact properly filled out
long before I sent it.   Are you telling me the remote server somehow 
removes
it from the time I send the initial request and get back the 180?

When is best time to re-insert it?  when I get back the 180 request?
Could I do it in my 180 request handler?   I dont think I can do it
there, because according to the logs,  I get called "After" it
tries to call "onNonDialogCreatingProvisional".  So I don't think
I can put it there.

Could I out it in when I get back a "100 trying" and re-insert it
then?

You see,  WHEN to do things is always confusing.  Although I'm sure
it's hidden in the RFC among all those other "fancy" words,  I just
haven't found it yet.

>>
>>Also,  my "gdb" output displays this:
>>
>>*warning: can't find class named `resip::SipMessage', as given by C++ RTTI
>>warning: can't find class named `resip::SipMessage', as given by C++ RTTI
>>warning: can't find class named `resip::SipMessage', as given by C++ RTTI
>>warning: can't find class named `resip::SipMessage', as given by C++ RTTI
>>
>>What does this mean?  I have that class,  why would it say it can't find it?
>>I don't get this all the time,  only sometimes...
>>
Nobody has yet addressed this issue above...  does anyone have any clue 
why I
ocassionally get this?    It appears as just a warning (gdb - I think),  
but knowing
what's going on may lead me to a solution.

John



More information about the resiprocate-devel mailing list