Oh, I've found € 0.02 :) > Benny, it would be useful to be able to comment a config file with > something > like -comment= Lines are commented out if starting with a '#'. This works fine, so there is no need for an extra keyword for me. Regards

Hello Benny, Benny Prijono a écrit : > Hi Olivier, > > Olivier Beytrison wrote: >> I still experience some issues : >> - When calling pjsua_acc_del(accountID), the on_reg_state() callback >> isn't called. Looking at the logs, pjsua delete the account before >> receiving the 200 OK from the server, this preventing it from calling >> the on_reg_state(pjsua_acc_id acc_id) callback, because the account >> have already been deleted > > I think that's the expected behavior. From application's view, the > deletion happens immediately. Once the account is deleted, it is > gone as far as application is concerned, thus it will not hear any > more callbacks called on behalf of the account. Well, i get your point. But still, I would love to be informed that my REGISTER with expire=0 has been taken into account by the SIP Server. That's why I'd like to be informed of this "200 OK" from the server ;) >> - During a call, some times It doesn't send any sound. After putting on >> hold the call, and retrieving it, the sounds works. And i get a lot >> of BAD Ptr for the RTP session > > Not sure about this. Maybe you can get more information by following > the troubleshooting procedure from the sound problem Wiki > (http://www.pjsip.org/trac/wiki). Will have a look today. i'll keep you informed > >> - when calling pjsua_call_hangup(), it takes most of the time 8 to 15 >> seconds for the call to hang up. Same goes when the other UA initiate >> the hang up > > This sounds like problem with Contact header calculation. Maybe the > IP address that is selected in Contact header is not the one that's > reachable from remote UA. > You're right. After doing some packets capture, the problem appears that my second UA (X-Lite) is on the same host than the sip server. The sip server saved the ip adress "127.0.0.1" as the contact for this UA. Off course, when message are sent, the contact IP is different as the one expected by pjsua, so it ignores them. >> About the IMS-Specific things for SIP, it is mainly Headers. (like the >> P-Access-Info header which describe which kind of "connection" the >> signaling is sent on, like 3gpp-umts-cell, wireless-network, ect ect). I >> can give you a small overview of the 3gpp-specific headers if you're >> interested. > > An IMS overview will be great! Not that I'm planning to implement > them (just yet), but any free info is always good. :) > I'll compile some of the documents we made here and i'll post a small pdf about it. thx for the answers :) Regards, Olivier B. > cheers, > -benny > >> That's it for now, work is going on for the GUI, and hopefully we should >> have a beta version in about 1 week. >> >> Regards, >> >> Olivier B. >> > > -- Olivier Beytrison Telecommunication Engineer Mobile: +41 (0)78 619 73 53 Mail: olivier@heliosnet.org GPG: 0x4FB83528 http://pgp.mit.edu/

Olivier Beytrison wrote: > Hello Benny, >> I think that's the expected behavior. From application's view, the >> deletion happens immediately. Once the account is deleted, it is >> gone as far as application is concerned, thus it will not hear any >> more callbacks called on behalf of the account. > > Well, i get your point. But still, I would love to be informed that my > REGISTER with expire=0 has been taken into account by the SIP Server. > That's why I'd like to be informed of this "200 OK" from the server ;) In that case, what about calling pjsua_acc_set_registration(FALSE) and then pjsua_acc_del() after the account is unregistered? IMO it's much easier to just call pjsua_acc_del() and just let pjsip unregister the account. Even after the account has been deleted, pjsip would still respond to 401/407 challenge for the unregistration, so you can trust it to complete successfully. If not, well it's a bug then. :) >> An IMS overview will be great! Not that I'm planning to implement >> them (just yet), but any free info is always good. :) >> > > I'll compile some of the documents we made here and i'll post a small > pdf about it. Cool! Looking forward to read it! FYI we're also in the process of developing support for AKAv1-MD5 authentication for IMS/3GPP (http://www.pjsip.org/trac/ticket/396), so any further info about what's missing in pjsip to support IMS will be great. cheers, -benny > thx for the answers :) > > Regards, > Olivier B. > >> cheers, >> -benny >> >>> That's it for now, work is going on for the GUI, and hopefully we should >>> have a beta version in about 1 week. >>> >>> Regards, >>> >>> Olivier B. >>> >> > -- Benny Prijono http://www.pjsip.org