<div dir="ltr"><div> ngcp-sercmd proxy ul.dump</div><div>error: 500 - Internal error creating aor struct</div><div><br></div><div>Any ideas on that?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 21, 2014 at 5:10 PM, Andreas Granig <span dir="ltr"><<a href="mailto:agranig@sipwise.com" target="_blank">agranig@sipwise.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Just to add my 2 cents:<br>
<br>
The proxy (kamailio) uses in-memory caching for registrations and writes<br>
them back to DB. The panel displays the registrations from the DB.<br>
<br>
Now if you delete something from the DB, it's not reflected in the<br>
proxy, because it still will be in the cache. So what we're doing is to<br>
delete a registration from the cache (by telling the proxy to purge it),<br>
and the proxy will propagate it down to the DB.<br>
<br>
The same happens if the proxy detects that a registration has expired.<br>
It will delete it from the cache and propagate the deletion down to the DB.<br>
<br>
Now here is where it's getting interesting: if the registration is no<br>
longer in the cache (for whatever reason) and it still is in the DB (for<br>
whatever else reason), you see it in the panel and can click on the<br>
delete button, but as the deletion request is sent to the proxy, it will<br>
just do nothing because it doesn't have it in the cache, so it will<br>
still persist in the DB.<br>
<br>
This scenario should never happen (famous last words), so to<br>
troubleshoot it, you'd need to dump the registrations from the cache<br>
using "ngcp-sercmd proxy ul.dump" and check the count (see<br>
"Stats"->"Records") and compare it to the db by doing "mysql kamailio -e<br>
"select id, username, domain, expires from location".<br>
<br>
Take into account that the cache count can/will potentially be lower<br>
than the db count because the proxy batches deletion in a separate<br>
process, which is executed every 60 sec. So to fetch the "real" expired<br>
registrations, do this: "mysql kamailio -e "select id, username, domain,<br>
expires from location where expires < date_sub(now(), interval 90 second)"<br>
<br>
So this will give you a representation of your current state. Note that<br>
if a registration is not in the cache but only in the DB, it's not a<br>
real operational issue, because the proxy will not know about it.<br>
<br>
It still doesn't answer the question how this can even happen, so you<br>
need to provide a full trace ("tcpdump -i any -s 0 -w /tmp/reg.pcap port<br>
5060") of a complete cycle (fresh registration and subsequent<br>
registrations, which will then cause the issue you described), along<br>
with the full kamailio-proxy.log, so we can check for errors etc. Also<br>
provide the output of "ngcp-sercmd proxy ul.dump" and "mysql kamailio -e<br>
"select id, username, domain, expires from location" along with the<br>
timestamps when you executed those commands.<br>
<br>
Andreas<br>
<span class=""><br>
On 11/21/2014 03:41 PM, Raúl Alexis Betancor Santana wrote:<br>
><br>
> Helo Aziz ... let's talk about ...<br>
><br>
> 1- Doesn't matter ... if you have more than one register for the same<br>
> user, the only thing that happens it's that on an outbound request to<br>
> that subscriber, SPCE will launch 2 branches ... one will fail and the<br>
> other one will sucess. No big deal at all.<br>
> 2- That should not happens ... as expired registration should be<br>
> auto-erased. Have you installed the system from 0 ? .. or did you<br>
> upgrade from older version?<br>
> 3- That sounds as an upgrades SPCE version that didn't complete the upgrade.<br>
><br>
><br>
</span><span class="">> ------------------------------------------------------------------------<br>
> *De: *"Aziz Palmer" <Aziz.Palmer@AirFIBER.com><br>
> *Para: *"Raúl Alexis Betancor Santana" <<a href="mailto:rabs@dimension-virtual.com">rabs@dimension-virtual.com</a>>,<br>
> <a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br>
</span>> *Enviados: *Viernes, 21 de Noviembre 2014 14:31:25<br>
<span class="">> *Asunto: *RE: sip registration stuck 3.5.16<br>
><br>
</span><span class="">> Thank you Raul for your input and suggestions. Not to get into a long<br>
> discussion but I at first didn't think it was a big deal until the<br>
> following accours<br>
> 1. the network environment at subscriber changes (change of IP) -<br>
> asterisk registers and now you have 2 active registrations in the db.<br>
> 2. Customers logging into the user portal and see the expired time stamp<br>
> 3. Deleting the registration in the UI will not completely delete it in<br>
> the db but add a second and third and so on registration.<br>
><br>
> all my test was with public IPs i've even tested it while both asterisk<br>
> and sipwise was connected to the same switch both in a virtual and hard<br>
> environment<br>
><br>
> Thank you again Raul but before placing into production it's absolutely<br>
> imperative that the basic functionality work properly - register and<br>
> register.<br>
><br>
> Warmest Regards,<br>
> Aziz<br>
><br>
><br>
</span><span class="">> ------------------------------------------------------------------------<br>
> *From:* Spce-user [<a href="mailto:spce-user-bounces@lists.sipwise.com">spce-user-bounces@lists.sipwise.com</a>] on behalf of<br>
> Raúl Alexis Betancor Santana [<a href="mailto:rabs@dimension-virtual.com">rabs@dimension-virtual.com</a>]<br>
</span>> *Sent:* Friday, November 21, 2014 6:06 AM<br>
<span class="">> *To:* <a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br>
> *Subject:* Re: [Spce-user] sip registration stuck 3.5.16<br>
><br>
</span><span class="">> Just to add ... that we are using SPCE since it's first versions ... and<br>
> don't have that issue. With lot of asterisk customers with versions from<br>
> Asterisk 1.2 to Asterisk 12 .<br>
><br>
> As it seems that the register doesn't get auto-expired (I don't<br>
> undestand why it hurts you that they are on the location table ... but<br>
> that another thing), if you are experiencing 'registration lost' with<br>
> Asterisk and SPCE ... 99.9% of the times it a fault on Asterisk or in a<br>
> middle router that 'modify' the SIP request.<br>
><br>
> Best and faster thing you could do to track the issue ... it to capture<br>
> the traffic JUST on the Asterisk ... and on the SPCE and compare them,<br>
> if you see any difference ... then you probably have a sip-alg-activated<br>
> device on the middle of the path.<br>
><br>
> If you don't have access to the Asterisk boxes ... just install one<br>
> yourself for testing, it's easy and fast. ... Faster than trying that<br>
> someneone give you the solution on a comunity list<br>
><br>
</span>> ------------------------------------------------------------------------<br>
> *De: *"Daniel Grotti" <<a href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a>><br>
> *Para: *"Aziz Palmer" <Aziz.Palmer@AirFIBER.com>, "Theo"<br>
> <<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a>><br>
> *CC: *<a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br>
> *Enviados: *Viernes, 21 de Noviembre 2014 14:08:31<br>
> *Asunto: *Re: [Spce-user] sip registration stuck 3.5.16<br>
<span class="">><br>
> Hi,<br>
> why are you so sure ?<br>
> Kamailio version is the same, so if there is an issue it's also in PRO.<br>
> I opened the internal ticket # 0010303.<br>
><br>
> We will update you soon.<br>
><br>
> Daniel<br>
><br>
><br>
><br>
> On 11/21/2014 02:54 PM, Aziz Palmer wrote:<br>
><br>
> Thank you Daniel!<br>
><br>
> quick question - i'm sure the customers that are using the pro<br>
> version aren't having this issue. Why is it happening on the CE<br>
> version? (I've spent so much time on it and i'm trying to more<br>
> understand it)<br>
><br>
> Thank you,<br>
> Aziz<br>
</span>> ------------------------------------------------------------------------<br>
> *From:* Daniel Grotti [<a href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a>]<br>
> *Sent:* Friday, November 21, 2014 1:17 AM<br>
> *To:* Aziz Palmer; Theo<br>
> *Cc:* <a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br>
<span class="">> *Subject:* Re: [Spce-user] sip registration stuck 3.5.16<br>
><br>
</span><span class="">> Aziz,<br>
> I was able to have a look at the issue, and I opened an internal<br>
> ticket about that.<br>
> We will have a look at this and let you know.<br>
><br>
> Daniel<br>
><br>
><br>
><br>
> On 11/19/2014 12:41 AM, Aziz Palmer wrote:<br>
><br>
> Theo,<br>
> can you send what you put in your sip trunk settings when you<br>
> connect to sipwise? (this part seems pretty straight forward but<br>
> would like to try someone else's settings.)<br>
><br>
> Thank you<br>
</span>> ------------------------------------------------------------------------<br>
> *From:* Theo [<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a>]<br>
> *Sent:* Thursday, November 13, 2014 5:40 AM<br>
> *To:* Aziz Palmer<br>
> *Cc:* Andreas Granig; <a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br>
<span class="">> *Subject:* Re: [Spce-user] sip registration stuck 3.5.16<br>
><br>
</span><span class="">> Hi<br>
><br>
> The problem is on the asterisk side so they are the ones to fix<br>
> it (assuming that is indeed your problem). The "fix" on the spce<br>
> is merely a work around to not ban the user and accept the<br>
> registration.<br>
><br>
> On Thu, Nov 13, 2014 at 3:38 PM, Aziz Palmer<br>
</span><span class="">> <<a href="mailto:Aziz.Palmer@airfiber.com">Aziz.Palmer@airfiber.com</a> <mailto:<a href="mailto:Aziz.Palmer@airfiber.com">Aziz.Palmer@airfiber.com</a>>> wrote:<br>
><br>
> Thank you Theo!<br>
><br>
> but what i don't understand if this is the case why wasn't<br>
> fixed ?<br>
><br>
> what should i be doing instead when having users register to<br>
> avoid this issue?<br>
><br>
> Is this happening to you also? if so what did you do to fix<br>
> it? (follow the steps below?)<br>
><br>
> Thank you!<br>
><br>
><br>
</span>> ------------------------------------------------------------------------<br>
> *From:* Theo [<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a><br>
> <mailto:<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a>>]<br>
> *Sent:* Thursday, November 13, 2014 5:30 AM<br>
> *To:* Aziz Palmer<br>
> *Cc:* Andreas Granig; <a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br>
> <mailto:<a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a>><br>
<span class="">><br>
> *Subject:* Re: [Spce-user] sip registration stuck 3.5.16<br>
><br>
</span><span class="">> Sorry I accidentally replied just to you rather than to the<br>
> list.:<br>
><br>
> Hi<br>
><br>
> This looks like the stale nonce issue which is an asterisk<br>
> problem. The workaround has been posted a few times - search<br>
> for stale nonce and I am sure you'll find it easily<br>
><br>
> Good luck<br>
><br>
><br>
><br>
><br>
><br>
><br>
</span>> to Aziz<br>
<span class="">><br>
> It would be this one:<br>
><br>
> <a href="http://lists.sipwise.com/pipermail/spce-user/2014-January/005712.html" target="_blank">http://lists.sipwise.com/pipermail/spce-user/2014-January/005712.html</a><br>
><br>
> On Thu, Nov 13, 2014 at 3:00 PM, Aziz Palmer<br>
</span>> <<a href="mailto:Aziz.Palmer@airfiber.com">Aziz.Palmer@airfiber.com</a> <mailto:<a href="mailto:Aziz.Palmer@airfiber.com">Aziz.Palmer@airfiber.com</a>>><br>
<span class="">> wrote:<br>
><br>
> kamailio.location<br>
> what command do I need to execute to provide this<br>
> information?<br>
><br>
><br>
> kamailio-proxy.log<br>
><br>
> Nov 13 06:49:36 tx-portal-2 proxy[22474]: NOTICE:<br>
> <script>: Authentication failed, stale nonce -<br>
> R=sip:sipwise.xyz..com<br>
> ID=<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a><br>
</span>> <mailto:<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a>><br>
<span class="">> Nov 13 06:49:36 tx-portal-2 proxy[22473]: NOTICE:<br>
> <script>: New request on proxy - M=REGISTER<br>
> R=sip:sipwise.xyz..com<br>
> F=sip:master.sample.edge@sipwise.xyz..com<br>
> T=sip:master.sample.edge@sipwise.xyz..com<br>
</span>> IP=<a href="http://104.34.42.10:5060" target="_blank">104.34.42.10:5060</a> <<a href="http://104.34.42.10:5060" target="_blank">http://104.34.42.10:5060</a>><br>
> (<a href="http://127.0.0.1:5060" target="_blank">127.0.0.1:5060</a> <<a href="http://127.0.0.1:5060" target="_blank">http://127.0.0.1:5060</a>>)<br>
> ID=<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a><br>
> <mailto:<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a>><br>
<span class="">> Nov 13 06:49:36 tx-portal-2 proxy[22473]: WARNING:<br>
> app_lua [app_lua_sr.c:100]: lua_sr_log(): lost database<br>
> connection. Reconnecting<br>
> Nov 13 06:49:36 tx-portal-2 proxy[22473]: NOTICE:<br>
> <script>: Contacts successfully updated, expires in 120s<br>
> - R=sip:sipwise.xyz..com<br>
> ID=<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a><br>
</span>> <mailto:<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a>><br>
<span class="">> Nov 13 06:51:21 tx-portal-2 proxy[22480]: NOTICE:<br>
> <script>: New request on proxy - M=REGISTER<br>
> R=sip:sipwise.xyz..com<br>
> F=sip:master.sample.edge@sipwise.xyz..com<br>
> T=sip:master.sample.edge@sipwise.xyz..com<br>
</span>> IP=<a href="http://104.34.42.10:5060" target="_blank">104.34.42.10:5060</a> <<a href="http://104.34.42.10:5060" target="_blank">http://104.34.42.10:5060</a>><br>
> (<a href="http://127.0.0.1:5060" target="_blank">127.0.0.1:5060</a> <<a href="http://127.0.0.1:5060" target="_blank">http://127.0.0.1:5060</a>>)<br>
> ID=<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a><br>
> <mailto:<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a>><br>
<span class="">> Nov 13 06:51:21 tx-portal-2 proxy[22480]: WARNING:<br>
> app_lua [app_lua_sr.c:100]: lua_sr_log(): lost database<br>
> connection. Reconnecting<br>
> Nov 13 06:51:21 tx-portal-2 proxy[22480]: NOTICE:<br>
> <script>: Contacts successfully updated, expires in 120s<br>
> - R=sip:sipwise.xyz..com<br>
> ID=<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a><br>
</span>> <mailto:<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a>><br>
<span class="">> Nov 13 06:53:06 tx-portal-2 proxy[22475]: NOTICE:<br>
> <script>: New request on proxy - M=REGISTER<br>
> R=sip:sipwise.xyz..com<br>
> F=sip:master.sample.edge@sipwise.xyz..com<br>
> T=sip:master.sample.edge@sipwise.xyz..com<br>
</span>> IP=<a href="http://104.34.42.10:5060" target="_blank">104.34.42.10:5060</a> <<a href="http://104.34.42.10:5060" target="_blank">http://104.34.42.10:5060</a>><br>
> (<a href="http://127.0.0.1:5060" target="_blank">127.0.0.1:5060</a> <<a href="http://127.0.0.1:5060" target="_blank">http://127.0.0.1:5060</a>>)<br>
> ID=<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a><br>
> <mailto:<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a>><br>
<span class="">> Nov 13 06:53:06 tx-portal-2 proxy[22475]: WARNING:<br>
> app_lua [app_lua_sr.c:100]: lua_sr_log(): lost database<br>
> connection. Reconnecting<br>
> Nov 13 06:53:06 tx-portal-2 proxy[22475]: NOTICE:<br>
> <script>: Contacts successfully updated, expires in 120s<br>
> - R=sip:sipwise.xyz..com<br>
> ID=<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a><br>
</span>> <mailto:<a href="mailto:7233034d51f47c1a7ca56eb2353030ae@104.34.42.10">7233034d51f47c1a7ca56eb2353030ae@104.34.42.10</a>><br>
<span class="">><br>
><br>
><br>
><br>
> what does this mean "WARNING: app_lua<br>
> [app_lua_sr.c:100]: lua_sr_log(): lost database<br>
> connection. Reconnecting"?<br>
><br>
><br>
><br>
> ________________________________________<br>
> From: Spce-user [<a href="mailto:spce-user-bounces@lists.sipwise.com">spce-user-bounces@lists.sipwise.com</a><br>
</span>> <mailto:<a href="mailto:spce-user-bounces@lists.sipwise.com">spce-user-bounces@lists.sipwise.com</a>>] on behalf<br>
> of Andreas Granig [<a href="mailto:agranig@sipwise.com">agranig@sipwise.com</a><br>
> <mailto:<a href="mailto:agranig@sipwise.com">agranig@sipwise.com</a>>]<br>
<span class="">> Sent: Thursday, November 13, 2014 1:26 AM<br>
> To: <a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br>
</span>> <mailto:<a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a>><br>
<div><div class="h5">> Subject: Re: [Spce-user] sip registration stuck 3.5.16<br>
><br>
> Hi,<br>
><br>
> It's most likely not a bug of the system, rather than a<br>
> problem with<br>
> your clients registering on said system. I risk to say<br>
> that because the<br>
> registrar is based on Kamailio, which is serving dozens<br>
> of millions of<br>
> SIP devices out there, so it would be a huge surprise<br>
> for it not to work<br>
> correctly.<br>
><br>
> The only way to find out what the REAL issue is for you<br>
> to send an<br>
> example entry in the kamailio.location table of the DB,<br>
> along with a<br>
> full network trace of this client trying to register on<br>
> the system, and<br>
> also the kamailio-proxy.log file.<br>
><br>
> Andreas<br>
><br>
> On 11/13/2014 06:47 AM, Aziz Palmer wrote:<br>
> > thats not the issue - the problem is when you<br>
> RE-register a sip trunk it<br>
> > will stop updating sipwise. in order to fix that you<br>
> need to manually go<br>
> > into the subscriber and delete the registration. it<br>
> will not delete but<br>
> > instead a new registration will appear.<br>
> ><br>
> ><br>
> > SPCE - are you aware of this bug (its a serous issue -<br>
> since it gives<br>
> > the admins a lot of manual work/tech support calls) I<br>
> would like to put<br>
> > this this into partial production but can't - please help?<br>
> ><br>
> > Thanks!<br>
> ><br>
> ------------------------------------------------------------------------<br>
> > *From:* Raúl Alexis Betancor Santana<br>
> [<a href="mailto:rabs@dimension-virtual.com">rabs@dimension-virtual.com</a><br>
</div></div>> <mailto:<a href="mailto:rabs@dimension-virtual.com">rabs@dimension-virtual.com</a>>]<br>
<span class="">> > *Sent:* Wednesday, November 12, 2014 1:54 PM<br>
> > *To:* Aziz Palmer<br>
> > *Subject:* Re: sip registration stuck 3.5.16<br>
> ><br>
> > 3600 secs ... 1 h ... it's default time on the config.xml<br>
> > kamailio.proxy.default_expire option ... you could<br>
> change it ... or set<br>
> > it on the web interface at domain-level or user-level<br>
> if you prefer, and<br>
> > as far as you don't touched the .cfg's ... they expire.<br>
> ><br>
> ><br>
> ------------------------------------------------------------------------<br>
> > *De: *"Aziz Palmer" <Aziz.Palmer@AirFIBER.com><br>
> > *Para: *"Raúl Alexis Betancor Santana"<br>
> <<a href="mailto:rabs@dimension-virtual.com">rabs@dimension-virtual.com</a><br>
</span>> <mailto:<a href="mailto:rabs@dimension-virtual.com">rabs@dimension-virtual.com</a>>>,<br>
> > <a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br>
> <mailto:<a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a>><br>
<span class="">> > *Enviados: *Miércoles, 12 de Noviembre 2014 21:17:53<br>
> > *Asunto: *RE: sip registration stuck 3.5.16<br>
> ><br>
> > they are not auto-expiring (I wish they were)<br>
> ><br>
> > if they are - taking a extremely long time<br>
> ><br>
> ------------------------------------------------------------------------<br>
> > *From:* Spce-user [<a href="mailto:spce-user-bounces@lists.sipwise.com">spce-user-bounces@lists.sipwise.com</a><br>
</span>> <mailto:<a href="mailto:spce-user-bounces@lists.sipwise.com">spce-user-bounces@lists.sipwise.com</a>>] on behalf of<br>
<span class="">> > Raúl Alexis Betancor Santana<br>
> [<a href="mailto:rabs@dimension-virtual.com">rabs@dimension-virtual.com</a><br>
</span>> <mailto:<a href="mailto:rabs@dimension-virtual.com">rabs@dimension-virtual.com</a>>]<br>
<span class="">> > *Sent:* Wednesday, November 12, 2014 1:04 PM<br>
> > *To:* <a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br>
</span>> <mailto:<a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a>><br>
<span class="">> > *Subject:* Re: [Spce-user] sip registration stuck 3.5.16<br>
> ><br>
> ><br>
> > Why did you whant to remove the old register? ...<br>
> location entries<br>
> > auto-expire, so you don't have to worry about them.<br>
> ><br>
> ><br>
> ------------------------------------------------------------------------<br>
> > *De: *"Aziz Palmer" <Aziz.Palmer@AirFIBER.com><br>
> > *Para: *<a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br>
</span>> <mailto:<a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a>><br>
<span class="">> > *Enviados: *Miércoles, 12 de Noviembre 2014 20:47:13<br>
> > *Asunto: *[Spce-user] sip registration stuck 3.5.16<br>
> ><br>
> > I hate to ask again but this is turning into a real<br>
> issue - the<br>
> > "registered devices" are not automatically being<br>
> removed and when trying<br>
> > to manually delete them, nothing happens.<br>
> ><br>
> > Can i set a timer on how long these orphan registered<br>
> devices stay part<br>
> > of sipwise?<br>
> ><br>
> > how can i delete these devices without having to issue<br>
> the below command<br>
> > - I would like to delete specific devices and not all<br>
> of them<br>
> ><br>
> > mysql kamailio -e "delete from location"<br>
> > /etc/init.d/kamailio-proxy restart<br>
> ><br>
> ><br>
> > Thanks again,<br>
> > Aziz<br>
> ><br>
> ><br>
> ------------------------------------------------------------------------<br>
> > *From:* Spce-user [<a href="mailto:spce-user-bounces@lists.sipwise.com">spce-user-bounces@lists.sipwise.com</a><br>
</span>> <mailto:<a href="mailto:spce-user-bounces@lists.sipwise.com">spce-user-bounces@lists.sipwise.com</a>>] on behalf of<br>
<span class="">> > Aziz Palmer [Aziz.Palmer@AirFIBER.com]<br>
> > *Sent:* Tuesday, November 11, 2014 12:15 PM<br>
> > *To:* <a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br>
</span>> <mailto:<a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a>><br>
<div><div class="h5">> > *Subject:* [Spce-user] sip registration stuck 5.3.16<br>
> ><br>
> > Hello SPCE Team,<br>
> > here is what appears to be a bug<br>
> ><br>
> > I enter sip registration settings into asterisk,<br>
> registers fine with<br>
> > sipwise. Then I make a change within the sip trunk<br>
> settings of asterisk<br>
> > and apply the new settings. Then previous sip<br>
> registration gets stuck;<br>
> > meaning within sipwise 2 registrations appear (old &<br>
> new). When i try to<br>
> > delete the old one, it stays stuck. The only way i<br>
> discovered to be able<br>
> > to remove the old registration is by issuing this<br>
> command, then i can<br>
> > delete the registration.<br>
> ><br>
> > /etc/init.d/kamailio-proxy restart<br>
> ><br>
> > what additional information can i provide to have your<br>
> team troubleshoot<br>
> > this issue?<br>
> ><br>
> > Thank you,<br>
> > Anees<br>
> ><br>
> > _______________________________________________<br>
> > Spce-user mailing list<br>
> > <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
</div></div>> <mailto:<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>><br>
<span class="">> > <a href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Spce-user mailing list<br>
> > <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
</span>> <mailto:<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>><br>
<span class="">> > <a href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
> ><br>
> _______________________________________________<br>
> Spce-user mailing list<br>
> <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
</span>> <mailto:<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>><br>
<span class="">> <a href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
> _______________________________________________<br>
> Spce-user mailing list<br>
> <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
</span>> <mailto:<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>><br>
<div class="HOEnZb"><div class="h5">> <a href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Spce-user mailing list<br>
> <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
> <a href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Spce-user mailing list<br>
> <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
> <a href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Spce-user mailing list<br>
> <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
> <a href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
><br>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
</div></div></blockquote></div><br></div>