Hi Team,
I am using PJSIP as a client and initiates INVITE request towards the Server.
I generate lot of outgoing requests (INVITE) towards the server, but I see the source transport used in the TCP connection remains same until the 33 sec(TRANSPORT_IDLE_TIME expires).
My requirement is each INVITE request should go on a different source port for TCP connection. Could you please suggest how can I achieve this ?
Unfortunately I am not getting any responses for my earlier posts. Hope I am posting my questions on to a right mailing list ?
Regards
Naveen.S
NOTE: This e-mail (including any attachments) is for the sole use of the intended recipient(s) and may contain information that is confidential and/or protected by legal privilege. Any unauthorized review, use, copy, disclosure or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please notify Mitel immediately and destroy all copies of this e-mail. Mitel does not accept any liability for breach of security, error or virus that may result from the transmission of this message.
Hi Team,
I am using PJSIP as a client and initiates INVITE request towards the Server.
I generate lot of outgoing requests (INVITE) towards the server, but I see the source transport used in the TCP connection remains same until the 33 sec(TRANSPORT_IDLE_TIME expires).
My requirement is each INVITE request should go on a different source port for TCP connection. Could you please suggest how can I achieve this ?
Unfortunately I am not getting any responses for my earlier posts. Hope I am posting my questions on to a right mailing list ?
Regards
Naveen.S
________________________________
NOTE: This e-mail (including any attachments) is for the sole use of the intended recipient(s) and may contain information that is confidential and/or protected by legal privilege. Any unauthorized review, use, copy, disclosure or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please notify Mitel immediately and destroy all copies of this e-mail. Mitel does not accept any liability for breach of security, error or virus that may result from the transmission of this message.