[Osip] exosip2 comments

Klaus Darilion klaus.mailinglists at pernau.at
Tue Apr 12 13:54:00 CEST 2005


Hi Aymeric!

Aymeric Moizard wrote:
> On Mon, 11 Apr 2005, Klaus Darilion wrote:
>> 1. I tried a call transfer scenario with a Cisco 7960 and it does not 
>> work because Cisco does not accept REFER without Referred-By: header. 
>> Adding it manually in the application before sending the REFER, e.g.
>>    osip_message_set_header(refer, "Referred-By", "sip:klaus at enum.at");
>> works fine. Although the Referred-By header is not mandatory, RFC 3892 
>> suggest to use ("...client may refuse without referred-by header..."). 
>> Thus, I suggest to add the "Refered-By" header automatically by eXosip.
> 
> In order to keep a maximum of flexibility in the eXosip2 stack, I prefer
> to not add this header automatically even if it sounds like a good idea.
> 
> Adding in the application layer seems the correct way to do it.

ACK. Maybe you can add a comment to the documentation, so others do not 
have the same troubles.

>> 2. After the call was referred, the Cisco phone sends a NOTIFY which 
>> generates a 400 response. Although I couldn't find any error in the 
>> NOTIFY, osip/eXosip does not like it. Can you give me some hints how 
>> to debug osip/eXosip to find the problem?

Can you give me hints how to debug osip/exosip? Their are OSIP_TRACE 
definitions and I use
         TRACE_INITIALIZE (6, stdout);
in my application. But there is no logging to stdout.

> 
> I did not test the REFER method yet with eXosip2. I won't be surprised
> that some bugs exist within the stack.
> 
> However, it seems in your case that the NOTIFY is missing
> a mandatory header for NOTIFY:
> 
> Subscription-State: active;expires=(depends on Refer-To URI)
> 
> which in eXosip2 is rejected with a 400. A patch has to be made to
> allow this case!
> 
> I made a fix for this (allowing NOTIFY without Subscription-State.
> You can use the latest CVS for this with -DCISCO_BUG defined.
> 
> Let me know if you can test it successfully.

You are right. Using the new version and compiling exosip with 
-DCISCO_BUG works fine.

Some problems you are probably aware of:
- Under Windows, I use libosip2-2.2.0 and the project file "osip.sln". I 
had to add the osip_authentication_info.c/.h and 
osip_proxy_authentication_info.c/.h to the projectfile to make my 
application work. Nevertheless, it generates lots of warnings :-(

- The list of events and their ->textinfo in 
src/jevents.c#eXosip_event_init is incomplete.

Thanks for your help,
Klaus



More information about the Osip mailing list