[reSIProcate] [reSIProcate-users] Help - Facing problem to send sip message towards proxy

[Scott Godin]

On Wed, Jul 12, 2017 at 9:30 AM, LavanyaKumar <lavanyakumar.s at sonetel.com>
wrote:

> Hi Scott,
>
>
>
> Hope you are doing good.
>
>
>
> Thanks for your previous suggestion. I’m facing another issue while
> enhancing my application.
>
>
>
> I have tried to integrate StackThread class in my application by referring
> stack/test/testStack hxx and cxx files with some minor configuration
> changes in transport ports. I have taken two SipStack pointers each for
> receiving, sending and assigned 2271 as receiving port and 2272 as sending
> port.
>

[Scott] You really only need one SipStack for any SIP based application.
It can both send and receive messages.  The testStack program creates
multiple stacks for testing only.


> When i make a call, I'm receiving the message to application and able to
> process successfully. But when i'm trying to send new request from
> application, i'm getting this below error
>
>
>
> ERR | 20170712-134943.117 |  | RESIP | 140053664692192 |
> DataParameter.cxx:91 | Accessing defaulted DataParameter: 'tag'
>
> B2BServer: DataParameter.cxx:93: virtual std::ostream&
> resip::DataParameter::encode(std::ostream&) const: Assertion
> `!mValue.empty()' failed.
>
>
>
> When i debugged this i got to know this error is for headerEnum 11, which
> is of Contact header. Though it is of NameAddr type, tag is not mandatory
> parameter for Contact right?
>
>
>
> I'm providing complete output in the attached file ‘Stack_Error2.txt’ .
> Can you suggest some clue to resolve my issue if i'm doing anything wrong.
>

[Scott]  It is too hard to troubleshoot this without seeing your code.


> Can we use same SipStack pointer with only one transport to send and
> receive sip messages which are out of transaction?
>

[Scott]  You only need 1 SipStack and at least one transport.  You cannot
pass the same transport to 2 SipStacks.

Also I have few queries in StackThread class. As per your previous comment,
> process() should be in loop, i couldn't find explicit while or for loop in
> the file.
>
> Does these statements runs in loop?
>
>
>
> receiver->process(fdset);
>
> sender->process(fdset);
>
>
>
> Could you explain how its working?
>

[Scott]  Sorry I forgot testStack got reasonably complicated recently.
 testSipStackInvite might be an easier example to read.
Some information here:
https://www.resiprocate.org/Faq#How_does_the_buildFdSet.2C_select.2C_process_loop_work.3F
and
https://www.resiprocate.org/Event/Threading_Model
and
https://www.resiprocate.org/Mahoney_threading_info


>
>
> Thanks & Regards,
>
> LavanyaKumar S
>
> +91 9603323366 <+91%2096033%2023366>
>
>
>
> *From:* slgodin at gmail.com [mailto:slgodin at gmail.com <slgodin at gmail.com>] *On
> Behalf Of *Scott Godin
> *Sent:* Thursday, June 29, 2017 08:27 PM
> *To:* LavanyaKumar <lavanyakumar.s at sonetel.com>
> *Cc:* resiprocate-users at resiprocate.org; resiprocate-devel at resiprocate.org
> *Subject:* Re: [reSIProcate-users] Help - Facing problem to send sip
> message towards proxy
>
>
>
> You need to process in a loop.  Check out stack/test/testStack and other
> programs in the test directory.   You can use StackThread class to help.
>
>
>
> There is also info on the wiki for this:  http://www.resiprocate.org/
> DUM_Threading
>
>
>
> Just ignore the DUM parts of the wiki page.
>
>
>
> Good luck,
>
> Scott
>
>
>
>
>
> On Wed, Jun 28, 2017 at 3:57 AM, LavanyaKumar <lavanyakumar.s at sonetel.com>
> wrote:
>
> Hi,
>
>
>
> I'm new to resiprocate. I'm trying to send an INVITE request from my linux
> machine. I'm able to generate a SIP message. But unable to forward to my
> proxy with the details filled in Route header. My requirement is to use
> resip but not dum as our application will handle session.
>
>
>
> Here i'm attaching my code and output. Not sure whether i missed something.
>
>
>
> Could someone please help probably with some sample references or examples.
>
>
>
> We are using resiprocate-1.9.10.
>
>
>
> Thanks & Regards,
>
> LavanyaKumar S
>
>
>
>
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users at resiprocate.org
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20170712/bd20c246/attachment.htm>