Re: [osip-dev] Transition to v4 API

[Felix Lechner]

Hi Aymeric,

Thank you for your response.

On Debian unstable, the symbol 'eXosip_tls_verify_certificate' is present in the library, but I cannot find it in the API. Is that functionality is now handled by 'eXosuip_set_option(EXOSIP_OPT_SET_TLS_VERIFY_CERTIFICATE, ...)'?

Felix

On Fri, Jul 26, 2013 at 2:49 AM, Aymeric Moizard <address@hidden> wrote:

2013/7/26 Felix Lechner <address@hidden>

Hello,

Hi -again- Felix,

 

I recently ported Linphone to the new API but have a few questions:

 

Good!

 

1. What is the best way to determine the presence of 'eXosip_t' for 'autoconf'? Linphone ships with a 'exosip.m4' macro, but it needs to be updated. There is no pre-processor declaration for EXOSIP_VERSION, and no 'pkg-config' file (although there is one for 'libosip2'). Should the version be determined by calling eXosip_get_version()?

I'm not maintaining anything related to m4, pkg-config, etc... I think I have updated

some info when going to 4.0. However, nothing verified.

In order to detect version 4.0, you should check if the installed library

contains eXosip_malloc which is specific to 4.0:

/**
 * Allocate an eXosip context.
 *
 * @return  a new allocated eXosip_t instance.
 */
  struct eXosip_t *eXosip_malloc (void);

 

2. Does the new event EXOSIP_CALL_NOANSWER now also include the old EXOSIP_CALL_TIMEOUT?

 

According to me, EXOSIP_CALL_TIMEOUT is not fired for years by exosip.

You can safely remove that code and it won't hurt!

EXOSIP_CALL_NOANSWER is not new, and will fire (as before) when you don't

receive any "final answer" within 180 seconds from a SIP proxy.

3. What happened to the events EXOSIP_IN_SUBSCRIPTION_RELEASED, EXOSIP_SUBSCRIPTION_UPDATE and EXOSIP_SUBSCRIPTION_CLOSED?

 

They were deleted because they was NOT used. You can safely remove the code

that use them....

4. Does the option EXOSIP_OPT_DONT_SEND_101 still exist?

 

Once upon a time I was doing fancy signaling: I was young ;)

Now, I'm older and... I have customer... so I removed this fancy

option...

101 message are not always dropped in _eXosip_snd_message:

 

  if (sip->status_code == 101)

    return OSIP_SUCCESS;

Thank you

You're welcome!

Aymeric

 

Felix Lechner

_______________________________________________
osip-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/osip-dev

--
Antisip - http://www.antisip.com