Re: [reSIProcate] Problem with respect to Tag field
The Helper methods for creating requests are not intended to manage
the Dialog for you. You may want to take a look at the dum library.
On 9/23/05, sumit <p.sumit@xxxxxxxxx> wrote:
> Hi All
>
> There is a very strange problem that I am facing now.
> When I am framing the messages say invite and bye in that case what I am
> finding is that the tag is not set properly on the TO side.In the Invite
> message where the tag is not to be present I am finding the Tag is
> present with the tag field (TO) in the message set to SIP tag : udp >
> (On analysing with ethereal capture)
> In a similar way when I am framing the bye message too I am coming
> across the problem where I am finding
> SIP tag : udp > in the TO field of the SIP message.
> The fields which I am setting and then constructing are given below for
> a better understanding
>
> char *proto ="udp";
> NameAddr target
> target.uri().scheme() = "sip";
> target.uri().user() = "sumit";
> target.uri().host()="192.168.115.33";
> target.uri().port() = 5060;
> target.uri().param(p_transport) = proto;
>
> NameAddr contact;
> contact.uri().host() = "192.168.115.41";
> contact.uri().port() = 5060;
> contact.uri().user() = "sumit";
>
> auto_ptr<SipMessage> message(Helper::makeRequest( target, contact, BYE));
> mStack.send(*message);
>
> If anyone has come across a similar problem can you let me know what is
> to be done as observing the same problem whenever I am constructing a
> message using the Helper class.Is there any other method the messages
> can be constructed.
>
> An early response will be really beneficial.
>
> Regards
> Sumit
>
>
>
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>