[pjsip] Impossible to register when you receive message 500

Benny Prijono bennylp at pjsip.org
Mon May 19 05:31:19 EDT 2008


On Mon, May 19, 2008 at 10:22 AM, samuel.vinson <samuelv at laposte.net> wrote:
>
> Yep, incoming call works.
>

Okay, thanks for the info. In this case you can disable
allow_contact_rewrite since the server will send INVITE to the source
IP address of the REGISTER instead of the IP in the Contact.

Cheers
 Benny

> Samuel
>
>
>
>> Message du 19/05/08 11:13
>> De : "Benny Prijono"
>> A : "pjsip list"
>> Copie à :
>> Objet : Re: [pjsip] Impossible to register when you receive message 500
>>
>> On Sun, May 18, 2008 at 11:35 PM, Samuel Vinson wrote:
>> > Hi Benny,
>> >
>> > I found one solution to this problem. In fact the problem becomes when I
>> > see "IP address change detected, Updating registration" so I deactivate
>> > allow_contact_rewrite option in my account config. And now my app works
>> > like before.
>> >
>>
>> Yep, you can always disable allow_contact_rewrite. But now I'm not
>> sure if you could receive incoming calls.
>>
>> > I think it's a problem between pjsip and Cirpack server because with and
>> > without this option I can register to gizmo server. But I don't know
>> > which SIP server gizmo uses.
>> >
>>
>> Not sure either, but as far as I know it's fine with (Open)SER.
>>
>> Cheers
>> Benny
>>
>>
>> > Samuel
>> >
>> > Benny Prijono a écrit :
>> >> On Fri, May 16, 2008 at 8:52 PM, Samuel Vinson wrote:
>> >>> Benny Prijono a écrit :
>> >>>
>> >>>> On Fri, May 16, 2008 at 1:30 AM, Samuel Vinson wrote:
>> >>> >> [...]
>> >>>
>> >>> > Normally this scenario should work okay, the registrar should treat
>> >>> > this as normal multiple registrations (that is, the same AOR is
>> >>> > registered by more than one user agents), delete the binding of the
>> >>> > old call-id and add new binding for the new call-id. Unless of
>> >>> > course
>> >>> > if the registrar doesn't support multiple registrations.
>> >>>
>> >>> I think the registrar doesn't support multiple registration with the
>> >>> same account.
>> >>>
>> >>
>> >> Okay that explains it.
>> >>
>> >>> Why doesn't pjsip retry register after delay ?
>> >>
>> >> Because the existing method is the simplest from programming point of
>> >> view, and I thought all registrars should support multiple
>> >> registrations. Using timer delay is more complicated, and it may not
>> >> work in all cases. The most reliable way perhaps is to send the new
>> >> registration only after the unregistration transaction has completed.
>> >>
>> >> Actually I was thinking to use registration update, that is using the
>> >> same call-id we send another REGISTER request containing two Contact
>> >> headers: the old contact which is to be removed by adding expires=0
>> >> param, and a new contact. This is standard of course, but I'm not sure
>> >> it'll work with all registrars. Seems that the "wait for
>> >> unregistration to complete" approach is the safest way.
>> >>
>> >>> Should I retry in my application to re-register ?
>> >>>
>> >>
>> >> I don't think you can. Your callback will not even get called.
>> >>
>> >>> > What server is this?
>> >>>
>> >>> From SIP message incoming :
>> >>> Server: Cirpack/v4.41c (gw_sip)
>> >>>
>> >>> This is my sip provider
>> >>>
>> >>
>> >> Thanks for the info.
>> >>
>> >> Cheers
>> >> Benny
>> >>
>> >>
>> >>> >
>> >>> >> - Why when IP address change detected you need to create a new
>> >>> >> call-id,
>> >>> >> and you can't use same with new ip ?
>> >>> >>
>> >>> >
>> >>> > It's because currently our registration client session doesn't
>> >>> > support
>> >>> > updating binding. But I can add this as I'm currently modifying it
>> >>> > for
>> >>> > other purpose (see "re: [pjsip] Parsing expires from REGISTER reply"
>> >>> > thread).
>> >>> >
>> >>> > Cheers
>> >>> > Benny
>> >>> >
>> >>> >> Thanks
>> >>> >>
>> >>> >> Samuel
>> >>> >>




More information about the pjsip mailing list