On 04.07.17 14:07, Marant, Jerome (External) wrote: you can also use that approach. You stated previously: "I would like to modify some SDP parameters of the ACK before it is sent, like IP addresses and ports, because for some reasons, the *receiver of the media will not be the one running pjsip*". With the pjsip_module though, you would have a broader control over the resulting buffer that is sent to the peer. But for most cases altering the SDP in *on_call_sdp_created* is fully sufficient.What about the on_call_sdp_created callback of the pjsua_callback? Cheers, Alain Documentation tells: Notify application when a call has just created a local SDP (for initial or subsequent SDP offer/answer). Application can implement this callback to modify the SDP, before it is being sent and/or negotiated with remote SDP, for example to apply per account/call basis codecs priority or to add custom/proprietary SDP attributes. From: Alain Totouom [mailto:alain.totouom@xxxxxx] Sent: Tuesday, July 04, 2017 12:22 PM To: pjsip list; Marant, Jerome (External) Subject: Re: SIP INVITE/ACK and SDP (2) Hi Jérôme, this can be achieved by using an appropriate pjsip_module with the right priority. Check the *sipecho* sample for illustration purpose. Cheers, Alain On 03.07.17 10:56, Marant, Jerome (External) wrote: Hi, Following my previous message, I made a mistake : It is precisely not about the ACK(180), but the OK(200). Best Regards, Jérôme. <html><head></head><body><font color="black" face="arial" size="2"> The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. </font> </body> </html> _______________________________________________ Visit our blog: http://blog.pjsip.org pjsip mailing list pjsip@xxxxxxxxxxxxxxx<mailto:pjsip@xxxxxxxxxxxxxxx> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org -- 1024D/A9F85A52 2000-01-18 Alain Totouom <totouom@xxxxxx><mailto:totouom@xxxxxx> PGP Fingerprint DA18 0DF2 FBD2 5F67 0656 452D E3A2 7531 A9F8 5A52 <html><head></head><body><font color="black" face="arial" size="2"> The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. </font> </body> </html> -- 1024D/A9F85A52 2000-01-18 Alain Totouom <totouom@xxxxxx> PGP Fingerprint DA18 0DF2 FBD2 5F67 0656 452D E3A2 7531 A9F8 5A52 |
_______________________________________________ Visit our blog: http://blog.pjsip.org pjsip mailing list pjsip@xxxxxxxxxxxxxxx http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org