This problem is probably similar to the one describe here: https://issues.asterisk.org/bug_view_advanced_page.php?bug_id=12312 It turns out that Callcentric is doing load balancing on its infrastructure and querying for a DNS resolution on the callcentric domain returns in most cases a different IP address. When the client wants to register, it sends a REGISTER to which Callcentric replies with a 407 challenge. The client must then send back a new REGISTER with a "Proxy-Authorization" section to that same IP address to which the first REGISTER was sent to. PJSIP is sending REGISTER to a new ip address each time. The registration only succeeds when the resolution persists long enough within the same registration session. A hack might be feasible where our application queries manually for an initial ip address that is then used for all subsequent operations. This approach might clearly suffers from the benefit of load balancing performed by the provider. Is that something that the PJSIP development team is aware of ? Do you consider this as a bug in the first place ? I haven't found a bug report about that yet. On Tue, 2009-07-14 at 09:31 -0400, Pierre-Luc Bacon wrote: > Some of our users are experiencing problems with Callcentric as a voip > provider. > > Trying to troubleshoot the problem, I noticed under wireshark that a > great amount of "407" are returned in response to our REGISTER. The > client might be able to connect on the first try, but sometimes, one > have to repeat the action quite a few times before succeeding. > > In those cases, pjsip returns: > "Maximum number of stale retries exceeded (PJSIP_EAUTHSTALECOUNT)" > in our pjsip_regc_cb. > > I tried to set the expire value to PJSIP_REGC_EXPIRATION_NOT_SPECIFIED > as recommended (expire not set) on their support page but this change > had no effect. > > How should we tackle this problem ? What might cause the PBX to return > 407 all the time, considering that the authentication information is > valid, and that it succeeds registering say 2/3 of the time. > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
