< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [repro-users] [lumicall-users] Call not received after registered for prolonged period


Although repro is currently not my primary SIP server, I have taken the time to test the SIP traffic relating to this problem.  As expected, it is a strange one, "430 Flow failed", and it does not occur with my other server.

SIP/2.0 430 Flow failed
    Via: SIP/2.0/TLS 10.21.111.64:40020;rport=22008;branch=z9hG4bK72578;received=188.29.164.197
    To: <sip:+447984977574@xxxxxxxxxxxxx;transport=tls>;tag=cfa7be54
    From: <sip:+447479185410@xxxxxxxxxxxxx>;tag=z9hG4bK69175780
    Call-ID: 279774228877@10.21.111.64
    CSeq: 2 INVITE
    Server: repro 1.9.10
    Warning: 399 server1.sipdomain.com "Flow no longer exists"
    Content-Length: 0


On 29 July 2015 at 19:40, Nabeel <nabeelshikder@xxxxxxxxx> wrote:
In both cases I used the same client Lumicall, but the server was different.  I have not compared SIP traffic because I'm not familiar this process, but please feel free to test this yourself and post the results.

On 29 July 2015 at 12:07, Nikolay Shopik <shopik@xxxxxxxxxx> wrote:
Did you try to capture traffic, to see actual difference, where exactly
it fails?

We had something similar, and in all cases it was client issue, and with
RFC5626 support enabled everything works just fine.


On 29/07/15 10:00, Nabeel wrote:
> I have tested this by using an OpenSIPS server instead of repro server with
> Lumicall.  The registration issue does not occur on OpenSIPS at all; calls
> go through fine after a significant period of idle registration on both
> phones.  In my opinion, this is a serious bug which makes repro unusable.
>
> On 18 July 2015 at 18:42, Nabeel <nabeelshikder@xxxxxxxxx> wrote:
>
>> I am unsure if the issue is related to repro or Lumicall, but I feel it is
>> repro because the issue resolves with a repro restart.
>>
>> I checked the web interface and it shows normal registration of the users
>> even when the calls don't work.
>>
>> As for b) and c), I am not experienced enough to do these tests
>> effectively.
>>
>> This problem is just as critical as the other issue because users need to
>> be able to receive calls after being away from the phone for a few
>> minutes.  Restarting the server every few minutes can't be a good thing.
>>
>>
>>
>> On 18 July 2015 at 18:00, Daniel Pocock <daniel@xxxxxxxxxx> wrote:
>>
>>>
>>>
>>> On 04/06/15 18:22, Nabeel wrote:
>>>> This is a problem I noticed in all versions of Lumicall but had been
>>>> ignoring it.   Calls are only received when the recipient has recently
>>>> been registered to the server.   After a prolonged period of registered,
>>>> even while connected to the server, the recipient does not receive the
>>>> call (phone does not ring).  Manually registering the recipient phone
>>>> again allows the phone to receive call again.
>>>>
>>>
>>> Do you feel this is a server issue or an issue with Lumicall?
>>>
>>> Here are some things you can check:
>>>
>>> a) look at the registration details in the repro web interface
>>>
>>> b) use lsof or netstat to try and identify the TCP socket with the
>>> connection from the phone you are trying to call.  Is there more than
>>> one TCP socket open to that phone's IP address?
>>>
>>> c) look in the log from the phone, use 'adb logcat' - does the phone
>>> receive the INVITE message at all?  Is it sending keepalive on the TLS
>>> connection?
>>>
>>> _______________________________________________
>>> lumicall-users mailing list
>>> lumicall-users@xxxxxxxxxxxxxxxxxx
>>> http://lists.lumicall.org/mailman/listinfo/lumicall-users
>>>
>>
>>
>
>
>
> _______________________________________________
> repro-users mailing list
> repro-users@xxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/repro-users
>
_______________________________________________
repro-users mailing list
repro-users@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/repro-users