Re: Using nist sip stack
"Venkata Ramana Kunapuli" <[email protected]> Wed, 3 Oct 2007 14:03:57 -0400
| Newsgroups | gmane.comp.voip.nist-sip |
|---|---|
| Message-ID | <[email protected]> |
--===============7362973981410151191== Content-Type: multipart/alternative; boundary="----=_Part_27146_22868730.1191434637383" ------=_Part_27146_22868730.1191434637383 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Sorry actually it is my mistake in using that API. Display name works good. I realized right after sending the post. My bad I did not update the post. However I had issue in setting the branch name in Via header. There is API called setBranch to set branch ID say in Invite but when I actually create transaction using getNewClientTransaction the sip stack seems to overwrite the branch ID. and it over writes with 39 character id (max possible) while I am looking for 32 character ID. so am little uncomfortable with stack , in the sense it does not allow me set branch nor it does not allow me set the size of branch ID. May be if there is option of setting branch size or user provided branch ID ( that will not overwritten) please let me know. Thanks Venkat On 10/3/07, Jeroen van Bemmel <[email protected]> wrote: > > Some of the TCK test cases contain similar code (for the displayname, > not custom via branch), and they seem to work (although not asserted) > > When you say "I don't see the display name being added", at what > checkpoint do you mean? on the wire? or in a println? at uac/uas? > > Regards, > Jeroen > > M. (Neo-Ranga) Ranganathan wrote: > > Looks pretty valid. Please open up an issue and attach a self > > contained test case. I'll look into it. > > > > Ranga > > > > On 9/26/07, Venkata Ramana Kunapuli <[email protected]> wrote: > >> Thanks Ranga for the info.. I had another issue I am trying to add > display > >> name in "From" and "To" headers. I tried the following but not > successful. I > >> mean "from" header being constructed, but I do not see display name > being > >> added anywhere > >> > >> Address fromAddress = addressFactory.createAddress > (sipURI); > >> fromAddress.setDisplayName("sipPhone"); > >> fromHeader = headerFactory.createFromHeader(fromAddress, > "1234" > >> /*tag*/); > >> > >> Is this not correct usage to set display name? > >> > >> Thanks > >> Venkat > >> > >> On 9/21/07, M. (Neo-Ranga) Ranganathan <[email protected]> wrote: > >>> There is no explicit support for multipart mime. You have to construct > >>> the body by yourself and add it. > >>> > >>> Regards, > >>> > >>> Ranga. > >>> > >>> On 9/21/07, Venkata Ramana Kunapuli <[email protected]> wrote: > >>>> Hi > >>>> > >>>> I am trying to explore the nist implementation of jain-sip. I am > trying > >> to > >>>> add multipart message body but could not find right methods to insert > >>>> multipart message body in a sip message (say INVITE). I appreciate > your > >>>> help. > >>>> > >>>> Thanks > >>>> Venkat > >>>> > >>>> example: > >>>> > >>>> Content-Type:multipart/mixed;bounadry=separator > >>>> --separator > >>>> Content-Type:application/sdp > >>>> ..... > >>>> --separator > >>>> Content-Type:application/x-My-App > >>>> Content-Dispostion:signal;handling=required > >>>> ..... > >>>> --separator > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> nist-sip mailing list > >>>> [email protected] > >>>> http://www-x.antd.nist.gov/mailman/listinfo/nist-sip > >>>> > >>>> > >>> > >>> -- > >>> M. Ranganathan > >>> "There are two ways to write error-free programs; only the third one > >>> works." -- Alan Perlis > >>> > >> http://www.animenewsnetwork.com/encyclopedia/anime.php?id=1052 > >> > > > > > > ------=_Part_27146_22868730.1191434637383 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline <div><br>Sorry actually it is my mistake in using that API. Display name works good. I realized right after sending the post. My bad I did not update the post.</div> <div> </div> <div>However I had issue in setting the branch name in Via header. There is API called setBranch to set branch ID say in Invite but when I actually create transaction using getNewClientTransaction the sip stack seems to overwrite the branch ID. and it over writes with 39 character id (max possible) while I am looking for 32 character ID. so am little uncomfortable with stack , in the sense it does not allow me set branch nor it does not allow me set the size of branch ID. </div> <div> </div> <div>May be if there is option of setting branch size or user provided branch ID ( that will not overwritten) please let me know. </div> <div> </div> <div>Thanks</div> <div>Venkat <br> </div> <div><span class="gmail_quote">On 10/3/07, <b class="gmail_sendername">Jeroen van Bemmel</b> <<a href="mailto:[email protected]">[email protected]</a>> wrote:</span> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Some of the TCK test cases contain similar code (for the displayname,<br>not custom via branch), and they seem to work (although not asserted) <br><br>When you say "I don't see the display name being added", at what<br>checkpoint do you mean? on the wire? or in a println? at uac/uas?<br><br>Regards,<br>Jeroen<br><br>M. (Neo-Ranga) Ranganathan wrote: <br>> Looks pretty valid. Please open up an issue and attach a self<br>> contained test case. I'll look into it.<br>><br>> Ranga<br>><br>> On 9/26/07, Venkata Ramana Kunapuli <<a href="mailto:[email protected]"> [email protected]</a>> wrote:<br>>> Thanks Ranga for the info.. I had another issue I am trying to add display<br>>> name in "From" and "To" headers. I tried the following but not successful. I <br>>> mean "from" header being constructed, but I do not see display name being<br>>> added anywhere<br>>><br>>> Address fromAddress = addressFactory.createAddress(sipURI);<br> >> fromAddress.setDisplayName("sipPhone");<br>>> fromHeader = headerFactory.createFromHeader(fromAddress, "1234"<br>>> /*tag*/);<br>>><br>>> Is this not correct usage to set display name? <br>>><br>>> Thanks<br>>> Venkat<br>>><br>>> On 9/21/07, M. (Neo-Ranga) Ranganathan <<a href="mailto:[email protected]">[email protected]</a>> wrote:<br>>>> There is no explicit support for multipart mime. You have to construct <br>>>> the body by yourself and add it.<br>>>><br>>>> Regards,<br>>>><br>>>> Ranga.<br>>>><br>>>> On 9/21/07, Venkata Ramana Kunapuli <<a href="mailto:[email protected]"> [email protected]</a>> wrote:<br>>>>> Hi<br>>>>><br>>>>> I am trying to explore the nist implementation of jain-sip. I am trying<br>>> to<br>>>>> add multipart message body but could not find right methods to insert <br>>>>> multipart message body in a sip message (say INVITE). I appreciate your<br>>>>> help.<br>>>>><br>>>>> Thanks<br>>>>> Venkat<br>>>>><br>>>>> example: <br>>>>><br>>>>> Content-Type:multipart/mixed;bounadry=separator<br>>>>> --separator<br>>>>> Content-Type:application/sdp<br>>>>> .....<br>>>>> --separator <br>>>>> Content-Type:application/x-My-App<br>>>>> Content-Dispostion:signal;handling=required<br>>>>> .....<br>>>>> --separator<br>>>>><br>>>>><br>>>>> <br>>>>> _______________________________________________<br>>>>> nist-sip mailing list<br>>>>> <a href="mailto:[email protected]">[email protected]</a><br>>>>> <a href="http://www-x.antd.nist.gov/mailman/listinfo/nist-sip"> http://www-x.antd.nist.gov/mailman/listinfo/nist-sip</a><br>>>>><br>>>>><br>>>><br>>>> --<br>>>> M. Ranganathan<br>>>> "There are two ways to write error-free programs; only the third one <br>>>> works." -- Alan Perlis<br>>>><br>>> <a href="http://www.animenewsnetwork.com/encyclopedia/anime.php?id=1052">http://www.animenewsnetwork.com/encyclopedia/anime.php?id=1052</a><br>>> <br>><br>><br><br></blockquote></div><br> ------=_Part_27146_22868730.1191434637383-- --===============7362973981410151191== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ nist-sip mailing list [email protected] http://www-x.antd.nist.gov/mailman/listinfo/nist-sip --===============7362973981410151191==--