reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate-users] TOS is removed from function pointer "AfterSocketCreationFuncPtr"

Earlier in release 1.6, following prototype was used.

//c function pointer because of ares
extern "C" {
typedef void(*AfterSocketCreationFuncPtr)(Socket s, int transportType, const char* file, int line, int tos);
}

Please refer the attached file "socket.hxx" from release 1.6.

Also the TOS related changes has been removed from other files like "InternalTransport.cxx". You can refer the attached files.



On Tue, Nov 4, 2014 at 8:11 PM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:
It's not clear to me what you are referring to.  To my knowledge we have never had a TOS field in any of the API's.  Can you please paste in the exact code you are referring to?  Show us the old code compared to the new code to help us understand.

The signature for the AfterSocketCreationFuncPtr has always been:
//c function pointer because of ares
typedef void(*AfterSocketCreationFuncPtr)(Socket s, int transportType, const char* file, int line);


Thanks,
Scott

On Tue, Nov 4, 2014 at 4:41 AM, Alok Tiwari <alok.t@xxxxxxxxxxxxxxx> wrote:
In our product, there are multiple socket created with different TOS. Here, in AfterSocketCreationFuncPtr we can not map the socket with the interface and therefore we can set the appropriate TOS value. Earlier we use to provide tos info in addInterface function which propagates till AfterSocketCreationFuncPtr and we set the TOS using setsockopt.  Would you able to provide some other way in Sip Stack to meet my requirement.

Thanks,
Alok Tiwari

On Tue, Nov 4, 2014 at 8:15 AM, Alok Tiwari <alok.t@xxxxxxxxxxxxxxx> wrote:
But TOS value required in setsockopt ​comes via "int tos" parameter earlier. Now, it is not there. Do you mean to say that setsockopt should be called outside this function?

On Mon, Nov 3, 2014 at 9:01 PM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:
I'm pretty sure the AfterSocketCreationFuncPtr always just handed you socket handle and you can call setsockopt on it to set the QOS (at least for non-windows OS's - for windows is more complicated).

Scott

On Mon, Nov 3, 2014 at 4:48 AM, Alok Tiwari <alok.t@xxxxxxxxxxxxxxx> wrote:
Hi,

In previous resiprocate release 1.6, this function had a parameter "int tos" which is removed in latest release . Can somebody help me to understand why it was happen? Also let me know the new way to set the TOS provided by application.

​Thanks,
Alok Tiwari

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/




--



--

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/




--
Alok Tiwari | Consultant
GlobalLogic
P +91.120.406.2000 x 2477  M +91.991.034.7139 S alok.t@xxxxxxxxxxxxxxx
www.globallogic.com

http://www.globallogic.com/email_disclaimer.txt

Attachment: InternalTransport.cxx
Description: Binary data

Attachment: Socket.hxx
Description: Binary data