Two different proxies for one INVITE transaction when DNS SRV is used

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I also noticed that PJSIP sends REGISTER and INTIVE to all proxies
from the SRV record. Shouldn't it select just one of them? (Haven't
tried the patched version yet.)

Alexei

On Fri, Jul 10, 2009 at 8:59 PM, Benny Prijono<bennylp at teluu.com> wrote:
> This is a valid issue indeed. I created
> http://trac.pjsip.org/repos/ticket/917 for this.
>
> Thanks
> ?-benny
>
> On Tue, Jun 30, 2009 at 9:43 PM, Alexei Kuznetsov <eofster at gmail.com> wrote:
>>
>> Hi,
>>
>> I've noticed that pjsua-lib 1.0.2 uses different proxies within one
>> INVITE transaction when DNS SRV is used. As far as I understood RFC
>> 3263, the client must do procedures to discover and select proxy only
>> once per transaction.
>>
>> Fox example, I'm using callcentric.com as a SIP provider. It has the
>> following records in DNS.
>>
>> ;; ANSWER SECTION:
>> _sip._udp.callcentric.com. 3600 IN ? ? ?SRV ? ? 15 7 5080
>> alpha1.callcentric.com.
>> _sip._udp.callcentric.com. 3600 IN ? ? ?SRV ? ? 15 7 5080
>> alpha3.callcentric.com.
>>
>> I make a call to sip:12345678901 at callcentric.com, pjsua-lib sends
>> INVITE to alpha1.callcentric.com. Then, without call ever being
>> confirmed, I hang-up and pjsua-lib sends CANCEL to
>> alpha3.callcentric.com. It keeps resending CANCEL to
>> alpha3.callcentric.com without any reply from it because it probably
>> doesn't know anything about my call. The calling ends with the
>> timeout. Sometimes it chooses the same proxy, in which case everything
>> is fine.
>>
>> Did I understand everything right and pjsip shouldn't behave that way
>> or is that a problem with the provider?
>>
>> Alexei



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux