[Spce-user] sip registration stuck 3.5.16

Thu Nov 13 09:08:06 EST 2014

I also saw this on 4PSA VoipNOW -- Asterisk 11/12 issue AFAIK.

Jeremy D. Ward, CWNE
(954) 661-4965
On Nov 13, 2014 9:02 AM, "Theo" <axessofficetheo at gmail.com> wrote:

> Hi
>
> Assuming the stale nonce issue is the problem, I gave the answer to the
> fix already earlier:
> http://lists.sipwise.com/pipermail/spce-user/2014-January/005712.html
>
> On Thu, Nov 13, 2014 at 3:51 PM, Martin Stix <ms at pluteus.at> wrote:
>
>>  Hi!
>>
>>
>>
>> Also had this issue with older 3CX Version, it was not an issue of spce.
>>
>>
>>
>> regards
>>
>>
>>
>>
>>
>> mit freundlichen Grüßen
>> best regards
>>
>> *Martin Stix*
>>
>> CEO
>> pluteus communication solutions
>> ms at pluteus.at
>>
>> Dampfsägestraße 17
>> 3300 Amstetten
>> Austria
>> tel.: +43 7472 28165 20
>> fax.: +43 7472 28165 22
>>
>>
>>
>> *Von:* Aziz Palmer [mailto:Aziz.Palmer at AirFIBER.com]
>> *Gesendet:* Donnerstag, 13. November 2014 14:39
>> *An:* Theo
>> *Cc:* spce-user at lists.sipwise.com
>> *Betreff:* Re: [Spce-user] sip registration stuck 3.5.16
>>
>>
>>
>> Thank you Theo!
>>
>>
>>
>> but what i don't understand if this is the case why wasn't fixed ?
>>
>>
>>
>> what should i be doing instead when having users register to avoid this
>> issue?
>>
>>
>>
>> Is this happening to you also? if so what did you do to fix it? (follow
>> the steps below?)
>>
>>
>>
>> Thank you!
>>
>>
>>
>>
>>    ------------------------------
>>
>> *From:* Theo [axessofficetheo at gmail.com]
>> *Sent:* Thursday, November 13, 2014 5:30 AM
>> *To:* Aziz Palmer
>> *Cc:* Andreas Granig; spce-user at lists.sipwise.com
>> *Subject:* Re: [Spce-user] sip registration stuck 3.5.16
>>
>> Sorry I accidentally replied just to you rather than to the list.:
>>
>>
>>
>> Hi
>>
>>
>>
>> This looks like the stale nonce issue which is an asterisk problem. The
>> workaround has been posted a few times - search for stale nonce and I am
>> sure you'll find it easily
>>
>>
>>
>> Good luck
>>
>> [image: https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif]
>>
>>
>>
>> [image: https://mail.google.com/mail/u/0/images/cleardot.gif]
>>
>> [image: https://mail.google.com/mail/u/0/images/cleardot.gif]
>>
>> [image: https://mail.google.com/mail/u/0/images/cleardot.gif]
>>
>> to Aziz
>>
>> [image: https://mail.google.com/mail/u/0/images/cleardot.gif]
>>
>> It would be this one:
>>
>>
>>
>> http://lists.sipwise.com/pipermail/spce-user/2014-January/005712.html
>>
>>
>>
>> On Thu, Nov 13, 2014 at 3:00 PM, Aziz Palmer <Aziz.Palmer at airfiber.com>
>> wrote:
>>
>> kamailio.location
>> what command do I need to execute to provide this information?
>>
>>
>> kamailio-proxy.log
>>
>> Nov 13 06:49:36 tx-portal-2 proxy[22474]: NOTICE: <script>:
>> Authentication failed, stale nonce - R=sip:sipwise.xyz..com ID=
>> 7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>> Nov 13 06:49:36 tx-portal-2 proxy[22473]: NOTICE: <script>: New request
>> on proxy - M=REGISTER R=sip:sipwise.xyz..com
>> F=sip:master.sample.edge at sipwise.xyz..com
>> T=sip:master.sample.edge at sipwise.xyz..com IP=104.34.42.10:5060 (
>> 127.0.0.1:5060) ID=7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>> Nov 13 06:49:36 tx-portal-2 proxy[22473]: WARNING: app_lua
>> [app_lua_sr.c:100]: lua_sr_log(): lost database connection. Reconnecting
>> Nov 13 06:49:36 tx-portal-2 proxy[22473]: NOTICE: <script>: Contacts
>> successfully updated, expires in 120s - R=sip:sipwise.xyz..com ID=
>> 7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>> Nov 13 06:51:21 tx-portal-2 proxy[22480]: NOTICE: <script>: New request
>> on proxy - M=REGISTER R=sip:sipwise.xyz..com
>> F=sip:master.sample.edge at sipwise.xyz..com
>> T=sip:master.sample.edge at sipwise.xyz..com IP=104.34.42.10:5060 (
>> 127.0.0.1:5060) ID=7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>> Nov 13 06:51:21 tx-portal-2 proxy[22480]: WARNING: app_lua
>> [app_lua_sr.c:100]: lua_sr_log(): lost database connection. Reconnecting
>> Nov 13 06:51:21 tx-portal-2 proxy[22480]: NOTICE: <script>: Contacts
>> successfully updated, expires in 120s - R=sip:sipwise.xyz..com ID=
>> 7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>> Nov 13 06:53:06 tx-portal-2 proxy[22475]: NOTICE: <script>: New request
>> on proxy - M=REGISTER R=sip:sipwise.xyz..com
>> F=sip:master.sample.edge at sipwise.xyz..com
>> T=sip:master.sample.edge at sipwise.xyz..com IP=104.34.42.10:5060 (
>> 127.0.0.1:5060) ID=7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>> Nov 13 06:53:06 tx-portal-2 proxy[22475]: WARNING: app_lua
>> [app_lua_sr.c:100]: lua_sr_log(): lost database connection. Reconnecting
>> Nov 13 06:53:06 tx-portal-2 proxy[22475]: NOTICE: <script>: Contacts
>> successfully updated, expires in 120s - R=sip:sipwise.xyz..com ID=
>> 7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>>
>>
>>
>>
>> what does this mean "WARNING: app_lua [app_lua_sr.c:100]: lua_sr_log():
>> lost database connection. Reconnecting"?
>>
>>
>>
>> ________________________________________
>> From: Spce-user [spce-user-bounces at lists.sipwise.com] on behalf of
>> Andreas Granig [agranig at sipwise.com]
>> Sent: Thursday, November 13, 2014 1:26 AM
>> To: spce-user at lists.sipwise.com
>> Subject: Re: [Spce-user] sip registration stuck 3.5.16
>>
>>
>> Hi,
>>
>> It's most likely not a bug of the system, rather than a problem with
>> your clients registering on said system. I risk to say that because the
>> registrar is based on Kamailio, which is serving dozens of millions of
>> SIP devices out there, so it would be a huge surprise for it not to work
>> correctly.
>>
>> The only way to find out what the REAL issue is for you to send an
>> example entry in the kamailio.location table of the DB, along with a
>> full network trace of this client trying to register on the system, and
>> also the kamailio-proxy.log file.
>>
>> Andreas
>>
>> On 11/13/2014 06:47 AM, Aziz Palmer wrote:
>> > thats not the issue - the problem is when you RE-register a sip trunk it
>> > will stop updating sipwise. in order to fix that you need to manually go
>> > into the subscriber and delete the registration. it will not delete but
>> > instead a new registration will appear.
>> >
>> >
>> > SPCE - are you aware of this bug (its a serous issue - since it gives
>> > the admins a lot of manual work/tech support calls) I would like to put
>> > this this into partial production but can't - please help?
>> >
>> > Thanks!
>> > ------------------------------------------------------------------------
>> > *From:* Raúl Alexis Betancor Santana [rabs at dimension-virtual.com]
>> > *Sent:* Wednesday, November 12, 2014 1:54 PM
>> > *To:* Aziz Palmer
>> > *Subject:* Re: sip registration stuck 3.5.16
>> >
>> > 3600 secs ... 1 h ... it's default time on the config.xml
>> >  kamailio.proxy.default_expire option ... you could change it ... or set
>> > it on the web interface at domain-level or user-level if you prefer, and
>> > as far as you don't touched the .cfg's ... they expire.
>> >
>> > ------------------------------------------------------------------------
>> > *De: *"Aziz Palmer" <Aziz.Palmer at AirFIBER.com>
>> > *Para: *"Raúl Alexis Betancor Santana" <rabs at dimension-virtual.com>,
>> > spce-user at lists.sipwise.com
>> > *Enviados: *Miércoles, 12 de Noviembre 2014 21:17:53
>> > *Asunto: *RE: sip registration stuck 3.5.16
>> >
>> > they are not auto-expiring (I wish they were)
>> >
>> > if they are - taking a extremely long time
>> > ------------------------------------------------------------------------
>> > *From:* Spce-user [spce-user-bounces at lists.sipwise.com] on behalf of
>> > Raúl Alexis Betancor Santana [rabs at dimension-virtual.com]
>> > *Sent:* Wednesday, November 12, 2014 1:04 PM
>> > *To:* spce-user at lists.sipwise.com
>> > *Subject:* Re: [Spce-user] sip registration stuck 3.5.16
>> >
>> >
>> > Why did you whant to remove the old register? ... location entries
>> > auto-expire, so you don't have to worry about them.
>> >
>> > ------------------------------------------------------------------------
>> > *De: *"Aziz Palmer" <Aziz.Palmer at AirFIBER.com>
>> > *Para: *spce-user at lists.sipwise.com
>> > *Enviados: *Miércoles, 12 de Noviembre 2014 20:47:13
>> > *Asunto: *[Spce-user] sip registration stuck 3.5.16
>> >
>> > I hate to ask again but this is turning into a real issue - the
>> > "registered devices" are not automatically being removed and when trying
>> > to manually delete them, nothing happens.
>> >
>> > Can i set a timer on how long these orphan registered devices stay part
>> > of sipwise?
>> >
>> > how can i delete these devices without having to issue the below command
>> > - I would like to delete specific devices and not all of them
>> >
>> > mysql kamailio -e "delete from location"
>> > /etc/init.d/kamailio-proxy restart
>> >
>> >
>> > Thanks again,
>> > Aziz
>> >
>> > ------------------------------------------------------------------------
>> > *From:* Spce-user [spce-user-bounces at lists.sipwise.com] on behalf of
>> > Aziz Palmer [Aziz.Palmer at AirFIBER.com]
>> > *Sent:* Tuesday, November 11, 2014 12:15 PM
>> > *To:* spce-user at lists.sipwise.com
>> > *Subject:* [Spce-user] sip registration stuck 5.3.16
>> >
>> > Hello SPCE Team,
>> > here is what appears to be a bug
>> >
>> > I enter sip registration settings into asterisk, registers fine with
>> > sipwise. Then I make a change within the sip trunk settings of asterisk
>> > and apply the new settings. Then previous sip registration gets stuck;
>> > meaning within sipwise 2 registrations appear (old & new). When i try to
>> > delete the old one, it stays stuck. The only way i discovered to be able
>> > to remove the old registration is by issuing this command, then i can
>> > delete the registration.
>> >
>> > /etc/init.d/kamailio-proxy restart
>> >
>> > what additional information can i provide to have your team troubleshoot
>> > this issue?
>> >
>> > Thank you,
>> > Anees
>> >
>> > _______________________________________________
>> > Spce-user mailing list
>> > Spce-user at lists.sipwise.com
>> > https://lists.sipwise.com/listinfo/spce-user
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > Spce-user mailing list
>> > Spce-user at lists.sipwise.com
>> > https://lists.sipwise.com/listinfo/spce-user
>> >
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>>
>>
>>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20141113/9c01d032/attachment-0001.html>