From ms at pluteus.at  Fri Aug  1 03:39:18 2014
From: ms at pluteus.at (Martin Stix)
Date: Fri, 1 Aug 2014 07:39:18 +0000
Subject: [Spce-user] Right way to move existing CE install to a fresh
 new install
In-Reply-To: <53DA241C.2050602@sipwise.com>
References: <60b3724110ea4e4b8bd646b7387789ed@post.familie.local>
 <53DA1930.70207@sipwise.com>
 <0885a4afd51343ae9e837a27b64f54be@post.familie.local>
 <53DA241C.2050602@sipwise.com>
Message-ID: <7f88d426a39e4f03b44323e2c36279c8@post.familie.local>

Hi!

Thanks, renaming the host did the trick.

Works fine now.


mit freundlichen Gr??en
best regards
Martin Stix
CEO
pluteus communication solutions
ms at pluteus.at
www.pluteus.at
Dampfs?gestra?e 17
3300 Amstetten
Austria
tel.: +43 7472 28165 20
fax.: +43 7472 28165 22

-----Urspr?ngliche Nachricht-----
Von: Alex Lutay [mailto:alutay at sipwise.com] 
Gesendet: Donnerstag, 31. Juli 2014 13:10
An: spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Right way to move existing CE install to a fresh new install

Hi,

0070 is very old statement and you should have it already.
Probably you have installed the server using new hostname, while the information about the host and executed statements are stored in MySQL (please check column "node" for tables "ngcp.cfg_schema" and "ngcp.db_schema").

I would suggest you to use the same hostname or update the tables ngcp.cfg_schema and ngcp.db_schema with new/proper value and repeat ngcp-update-{db|cfg}-schema.

On 31/07/14 12:53, Martin Stix wrote:
> Yes I forgot, it states:
> Applying revision script 
> /usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: 
> ERROR 1050 (42S01) at line 2: Table 'acc_backup' already exists

--
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user


From liglesia at por-aire.es  Fri Aug  1 07:50:50 2014
From: liglesia at por-aire.es (Leopoldo Iglesia)
Date: Fri, 01 Aug 2014 13:50:50 +0200
Subject: [Spce-user] Call hangs at about 15 seconds
Message-ID: <53DB7F1A.9030900@por-aire.es>

If i call, from a suscriber to a foreign number,  via peering, or to 
other suscriber it hangs at about 15 secs.

I send a wireshark capture and proxy log.


Aug  1 13:13:37 sipwise proxy[4400]: NOTICE: <script>: Authentication 
failed, no credentials - R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: New request - 
M=INVITE R=sip:606105877 at 154.58.3.135 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=154.58.3.158:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-Provided CLI 
'x1009' taken from From-User as fallback, should be from 'rpid_user' - 
R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-provided CLI 
'x1009' rejected, using network-provided CLI '34984099519' - 
R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
'34984099519 at 154.58.3.135' as initiating user-provided CLI - 
R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
'34984099519 at 154.58.3.135' as initiating network-provided CLI - 
R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting called 
party '606105877' to '34606105877' - R=sip:606105877 at 154.58.3.135 
ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Callee is not 
local - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Call to SIP 
Peering - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Load gws matching 
calling part 'sip:34984099519 at 154.58.3.135' and called user 
'34606105877' and called part 'sip:34606105877 at 154.58.3.135' - 
R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc 
source-leg for uuid 'c2731ab4-e7f5-4440-a821-d95c5d94eeac': 
'c2731ab4-e7f5-4440-a821-d95c5d94eeac|x1009|154.58.3.135|34984099519|||2|||0|call|154.58.3.158|1406891617.480275' 
- R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc 
destination-leg for uuid '0': 
'0|||0|606105877|0|34606105877|212.231.4.206|34606105877|154.58.3.135' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: ERROR: rtpengine 
[rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
Failed to parse SDP
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting first 
user-provided CLI '34984099519' to '984099519' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting first 
network-provided CLI '34984099519' to '984099519' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for 
npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for 
npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting From to 
'984099519 <sip:984099519 at 154.58.3.135>' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for 
npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting PAI to 
'<sip:984099519 at 154.58.3.135>' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
P-Called-Party-ID '<sip:34606105877 at 212.231.4.206>' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
'sip:212.231.4.206:5060' taken from R-URI as next hop after lb for PSTN 
call - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Appending P-D-URI 
'sip:127.0.0.1:5060;received='sip:212.231.4.206:5060;lr;transport=udp'' 
- R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Forcing request 
via B2BUA 'sip:127.0.0.1:5080' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Request leaving 
server, D-URI='sip:127.0.0.1:5080' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4404]: NOTICE: <script>: NAT-Reply - S=100 
- Connecting M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) 
ID=16888 at 154.58.3.158
Aug  1 13:13:38 sipwise proxy[4408]: NOTICE: <script>: NAT-Reply - S=183 
- Session Progress M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) 
ID=16888 at 154.58.3.158
Aug  1 13:13:38 sipwise proxy[4408]: ERROR: rtpengine 
[rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
Unknown call-id
Aug  1 13:13:48 sipwise proxy[4400]: NOTICE: <script>: NAT-Reply - S=200 
- OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) ID=16888 at 154.58.3.158
Aug  1 13:13:48 sipwise proxy[4400]: ERROR: rtpengine 
[rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
Unknown call-id
Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
Aug  1 13:13:48 sipwise proxy[4412]: ERROR: db_mysql [km_dbase.c:122]: 
db_mysql_submit_query(): driver error on query: Duplicate entry 
'uloc-53db7100-112e-1' for key 'ruid_idx'
Aug  1 13:13:48 sipwise proxy[4412]: ERROR: <core> [db_query.c:235]: 
db_do_insert_cmd(): error while submitting query
Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [ucontact.c:627]: 
db_insert_ucontact(): inserting contact in db failed
Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [urecord.c:386]: 
wb_timer(): inserting contact into database failed (aor: 
x984099517 at 154.58.3.135)
Aug  1 13:13:48 sipwise proxy[4402]: NOTICE: <script>: NAT-Reply - S=200 
- OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) ID=16888 at 154.58.3.158
Aug  1 13:13:48 sipwise proxy[4402]: ERROR: rtpengine 
[rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
Unknown call-id
Aug  1 13:13:48 sipwise proxy[4404]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:13:49 sipwise proxy[4404]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: New request - 
M=REGISTER R=sip:154.58.3.135 F=sip:x1010 at 154.58.3.135 
T=sip:x1010 at 154.58.3.135 IP=154.58.3.149:5060 (127.0.0.1:5060) 
ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: Authentication 
failed, no credentials - R=sip:154.58.3.135 
ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
Aug  1 13:13:49 sipwise proxy[4410]: NOTICE: <script>: NAT-Reply - S=200 
- OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) ID=16888 at 154.58.3.158
Aug  1 13:13:49 sipwise proxy[4410]: ERROR: rtpengine 
[rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
Unknown call-id
Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
Aug  1 13:14:03 sipwise proxy[4406]: NOTICE: <script>: New request - 
M=BYE R=sip:x1009 at 154.58.3.158:5060 F=sip:606105877 at 154.58.3.135 
T=sip:984099519 at 154.58.3.135 IP=127.0.0.1:5080 (127.0.0.1:5080) 
ID=16888 at 154.58.3.158
Aug  1 13:14:03 sipwise proxy[4398]: NOTICE: <script>: NAT-Reply - S=200 
- OK M=BYE IP=127.0.0.1:5080 (127.0.0.1:5060) ID=16888 at 154.58.3.158
Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:984099519 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
root at sipwise:/var/log/ngcp# tail -n 1000 kamailio-proxy.log

-------------- next part --------------
A non-text attachment was scrubbed...
Name: telefoniae5.cap
Type: application/octet-stream
Size: 635978 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140801/45ae5595/attachment.cap>

From mstorck at voipgate.com  Fri Aug  1 07:20:38 2014
From: mstorck at voipgate.com (Marc Storck)
Date: Fri, 1 Aug 2014 11:20:38 +0000
Subject: [Spce-user] Web Password requirements
Message-ID: <EF586431-A929-4490-9A8E-673D51C3D6D5@voipgate.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Good afternoon,

it seems that the customer can change his web password to an all numeric password. However this makes it impossible for an admin to change any of the settings in Master Data, because the NGCP complains that the web password ?must contain lower-case characters?.

Also, although it say characterS (plural), 1 single lower-case character (singular) is actually required. :-D

Best regards,

Marc
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJT23h3AAoJEBqZdpQUXtTC99MP/28HJBg7HBJCxzqZ1yCHHC0D
tPze0SJo8h4fW4W9hCCAQoUsboeQdDcTFynI6Xac1si/pqCjzT5E71ZTTGf2njDI
FvEm/uN3598FN6Uat6KKJDILBhJfq+Ilm8qbfJERiUmpv5v7RHtCqSJmCkbcZclS
UkUk2BqjOnfe2L07Q0zVMoViVOV/RxZ07yNyawIDIVnNtqm81aG+ScYsn5gtakY4
nSLPFf7xTY8Mi9V+hksogIHDQKgHtQnvorpWisMT5QMZ6v020Aqx0lt3lBtjTULw
yNsXiQ/y/C+QsZxHd5GpbLae+r53fhhJDdDLyOq3QNrdtz4xDdTy9zHP1eXMFDIP
JZ8BiSQGg47Etm0bWOIVS6YAx6fFXPSt65QiSMj/rZd6V5OGayRXmA4lXfrWJeQF
6BnSNRcxlI1f/p0SGsPPIYcSiV8T6lrJyXrvzPdyy6Kwld29TWMWZ8r3WEHDg/eH
0rUn4jDg2f6oX3JNwN25dAWW03KdvcEjt3dr0psPofL6I6TvX0/600Do6156IdVS
msZK2jyEShp4HCYrsYBDPkmrMdQByo80ucFtHV0l2KJwZXhNiclVC0qEOOht1GVH
NmU9HMNxx2fOJTJW2vCbLCb1usA/VPnK5AoMUx3m1nBtlGeKG2TR++BUGCTcorGn
vxRJZpUDzRJXpRctF4iG
=GCXg
-----END PGP SIGNATURE-----

From dgrotti at sipwise.com  Fri Aug  1 08:13:04 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 14:13:04 +0200
Subject: [Spce-user] Web Password requirements
In-Reply-To: <EF586431-A929-4490-9A8E-673D51C3D6D5@voipgate.com>
References: <EF586431-A929-4490-9A8E-673D51C3D6D5@voipgate.com>
Message-ID: <53DB8450.5000708@sipwise.com>

Thanks Marc,
which version are you using ?

Daniel



On 08/01/2014 01:20 PM, Marc Storck wrote:
> Good afternoon,
>
> it seems that the customer can change his web password to an all
> numeric password. However this makes it impossible for an admin to
> change any of the settings in Master Data, because the NGCP complains
> that the web password ?must contain lower-case characters?.
>
> Also, although it say characterS (plural), 1 single lower-case
> character (singular) is actually required. :-D
>
> Best regards,
>
> Marc
> _______________________________________________
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140801/6ef2b72d/attachment.html>

From dgrotti at sipwise.com  Fri Aug  1 08:18:15 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 14:18:15 +0200
Subject: [Spce-user] Call hangs at about 15 seconds
In-Reply-To: <53DB7F1A.9030900@por-aire.es>
References: <53DB7F1A.9030900@por-aire.es>
Message-ID: <53DB8587.3060407@sipwise.com>

Hi,
there is no such call (ID=16888 at 154.58.3.158) in the trace attached.

Also you have a lot of ERROR:

ERROR: rtpengine [rtpengine.c:1491]: rtpp_function_call(): proxy replied
with error: Failed to parse SDP

But the reason why the call is drop is because the ACK is wrong and it
is not delivered:

NOTICE: <script>: New request - M=ACK R=sip:127.0.0.1:5080
F=sip:x1009 at 154.58.3.135 T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060
(127.0.0.1:5060) ID=16888 at 154.58.3.158
NOTICE: <script>: Dropping mis-routed request - R=sip:127.0.0.1:5080
ID=16888 at 154.58.3.158


Can't check the ACK inside cause there is no trace for that callid
16888 at 154.58.3.158.


Daniel



On 08/01/2014 01:50 PM, Leopoldo Iglesia wrote:
> If i call, from a suscriber to a foreign number,  via peering, or to
> other suscriber it hangs at about 15 secs.
>
> I send a wireshark capture and proxy log.
>
>
> Aug  1 13:13:37 sipwise proxy[4400]: NOTICE: <script>: Authentication
> failed, no credentials - R=sip:606105877 at 154.58.3.135
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: New request -
> M=INVITE R=sip:606105877 at 154.58.3.135 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=154.58.3.158:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-Provided
> CLI 'x1009' taken from From-User as fallback, should be from
> 'rpid_user' - R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-provided
> CLI 'x1009' rejected, using network-provided CLI '34984099519' -
> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> '34984099519 at 154.58.3.135' as initiating user-provided CLI -
> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> '34984099519 at 154.58.3.135' as initiating network-provided CLI -
> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting
> called party '606105877' to '34606105877' -
> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Callee is not
> local - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Call to SIP
> Peering - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Load gws
> matching calling part 'sip:34984099519 at 154.58.3.135' and called user
> '34606105877' and called part 'sip:34606105877 at 154.58.3.135' -
> R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc
> source-leg for uuid 'c2731ab4-e7f5-4440-a821-d95c5d94eeac':
> 'c2731ab4-e7f5-4440-a821-d95c5d94eeac|x1009|154.58.3.135|34984099519|||2|||0|call|154.58.3.158|1406891617.480275'
> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc
> destination-leg for uuid '0':
> '0|||0|606105877|0|34606105877|212.231.4.206|34606105877|154.58.3.135'
> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: ERROR: rtpengine
> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
> Failed to parse SDP
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting first
> user-provided CLI '34984099519' to '984099519' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting first
> network-provided CLI '34984099519' to '984099519' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for
> npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for
> npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting From to
> '984099519 <sip:984099519 at 154.58.3.135>' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for
> npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting PAI to
> '<sip:984099519 at 154.58.3.135>' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> P-Called-Party-ID '<sip:34606105877 at 212.231.4.206>' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> 'sip:212.231.4.206:5060' taken from R-URI as next hop after lb for
> PSTN call - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Appending
> P-D-URI
> 'sip:127.0.0.1:5060;received='sip:212.231.4.206:5060;lr;transport=udp'' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Forcing request
> via B2BUA 'sip:127.0.0.1:5080' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Request leaving
> server, D-URI='sip:127.0.0.1:5080' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4404]: NOTICE: <script>: NAT-Reply -
> S=100 - Connecting M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:38 sipwise proxy[4408]: NOTICE: <script>: NAT-Reply -
> S=183 - Session Progress M=INVITE IP=154.58.3.158:5060
> (127.0.0.1:5080) ID=16888 at 154.58.3.158
> Aug  1 13:13:38 sipwise proxy[4408]: ERROR: rtpengine
> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
> Unknown call-id
> Aug  1 13:13:48 sipwise proxy[4400]: NOTICE: <script>: NAT-Reply -
> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:48 sipwise proxy[4400]: ERROR: rtpengine
> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
> Unknown call-id
> Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Duplicate entry
> 'uloc-53db7100-112e-1' for key 'ruid_idx'
> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [ucontact.c:627]:
> db_insert_ucontact(): inserting contact in db failed
> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [urecord.c:386]:
> wb_timer(): inserting contact into database failed (aor:
> x984099517 at 154.58.3.135)
> Aug  1 13:13:48 sipwise proxy[4402]: NOTICE: <script>: NAT-Reply -
> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:48 sipwise proxy[4402]: ERROR: rtpengine
> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
> Unknown call-id
> Aug  1 13:13:48 sipwise proxy[4404]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:49 sipwise proxy[4404]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: New request -
> M=REGISTER R=sip:154.58.3.135 F=sip:x1010 at 154.58.3.135
> T=sip:x1010 at 154.58.3.135 IP=154.58.3.149:5060 (127.0.0.1:5060)
> ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
> Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: Authentication
> failed, no credentials - R=sip:154.58.3.135
> ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
> Aug  1 13:13:49 sipwise proxy[4410]: NOTICE: <script>: NAT-Reply -
> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:49 sipwise proxy[4410]: ERROR: rtpengine
> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
> Unknown call-id
> Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> Aug  1 13:14:03 sipwise proxy[4406]: NOTICE: <script>: New request -
> M=BYE R=sip:x1009 at 154.58.3.158:5060 F=sip:606105877 at 154.58.3.135
> T=sip:984099519 at 154.58.3.135 IP=127.0.0.1:5080 (127.0.0.1:5080)
> ID=16888 at 154.58.3.158
> Aug  1 13:14:03 sipwise proxy[4398]: NOTICE: <script>: NAT-Reply -
> S=200 - OK M=BYE IP=127.0.0.1:5080 (127.0.0.1:5060) ID=16888 at 154.58.3.158
> Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:984099519 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> root at sipwise:/var/log/ngcp# tail -n 1000 kamailio-proxy.log
>
>
>
> _______________________________________________
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140801/40946250/attachment.html>

From mstorck at voipgate.com  Fri Aug  1 08:18:13 2014
From: mstorck at voipgate.com (Marc Storck)
Date: Fri, 1 Aug 2014 12:18:13 +0000
Subject: [Spce-user] Web Password requirements
In-Reply-To: <53DB8450.5000708@sipwise.com>
References: <EF586431-A929-4490-9A8E-673D51C3D6D5@voipgate.com>
 <53DB8450.5000708@sipwise.com>
Message-ID: <4F0D0E0B-B64C-482F-BADA-E5E79476E613@voipgate.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry forgot to mention:

cat /etc/ngcp_version 
mr3.3.1

Regards,

Marc

On Aug 1, 2014, at 2:13 PM, Daniel Grotti <dgrotti at sipwise.com> wrote:

Thanks Marc,
which version are you using ?

Daniel



On 08/01/2014 01:20 PM, Marc Storck wrote:
Good afternoon,

it seems that the customer can change his web password to an all numeric password. However this makes it impossible for an admin to change any of the settings in Master Data, because the NGCP complains that the web password ?must contain lower-case characters?.

Also, although it say characterS (plural), 1 single lower-case character (singular) is actually required. :-D

Best regards,

Marc
>
      _______________________________________________

      > 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

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJT24X3AAoJEBqZdpQUXtTCy5QP/048q1hiPLArDDu83JYPtvN9
hOQZTbUTOguKH0+9HO3K5L3A7pMVWVHlkcmxrM8wboKsQrAvRscL+jTfE1CPZG/d
qKYyZEoCsBKU6yImUoWlYzdn3vNyPcsaVIBcjndFBEJmy4fAOp1SRumaoMzn4NHu
N3Cx47DV77BzY7KHVze2kmugBpkdfOwZcq5HfA811IkRa369pq8gQ50R69xqDk9o
EHJRcuFVxPERxz2/3QAk7Xgkn09kXiW9GINDSG9yNuyye1UJbpjqGPWpug1BHU2V
ycWJCkfJbQVsqh9nLWZ1EayH8tfP4mLwdRdysmIw6VR/v5tdu1ZWnEPFkB9Oi2VV
9OW8wPG7v1H9wWdza0CLkhvJtMLNT+ZyaJce627L5Dlrd5usA0hAIDGSiFJXWN6E
JFq/NQSqv81afy+zu/HI02+cRfnFhki19xsRx6kjWdIGtRnruBjtMV78Yj3vi/Tj
ZJjquMOND5syUc41x9xQ3xEijcG5J4OBZSGyZgkK5ng/PyM8vUQuGIPRVlt8qGuU
UC5XYDTYiFHhgQEIpQSKMObi7wuNSHvbsXPF8jYj+MrCYUyCxwuz19uObn9cemP5
t35qpgRFf8S/Q12aodMJeAC1OlprvXnzIPZvEw0xmYLKrl3Hoi7CHt7+D1TT2ZUv
k465QCqQRK6Up3/nw9Zx
=t2EC
-----END PGP SIGNATURE-----

From dgrotti at sipwise.com  Fri Aug  1 08:25:08 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 14:25:08 +0200
Subject: [Spce-user] Web Password requirements
In-Reply-To: <4F0D0E0B-B64C-482F-BADA-E5E79476E613@voipgate.com>
References: <EF586431-A929-4490-9A8E-673D51C3D6D5@voipgate.com>
 <53DB8450.5000708@sipwise.com>
 <4F0D0E0B-B64C-482F-BADA-E5E79476E613@voipgate.com>
Message-ID: <53DB8724.1090000@sipwise.com>

Hi,
opened an internal ticket for this.

Daniel



On 08/01/2014 02:18 PM, Marc Storck wrote:
> it seems that the customer can change his web password to an all numeric password. However this makes it impossible for an admin to change any of the settings in Master Data, because the NGCP complains that the web password ?must contain lower-case characters?.
>
> Also, although it say characterS (plural), 1 single lower-case character (singular) is actually required.



From liglesia at por-aire.es  Fri Aug  1 08:27:46 2014
From: liglesia at por-aire.es (Leopoldo Iglesia)
Date: Fri, 01 Aug 2014 14:27:46 +0200
Subject: [Spce-user] Call hangs at about 15 seconds
In-Reply-To: <53DB8587.3060407@sipwise.com>
References: <53DB7F1A.9030900@por-aire.es> <53DB8587.3060407@sipwise.com>
Message-ID: <53DB87C2.6020105@por-aire.es>

Check this call in the pervious trace,   is the same call but 2 minutes 
before

6869 at 154.58.3.158

El 01/08/2014 14:18, Daniel Grotti escribi?:
> Hi,
> there is no such call (ID=16888 at 154.58.3.158) in the trace attached.
>
> Also you have a lot of ERROR:
>
> ERROR: rtpengine [rtpengine.c:1491]: rtpp_function_call(): proxy 
> replied with error: Failed to parse SDP
>
> But the reason why the call is drop is because the ACK is wrong and it 
> is not delivered:
>
> NOTICE: <script>: New request - M=ACK R=sip:127.0.0.1:5080 
> F=sip:x1009 at 154.58.3.135 T=sip:606105877 at 154.58.3.135 
> IP=127.0.0.1:5060 (127.0.0.1:5060) ID=16888 at 154.58.3.158
> NOTICE: <script>: Dropping mis-routed request - R=sip:127.0.0.1:5080 
> ID=16888 at 154.58.3.158
>
>
> Can't check the ACK inside cause there is no trace for that callid 
> 16888 at 154.58.3.158.
>
>
> Daniel
>
>
>
> On 08/01/2014 01:50 PM, Leopoldo Iglesia wrote:
>> If i call, from a suscriber to a foreign number,  via peering, or to 
>> other suscriber it hangs at about 15 secs.
>>
>> I send a wireshark capture and proxy log.
>>
>>
>> Aug  1 13:13:37 sipwise proxy[4400]: NOTICE: <script>: Authentication 
>> failed, no credentials - R=sip:606105877 at 154.58.3.135 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: New request - 
>> M=INVITE R=sip:606105877 at 154.58.3.135 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=154.58.3.158:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-Provided 
>> CLI 'x1009' taken from From-User as fallback, should be from 
>> 'rpid_user' - R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-provided 
>> CLI 'x1009' rejected, using network-provided CLI '34984099519' - 
>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> '34984099519 at 154.58.3.135' as initiating user-provided CLI - 
>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> '34984099519 at 154.58.3.135' as initiating network-provided CLI - 
>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting 
>> called party '606105877' to '34606105877' - 
>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Callee is not 
>> local - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Call to SIP 
>> Peering - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Load gws 
>> matching calling part 'sip:34984099519 at 154.58.3.135' and called user 
>> '34606105877' and called part 'sip:34606105877 at 154.58.3.135' - 
>> R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc 
>> source-leg for uuid 'c2731ab4-e7f5-4440-a821-d95c5d94eeac': 
>> 'c2731ab4-e7f5-4440-a821-d95c5d94eeac|x1009|154.58.3.135|34984099519|||2|||0|call|154.58.3.158|1406891617.480275' 
>> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc 
>> destination-leg for uuid '0': 
>> '0|||0|606105877|0|34606105877|212.231.4.206|34606105877|154.58.3.135' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: ERROR: rtpengine 
>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
>> Failed to parse SDP
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting 
>> first user-provided CLI '34984099519' to '984099519' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting 
>> first network-provided CLI '34984099519' to '984099519' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for 
>> npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for 
>> npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting From 
>> to '984099519 <sip:984099519 at 154.58.3.135>' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for 
>> npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting PAI to 
>> '<sip:984099519 at 154.58.3.135>' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> P-Called-Party-ID '<sip:34606105877 at 212.231.4.206>' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> 'sip:212.231.4.206:5060' taken from R-URI as next hop after lb for 
>> PSTN call - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Appending 
>> P-D-URI 
>> 'sip:127.0.0.1:5060;received='sip:212.231.4.206:5060;lr;transport=udp'' 
>> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Forcing 
>> request via B2BUA 'sip:127.0.0.1:5080' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Request 
>> leaving server, D-URI='sip:127.0.0.1:5080' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4404]: NOTICE: <script>: NAT-Reply - 
>> S=100 - Connecting M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:38 sipwise proxy[4408]: NOTICE: <script>: NAT-Reply - 
>> S=183 - Session Progress M=INVITE IP=154.58.3.158:5060 
>> (127.0.0.1:5080) ID=16888 at 154.58.3.158
>> Aug  1 13:13:38 sipwise proxy[4408]: ERROR: rtpengine 
>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
>> Unknown call-id
>> Aug  1 13:13:48 sipwise proxy[4400]: NOTICE: <script>: NAT-Reply - 
>> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:48 sipwise proxy[4400]: ERROR: rtpengine 
>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
>> Unknown call-id
>> Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: db_mysql 
>> [km_dbase.c:122]: db_mysql_submit_query(): driver error on query: 
>> Duplicate entry 'uloc-53db7100-112e-1' for key 'ruid_idx'
>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: <core> [db_query.c:235]: 
>> db_do_insert_cmd(): error while submitting query
>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [ucontact.c:627]: 
>> db_insert_ucontact(): inserting contact in db failed
>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [urecord.c:386]: 
>> wb_timer(): inserting contact into database failed (aor: 
>> x984099517 at 154.58.3.135)
>> Aug  1 13:13:48 sipwise proxy[4402]: NOTICE: <script>: NAT-Reply - 
>> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:48 sipwise proxy[4402]: ERROR: rtpengine 
>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
>> Unknown call-id
>> Aug  1 13:13:48 sipwise proxy[4404]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:49 sipwise proxy[4404]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: New request - 
>> M=REGISTER R=sip:154.58.3.135 F=sip:x1010 at 154.58.3.135 
>> T=sip:x1010 at 154.58.3.135 IP=154.58.3.149:5060 (127.0.0.1:5060) 
>> ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
>> Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: Authentication 
>> failed, no credentials - R=sip:154.58.3.135 
>> ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
>> Aug  1 13:13:49 sipwise proxy[4410]: NOTICE: <script>: NAT-Reply - 
>> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:49 sipwise proxy[4410]: ERROR: rtpengine 
>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
>> Unknown call-id
>> Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> Aug  1 13:14:03 sipwise proxy[4406]: NOTICE: <script>: New request - 
>> M=BYE R=sip:x1009 at 154.58.3.158:5060 F=sip:606105877 at 154.58.3.135 
>> T=sip:984099519 at 154.58.3.135 IP=127.0.0.1:5080 (127.0.0.1:5080) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:14:03 sipwise proxy[4398]: NOTICE: <script>: NAT-Reply - 
>> S=200 - OK M=BYE IP=127.0.0.1:5080 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:984099519 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> root at sipwise:/var/log/ngcp# tail -n 1000 kamailio-proxy.log
>>
>>
>>
>> _______________________________________________
>> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140801/15b36893/attachment.html>

From dgrotti at sipwise.com  Fri Aug  1 08:52:09 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 14:52:09 +0200
Subject: [Spce-user] Call hangs at about 15 seconds
In-Reply-To: <53DB87C2.6020105@por-aire.es>
References: <53DB7F1A.9030900@por-aire.es> <53DB8587.3060407@sipwise.com>
 <53DB87C2.6020105@por-aire.es>
Message-ID: <53DB8D79.2000508@sipwise.com>

Hi,
looks like in the ACK the port 5062 is missing from one of the Route header.
Do you have all the trace ? I mean also messages inside spce
(lb,proxy,sems).

Daniel




On 08/01/2014 02:27 PM, Leopoldo Iglesia wrote:
> Check this call in the pervious trace,   is the same call but 2
> minutes before
>
> 6869 at 154.58.3.158
>
> El 01/08/2014 14:18, Daniel Grotti escribi?:
>> Hi,
>> there is no such call (ID=16888 at 154.58.3.158) in the trace attached.
>>
>> Also you have a lot of ERROR:
>>
>> ERROR: rtpengine [rtpengine.c:1491]: rtpp_function_call(): proxy
>> replied with error: Failed to parse SDP
>>
>> But the reason why the call is drop is because the ACK is wrong and
>> it is not delivered:
>>
>> NOTICE: <script>: New request - M=ACK R=sip:127.0.0.1:5080
>> F=sip:x1009 at 154.58.3.135 T=sip:606105877 at 154.58.3.135
>> IP=127.0.0.1:5060 (127.0.0.1:5060) ID=16888 at 154.58.3.158
>> NOTICE: <script>: Dropping mis-routed request - R=sip:127.0.0.1:5080
>> ID=16888 at 154.58.3.158
>>
>>
>> Can't check the ACK inside cause there is no trace for that callid
>> 16888 at 154.58.3.158.
>>
>>
>> Daniel
>>
>>
>>
>> On 08/01/2014 01:50 PM, Leopoldo Iglesia wrote:
>>> If i call, from a suscriber to a foreign number,  via peering, or to
>>> other suscriber it hangs at about 15 secs.
>>>
>>> I send a wireshark capture and proxy log.
>>>
>>>
>>> Aug  1 13:13:37 sipwise proxy[4400]: NOTICE: <script>:
>>> Authentication failed, no credentials - R=sip:606105877 at 154.58.3.135
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: New request -
>>> M=INVITE R=sip:606105877 at 154.58.3.135 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=154.58.3.158:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-Provided
>>> CLI 'x1009' taken from From-User as fallback, should be from
>>> 'rpid_user' - R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-provided
>>> CLI 'x1009' rejected, using network-provided CLI '34984099519' -
>>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> '34984099519 at 154.58.3.135' as initiating user-provided CLI -
>>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> '34984099519 at 154.58.3.135' as initiating network-provided CLI -
>>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting
>>> called party '606105877' to '34606105877' -
>>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Callee is not
>>> local - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Call to SIP
>>> Peering - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Load gws
>>> matching calling part 'sip:34984099519 at 154.58.3.135' and called user
>>> '34606105877' and called part 'sip:34606105877 at 154.58.3.135' -
>>> R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc
>>> source-leg for uuid 'c2731ab4-e7f5-4440-a821-d95c5d94eeac':
>>> 'c2731ab4-e7f5-4440-a821-d95c5d94eeac|x1009|154.58.3.135|34984099519|||2|||0|call|154.58.3.158|1406891617.480275'
>>> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc
>>> destination-leg for uuid '0':
>>> '0|||0|606105877|0|34606105877|212.231.4.206|34606105877|154.58.3.135'
>>> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: ERROR: rtpengine
>>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
>>> Failed to parse SDP
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting
>>> first user-provided CLI '34984099519' to '984099519' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting
>>> first network-provided CLI '34984099519' to '984099519' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135'
>>> for npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135'
>>> for npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting From
>>> to '984099519 <sip:984099519 at 154.58.3.135>' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135'
>>> for npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting PAI
>>> to '<sip:984099519 at 154.58.3.135>' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> P-Called-Party-ID '<sip:34606105877 at 212.231.4.206>' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> 'sip:212.231.4.206:5060' taken from R-URI as next hop after lb for
>>> PSTN call - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Appending
>>> P-D-URI
>>> 'sip:127.0.0.1:5060;received='sip:212.231.4.206:5060;lr;transport=udp''
>>> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Forcing
>>> request via B2BUA 'sip:127.0.0.1:5080' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Request
>>> leaving server, D-URI='sip:127.0.0.1:5080' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4404]: NOTICE: <script>: NAT-Reply -
>>> S=100 - Connecting M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:38 sipwise proxy[4408]: NOTICE: <script>: NAT-Reply -
>>> S=183 - Session Progress M=INVITE IP=154.58.3.158:5060
>>> (127.0.0.1:5080) ID=16888 at 154.58.3.158
>>> Aug  1 13:13:38 sipwise proxy[4408]: ERROR: rtpengine
>>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
>>> Unknown call-id
>>> Aug  1 13:13:48 sipwise proxy[4400]: NOTICE: <script>: NAT-Reply -
>>> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:48 sipwise proxy[4400]: ERROR: rtpengine
>>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
>>> Unknown call-id
>>> Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: db_mysql
>>> [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>>> Duplicate entry 'uloc-53db7100-112e-1' for key 'ruid_idx'
>>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: <core> [db_query.c:235]:
>>> db_do_insert_cmd(): error while submitting query
>>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [ucontact.c:627]:
>>> db_insert_ucontact(): inserting contact in db failed
>>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [urecord.c:386]:
>>> wb_timer(): inserting contact into database failed (aor:
>>> x984099517 at 154.58.3.135)
>>> Aug  1 13:13:48 sipwise proxy[4402]: NOTICE: <script>: NAT-Reply -
>>> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:48 sipwise proxy[4402]: ERROR: rtpengine
>>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
>>> Unknown call-id
>>> Aug  1 13:13:48 sipwise proxy[4404]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:49 sipwise proxy[4404]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: New request -
>>> M=REGISTER R=sip:154.58.3.135 F=sip:x1010 at 154.58.3.135
>>> T=sip:x1010 at 154.58.3.135 IP=154.58.3.149:5060 (127.0.0.1:5060)
>>> ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
>>> Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>:
>>> Authentication failed, no credentials - R=sip:154.58.3.135
>>> ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
>>> Aug  1 13:13:49 sipwise proxy[4410]: NOTICE: <script>: NAT-Reply -
>>> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:49 sipwise proxy[4410]: ERROR: rtpengine
>>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
>>> Unknown call-id
>>> Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> Aug  1 13:14:03 sipwise proxy[4406]: NOTICE: <script>: New request -
>>> M=BYE R=sip:x1009 at 154.58.3.158:5060 F=sip:606105877 at 154.58.3.135
>>> T=sip:984099519 at 154.58.3.135 IP=127.0.0.1:5080 (127.0.0.1:5080)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:14:03 sipwise proxy[4398]: NOTICE: <script>: NAT-Reply -
>>> S=200 - OK M=BYE IP=127.0.0.1:5080 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:984099519 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> root at sipwise:/var/log/ngcp# tail -n 1000 kamailio-proxy.log
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140801/18a418e8/attachment.html>

From sipwise.support at mtkom.de  Fri Aug  1 09:41:14 2014
From: sipwise.support at mtkom.de (Pascal Schwarz)
Date: Fri, 1 Aug 2014 15:41:14 +0200 (CEST)
Subject: [Spce-user] security bans / 403 Errror
Message-ID: <alpine.DEB.2.10.1408011514080.32451@gucky>

Hy All,

i have setup a sip_provider_CE_mr3.3.2_virtualbox.ova .
i have configured 616 Subscribers.
All 616 Subscribers are automatic configured from me so the username and 
password of client and Server 100% the same and works.
All 616 Subscribers ar FritzBox from AVM mostly 7360 7270 and 7390 .

every h i can check the security bans and see that there are  Subscribers.
I now that at FritzBox and and the spce the same password and username so 
i don't understand why so mutch Subscribers will bee there .

i i delete them from security bans the fritbox works fine but without any
changes some of this Subscribers will bee back some houre later to ban.

At the logile of the AVM FritzBOx7270 i see there are often problems:

  date:
  29.07.14      27 x 403 error
  30.07.14     164 x 403 error
  01.08.14      35 x 403 error

bevor i use sip_provider_CE_mr3.3.2_virtualbox.ova i use asterisks there
i have no problems with the FritzBod autorisation.
Thas not only one fritzbox . I see this Problem at alle FritzBox .

Any One any Idee what i can do to fix this problem ?

regards
Pascal Schwarz




From dgrotti at sipwise.com  Fri Aug  1 10:05:40 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 16:05:40 +0200
Subject: [Spce-user] security bans / 403 Errror
In-Reply-To: <alpine.DEB.2.10.1408011514080.32451@gucky>
References: <alpine.DEB.2.10.1408011514080.32451@gucky>
Message-ID: <53DB9EB4.2090803@sipwise.com>

Hi,
please grep your kamailio-lb.log file with:

grep "Consecutive Authentication Failure" kamailio-lb.log

And check why you get some users banned.

An option is to increase the number of attempt from 3 to 6 for ex.

Daniel




On 08/01/2014 03:41 PM, Pascal Schwarz wrote:
> Hy All,
>
> i have setup a sip_provider_CE_mr3.3.2_virtualbox.ova .
> i have configured 616 Subscribers.
> All 616 Subscribers are automatic configured from me so the username
> and password of client and Server 100% the same and works.
> All 616 Subscribers ar FritzBox from AVM mostly 7360 7270 and 7390 .
>
> every h i can check the security bans and see that there are 
> Subscribers.
> I now that at FritzBox and and the spce the same password and username
> so i don't understand why so mutch Subscribers will bee there .
>
> i i delete them from security bans the fritbox works fine but without any
> changes some of this Subscribers will bee back some houre later to ban.
>
> At the logile of the AVM FritzBOx7270 i see there are often problems:
>
>  date:
>  29.07.14      27 x 403 error
>  30.07.14     164 x 403 error
>  01.08.14      35 x 403 error
>
> bevor i use sip_provider_CE_mr3.3.2_virtualbox.ova i use asterisks there
> i have no problems with the FritzBod autorisation.
> Thas not only one fritzbox . I see this Problem at alle FritzBox .
>
> Any One any Idee what i can do to fix this problem ?
>
> regards
> Pascal Schwarz
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user



From paul.belanger at polybeacon.com  Fri Aug  1 10:22:56 2014
From: paul.belanger at polybeacon.com (Paul Belanger)
Date: Fri, 1 Aug 2014 10:22:56 -0400
Subject: [Spce-user] fresh install debian 7 not web access
Message-ID: <CALLKq0SFYGHf5eCna7UpeDPaq=+=dw6Y2txmKUGs9MDmNcuu5A@mail.gmail.com>

I've just done a fresh install on debian 7 using the follow
directions[1] but for some reason it doesn't appear the web interface
is working correctly.  Any attempt to access the system results in no
web pages being loaded.

Is it possible the system did not properly configure itself?

[1] https://www.sipwise.com/doc/mr3.3.2/spce/ar01s04.html#_installing_the_sip_provider_ce

-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger


From dgrotti at sipwise.com  Fri Aug  1 10:33:50 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 16:33:50 +0200
Subject: [Spce-user] fresh install debian 7 not web access
Message-ID: <20140801143415.B61A81502088@zimbra.sipwise.com>

Are you accessing port 1443?
Is that port listening on your system?

Daniel

On 1 Aug 2014 16:22, Paul Belanger <paul.belanger at polybeacon.com> wrote:
>
> I've just done a fresh install on debian 7 using the follow 
> directions[1] but for some reason it doesn't appear the web interface 
> is working correctly.? Any attempt to access the system results in no 
> web pages being loaded. 
>
> Is it possible the system did not properly configure itself? 
>
> [1] https://www.sipwise.com/doc/mr3.3.2/spce/ar01s04.html#_installing_the_sip_provider_ce 
>
> -- 
> Paul Belanger | PolyBeacon, Inc. 
> Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode) 
> Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger 
> _______________________________________________ 
> Spce-user mailing list 
> Spce-user at lists.sipwise.com 
> https://lists.sipwise.com/listinfo/spce-user 

From gsims94 at gmail.com  Fri Aug  1 10:39:37 2014
From: gsims94 at gmail.com (Gordon Sims)
Date: Fri, 01 Aug 2014 09:39:37 -0500
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <CALLKq0SFYGHf5eCna7UpeDPaq=+=dw6Y2txmKUGs9MDmNcuu5A@mail.gmail.com>
Message-ID: <D00110A2.1D695%gsims94@gmail.com>

I had the same thing happen on fresh install.  Check to make sure iptables
are not enabled and then do a reboot.  Usually after the reboot,
everything works just fine.

Gordon

On 8/1/14, 9:22 AM, "Paul Belanger" <paul.belanger at polybeacon.com> wrote:

>I've just done a fresh install on debian 7 using the follow
>directions[1] but for some reason it doesn't appear the web interface
>is working correctly.  Any attempt to access the system results in no
>web pages being loaded.
>
>Is it possible the system did not properly configure itself?
>
>[1] 
>https://www.sipwise.com/doc/mr3.3.2/spce/ar01s04.html#_installing_the_sip_
>provider_ce
>
>-- 
>Paul Belanger | PolyBeacon, Inc.
>Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
>Github: https://github.com/pabelanger | Twitter:
>https://twitter.com/pabelanger
>_______________________________________________
>Spce-user mailing list
>Spce-user at lists.sipwise.com
>https://lists.sipwise.com/listinfo/spce-user




From j.fresneda at ibersontel.com  Fri Aug  1 10:39:17 2014
From: j.fresneda at ibersontel.com (Jorge Fresneda - Ibersontel)
Date: Fri, 01 Aug 2014 16:39:17 +0200
Subject: [Spce-user] Session-timers
In-Reply-To: <53DA2B75.2000703@sipwise.com>
References: <53D90E1B.6090701@ibersontel.com> <53DA20A5.20109@ibersontel.com>
 <53DA2B75.2000703@sipwise.com>
Message-ID: <53DBA695.7000607@ibersontel.com>

Hi,

One question, When I change the sst_enable to "yes", is need execute 
"ngcpcfg apply"?????

Thanks so much
Regards,
Jorge



El 31/07/2014 13:41, Daniel Grotti escribi?:
> Hi,
> you can enable/disable session-timers on peer/subscribers preferences.
>
> Daniel
>
>
>
> On 07/31/2014 12:55 PM, Jorge Fresneda - Ibersontel wrote:
>> Hello,
>>
>>
>> I have a problem with session-timers. A carrier send me a
>> "session-expire=1800;refresher=uac" header at 30 minutes and he say me
>> that I have enable the session-timer option. How I can do? I would like
>> to that session-option are enable on end-point and not in sipwise.
>>
>> Thank you so much,
>> Regards
>> Jorge
>>
>>
>> _______________________________________________
>> 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



From sipwise.support at mtkom.de  Fri Aug  1 10:54:30 2014
From: sipwise.support at mtkom.de (Pascal Schwarz)
Date: Fri, 1 Aug 2014 16:54:30 +0200 (CEST)
Subject: [Spce-user] security bans / 403 Errror
In-Reply-To: <53DB9EB4.2090803@sipwise.com>
References: <alpine.DEB.2.10.1408011514080.32451@gucky>
 <53DB9EB4.2090803@sipwise.com>
Message-ID: <alpine.DEB.2.10.1408011647570.32451@gucky>

Hallo Daniel,

> grep "Consecutive Authentication Failure" kamailio-lb.log

root at viax00:/var/log/ngcp# grep "Consecutive Authentication Failure" 
kamailio-lb.log | wc -l
1249
root at viax00:/var/log/ngcp#

thats only entry from 01.08.2014
it all the same ia change the username to XXXXXXXXXXX

Jul 31 23:59:51 viax00 lb[6845]: WARNING: <script>: Consecutive 
Authentication Failure for 'XXXXXXXXXXX at voice.mtkom.de' UA='AVM FRITZ!Box 
7272 120.06.03 TAL (Feb  7 2014)' IP='82.206.74.185' -  R=<null> 
ID=AAEF7C33E85B415F at 82.206.74.185

Aug  1 00:00:33 viax00 lb[6845]: WARNING: <script>: Consecutive 
Authentication Failure for 'XXXXXXXXXXX at voice.mtkom.de' UA='AVM FRITZ!Box 
Fon WLAN 7390 84.06.04 TAL (Feb 10 2014)' IP='82.206.74.227' -  R=<null> 
ID=BBCBCEA04C88306F at 82.206.74.227

Aug  1 00:16:35 viax00 lb[6845]: WARNING: <script>: Consecutive 
Authentication Failure for 'XXXXXXXXXX at voice.mtkom.de' UA='Grandstream 
GXP2000 1.2.4.3' IP='217.140.73.162' -  R=<null> 
ID=16ad51adde8014d2 at 192.168.253.106

Aug  1 00:24:22 viax00 lb[6845]: WARNING: <script>: Consecutive 
Authentication Failure for 'XXXXXXXXXXX at voice.mtkom.de' 
UA='Linksys/SPA2102-3.3.6' IP='93.194.37.194' -  R=<null> 
ID=81840f46-eea3fc72 at 93.194.37.194

you see this problem is with other Hardware too.
we block the config-change at AVM so nobody can change username
and password and that user that here will be ban works afte delet ban 
entry some times fine .

> An option is to increase the number of attempt from 3 to 6 for ex.
but the user ask why more times every day he see 403 at the logile
auf his AVM . So thats must fix.


regards
pascal



From dgrotti at sipwise.com  Fri Aug  1 10:57:03 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 16:57:03 +0200
Subject: [Spce-user] Session-timers
Message-ID: <20140801145727.3EE911502088@zimbra.sipwise.com>

You can change it from web interface.
No apply is needed.

On 1 Aug 2014 16:39, Jorge Fresneda - Ibersontel <j.fresneda at ibersontel.com> wrote:
>
> Hi, 
>
> One question, When I change the sst_enable to "yes", is need execute 
> "ngcpcfg apply"????? 
>
> Thanks so much 
> Regards, 
> Jorge 
>
>
>
> El 31/07/2014 13:41, Daniel Grotti escribi?: 
> > Hi, 
> > you can enable/disable session-timers on peer/subscribers preferences. 
> > 
> > Daniel 
> > 
> > 
> > 
> > On 07/31/2014 12:55 PM, Jorge Fresneda - Ibersontel wrote: 
> >> Hello, 
> >> 
> >> 
> >> I have a problem with session-timers. A carrier send me a 
> >> "session-expire=1800;refresher=uac" header at 30 minutes and he say me 
> >> that I have enable the session-timer option. How I can do? I would like 
> >> to that session-option are enable on end-point and not in sipwise. 
> >> 
> >> Thank you so much, 
> >> Regards 
> >> Jorge 
> >> 
> >> 
> >> _______________________________________________ 
> >> 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 

From j.fresneda at ibersontel.com  Fri Aug  1 11:04:38 2014
From: j.fresneda at ibersontel.com (Jorge Fresneda - Ibersontel)
Date: Fri, 01 Aug 2014 17:04:38 +0200
Subject: [Spce-user] Session-timers
In-Reply-To: <20140801145727.3EE911502088@zimbra.sipwise.com>
References: <20140801145727.3EE911502088@zimbra.sipwise.com>
Message-ID: <53DBAC86.6070304@ibersontel.com>

Hi,

He cambiado el sst_enable, pero cuando reciben un INVITE del portador 
con "session-expire = 1,800; refresca = uac", la respuesta sipwise con 
200 OK. Me gustar?a que la respuesta sipwise con "session-expira = 7200".

Thanks
Regards


El 01/08/2014 16:57, Daniel Grotti escribi?:
> You can change it from web interface.
> No apply is needed.
>
> On 1 Aug 2014 16:39, Jorge Fresneda - Ibersontel <j.fresneda at ibersontel.com> wrote:
>> Hi,
>>
>> One question, When I change the sst_enable to "yes", is need execute
>> "ngcpcfg apply"?????
>>
>> Thanks so much
>> Regards,
>> Jorge
>>
>>
>>
>> El 31/07/2014 13:41, Daniel Grotti escribi?:
>>> Hi,
>>> you can enable/disable session-timers on peer/subscribers preferences.
>>>
>>> Daniel
>>>
>>>
>>>
>>> On 07/31/2014 12:55 PM, Jorge Fresneda - Ibersontel wrote:
>>>> Hello,
>>>>
>>>>
>>>> I have a problem with session-timers. A carrier send me a
>>>> "session-expire=1800;refresher=uac" header at 30 minutes and he say me
>>>> that I have enable the session-timer option. How I can do? I would like
>>>> to that session-option are enable on end-point and not in sipwise.
>>>>
>>>> Thank you so much,
>>>> Regards
>>>> Jorge
>>>>
>>>>
>>>> _______________________________________________
>>>> 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



From j.fresneda at ibersontel.com  Fri Aug  1 11:08:14 2014
From: j.fresneda at ibersontel.com (Jorge Fresneda - Ibersontel)
Date: Fri, 01 Aug 2014 17:08:14 +0200
Subject: [Spce-user] Session-timers
In-Reply-To: <20140801145727.3EE911502088@zimbra.sipwise.com>
References: <20140801145727.3EE911502088@zimbra.sipwise.com>
Message-ID: <53DBAD5E.6090901@ibersontel.com>

Oh, I'm sorry:

I'm changed the sst_enable, but when receive a INVITE from carrier with 
"session-expire=1800;refreshes=uac", the answer of sipwise is 200 ok. I 
would like that answer of sipwise with "session-expire=7200"

Thanks,
Regards


El 01/08/2014 16:57, Daniel Grotti escribi?:
> You can change it from web interface.
> No apply is needed.
>
> On 1 Aug 2014 16:39, Jorge Fresneda - Ibersontel <j.fresneda at ibersontel.com> wrote:
>> Hi,
>>
>> One question, When I change the sst_enable to "yes", is need execute
>> "ngcpcfg apply"?????
>>
>> Thanks so much
>> Regards,
>> Jorge
>>
>>
>>
>> El 31/07/2014 13:41, Daniel Grotti escribi?:
>>> Hi,
>>> you can enable/disable session-timers on peer/subscribers preferences.
>>>
>>> Daniel
>>>
>>>
>>>
>>> On 07/31/2014 12:55 PM, Jorge Fresneda - Ibersontel wrote:
>>>> Hello,
>>>>
>>>>
>>>> I have a problem with session-timers. A carrier send me a
>>>> "session-expire=1800;refresher=uac" header at 30 minutes and he say me
>>>> that I have enable the session-timer option. How I can do? I would like
>>>> to that session-option are enable on end-point and not in sipwise.
>>>>
>>>> Thank you so much,
>>>> Regards
>>>> Jorge
>>>>
>>>>
>>>> _______________________________________________
>>>> 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



From alutay at sipwise.com  Fri Aug  1 11:26:43 2014
From: alutay at sipwise.com (Alex Lutay)
Date: Fri, 01 Aug 2014 17:26:43 +0200
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <D00110A2.1D695%gsims94@gmail.com>
References: <D00110A2.1D695%gsims94@gmail.com>
Message-ID: <53DBB1B3.2000305@sipwise.com>

Dear Gordon!

First of all thank you for the bug report.

It is known CE problem, at the moment you have to reboot the server 
after fresh installation or start nginx manually.
You can use MT#6369 for further references to bugreport.

It happens because we install both Apache and Nginx WEB servers
(we are on a way of migration to Nginx). Both are default debian 
packages and install default configs, which are fighting for default 
ports... Apache won in your case while we need nginx.

At the end of installation "ngcpcfg apply" generate correct/new apache 
and nginx configs and remove port conflicts, but it tries to start 
ngingx before stopping apache:

> Restarting nginx: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
> nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
> ...
> nginx: [emerg] still could not bind()
> nginx.
> Restarting web server: apache2
> ...

I hope this information helped you understand the issue.
It will be automatically disappear as soon as we remove Apache,
also we are planning to add "Reboot (Y/N)?" hint for users,
but currently occupied with important new features ;-)

JFYI, Also we almost released mr3.4.1 with new CE install CD (which 
reboot the server after the installation):
> https://www.sipwise.com/doc/mr3.4.1/spce/ar01s04.html#_using_the_ngcp_install_cd_recommended
but it is a secret for now, don't tell anybody! :-)

Thank you for your bugreport one more time!

On 01/08/14 16:39, Gordon Sims wrote:
> I had the same thing happen on fresh install.  Check to make sure iptables
> are not enabled and then do a reboot.  Usually after the reboot,
> everything works just fine.

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From paul.belanger at polybeacon.com  Fri Aug  1 11:34:34 2014
From: paul.belanger at polybeacon.com (Paul Belanger)
Date: Fri, 1 Aug 2014 11:34:34 -0400
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <53DBB1B3.2000305@sipwise.com>
References: <D00110A2.1D695%gsims94@gmail.com> <53DBB1B3.2000305@sipwise.com>
Message-ID: <CALLKq0QSAORFnrXfk84GvPC7qMBvNPoo+3kktLmyAp8AgJhC2A@mail.gmail.com>

On Fri, Aug 1, 2014 at 11:26 AM, Alex Lutay <alutay at sipwise.com> wrote:
> Dear Gordon!
>
> First of all thank you for the bug report.
>
> It is known CE problem, at the moment you have to reboot the server after
> fresh installation or start nginx manually.
> You can use MT#6369 for further references to bugreport.
>
> It happens because we install both Apache and Nginx WEB servers
> (we are on a way of migration to Nginx). Both are default debian packages
> and install default configs, which are fighting for default ports... Apache
> won in your case while we need nginx.
>
> At the end of installation "ngcpcfg apply" generate correct/new apache and
> nginx configs and remove port conflicts, but it tries to start ngingx before
> stopping apache:
>
>> Restarting nginx: nginx: [emerg] bind() to [::]:80 failed (98: Address
>> already in use)
>> nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
>> ...
>> nginx: [emerg] still could not bind()
>> nginx.
>> Restarting web server: apache2
>> ...
>
>
> I hope this information helped you understand the issue.
> It will be automatically disappear as soon as we remove Apache,
> also we are planning to add "Reboot (Y/N)?" hint for users,
> but currently occupied with important new features ;-)
>
> JFYI, Also we almost released mr3.4.1 with new CE install CD (which reboot
> the server after the installation):
>>
>>
>> https://www.sipwise.com/doc/mr3.4.1/spce/ar01s04.html#_using_the_ngcp_install_cd_recommended
>
> but it is a secret for now, don't tell anybody! :-)
>
> Thank you for your bugreport one more time!
>
Okay, rebooting has gotten me a step closer. Aside from loosing ssh
access, I now get '502 Bad Gateway' from the web interface.  Looking
at the ngcp-panel error logs, I see the following:

2014/08/01 15:29:01 [error] 4046#0: *131 connect() to
unix:/var/run/fastcgi/ngcp-panel.sock failed (111: Connection refused)
while connecting to upstream, client: ::ffff:209.87.224.9, server: ,
request: "GET /login/admin HTTP/1.1", upstream:
"fastcgi://unix:/var/run/fastcgi/ngcp-panel.sock:", host:
"104.130.128.104:1443"

-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger


From gsims94 at gmail.com  Fri Aug  1 11:46:06 2014
From: gsims94 at gmail.com (Gordon Sims)
Date: Fri, 01 Aug 2014 10:46:06 -0500
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <14670942.9974.1406908190405.JavaMail.root@NXSSFUDF1.Nexepe.com>
Message-ID: <D0011E5D.1D6C3%GSims@Nexepe.com>

Is this server directly connected to the Internet? If not, check to make
sure that port 1443 is open on your firewall. As for SSH, you should be
able to check the status of sshd and make sure it is running with a
service sshd status .

-Gordon

On 8/1/14, 10:34 AM, "Paul Belanger" <paul.belanger at polybeacon.com> wrote:

>On Fri, Aug 1, 2014 at 11:26 AM, Alex Lutay <alutay at sipwise.com> wrote:
>> Dear Gordon!
>>
>> First of all thank you for the bug report.
>>
>> It is known CE problem, at the moment you have to reboot the server
>>after
>> fresh installation or start nginx manually.
>> You can use MT#6369 for further references to bugreport.
>>
>> It happens because we install both Apache and Nginx WEB servers
>> (we are on a way of migration to Nginx). Both are default debian
>>packages
>> and install default configs, which are fighting for default ports...
>>Apache
>> won in your case while we need nginx.
>>
>> At the end of installation "ngcpcfg apply" generate correct/new apache
>>and
>> nginx configs and remove port conflicts, but it tries to start ngingx
>>before
>> stopping apache:
>>
>>> Restarting nginx: nginx: [emerg] bind() to [::]:80 failed (98: Address
>>> already in use)
>>> nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
>>> ...
>>> nginx: [emerg] still could not bind()
>>> nginx.
>>> Restarting web server: apache2
>>> ...
>>
>>
>> I hope this information helped you understand the issue.
>> It will be automatically disappear as soon as we remove Apache,
>> also we are planning to add "Reboot (Y/N)?" hint for users,
>> but currently occupied with important new features ;-)
>>
>> JFYI, Also we almost released mr3.4.1 with new CE install CD (which
>>reboot
>> the server after the installation):
>>>
>>>
>>> 
>>>https://www.sipwise.com/doc/mr3.4.1/spce/ar01s04.html#_using_the_ngcp_in
>>>stall_cd_recommended
>>
>> but it is a secret for now, don't tell anybody! :-)
>>
>> Thank you for your bugreport one more time!
>>
>Okay, rebooting has gotten me a step closer. Aside from loosing ssh
>access, I now get '502 Bad Gateway' from the web interface.  Looking
>at the ngcp-panel error logs, I see the following:
>
>2014/08/01 15:29:01 [error] 4046#0: *131 connect() to
>unix:/var/run/fastcgi/ngcp-panel.sock failed (111: Connection refused)
>while connecting to upstream, client: ::ffff:209.87.224.9, server: ,
>request: "GET /login/admin HTTP/1.1", upstream:
>"fastcgi://unix:/var/run/fastcgi/ngcp-panel.sock:", host:
>"104.130.128.104:1443"
>
>-- 
>Paul Belanger | PolyBeacon, Inc.
>Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
>Github: https://github.com/pabelanger | Twitter:
>https://twitter.com/pabelanger
>_______________________________________________
>Spce-user mailing list
>Spce-user at lists.sipwise.com
>https://lists.sipwise.com/listinfo/spce-user
>
>
>-------------------------------------------------------------
>This email was processed through Nexepe Spam filter to filter junk
>messages.
>If you feel this message has been tagged incorrectly, you can
>change its category by clicking the link below.
>Click here 
>http://10.0.9.41:5272/FrontController?operation=mbeu&f=00001_-2300_2014080
>1_70980.eml&chkBayesian=1&pr=1&mt=1&ma=s to mark email as junk.
>-------------------------------------------------------------




From paul.belanger at polybeacon.com  Fri Aug  1 11:50:50 2014
From: paul.belanger at polybeacon.com (Paul Belanger)
Date: Fri, 1 Aug 2014 11:50:50 -0400
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <D0011E5D.1D6C3%GSims@Nexepe.com>
References: <14670942.9974.1406908190405.JavaMail.root@NXSSFUDF1.Nexepe.com>
 <D0011E5D.1D6C3%GSims@Nexepe.com>
Message-ID: <CALLKq0QQgqWdapCXALBOmCmPwthQkso5ShC6F3F6TZu+PZg82g@mail.gmail.com>

On Fri, Aug 1, 2014 at 11:46 AM, Gordon Sims <gsims94 at gmail.com> wrote:
> Is this server directly connected to the Internet? If not, check to make
> sure that port 1443 is open on your firewall. As for SSH, you should be
> able to check the status of sshd and make sure it is running with a
> service sshd status .
>
Yes, public web (rackspace instance for testing). No firewall is
running. This looks to be a provision error by looking at the logging
however, I don't have the knowledge yet to debug it.  This is also my
4 times re-provisioning the system so I suspect there is a bug in the
installer.

-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger


From gsims94 at gmail.com  Fri Aug  1 11:54:22 2014
From: gsims94 at gmail.com (Gordon Sims)
Date: Fri, 01 Aug 2014 10:54:22 -0500
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <CALLKq0QQgqWdapCXALBOmCmPwthQkso5ShC6F3F6TZu+PZg82g@mail.gmail.com>
Message-ID: <D00121B6.1D6E1%gsims94@gmail.com>

Did you do the net-installer and minimal install?  I?ve had issues before
using the standard install.  The only way that I got it to work was to not
install anything additional, including ssh.  The SPCE installer will
install all the appropriate packages and set it up the proper way.  Just
reboot after complete is all.

-Gordon

On 8/1/14, 10:50 AM, "Paul Belanger" <paul.belanger at polybeacon.com> wrote:

>On Fri, Aug 1, 2014 at 11:46 AM, Gordon Sims <gsims94 at gmail.com> wrote:
>> Is this server directly connected to the Internet? If not, check to make
>> sure that port 1443 is open on your firewall. As for SSH, you should be
>> able to check the status of sshd and make sure it is running with a
>> service sshd status .
>>
>Yes, public web (rackspace instance for testing). No firewall is
>running. This looks to be a provision error by looking at the logging
>however, I don't have the knowledge yet to debug it.  This is also my
>4 times re-provisioning the system so I suspect there is a bug in the
>installer.
>
>-- 
>Paul Belanger | PolyBeacon, Inc.
>Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
>Github: https://github.com/pabelanger | Twitter:
>https://twitter.com/pabelanger




From agranig at sipwise.com  Fri Aug  1 12:02:04 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Fri, 01 Aug 2014 18:02:04 +0200
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <CALLKq0QQgqWdapCXALBOmCmPwthQkso5ShC6F3F6TZu+PZg82g@mail.gmail.com>
References: <14670942.9974.1406908190405.JavaMail.root@NXSSFUDF1.Nexepe.com>
 <D0011E5D.1D6C3%GSims@Nexepe.com>
 <CALLKq0QQgqWdapCXALBOmCmPwthQkso5ShC6F3F6TZu+PZg82g@mail.gmail.com>
Message-ID: <53DBB9FC.8010108@sipwise.com>

Hi,

On 08/01/2014 05:50 PM, Paul Belanger wrote:
> Yes, public web (rackspace instance for testing). No firewall is
> running. This looks to be a provision error by looking at the logging
> however, I don't have the knowledge yet to debug it.  This is also my
> 4 times re-provisioning the system so I suspect there is a bug in the
> installer.

How much memory does your machine have? You'd need at least 2GB, more is
better.

What's the output when executing "/etc/init.d/ngcp-panel restart"
manually, and is there anything in /var/log/ngcp/oss.log?

Andreas


From alutay at sipwise.com  Fri Aug  1 12:28:33 2014
From: alutay at sipwise.com (Alex Lutay)
Date: Fri, 01 Aug 2014 18:28:33 +0200
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <CALLKq0QSAORFnrXfk84GvPC7qMBvNPoo+3kktLmyAp8AgJhC2A@mail.gmail.com>
References: <D00110A2.1D695%gsims94@gmail.com>	<53DBB1B3.2000305@sipwise.com>
 <CALLKq0QSAORFnrXfk84GvPC7qMBvNPoo+3kktLmyAp8AgJhC2A@mail.gmail.com>
Message-ID: <53DBC031.7010807@sipwise.com>

Dear Paul,

NGCP has a configuration file /etc/ngcp-config/network.yml which
contains IPs/service/roles attached to server/service.

For mr3.3 we improved security configuration, allowing to listen SSH
on specified interfaces only. Please find type ssh_ext into network.yml

So, we might have some issues there, lets try to debug.
Please check the list of IPs sshd currently listening:
 > netstat -anp | grep sshd

Does sshd listen IP(s) you are trying to reach?

If NO: please check that all interfaces in network.yml has type ssh_ext.
Update network.yml if necessary and run "ngcpcfg apply" to apply config
changes. Recheck the ssh connection.

If YES: it is local networking issue.

If you have no luck, please share:
1) netstat -anp | grep sshd
2) cat /etc/ngcp-config/network.yml
3) grep ListenAddress /etc/ssh/sshd_config

Tnx!

On 01/08/14 17:34, Paul Belanger wrote:
> Okay, rebooting has gotten me a step closer. Aside from loosing ssh
> access, I now get '502 Bad Gateway' from the web interface.  Looking
> at the ngcp-panel error logs, I see the following:

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From gary at netdiverse.com  Fri Aug  1 16:55:28 2014
From: gary at netdiverse.com (Gary Nieboer)
Date: Fri, 1 Aug 2014 14:55:28 -0600
Subject: [Spce-user] Peering Rules database vs. GUI Issue
Message-ID: <CAMXUi2ScE2u1tnGKSsbZUms+64yYTwAb-LsiKCfHJFAs1k7bsg@mail.gmail.com>

We have experienced a few issues with our "Peering Rules" on SPCE, 3.3.1.

A created rule exists in the GUI, but when routing a call through the SBC,
the call follows a route to a default peer rather than the peer indicated
in the GUI.

We recently did a comparison of what is shown in the database:  lcr_rules

                            select * from lcr_rule;


Here are a few lines from the database:   Some numbers are replaced with
"`" and not fully shown:

Note:  Rule 102 is missing from the database


| id  | lcr_id | prefix | request_uri | from_uri | stopper | enabled |
group_id |
+-----+--------+--------+-------------+----------+---------+---------+----------+
| 101 |      1 |        | ~~~~~20088  | NULL     |       0 |       1 |
  23 |
| 105 |      1 |        | ~~~~~20186  | NULL     |       0 |       1 |
  23 |
| 106 |      1 |        | ~~~~~74891  | NULL     |       0 |       1 |
  23 |



Now, here is a screenshot of the GUI for the same rules:
Note:  Rule 102 exists under peer group 23 for the GUI.
[image: Inline image 1]



It appears we should trust the data in the database and not the GUI, but
I'm assuming it is not desired behavior for the GUI and database to reflect
different info.

If you would like more information, we can share it.

Please let me know if there is anything we can do to ensure the GUI
reflects the actual activity of the database and ngcp/kamailio.

Thanks,

Gary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140801/6d896dc7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 30444 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140801/6d896dc7/attachment.png>

From sipwise.support at mtkom.de  Sat Aug  2 04:01:54 2014
From: sipwise.support at mtkom.de (Pascal Schwarz)
Date: Sat, 2 Aug 2014 10:01:54 +0200 (CEST)
Subject: [Spce-user] security bans / 403 Errror
In-Reply-To: <53DB9EB4.2090803@sipwise.com>
References: <alpine.DEB.2.10.1408011514080.32451@gucky>
 <53DB9EB4.2090803@sipwise.com>
Message-ID: <alpine.DEB.2.10.1408020959340.14896@jumpy>

Hello Daniel,

> An option is to increase the number of attempt from 3 to 6 for ex.
where can i change it ?

regards
Pascal



From dgrotti at sipwise.com  Sat Aug  2 04:06:05 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Sat, 02 Aug 2014 10:06:05 +0200
Subject: [Spce-user] security bans / 403 Errror
Message-ID: <20140802080631.1BC121502093@zimbra.sipwise.com>

Hi,
You can find ban configuration in the config.yml file.
After that run ngcpcfg apply.

Daniel

On 2 Aug 2014 10:01, Pascal Schwarz <sipwise.support at mtkom.de> wrote:
>
> Hello Daniel, 
>
> > An option is to increase the number of attempt from 3 to 6 for ex. 
> where can i change it ? 
>
> regards 
> Pascal 
>

From sipwise.support at mtkom.de  Sat Aug  2 04:16:32 2014
From: sipwise.support at mtkom.de (Pascal Schwarz)
Date: Sat, 2 Aug 2014 10:16:32 +0200 (CEST)
Subject: [Spce-user] default Ringtone
Message-ID: <alpine.DEB.2.10.1408021002340.14896@jumpy>

Hy All,

when I call on cell phone from the PSTN to spce Subscribers
then I get a rington with a frequency which is not common for Germany

can anyone explain where i can change this default Ringtone ?.

thanks
regards
pascal


From dgrotti at sipwise.com  Sat Aug  2 04:34:54 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Sat, 02 Aug 2014 10:34:54 +0200
Subject: [Spce-user] default Ringtone
Message-ID: <20140802083520.90D6A1502093@zimbra.sipwise.com>

Hi,
Spce doesn't generate any ringtones.
It could be generated by the called party inband or by the pstn provider.

Daniel

On 2 Aug 2014 10:16, Pascal Schwarz <sipwise.support at mtkom.de> wrote:
>
> Hy All, 
>
> when I call on cell phone from the PSTN to spce Subscribers 
> then I get a rington with a frequency which is not common for Germany 
>
> can anyone explain where i can change this default Ringtone ?. 
>
> thanks 
> regards 
> pascal 
> _______________________________________________ 
> Spce-user mailing list 
> Spce-user at lists.sipwise.com 
> https://lists.sipwise.com/listinfo/spce-user 

From sipwise.support at mtkom.de  Sat Aug  2 04:36:09 2014
From: sipwise.support at mtkom.de (Pascal Schwarz)
Date: Sat, 2 Aug 2014 10:36:09 +0200 (CEST)
Subject: [Spce-user] security bans / 403 Errror
In-Reply-To: <20140802080631.1BC121502093@zimbra.sipwise.com>
References: <20140802080631.1BC121502093@zimbra.sipwise.com>
Message-ID: <alpine.DEB.2.10.1408021029440.14896@jumpy>

Hy

>>> An option is to increase the number of attempt from 3 to 6 for ex.
>> where can i change it ?
@daniel thanks i changed it.

i don't understand why the authentifikation fails.
there is no changens on boths systems. so there is no reason
for authentifikation trouble .

regards
Pascal



From dgrotti at sipwise.com  Sat Aug  2 04:44:47 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Sat, 02 Aug 2014 10:44:47 +0200
Subject: [Spce-user] security bans / 403 Errror
Message-ID: <20140802084513.E8D031502093@zimbra.sipwise.com>

If you check the kamailio-proxy.log you can see the reason.

Daniel

On 2 Aug 2014 10:36, Pascal Schwarz <sipwise.support at mtkom.de> wrote:
>
> Hy 
>
> >>> An option is to increase the number of attempt from 3 to 6 for ex. 
> >> where can i change it ? 
> @daniel thanks i changed it. 
>
> i don't understand why the authentifikation fails. 
> there is no changens on boths systems. so there is no reason 
> for authentifikation trouble . 
>
> regards 
> Pascal 
>

From jward01 at gmail.com  Sat Aug  2 13:36:16 2014
From: jward01 at gmail.com (Jeremy Ward)
Date: Sat, 2 Aug 2014 13:36:16 -0400
Subject: [Spce-user] Question About Third-Party Asterisk Applications
In-Reply-To: <CAFfjrWp-wEUtbKXVn+31zN5v9Tyx1wMzJciv2dvVSfh8FRKQ0g@mail.gmail.com>
References: <CAFfjrWp-wEUtbKXVn+31zN5v9Tyx1wMzJciv2dvVSfh8FRKQ0g@mail.gmail.com>
Message-ID: <CAFfjrWrYzmbKtm7u6rbq-u+e=r1kEKj3dD7wiTOa5C4Gu6DFgQ@mail.gmail.com>

Greetings,

Is it possible to add third-party asterisk applications to SPCE? I ask
because we would like to add ACD/Queueing to the system.

Perhaps I missed this in the feature list, but does the system provide IVR
capabilities?

Thanks,

Jeremy D. Ward, CWNE
Neteligence Comnunications, Inc
(212) 901-5288
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140802/13d89777/attachment.html>

From paul.belanger at polybeacon.com  Sat Aug  2 14:10:29 2014
From: paul.belanger at polybeacon.com (Paul Belanger)
Date: Sat, 2 Aug 2014 14:10:29 -0400
Subject: [Spce-user] Question About Third-Party Asterisk Applications
In-Reply-To: <CAFfjrWrYzmbKtm7u6rbq-u+e=r1kEKj3dD7wiTOa5C4Gu6DFgQ@mail.gmail.com>
References: <CAFfjrWp-wEUtbKXVn+31zN5v9Tyx1wMzJciv2dvVSfh8FRKQ0g@mail.gmail.com>
 <CAFfjrWrYzmbKtm7u6rbq-u+e=r1kEKj3dD7wiTOa5C4Gu6DFgQ@mail.gmail.com>
Message-ID: <CALLKq0QWv0Zud_LarTdPtn4e89mti0zpxCX9jt7H6eSrX_PbpA@mail.gmail.com>

On Sat, Aug 2, 2014 at 1:36 PM, Jeremy Ward <jward01 at gmail.com> wrote:
> Greetings,
>
> Is it possible to add third-party asterisk applications to SPCE? I ask
> because we would like to add ACD/Queueing to the system.
>
> Perhaps I missed this in the feature list, but does the system provide IVR
> capabilities?
>
The issue you will have is because the phone are registered into
kamailio, app_queue will not be able to directly use their device
state.  The only way you could do something would be to write a bridge
between kamailio and asterisk to publish the state information about
the subscribers.  You'd use func_devicestate within asterisk.

-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger


From dgrotti at sipwise.com  Sat Aug  2 15:52:31 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Sat, 02 Aug 2014 21:52:31 +0200
Subject: [Spce-user] Question About Third-Party Asterisk Applications
Message-ID: <20140802195254.970AF1502098@zimbra.sipwise.com>

Hi Jeremy,
Ivr is a PBX feature and not a class 5.
Spce doesn't support a native ivr.
What you can do is to build your asterisk ivr outside ngcp and connect each others via sip trunk.

Otherwise you can move to our sip PRO version support a so called CloudPBX module, allowing you to handle pbx feature inside ngcp, such as ivr.

Regards,

Daniel

On 2 Aug 2014 19:36, Jeremy Ward <jward01 at gmail.com> wrote:
>
> Greetings,
>
> Is it possible to add third-party asterisk applications to SPCE? I ask because we would like to add ACD/Queueing to the system.
>
> Perhaps I missed this in the feature list, but does the system provide IVR capabilities?
>
> Thanks,
>
> Jeremy D. Ward, CWNE
> Neteligence Comnunications, Inc
> (212) 901-5288

From agranig at sipwise.com  Sat Aug  2 16:51:38 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Sat, 02 Aug 2014 22:51:38 +0200
Subject: [Spce-user] default Ringtone
In-Reply-To: <alpine.DEB.2.10.1408021002340.14896@jumpy>
References: <alpine.DEB.2.10.1408021002340.14896@jumpy>
Message-ID: <53DD4F5A.5040003@sipwise.com>

Hi,

On 08/02/2014 10:16 AM, Pascal Schwarz wrote:
> when I call on cell phone from the PSTN to spce Subscribers
> then I get a rington with a frequency which is not common for Germany
> 
> can anyone explain where i can change this default Ringtone ?.

You can't (on the server). Either your subscriber sends a 180 without
media, so the SPCE forwards the 180 to the gateway/peering-server, which
generates a ringtone (so if you have that gateway under your control,
you might be able to configure it there), or it sends a 183 with
early-media, which again (both in terms of signalling and media) is
forwarded to your gateway/peer, which play it to the caller as-is, so in
that case you might want to change your device your subscriber is using.

Andreas


From dgrotti at sipwise.com  Mon Aug  4 06:16:57 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Mon, 04 Aug 2014 12:16:57 +0200
Subject: [Spce-user] security bans / 403 Errror
In-Reply-To: <20140802084513.E8D031502093@zimbra.sipwise.com>
References: <20140802084513.E8D031502093@zimbra.sipwise.com>
Message-ID: <53DF5D99.9040508@sipwise.com>

Hi,
as I said in private, problem is that your user is trying to
authenticate with an old 'nonce'.
If you see "stale nonce" in the kamailio-proxy.log means, indeed, your
user is not using in the authenticate process the nonce provided by the
server.

This is a client issue.

Daniel




On 08/02/2014 10:44 AM, Daniel Grotti wrote:
> If you check the kamailio-proxy.log you can see the reason.
>
> Daniel
>
> On 2 Aug 2014 10:36, Pascal Schwarz <sipwise.support at mtkom.de> wrote:
>> Hy 
>>
>>>>> An option is to increase the number of attempt from 3 to 6 for ex. 
>>>> where can i change it ? 
>> @daniel thanks i changed it. 
>>
>> i don't understand why the authentifikation fails. 
>> there is no changens on boths systems. so there is no reason 
>> for authentifikation trouble . 
>>
>> regards 
>> Pascal 
>>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user



From j.fresneda at ibersontel.com  Mon Aug  4 06:29:33 2014
From: j.fresneda at ibersontel.com (Jorge Fresneda - Ibersontel)
Date: Mon, 04 Aug 2014 12:29:33 +0200
Subject: [Spce-user] Session-timers
In-Reply-To: <53DBAD5E.6090901@ibersontel.com>
References: <20140801145727.3EE911502088@zimbra.sipwise.com>
 <53DBAD5E.6090901@ibersontel.com>
Message-ID: <53DF608D.5090604@ibersontel.com>

Hello,
>
> I'm changed the sst_enable, but when receive a INVITE from carrier 
> with "session-expire=1800;refreshes=uac", the answer of sipwise is 200 
> ok. I would like that answer of sipwise with "session-expire=7200"
>
> Thanks,
> Regards
>
>
> El 01/08/2014 16:57, Daniel Grotti escribi?:
>> You can change it from web interface.
>> No apply is needed.
>>
>> On 1 Aug 2014 16:39, Jorge Fresneda - Ibersontel 
>> <j.fresneda at ibersontel.com> wrote:
>>> Hi,
>>>
>>> One question, When I change the sst_enable to "yes", is need execute
>>> "ngcpcfg apply"?????
>>>
>>> Thanks so much
>>> Regards,
>>> Jorge
>>>
>>>
>>>
>>> El 31/07/2014 13:41, Daniel Grotti escribi?:
>>>> Hi,
>>>> you can enable/disable session-timers on peer/subscribers preferences.
>>>>
>>>> Daniel
>>>>
>>>>
>>>>
>>>> On 07/31/2014 12:55 PM, Jorge Fresneda - Ibersontel wrote:
>>>>> Hello,
>>>>>
>>>>>
>>>>> I have a problem with session-timers. A carrier send me a
>>>>> "session-expire=1800;refresher=uac" header at 30 minutes and he 
>>>>> say me
>>>>> that I have enable the session-timer option. How I can do? I would 
>>>>> like
>>>>> to that session-option are enable on end-point and not in sipwise.
>>>>>
>>>>> Thank you so much,
>>>>> Regards
>>>>> Jorge
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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



From jbonilla at sipwise.com  Mon Aug  4 06:42:16 2014
From: jbonilla at sipwise.com (Jon Bonilla (Manwe))
Date: Mon, 4 Aug 2014 12:42:16 +0200
Subject: [Spce-user] Session-timers
In-Reply-To: <53DBAD5E.6090901@ibersontel.com>
References: <20140801145727.3EE911502088@zimbra.sipwise.com>
 <53DBAD5E.6090901@ibersontel.com>
Message-ID: <20140804124216.0f8701ab@quenya>

El Fri, 01 Aug 2014 17:08:14 +0200
Jorge Fresneda - Ibersontel <j.fresneda at ibersontel.com> escribi?:

> Oh, I'm sorry:
> 
> I'm changed the sst_enable, but when receive a INVITE from carrier with 
> "session-expire=1800;refreshes=uac", the answer of sipwise is 200 ok. I 
> would like that answer of sipwise with "session-expire=7200"
> 
> 

Then you need to set min_se to something higher. 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140804/1d6a5b1c/attachment.asc>

From matthew at tenacit.net  Mon Aug  4 07:48:49 2014
From: matthew at tenacit.net (Matthew Ogden)
Date: Mon, 4 Aug 2014 13:48:49 +0200
Subject: [Spce-user] security bans / 403 Errror
In-Reply-To: <53DF5D99.9040508@sipwise.com>
References: <20140802084513.E8D031502093@zimbra.sipwise.com>
 <53DF5D99.9040508@sipwise.com>
Message-ID: <d85d4c7d6795addecfe54b5f317e24bf@mail.gmail.com>

Hi Daniel,

You guys gave me a workaround for the stalenonce on the lists as well:
http://lists.sipwise.com/pipermail/spce-user/2014-January/005712.html

(Asterisk bug in my case).

Regards

-----Original Message-----
From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of
Daniel Grotti
Sent: 04 August 2014 12:17 PM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] security bans / 403 Errror

Hi,
as I said in private, problem is that your user is trying to authenticate
with an old 'nonce'.
If you see "stale nonce" in the kamailio-proxy.log means, indeed, your
user is not using in the authenticate process the nonce provided by the
server.

This is a client issue.

Daniel




On 08/02/2014 10:44 AM, Daniel Grotti wrote:
> If you check the kamailio-proxy.log you can see the reason.
>
> Daniel
>
> On 2 Aug 2014 10:36, Pascal Schwarz <sipwise.support at mtkom.de> wrote:
>> Hy
>>
>>>>> An option is to increase the number of attempt from 3 to 6 for ex.
>>>> where can i change it ?
>> @daniel thanks i changed it.
>>
>> i don't understand why the authentifikation fails.
>> there is no changens on boths systems. so there is no reason for
>> authentifikation trouble .
>>
>> regards
>> Pascal
>>
> _______________________________________________
> 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


From alutay at sipwise.com  Tue Aug  5 12:05:34 2014
From: alutay at sipwise.com (Alex Lutay)
Date: Tue, 05 Aug 2014 18:05:34 +0200
Subject: [Spce-user] New sip:provider CE mr3.4.1 available
Message-ID: <53E100CE.30609@sipwise.com>

Hi all,

This is to inform community about availability of the new spce mr3.4.1:

Please check the release notes here:
https://www.sipwise.com/news/announcements/sipprovider-mr3-4-1-released/

Thanks for your bugreports and feedback!

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From mprokop at sipwise.com  Tue Aug  5 15:24:11 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Tue, 5 Aug 2014 21:24:11 +0200
Subject: [Spce-user] New sip:provider CE features: install CD,
	EC2 AMI + Docker support
Message-ID: <2014-08-05T21-14-20@devnull.michael-prokop.at>

Hi,

our release notes for sip:provider CE mr3.4.1 at
https://www.sipwise.com/news/announcements/sipprovider-mr3-4-1-released/
already mention it, but I'd like to highlight three features where
we're especially interested in community feedback.

1) Sipwise NGCP install CD
https://www.sipwise.com/doc/mr3.4.1/spce/ar01s04.html#_using_the_ngcp_install_cd_recommended

This is the initial public release of our deployment system, being
based on what we use internally since several years. It's based on
the Grml live system (<http://grml.org/>) and provides a straight
forward way to install sip:provider CE in an automated fashion (or
also just plain Debian, and while at it you also get the option to
use a full featured live rescue system with it too).

2) Amazon EC2 AMI

The creation of sip:provider CE AMIs for usage on Amazon EC2 is
fully automated in our release process and we plan to provide
updated AMIs with each new sip:provider CE release. We even made
some of the scripts we use for AMI generation available to the
public: https://github.com/sipwise/ec2-tools

We plan to provide some more documentation about usage of our AMIs
on EC2 soon, in the meanwhile just launch the latest mr3.4.1 release
via https://console.aws.amazon.com/ec2/v2/home?region=eu-west-1#LaunchInstanceWizard:ami=ami-0bb6657c

3) Docker support

Starting with the mr3.4.1 release we provide initial docker support
for sip:provider CE. Generating the docker images is also part of
our automated release process, so we plan to provide updated docker
images for each new sip:provider CE release too. The documentation
is still on our agenda, but if you are familiar with docker or feel
like you'd like to play with it anyway please feel invited to do so:
https://registry.hub.docker.com/repos/sipwise/

If you should notice *any* problems with the install CD, the AMI(s)
or the Docker images please let us know, we appreciate any feedback.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140805/2e3ea7e4/attachment.asc>

From aalejandro at alliedtechnologygrouppr.com  Wed Aug  6 01:58:34 2014
From: aalejandro at alliedtechnologygrouppr.com (Abel Alejandro)
Date: Wed, 6 Aug 2014 01:58:34 -0400
Subject: [Spce-user] No PSTN gateways available when using *31* to hide CLIR
Message-ID: <CAKiNg22=aFv6KTYoPRK45yighLrS3Gfci4jBYKzftA67=Sgx5Q@mail.gmail.com>

Hello,

I am testing using *31* to hide the CLIR. However any number I call
(subscriber or peer) it gives me the same error. Is there something I
need to enable to use this code?


Aug  6 01:54:22 sip proxy[4231]: NOTICE: <script>: Contacts
successfully updated, expires in 60s - R=sip:sip.fusetelecom.com
ID=14269cb16fb84fda790fb6d1011c2899 at 127.0.0.1
Aug  6 01:54:27 sip proxy[4231]: NOTICE: <script>: New request -
M=REGISTER R=sip:sip.alliedtechpr.com
F=sip:alliedtech at sip.alliedtechpr.com
T=sip:alliedtech at sip.alliedtechpr.com IP=38.87.235.182:5060
(127.0.0.1:5060) ID=29fc3e6f7e7b02af4cc2c5b201a895f1 at 127.0.0.1
Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: New request -
M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
F=sip:aalejandro at sip.alliedtechpr.com:5060
T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
(127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: Authentication
failed, no credentials -
R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: New request -
M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
F=sip:aalejandro at sip.alliedtechpr.com:5060
T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
(127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-Provided CLI
'aalejandro' taken from From-User -
R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-provided CLI
'aalejandro' rejected, using network-provided CLI '17879190810' -
R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
'17879190810 at sip.alliedtechpr.com' as initiating user-provided CLI -
R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
'17879190810 at sip.alliedtechpr.com' as initiating network-provided CLI
- R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Per-call CLIR
enabled - R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Callee is not local
- R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Call to SIP Peering
- R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Load gws matching
calling part 'sip:17879190810 at sip.alliedtechpr.com' and called user
'7877050555' and called part
'sip:7877050555 at sip.alliedtechpr.com:5060' -
R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: ERROR: <script>: No PSTN gateways
available - R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
source-leg for uuid '1c62f6c2-cc4e-41a3-b0f2-140ead720f14':
'1c62f6c2-cc4e-41a3-b0f2-140ead720f14|aalejandro|sip.alliedtechpr.com|17879190810|17879190810|Allied
Technology|10|||1|call|24.55.105.153|1407304467.351906' -
R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
destination-leg for uuid '0':
'0|||0|*31*7877050555|0|7877050555|sip.alliedtechpr.com|7877050555|sip.alliedtechpr.com'
- R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.


-- 
Abel Alejandro

787 586 8313 | 787 705 0555

400 Calle Calaf 477
San Juan, PR 00918
aalejandro at alliedtechnologygrouppr.com


From dgrotti at sipwise.com  Wed Aug  6 02:11:29 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Wed, 06 Aug 2014 08:11:29 +0200
Subject: [Spce-user] No PSTN gateways available when using *31* to hide
 CLIR
Message-ID: <20140806061158.B2E72150208F@zimbra.sipwise.com>

Hi,
Problem is you don't have any peering rules matching the number 7877050555.

Daniel

On 6 Aug 2014 07:58, Abel Alejandro <aalejandro at alliedtechnologygrouppr.com> wrote:
>
> Hello, 
>
> I am testing using *31* to hide the CLIR. However any number I call 
> (subscriber or peer) it gives me the same error. Is there something I 
> need to enable to use this code? 
>
>
> Aug? 6 01:54:22 sip proxy[4231]: NOTICE: <script>: Contacts 
> successfully updated, expires in 60s - R=sip:sip.fusetelecom.com 
> ID=14269cb16fb84fda790fb6d1011c2899 at 127.0.0.1 
> Aug? 6 01:54:27 sip proxy[4231]: NOTICE: <script>: New request - 
> M=REGISTER R=sip:sip.alliedtechpr.com 
> F=sip:alliedtech at sip.alliedtechpr.com 
> T=sip:alliedtech at sip.alliedtechpr.com IP=38.87.235.182:5060 
> (127.0.0.1:5060) ID=29fc3e6f7e7b02af4cc2c5b201a895f1 at 127.0.0.1 
> Aug? 6 01:54:27 sip proxy[4217]: NOTICE: <script>: New request - 
> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> F=sip:aalejandro at sip.alliedtechpr.com:5060 
> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494 
> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4217]: NOTICE: <script>: Authentication 
> failed, no credentials - 
> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: New request - 
> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> F=sip:aalejandro at sip.alliedtechpr.com:5060 
> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494 
> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-Provided CLI 
> 'aalejandro' taken from From-User - 
> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-provided CLI 
> 'aalejandro' rejected, using network-provided CLI '17879190810' - 
> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting 
> '17879190810 at sip.alliedtechpr.com' as initiating user-provided CLI - 
> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting 
> '17879190810 at sip.alliedtechpr.com' as initiating network-provided CLI 
> - R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Per-call CLIR 
> enabled - R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Callee is not local 
> - R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Call to SIP Peering 
> - R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Load gws matching 
> calling part 'sip:17879190810 at sip.alliedtechpr.com' and called user 
> '7877050555' and called part 
> 'sip:7877050555 at sip.alliedtechpr.com:5060' - 
> R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: ERROR: <script>: No PSTN gateways 
> available - R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc 
> source-leg for uuid '1c62f6c2-cc4e-41a3-b0f2-140ead720f14': 
> '1c62f6c2-cc4e-41a3-b0f2-140ead720f14|aalejandro|sip.alliedtechpr.com|17879190810|17879190810|Allied 
> Technology|10|||1|call|24.55.105.153|1407304467.351906' - 
> R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc 
> destination-leg for uuid '0': 
> '0|||0|*31*7877050555|0|7877050555|sip.alliedtechpr.com|7877050555|sip.alliedtechpr.com' 
> - R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
>
>
> -- 
> Abel Alejandro 
>
> 787 586 8313 | 787 705 0555 
>
> 400 Calle Calaf 477 
> San Juan, PR 00918 
> aalejandro at alliedtechnologygrouppr.com 
> _______________________________________________ 
> Spce-user mailing list 
> Spce-user at lists.sipwise.com 
> https://lists.sipwise.com/listinfo/spce-user 

From aalejandro at alliedtechnologygrouppr.com  Wed Aug  6 07:32:15 2014
From: aalejandro at alliedtechnologygrouppr.com (Abel Alejandro)
Date: Wed, 6 Aug 2014 07:32:15 -0400
Subject: [Spce-user] No PSTN gateways available when using *31* to hide
	CLIR
In-Reply-To: <20140806061158.B2E72150208F@zimbra.sipwise.com>
References: <20140806061158.B2E72150208F@zimbra.sipwise.com>
Message-ID: <CAKiNg22g5qJ3zXp+oJ7R_Z+Z37J=20Z7gW7QDz-pjsu+F=tpzw@mail.gmail.com>

Hello,

Thats actually a subscriber. If I dial 7877050555 it works fine.
However if I dial *31*7877050555 it doesn't work.
The same thing happens with a number that goes thru a peer.

Abel.


On Wed, Aug 6, 2014 at 2:11 AM, Daniel Grotti <dgrotti at sipwise.com> wrote:
> Hi,
> Problem is you don't have any peering rules matching the number 7877050555.
>
> Daniel
>
> On 6 Aug 2014 07:58, Abel Alejandro <aalejandro at alliedtechnologygrouppr.com> wrote:
>>
>> Hello,
>>
>> I am testing using *31* to hide the CLIR. However any number I call
>> (subscriber or peer) it gives me the same error. Is there something I
>> need to enable to use this code?
>>
>>
>> Aug  6 01:54:22 sip proxy[4231]: NOTICE: <script>: Contacts
>> successfully updated, expires in 60s - R=sip:sip.fusetelecom.com
>> ID=14269cb16fb84fda790fb6d1011c2899 at 127.0.0.1
>> Aug  6 01:54:27 sip proxy[4231]: NOTICE: <script>: New request -
>> M=REGISTER R=sip:sip.alliedtechpr.com
>> F=sip:alliedtech at sip.alliedtechpr.com
>> T=sip:alliedtech at sip.alliedtechpr.com IP=38.87.235.182:5060
>> (127.0.0.1:5060) ID=29fc3e6f7e7b02af4cc2c5b201a895f1 at 127.0.0.1
>> Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: New request -
>> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> F=sip:aalejandro at sip.alliedtechpr.com:5060
>> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
>> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: Authentication
>> failed, no credentials -
>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: New request -
>> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> F=sip:aalejandro at sip.alliedtechpr.com:5060
>> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
>> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-Provided CLI
>> 'aalejandro' taken from From-User -
>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-provided CLI
>> 'aalejandro' rejected, using network-provided CLI '17879190810' -
>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
>> '17879190810 at sip.alliedtechpr.com' as initiating user-provided CLI -
>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
>> '17879190810 at sip.alliedtechpr.com' as initiating network-provided CLI
>> - R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Per-call CLIR
>> enabled - R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Callee is not local
>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Call to SIP Peering
>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Load gws matching
>> calling part 'sip:17879190810 at sip.alliedtechpr.com' and called user
>> '7877050555' and called part
>> 'sip:7877050555 at sip.alliedtechpr.com:5060' -
>> R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: ERROR: <script>: No PSTN gateways
>> available - R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
>> source-leg for uuid '1c62f6c2-cc4e-41a3-b0f2-140ead720f14':
>> '1c62f6c2-cc4e-41a3-b0f2-140ead720f14|aalejandro|sip.alliedtechpr.com|17879190810|17879190810|Allied
>> Technology|10|||1|call|24.55.105.153|1407304467.351906' -
>> R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
>> destination-leg for uuid '0':
>> '0|||0|*31*7877050555|0|7877050555|sip.alliedtechpr.com|7877050555|sip.alliedtechpr.com'
>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>
>>
>> --
>> Abel Alejandro
>>
>> 787 586 8313 | 787 705 0555
>>
>> 400 Calle Calaf 477
>> San Juan, PR 00918
>> aalejandro at alliedtechnologygrouppr.com
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user



-- 
Abel Alejandro

787 586 8313 | 787 705 0555

400 Calle Calaf 477
San Juan, PR 00918
aalejandro at alliedtechnologygrouppr.com


From kmasse at questblue.com  Wed Aug  6 07:54:41 2014
From: kmasse at questblue.com (Kevin Masse)
Date: Wed, 6 Aug 2014 07:54:41 -0400
Subject: [Spce-user] Subscriber Alias Entries in Database
References: <CEEE718799582B47A55D7897DCB264FC3F5E18@bvusaex.bestvoipusa.local><53C652BD.7000707@sipwise.com>
 <CEEE718799582B47A55D7897DCB264FC3F5E65@bvusaex.bestvoipusa.local>
 <CEEE718799582B47A55D7897DCB264FC3F5F7F@bvusaex.bestvoipusa.local>
Message-ID: <CEEE718799582B47A55D7897DCB264FC3F60D6@bvusaex.bestvoipusa.local>

Hello, I was wondering if there was a response to this that I missed.
There are two specific questions we are trying to answer.


Thank you
Kevin



-----Original Message-----
From: Kevin Masse 
Sent: Thursday, July 24, 2014 10:02 AM
To: Kevin Masse; Andreas Granig; spce-user at lists.sipwise.com
Subject: RE: [Spce-user] Subscriber Alias Entries in Database

Andraes one additional scenario has come up based on our last thread:
I wanted to post to the group the question from our dev team:

****  Begin Comment ****
It is going to be a long post because I can't explain in a short
message. I'll provide some example to explain what I mean. 

We have SIP named QBATRUNK.  If you open administrator page
(https://DOMAIN:1443/subscriber/detail?subscriber_id=395) you can see
there following info:

Contract ID (405) - This is main ID which we store in (customer site -
not part of Sipwise it is our Database) . All operations like
lock/unlock SIP, add/remove DID using the ID in it request to API.

Subscriber ID (395) - I can call it internal info, it is not used in any
request to Sipwise API but to make direct request to Sipwise DB I have
to use it.

I routed 3384066 DID to the SIP to work with the example. 
According to previous instructions we use two databases to store
aliases. Now I'll show you request to retrieve the DID from Sipwise DB.

First I use billing DB. Let's retrieve Subscriber ID (we do not know it
when call DB directly). I use voip_subscribers table which stores the
info.

mysql> select * from voip_subscribers where contract_id = 405;
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+
| id | contract_id | uuid | username | domain_id | status |
primary_number_id | external_id |
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+
| 395 | 405 | 14a58c84-c83e-4673-9d10-361a1a6b990e | QBATRUNK | 1 |
active | NULL | NULL |
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+

OK you can see that I receive id 395. We need it.

 

Let's get DIDs info from voip_numbers, DB - 

mysql> select * from voip_numbers where subscriber_id = 395;
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+
| id | cc | ac | sn | reseller_id | subscriber_id | status | ported |
list_timestamp |
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+
| 2119 | 1 | 910 | 3384066 | NULL | 395 | active | 1 | 2014-07-22
18:32:16 |
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+

Everything is OK we got it as expected. Lets' get DID info from second
DB (provisioning) I'll do it using DID number

mysql> select * from voip_dbaliases where username like '%3384066%';
+------+-------------+-----------+---------------+
| id | username | domain_id | subscriber_id |
+------+-------------+-----------+---------------+
| 2821 | 19103384066 | 3 | 398 |

As you can see subscriber_id in the table does not corresponds to the
subscriber_id which we retrieve from billing DB. That is the question
for me.

I found that the subscriber_id is stored in voip_dbaliases table but the
ID does not corresponds to the subscriber_id from billing table.

Question 1
I do not understand how subscriber_id in billing DB (table voip_numbers)
related with subscriber_id in provisioning DB (table voip_dbaliases ).

Question 2
Another question. I found that DIDs info is stored in voip_dbaliases
table (provisioning) but I did not told to creae the record by VoIP
specialist.

mysql> select * from voip_dbaliases where username like '%3384066%';
+------+-------------+-----------+---------------+
| id | username | domain_id | subscriber_id |
+------+-------------+-----------+---------------+
| 2821 | 19103384066 | 3 | 398 |
+------+-------------+-----------+---------------+

Hopefully I explained my questions clear. If not please let me know

Thanks,
*** End Comment from DEV ***



In conclusion Andreas do you think there is a proper answer for the
above Question 1 and Question 2?
Thank you
Kevin 





-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Kevin Masse
Sent: Wednesday, July 16, 2014 8:56 AM
To: Andreas Granig; spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Subscriber Alias Entries in Database

Thank you Andreas, I appreciate the detailed response.  Works as
described.
Kevin



-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Andreas Granig
Sent: Wednesday, July 16, 2014 6:24 AM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Subscriber Alias Entries in Database

Hi,

On 07/15/2014 03:05 PM, Kevin Masse wrote:

> **  Current operation:   We use SOAP to add alias numbers to a
subscriber 
> 
> Requested operation:  We would like to write a new alias number for a 
> subscriber directly to the database.

As long as you make sure to write it to both billing.voip_numbers and
provisioning.voip_dbaliases, it should be fine.

Andreas

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/listinfo/spce-user

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/listinfo/spce-user


From mstorck at voipgate.com  Wed Aug  6 08:02:12 2014
From: mstorck at voipgate.com (Marc Storck)
Date: Wed, 6 Aug 2014 12:02:12 +0000
Subject: [Spce-user] change of IP address
Message-ID: <44D6B68F-59E4-46E3-B2BD-65371E9220F7@voipgate.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Good afternoon,

I need to change the IP address of a system (*NOT* the domain name). I tried seraching for instruction but I wasn?t successful.

Could someone please point me into the right direction?

Best regards,

Marc
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJT4hnIAAoJEBqZdpQUXtTCvhAP/1qrA08tWkgjl+wKtOU3tBV2
vLo2uK9xX0guTbMiZ3rAAwZ2hmpqfsbZ8nAXj4+PLo6h7P5oM4boiiAWg6CGg4DM
XWgX9hEHIlvHF27OdOj/pmP2UfFC9MRfcKfIvU+7fCcGn9Mt+6WlfEHalbUOgbIq
XrTyWRAgob1WEwQnlpTz9fwzqQ+idUBdHheSa3r9LyabrCHktLx8nQA0ZxkH9AUR
kp5gbWRlAATPHqzGaSkbAy2CVFRmHGjc3ELG0d/1KbEgoz2BnWT3rX7yevnM7q7a
ZSVaIS85UdnnL1nBggSYk54H8ybF5wphN5746AYLh89jqbiqoRDooSAwAyUEvG0J
NYw7Ft0qSDCGaQb982zgOQbkZeG2Qv1j1sRpX6bZjfia+zLjZq8jVl+Aquzyaerm
9tOh/abxWymvXutnT0Begl+snWph94kQr+HFl3VnHeycd6HiaXh3jCSO1g00LxZu
W0OEgbvPjFanIm+qAzRFfBo+MuHkpXxhY19TlJRYP1k3aGBeiP+CxqAzH63mcOiE
Vf2rSaY0jYrc43P/cjaEEpe8drE47NRmCTgH5qR0nn2yh/vfYi6XI6tkc+aTeZ2F
KBjKt501DBDGfiEBT/qcC8ezb8KxB82qbSgMqxaY69oB7158uEnKURuW/zGgmh6c
i9zbbfSGr53Nf4YREP7F
=m8Fr
-----END PGP SIGNATURE-----

From vseva at sipwise.com  Wed Aug  6 08:12:38 2014
From: vseva at sipwise.com (Victor Seva)
Date: Wed, 06 Aug 2014 14:12:38 +0200
Subject: [Spce-user] change of IP address
In-Reply-To: <44D6B68F-59E4-46E3-B2BD-65371E9220F7@voipgate.com>
References: <44D6B68F-59E4-46E3-B2BD-65371E9220F7@voipgate.com>
Message-ID: <53E21BB6.4030701@sipwise.com>

On 08/06/2014 02:02 PM, Marc Storck wrote:
> Good afternoon,
> 
> I need to change the IP address of a system (*NOT* the domain name). I tried seraching for instruction but I wasn?t successful.
> 
> Could someone please point me into the right direction?

https://www.sipwise.com/doc/mr3.4.1/spce/ar01s05.html#_network_configuration



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140806/201a7302/attachment.asc>

From aalejandro at alliedtechnologygrouppr.com  Wed Aug  6 08:26:19 2014
From: aalejandro at alliedtechnologygrouppr.com (Abel Alejandro)
Date: Wed, 6 Aug 2014 08:26:19 -0400
Subject: [Spce-user] No PSTN gateways available when using *31* to hide
	CLIR
In-Reply-To: <CAKiNg22g5qJ3zXp+oJ7R_Z+Z37J=20Z7gW7QDz-pjsu+F=tpzw@mail.gmail.com>
References: <20140806061158.B2E72150208F@zimbra.sipwise.com>
 <CAKiNg22g5qJ3zXp+oJ7R_Z+Z37J=20Z7gW7QDz-pjsu+F=tpzw@mail.gmail.com>
Message-ID: <CAKiNg201dJE1EfYnGbGpU5anTR-5JKgCQHKB6QL1tQGq_HVbfA@mail.gmail.com>

I see what happened now. If I use *31* the rewrite rules wont work. I
guess I need to account for the service codes in the rewrite rules as
well, yes?
I thought the *31* would be like a special code and hidden from the
system as soon as it entered.

Thanks.


On Wed, Aug 6, 2014 at 7:32 AM, Abel Alejandro
<aalejandro at alliedtechnologygrouppr.com> wrote:
> Hello,
>
> Thats actually a subscriber. If I dial 7877050555 it works fine.
> However if I dial *31*7877050555 it doesn't work.
> The same thing happens with a number that goes thru a peer.
>
> Abel.
>
>
> On Wed, Aug 6, 2014 at 2:11 AM, Daniel Grotti <dgrotti at sipwise.com> wrote:
>> Hi,
>> Problem is you don't have any peering rules matching the number 7877050555.
>>
>> Daniel
>>
>> On 6 Aug 2014 07:58, Abel Alejandro <aalejandro at alliedtechnologygrouppr.com> wrote:
>>>
>>> Hello,
>>>
>>> I am testing using *31* to hide the CLIR. However any number I call
>>> (subscriber or peer) it gives me the same error. Is there something I
>>> need to enable to use this code?
>>>
>>>
>>> Aug  6 01:54:22 sip proxy[4231]: NOTICE: <script>: Contacts
>>> successfully updated, expires in 60s - R=sip:sip.fusetelecom.com
>>> ID=14269cb16fb84fda790fb6d1011c2899 at 127.0.0.1
>>> Aug  6 01:54:27 sip proxy[4231]: NOTICE: <script>: New request -
>>> M=REGISTER R=sip:sip.alliedtechpr.com
>>> F=sip:alliedtech at sip.alliedtechpr.com
>>> T=sip:alliedtech at sip.alliedtechpr.com IP=38.87.235.182:5060
>>> (127.0.0.1:5060) ID=29fc3e6f7e7b02af4cc2c5b201a895f1 at 127.0.0.1
>>> Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: New request -
>>> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> F=sip:aalejandro at sip.alliedtechpr.com:5060
>>> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
>>> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: Authentication
>>> failed, no credentials -
>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: New request -
>>> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> F=sip:aalejandro at sip.alliedtechpr.com:5060
>>> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
>>> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-Provided CLI
>>> 'aalejandro' taken from From-User -
>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-provided CLI
>>> 'aalejandro' rejected, using network-provided CLI '17879190810' -
>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
>>> '17879190810 at sip.alliedtechpr.com' as initiating user-provided CLI -
>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
>>> '17879190810 at sip.alliedtechpr.com' as initiating network-provided CLI
>>> - R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Per-call CLIR
>>> enabled - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Callee is not local
>>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Call to SIP Peering
>>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Load gws matching
>>> calling part 'sip:17879190810 at sip.alliedtechpr.com' and called user
>>> '7877050555' and called part
>>> 'sip:7877050555 at sip.alliedtechpr.com:5060' -
>>> R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: ERROR: <script>: No PSTN gateways
>>> available - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
>>> source-leg for uuid '1c62f6c2-cc4e-41a3-b0f2-140ead720f14':
>>> '1c62f6c2-cc4e-41a3-b0f2-140ead720f14|aalejandro|sip.alliedtechpr.com|17879190810|17879190810|Allied
>>> Technology|10|||1|call|24.55.105.153|1407304467.351906' -
>>> R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
>>> destination-leg for uuid '0':
>>> '0|||0|*31*7877050555|0|7877050555|sip.alliedtechpr.com|7877050555|sip.alliedtechpr.com'
>>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>
>>>
>>> --
>>> Abel Alejandro
>>>
>>> 787 586 8313 | 787 705 0555
>>>
>>> 400 Calle Calaf 477
>>> San Juan, PR 00918
>>> aalejandro at alliedtechnologygrouppr.com
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>
>
>
> --
> Abel Alejandro
>
> 787 586 8313 | 787 705 0555
>
> 400 Calle Calaf 477
> San Juan, PR 00918
> aalejandro at alliedtechnologygrouppr.com



-- 
Abel Alejandro

787 586 8313 | 787 705 0555

400 Calle Calaf 477
San Juan, PR 00918
aalejandro at alliedtechnologygrouppr.com


From dgrotti at sipwise.com  Wed Aug  6 08:32:17 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Wed, 06 Aug 2014 14:32:17 +0200
Subject: [Spce-user] No PSTN gateways available when using *31* to hide
 CLIR
In-Reply-To: <CAKiNg201dJE1EfYnGbGpU5anTR-5JKgCQHKB6QL1tQGq_HVbfA@mail.gmail.com>
References: <20140806061158.B2E72150208F@zimbra.sipwise.com>	<CAKiNg22g5qJ3zXp+oJ7R_Z+Z37J=20Z7gW7QDz-pjsu+F=tpzw@mail.gmail.com>
 <CAKiNg201dJE1EfYnGbGpU5anTR-5JKgCQHKB6QL1tQGq_HVbfA@mail.gmail.com>
Message-ID: <53E22051.1020200@sipwise.com>

Hi,
yes you should rewrite the call first

*31*7877050555 ---> *31*e164-number


Daniel




On 08/06/2014 02:26 PM, Abel Alejandro wrote:
> I see what happened now. If I use *31* the rewrite rules wont work. I
> guess I need to account for the service codes in the rewrite rules as
> well, yes?
> I thought the *31* would be like a special code and hidden from the
> system as soon as it entered.
>
> Thanks.
>
>
> On Wed, Aug 6, 2014 at 7:32 AM, Abel Alejandro
> <aalejandro at alliedtechnologygrouppr.com> wrote:
>> Hello,
>>
>> Thats actually a subscriber. If I dial 7877050555 it works fine.
>> However if I dial *31*7877050555 it doesn't work.
>> The same thing happens with a number that goes thru a peer.
>>
>> Abel.
>>
>>
>> On Wed, Aug 6, 2014 at 2:11 AM, Daniel Grotti <dgrotti at sipwise.com> wrote:
>>> Hi,
>>> Problem is you don't have any peering rules matching the number 7877050555.
>>>
>>> Daniel
>>>
>>> On 6 Aug 2014 07:58, Abel Alejandro <aalejandro at alliedtechnologygrouppr.com> wrote:
>>>> Hello,
>>>>
>>>> I am testing using *31* to hide the CLIR. However any number I call
>>>> (subscriber or peer) it gives me the same error. Is there something I
>>>> need to enable to use this code?
>>>>
>>>>
>>>> Aug  6 01:54:22 sip proxy[4231]: NOTICE: <script>: Contacts
>>>> successfully updated, expires in 60s - R=sip:sip.fusetelecom.com
>>>> ID=14269cb16fb84fda790fb6d1011c2899 at 127.0.0.1
>>>> Aug  6 01:54:27 sip proxy[4231]: NOTICE: <script>: New request -
>>>> M=REGISTER R=sip:sip.alliedtechpr.com
>>>> F=sip:alliedtech at sip.alliedtechpr.com
>>>> T=sip:alliedtech at sip.alliedtechpr.com IP=38.87.235.182:5060
>>>> (127.0.0.1:5060) ID=29fc3e6f7e7b02af4cc2c5b201a895f1 at 127.0.0.1
>>>> Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: New request -
>>>> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> F=sip:aalejandro at sip.alliedtechpr.com:5060
>>>> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
>>>> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: Authentication
>>>> failed, no credentials -
>>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: New request -
>>>> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> F=sip:aalejandro at sip.alliedtechpr.com:5060
>>>> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
>>>> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-Provided CLI
>>>> 'aalejandro' taken from From-User -
>>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-provided CLI
>>>> 'aalejandro' rejected, using network-provided CLI '17879190810' -
>>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
>>>> '17879190810 at sip.alliedtechpr.com' as initiating user-provided CLI -
>>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
>>>> '17879190810 at sip.alliedtechpr.com' as initiating network-provided CLI
>>>> - R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Per-call CLIR
>>>> enabled - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Callee is not local
>>>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Call to SIP Peering
>>>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Load gws matching
>>>> calling part 'sip:17879190810 at sip.alliedtechpr.com' and called user
>>>> '7877050555' and called part
>>>> 'sip:7877050555 at sip.alliedtechpr.com:5060' -
>>>> R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: ERROR: <script>: No PSTN gateways
>>>> available - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
>>>> source-leg for uuid '1c62f6c2-cc4e-41a3-b0f2-140ead720f14':
>>>> '1c62f6c2-cc4e-41a3-b0f2-140ead720f14|aalejandro|sip.alliedtechpr.com|17879190810|17879190810|Allied
>>>> Technology|10|||1|call|24.55.105.153|1407304467.351906' -
>>>> R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
>>>> destination-leg for uuid '0':
>>>> '0|||0|*31*7877050555|0|7877050555|sip.alliedtechpr.com|7877050555|sip.alliedtechpr.com'
>>>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>>
>>>>
>>>> --
>>>> Abel Alejandro
>>>>
>>>> 787 586 8313 | 787 705 0555
>>>>
>>>> 400 Calle Calaf 477
>>>> San Juan, PR 00918
>>>> aalejandro at alliedtechnologygrouppr.com
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com
>>>> https://lists.sipwise.com/listinfo/spce-user
>>
>>
>> --
>> Abel Alejandro
>>
>> 787 586 8313 | 787 705 0555
>>
>> 400 Calle Calaf 477
>> San Juan, PR 00918
>> aalejandro at alliedtechnologygrouppr.com
>
>



From rabs at dimension-virtual.com  Thu Aug  7 08:19:53 2014
From: rabs at dimension-virtual.com (=?iso-8859-1?B?UmHDumw=?= Alexis Betancor Santana)
Date: Thu, 7 Aug 2014 13:19:53 +0100
Subject: [Spce-user] MySQL errors
Message-ID: <20140807121952.GA23093@salma.divi.prv>

Hi all, since we upgrades a test system from 3.2 to mr3.3 and
yesterday to mr3.4.1 this is getting worst:

Aug  7 14:18:56 sipapp01 proxy[16074]: ERROR: db_mysql
[km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Lost
connection to MySQL server during query
Aug  7 14:18:56 sipapp01 proxy[16074]: ERROR: <core> [db_query.c:337]:
db_do_update(): error while submitting query
Aug  7 14:18:56 sipapp01 proxy[16074]: ERROR: usrloc [ucontact.c:815]:
db_update_ucontact_addr(): updating database failed
Aug  7 14:18:56 sipapp01 proxy[16074]: ERROR: usrloc
[ucontact.c:1502]: update_ucontact(): failed to update database
Aug  7 14:18:56 sipapp01 proxy[16074]: ERROR: registrar [save.c:775]:
update_contacts(): failed to update contact
Aug  7 14:18:56 sipapp01 proxy[16077]: ERROR: db_mysql
[km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Lost
connection to MySQL server during query
Aug  7 14:18:56 sipapp01 proxy[16077]: ERROR: <core> [db_query.c:337]:
db_do_update(): error while submitting query
Aug  7 14:18:56 sipapp01 proxy[16077]: ERROR: usrloc [ucontact.c:815]:
db_update_ucontact_addr(): updating database failed
Aug  7 14:18:56 sipapp01 proxy[16077]: ERROR: usrloc
[ucontact.c:1502]: update_ucontact(): failed to update database
Aug  7 14:18:56 sipapp01 proxy[16077]: ERROR: registrar [save.c:775]:
update_contacts(): failed to update contact
Aug  7 14:18:57 sipapp01 proxy[16083]: ERROR: db_mysql
[km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Lost
connection to MySQL server during query
Aug  7 14:18:57 sipapp01 proxy[16083]: ERROR: <core> [db_query.c:337]:
db_do_update(): error while submitting query
Aug  7 14:18:57 sipapp01 proxy[16083]: ERROR: usrloc [ucontact.c:815]:
db_update_ucontact_addr(): updating database failed
Aug  7 14:18:57 sipapp01 proxy[16083]: ERROR: usrloc
[ucontact.c:1502]: update_ucontact(): failed to update database
Aug  7 14:18:57 sipapp01 proxy[16083]: ERROR: registrar [save.c:775]:
update_contacts(): failed to update contact


Also notice a lot of 'slow queries' on the logs of mysql.

Test system it's a  dual Intel(R) Xeon(R) CPU E5420  @ 2.50GHz, with 4
cores each CPU and 16Gb of RAM.

There is also errors about ACC inserts:

Aug  7 14:21:10 sipapp01 proxy[16085]: ERROR: db_mysql
[km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Lost
connection to MySQL server duri
ng query
Aug  7 14:21:10 sipapp01 proxy[16085]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug  7 14:21:10 sipapp01 proxy[16085]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database


Any hint about what could be wrong ?

Best regards


From jward01 at gmail.com  Fri Aug  8 02:58:49 2014
From: jward01 at gmail.com (Jeremy Ward)
Date: Fri, 8 Aug 2014 02:58:49 -0400
Subject: [Spce-user] Issues on Install
Message-ID: <CAFfjrWp=L=WgjHAyoAn8tjV8qr3nw6nUTsz3P0SgPjQ4ub_NPA@mail.gmail.com>

Greetings,

After two installation attempts, I have seen the installer appear to hang
(not complete) after several hours of execution.

System is a clean install of Linux debian 3.2.0-4-amd64 #1 SMP Debian
3.2.60-1+deb7u3 x86_64.

Below is the output of the installer script on the screen, and attached is
the ngcp-installer.log file.


######BEGIN SCREEN SCRAPE######
root at debian:~# dpkg -i ${PKG}
(Reading database ... 24568 files and directories currently installed.)
Preparing to replace ngcp-installer-ce 0.15.1.2+0~mr3.4.1.2 (using
ngcp-installer-latest.deb) ...
Unpacking replacement ngcp-installer-ce ...
Setting up ngcp-installer-ce (0.15.1.2+0~mr3.4.1.2) ...
root at debian:~# ngcp-installer
Welcome to Sipwise sip:provider installer.

This software comes WITH NO WARRANTY.
If you need SLA please consider upgrading to Sipwise sip:provider Pro
Edition.

This installation script is not intended to run in a shared system,
as it can add/delete/update existing configurations.
Please run this script only in a base install of 64 bit Debian 7.x on a
dedicated server.

Do you want to continue with the installation process? (y/n)y


Running as root... OK
Internet access... OK
Looks like a clean install... OK
Generate /etc/ngcp_nodename as spce
Check Debian version... OK
Check 64 bit capable system... OK
Updating package repository...OK
Installing ngcp-keyring package
OK
Installing package list. This might take several minutes depending on your
network connection...

######END SCREEN SCRAPE######

Any idea whats going on?

Thanks.

-- 
Jeremy D. Ward
Consulting Network Engineer
(954) 661-4965
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140808/476bbc6e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ngcp-installer.log
Type: application/octet-stream
Size: 6706 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140808/476bbc6e/attachment.log>

From mprokop at sipwise.com  Fri Aug  8 04:19:29 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Fri, 8 Aug 2014 10:19:29 +0200
Subject: [Spce-user] Issues on Install
In-Reply-To: <CAFfjrWp=L=WgjHAyoAn8tjV8qr3nw6nUTsz3P0SgPjQ4ub_NPA@mail.gmail.com>
References: <CAFfjrWp=L=WgjHAyoAn8tjV8qr3nw6nUTsz3P0SgPjQ4ub_NPA@mail.gmail.com>
Message-ID: <2014-08-08T10-19-01@devnull.michael-prokop.at>

* Jeremy Ward [Fri Aug 08, 2014 at 02:58:49AM -0400]:

> After two installation attempts, I have seen the installer appear to hang
> (not complete) after several hours of execution.

> System is a clean install of Linux debian 3.2.0-4-amd64 #1 SMP Debian
> 3.2.60-1+deb7u3 x86_64.

> Below is the output of the installer script on the screen, and attached is
> the ngcp-installer.log file.

[...]
> Installing package list. This might take several minutes depending on your
> network connection...

What's inside /tmp/ngcp-installer.log?

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140808/a7923cfd/attachment.asc>

From mstorck at voipgate.com  Fri Aug  8 07:02:57 2014
From: mstorck at voipgate.com (Marc Storck)
Date: Fri, 8 Aug 2014 11:02:57 +0000
Subject: [Spce-user] change of IP address
In-Reply-To: <53E21BB6.4030701@sipwise.com>
References: <44D6B68F-59E4-46E3-B2BD-65371E9220F7@voipgate.com>
 <53E21BB6.4030701@sipwise.com>
Message-ID: <C0469670-92EA-4786-B1E0-25749015DCE1@voipgate.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I tried that, but a few places still had the old IP address. Here is a list

/etc/default/ngcp-mediaproxy-ng-daemon
/etc/kamailio/lb/kamailio.cfg.custom
/etc/sems/etc/db_reg_agent.conf
/etc/sems/etc/reg_agent.conf
/etc/sems/sems.conf

Some of these files might be obsolete? as I have these system since version 2.8 and it is currently running 3.4.1

Can anybody advise on how to proceed?

Regards,

Marc

Do I have to 
On Aug 6, 2014, at 2:12 PM, Victor Seva <vseva at sipwise.com> wrote:

On 08/06/2014 02:02 PM, Marc Storck wrote:
Good afternoon,

I need to change the IP address of a system (*NOT* the domain name). I tried seraching for instruction but I wasn?t successful.

Could someone please point me into the right direction?

https://www.sipwise.com/doc/mr3.4.1/spce/ar01s05.html#_network_configuration



_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJT5K7rAAoJEBqZdpQUXtTCBckP/iwRVV4ZLNE2jKbqw+xwsOZ2
w+trGUAkxSqyYgw7OwYmfeV2tLWkaZrVozCB8130zEgqBvrWotpFr8AAIHNbcINs
RFepBlZa+LN86RxHeuxDpig3+wIZQRDDRbPjypsA5vM6bSP/0tfkvbp1GpcKE3/N
IjKxD/KQm872YV3s1NCj5RU4R2reeifID5nAog91mgPss8hlGovzRzVO/W1uDFHD
PqlMjuZ1CupWZ67t2cwyzrDac41BTTeFW2wIkEJSt6iS/+cB+4c+0csssDRU+FVR
ZbqFSN7fBkqbPCr4ZeAaedlAAzW4uNQuQ4ApHoetW/0KwpWvNlQjEv6PCMEgaZA8
vbEOXaCTcePCConQashDbjMBLh4HitE0awi0HVUO6MGZLsciun0gVYhemb/Dc9To
zGYjvD0KFGLT/oE0KJ/gF99jhmLZ+mtVMHRbnrIjf/tY5J0uRasB6Iw+cJ/NNoUF
LqtcjOrjmAy+tFkeQiHdMJJsCcEy8Q18Xatgxt9lGctKAm7iF8FrVLHr9mCWjafM
u5jKdhH0L1buxGr6nCorRFdGg8FOows9sBJl8bsdRP1AjM1/h05w7tzsRqGtrx+O
1pLHrqZT4JOurNuI6Hb8Rt3EwabMpM/xyj3XL8/cVr0T7VZMkyZEjN8ccdhW6pva
NdEGyyFvvtwNySpNESSa
=8Fw7
-----END PGP SIGNATURE-----

From dgrotti at sipwise.com  Fri Aug  8 09:07:46 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 08 Aug 2014 15:07:46 +0200
Subject: [Spce-user] change of IP address
In-Reply-To: <C0469670-92EA-4786-B1E0-25749015DCE1@voipgate.com>
References: <44D6B68F-59E4-46E3-B2BD-65371E9220F7@voipgate.com>
 <53E21BB6.4030701@sipwise.com>
 <C0469670-92EA-4786-B1E0-25749015DCE1@voipgate.com>
Message-ID: <53E4CBA2.4040801@sipwise.com>

Hi,
if you have to change the IP serving the Voip services, you just need to
change the shared_ip in your network.yml and then apply the changes.
The files you have mentioned are automatically generated by the ngcp
framework, and if you change the netwrok.yml, as soon as you apply the
changes those file will be regenerated.

Daniel






On 08/08/2014 01:02 PM, Marc Storck wrote:
> Hello,
>
> I tried that, but a few places still had the old IP address. Here is a
> list
>
> /etc/default/ngcp-mediaproxy-ng-daemon
> /etc/kamailio/lb/kamailio.cfg.custom
> /etc/sems/etc/db_reg_agent.conf
> /etc/sems/etc/reg_agent.conf
> /etc/sems/sems.conf
>
> Some of these files might be obsolete? as I have these system since
> version 2.8 and it is currently running 3.4.1
>
> Can anybody advise on how to proceed?
>
> Regards,
>
> Marc
>
> Do I have to
> On Aug 6, 2014, at 2:12 PM, Victor Seva <vseva at sipwise.com> wrote:
>
> On 08/06/2014 02:02 PM, Marc Storck wrote:
> Good afternoon,
>
> I need to change the IP address of a system (*NOT* the domain name). I
> tried seraching for instruction but I wasn?t successful.
>
> Could someone please point me into the right direction?
>
> https://www.sipwise.com/doc/mr3.4.1/spce/ar01s05.html#_network_configuration
>
>
>
> _______________________________________________
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140808/714b103d/attachment.html>

From agranig at sipwise.com  Fri Aug  8 15:32:44 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Fri, 08 Aug 2014 21:32:44 +0200
Subject: [Spce-user] change of IP address
In-Reply-To: <53E4CBA2.4040801@sipwise.com>
References: <44D6B68F-59E4-46E3-B2BD-65371E9220F7@voipgate.com>
 <53E21BB6.4030701@sipwise.com>
 <C0469670-92EA-4786-B1E0-25749015DCE1@voipgate.com>
 <53E4CBA2.4040801@sipwise.com>
Message-ID: <53E525DC.5050900@sipwise.com>

Hi,

Newer version use /etc/ngcp-sems instead of /etc/sems, and they use
rtpengine instead if meadiaproxy-ng, and custom files are ignored
anyways, so all in all, you should be good.

Andreas

On 08/08/2014 03:07 PM, Daniel Grotti wrote:
> Hi,
> if you have to change the IP serving the Voip services, you just need to
> change the shared_ip in your network.yml and then apply the changes.
> The files you have mentioned are automatically generated by the ngcp
> framework, and if you change the netwrok.yml, as soon as you apply the
> changes those file will be regenerated.
> 
> Daniel
> 
> 
> 
> 
> 
> 
> On 08/08/2014 01:02 PM, Marc Storck wrote:
>> Hello,
>>
>> I tried that, but a few places still had the old IP address. Here is a
>> list
>>
>> /etc/default/ngcp-mediaproxy-ng-daemon
>> /etc/kamailio/lb/kamailio.cfg.custom
>> /etc/sems/etc/db_reg_agent.conf
>> /etc/sems/etc/reg_agent.conf
>> /etc/sems/sems.conf
>>
>> Some of these files might be obsolete? as I have these system since
>> version 2.8 and it is currently running 3.4.1
>>
>> Can anybody advise on how to proceed?
>>
>> Regards,
>>
>> Marc
>>
>> Do I have to
>> On Aug 6, 2014, at 2:12 PM, Victor Seva <vseva at sipwise.com> wrote:
>>
>> On 08/06/2014 02:02 PM, Marc Storck wrote:
>> Good afternoon,
>>
>> I need to change the IP address of a system (*NOT* the domain name). I
>> tried seraching for instruction but I wasn?t successful.
>>
>> Could someone please point me into the right direction?
>>
>> https://www.sipwise.com/doc/mr3.4.1/spce/ar01s05.html#_network_configuration
>>
>>
>>
>> _______________________________________________
>> 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
> 


From jchism2 at gmail.com  Fri Aug  8 15:36:43 2014
From: jchism2 at gmail.com (Jeremie Chism)
Date: Fri, 8 Aug 2014 14:36:43 -0500
Subject: [Spce-user] Block International Calls from Subscribers with US
	numbers
Message-ID: <CAG-pSShVobai8vRbFx5F-wKwCgKJTjwv0QsuXaL6CuPo740BWQ@mail.gmail.com>

I have some subscribers with US telephone numbers that I would like to
block calls to 011+ numbers.  I tried to use the NCOS with 011*  and it was
blocking other numbers that had 011 elsewhere in the number.  Is there a
definite way with either NCOS or rewrite rules that I can prevent
International calls from being sent to a peer from my US based customers.

Thanks

-- 
Jeremie Chism
Triton Communications
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140808/0652b963/attachment.html>

From jward01 at gmail.com  Fri Aug  8 19:13:25 2014
From: jward01 at gmail.com (Jeremy Ward)
Date: Fri, 8 Aug 2014 19:13:25 -0400
Subject: [Spce-user] Fwd: Issues on Install
In-Reply-To: <2014-08-08T12-33-43@devnull.michael-prokop.at>
References: <CAFfjrWp=L=WgjHAyoAn8tjV8qr3nw6nUTsz3P0SgPjQ4ub_NPA@mail.gmail.com>
 <CAFfjrWq21g+OJ2GWMP+Uxw96-x=m6ZSEtBZL_2wz0X7wAhMv7Q@mail.gmail.com>
 <2014-08-08T12-07-06@devnull.michael-prokop.at>
 <CAFfjrWp07dnZo7EZEgLTzRPa8f6aM0YUcsT-Vg8ofFOaSfipOQ@mail.gmail.com>
 <2014-08-08T12-33-43@devnull.michael-prokop.at>
Message-ID: <CAFfjrWpYDk=QxJD8d8VL6TzO3ewo2J2W_0t2x0ff0Xz0DU5fDA@mail.gmail.com>

Hi Michael,

I performed a package installation test by running the apt-get install
[package]. I received the following prompt after instructing apt-get to
proceed (typing 'y'):

*Media change: please insert the disc labeled 'Debian GNU/Linux 7.6.0
_Wheezy_ - Official amd64 CD Binary-1 20140712-14:11' in the drive
'/media/cdrom/' and press enter*

I turns out that I had to remove the cdrom entry from the sources.list file
on the server. This was causing an issue on the system during spce
installation.

This is why the NetInstall CD is probably the best way to go, as sipwise
recommends ;-).


*But either way, here's how I fixed it*:

I removed the cdrom entry from sources.list by running the following:

sed -i '/cdrom/d' /etc/apt/sources.list

I then verified the removal of the cdrom entry from sourced.list and
verified the active repositories that were setup on the system by running
the following:

grep -v '#' /etc/apt/sources.list

This fixed the issues encountered during the previous two installation
attempts; install was completed in less than five minutes.


Hope that this is helpful to someone else.


Jeremy D. Ward, CWNE
(954) 661-4965
---------- Forwarded message ----------
From: "Michael Prokop" <mprokop at sipwise.com>
Date: Aug 8, 2014 6:34 AM
Subject: Re: Fwd: Issues on Install
To: "Jeremy Ward" <jward01 at gmail.com>
Cc:

Hi,

yes, the all-in-one ISO should be a good way, just let me know if
you should note any problems with it.

regards,
-mika-

* Jeremy Ward [Fri Aug 08, 2014 at 06:19:24AM -0400]:
> Thanks, Michael.

> It took approximately 20 mins to get to where the log ended, and waited
two
> hours longer. This is when I became concerned that there was an issue.

> I'm going to try the all-in-one ISO that you guys just released with
> version 3.4.1.

> Do you think that would that be the easiest way to do the installation at
> this point?

> Thanks Again,

> Jeremy D. Ward, CWNE
> (954) 661-4965
> On Aug 8, 2014 6:11 AM, "Michael Prokop" <mprokop at sipwise.com> wrote:

> > Hi,

> > there's nothing unusual in the log, besides that's it's truncated
> > before any actual issues arrised. ;)

> > It definitely takes some time to get past the package installation,
> > but while it's running you should see what's going on in
> > /tmp/ngcp-installer.log and by also checking process output (ps
> > auxwwww).

> > The CD issue *shouldn't* be a problem, but I can't answer that
> > without having further details about your system. As documented at
> > https://www.sipwise.com/doc/mr3.4.1/spce/ar01s04.html "Sipwise
> > recommends using the latest Netinstall ISO as installation medium."

> > So from my PoV rerun installer from a clean Debian system and if
> > stucks again share the installer logs to have a closer look. And use
> > the netinstall ISO instead this time. :)

> > regards,
> > -mika-

> > * Jeremy Ward [Fri Aug 08, 2014 at 05:57:15AM -0400]:
> > > Michael,

> > > Here's the original message with the log attached. I dont think it
made
> > it
> > > through the support list.

> > > I don't see anything other than packages being installed.

> > > The first log (truncated) had a few lines referring to the Debian
> > > installation CD (insert CD). Do you think its a repository issue?

> > > Its also worth mentioning that the first time I ran the installer, it
> > took
> > > awhile for it to eventually stall out... The operations underway
during
> > the
> > > install took much longer than I would have expected it to have taken
> > given
> > > server perfomance and Internet bandwidth (250Mbps).

> > > Thanks,

> > > Jeremy D. Ward, CWNE
> > > (954) 661-4965
> > > ---------- Forwarded message ----------
> > > From: "Jeremy Ward" <jward01 at gmail.com>
> > > Date: Aug 8, 2014 2:58 AM
> > > Subject: Issues on Install
> > > To: <spce-user at lists.sipwise.com>
> > > Cc:

> > > Greetings,

> > > After two installation attempts, I have seen the installer appear to
hang
> > > (not complete) after several hours of execution.

> > > System is a clean install of Linux debian 3.2.0-4-amd64 #1 SMP Debian
> > > 3.2.60-1+deb7u3 x86_64.

> > > Below is the output of the installer script on the screen, and
attached
> > is
> > > the ngcp-installer.log file.


> > > ######BEGIN SCREEN SCRAPE######
> > > root at debian:~# dpkg -i ${PKG}
> > > (Reading database ... 24568 files and directories currently
installed.)
> > > Preparing to replace ngcp-installer-ce 0.15.1.2+0~mr3.4.1.2 (using
> > > ngcp-installer-latest.deb) ...
> > > Unpacking replacement ngcp-installer-ce ...
> > > Setting up ngcp-installer-ce (0.15.1.2+0~mr3.4.1.2) ...
> > > root at debian:~# ngcp-installer
> > > Welcome to Sipwise sip:provider installer.

> > > This software comes WITH NO WARRANTY.
> > > If you need SLA please consider upgrading to Sipwise sip:provider Pro
> > > Edition.

> > > This installation script is not intended to run in a shared system,
> > > as it can add/delete/update existing configurations.
> > > Please run this script only in a base install of 64 bit Debian 7.x on
a
> > > dedicated server.

> > > Do you want to continue with the installation process? (y/n)y


> > > Running as root... OK
> > > Internet access... OK
> > > Looks like a clean install... OK
> > > Generate /etc/ngcp_nodename as spce
> > > Check Debian version... OK
> > > Check 64 bit capable system... OK
> > > Updating package repository...OK
> > > Installing ngcp-keyring package
> > > OK
> > > Installing package list. This might take several minutes depending on
> > your
> > > network connection...

> > > ######END SCREEN SCRAPE######

> > > Any idea whats going on?

> > > Thanks.

> > > --
> > > Jeremy D. Ward
> > > Consulting Network Engineer
> > > (954) 661-4965



> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.9 (GNU/Linux)

> > iEYEARECAAYFAlPkoi0ACgkQ2N9T+zficugbbwCeId4X/cFZRQZ4Lpg5vtWbEOxG
> > jgoAn3jEBDjhTmsUQZ3/CTMJ5/fXG1uR
> > =I5sR
> > -----END PGP SIGNATURE-----



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAlPkp54ACgkQ2N9T+zficujPogCePe4umPZeyElsUfl4WeyHgJW+
j5gAn1Ozgt/NxIgUXec5Ci0UZDf5YqZQ
=Cqs/
-----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140808/d501e9fe/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140808/d501e9fe/attachment.asc>

From agranig at sipwise.com  Sat Aug  9 07:57:50 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Sat, 09 Aug 2014 13:57:50 +0200
Subject: [Spce-user] Block International Calls from Subscribers with US
 numbers
In-Reply-To: <CAG-pSShVobai8vRbFx5F-wKwCgKJTjwv0QsuXaL6CuPo740BWQ@mail.gmail.com>
References: <CAG-pSShVobai8vRbFx5F-wKwCgKJTjwv0QsuXaL6CuPo740BWQ@mail.gmail.com>
Message-ID: <53E60CBE.1020306@sipwise.com>

Hi,

NCOS use regular expressions, so you can create a blacklist and put ^011
there to block anything starting with 011. However, note that the ncos
check is done after incoming rewriting, so if you have rewrite rules in
place rewriting your 011, make sure to put the format into NCOS which
you expect after running through rewrite rules.

Andreas

On 08/08/2014 09:36 PM, Jeremie Chism wrote:
> I have some subscribers with US telephone numbers that I would like to
> block calls to 011+ numbers.  I tried to use the NCOS with 011*  and it
> was blocking other numbers that had 011 elsewhere in the number.  Is
> there a definite way with either NCOS or rewrite rules that I can
> prevent International calls from being sent to a peer from my US based
> customers.
> 
> Thanks
> 
> -- 
> Jeremie Chism
> Triton Communications
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From gary at netdiverse.com  Mon Aug 11 02:33:32 2014
From: gary at netdiverse.com (Gary Nieboer)
Date: Mon, 11 Aug 2014 00:33:32 -0600
Subject: [Spce-user] Peering Rules database vs. GUI Issue
In-Reply-To: <CAMXUi2ScE2u1tnGKSsbZUms+64yYTwAb-LsiKCfHJFAs1k7bsg@mail.gmail.com>
References: <CAMXUi2ScE2u1tnGKSsbZUms+64yYTwAb-LsiKCfHJFAs1k7bsg@mail.gmail.com>
Message-ID: <CAMXUi2S1DkXDE-EWG5N5UKxTqWLz19_T6iLV5mjj4sqU5K2u_g@mail.gmail.com>

I have another instance of the GUI not matching the database.

A peering rule ID 233 exists in the database & it was different than the
rule showing in the GUI.  Changing the rule in the GUI didn't adjust the
database.  Deleting the rule in the GUI didn't adjust the database.

Is there anything that can be done to "refresh" the GUI to reflect what is
actually in the database.

Also, is it safe to use mysql and delete the rule?

Thanks,

Gary

The Example:   In

--
Gary Nieboer


877-763-1014 Toll Free  |  801-657-5484 Utah  |  615-800-6946 Tennessee  |
801-694-6106 Mobile
gary at netdiverse.com  |   www.netdiverse.com


On Fri, Aug 1, 2014 at 2:55 PM, Gary Nieboer <gary at netdiverse.com> wrote:

>
> We have experienced a few issues with our "Peering Rules" on SPCE, 3.3.1.
>
> A created rule exists in the GUI, but when routing a call through the SBC,
> the call follows a route to a default peer rather than the peer indicated
> in the GUI.
>
> We recently did a comparison of what is shown in the database:  lcr_rules
>
>                             select * from lcr_rule;
>
>
> Here are a few lines from the database:   Some numbers are replaced with
> "`" and not fully shown:
>
> Note:  Rule 102 is missing from the database
>
>
> | id  | lcr_id | prefix | request_uri | from_uri | stopper | enabled |
> group_id |
>
> +-----+--------+--------+-------------+----------+---------+---------+----------+
> | 101 |      1 |        | ~~~~~20088  | NULL     |       0 |       1 |
>   23 |
> | 105 |      1 |        | ~~~~~20186  | NULL     |       0 |       1 |
>   23 |
> | 106 |      1 |        | ~~~~~74891  | NULL     |       0 |       1 |
>   23 |
>
>
>
> Now, here is a screenshot of the GUI for the same rules:
> Note:  Rule 102 exists under peer group 23 for the GUI.
> [image: Inline image 1]
>
>
>
> It appears we should trust the data in the database and not the GUI, but
> I'm assuming it is not desired behavior for the GUI and database to reflect
> different info.
>
> If you would like more information, we can share it.
>
> Please let me know if there is anything we can do to ensure the GUI
> reflects the actual activity of the database and ngcp/kamailio.
>
> Thanks,
>
> Gary
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140811/dce0f21a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 30444 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140811/dce0f21a/attachment.png>

From agranig at sipwise.com  Mon Aug 11 04:09:50 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Mon, 11 Aug 2014 10:09:50 +0200
Subject: [Spce-user] Peering Rules database vs. GUI Issue
In-Reply-To: <CAMXUi2S1DkXDE-EWG5N5UKxTqWLz19_T6iLV5mjj4sqU5K2u_g@mail.gmail.com>
References: <CAMXUi2ScE2u1tnGKSsbZUms+64yYTwAb-LsiKCfHJFAs1k7bsg@mail.gmail.com>
 <CAMXUi2S1DkXDE-EWG5N5UKxTqWLz19_T6iLV5mjj4sqU5K2u_g@mail.gmail.com>
Message-ID: <53E87A4E.7030207@sipwise.com>

Hi,

Can you share some information about the history of your setup? Which
version did you use for the initial setup? Any things you remember doing
to your peerings, like deleting groups or something?

There have been some issues with older versions couple of months ago in
the triggers synchronizing the databases provisioning and kamailio, but
they have been fixed in 3.1 already.

Andreas

On 08/11/2014 08:33 AM, Gary Nieboer wrote:
> I have another instance of the GUI not matching the database.
> 
> A peering rule ID 233 exists in the database & it was different than the
> rule showing in the GUI.  Changing the rule in the GUI didn't adjust the
> database.  Deleting the rule in the GUI didn't adjust the database.
> 
> Is there anything that can be done to "refresh" the GUI to reflect what
> is actually in the database.
> 
> Also, is it safe to use mysql and delete the rule?
> 
> Thanks,
> 
> Gary
> 
> The Example:   In 
> 
> --
> Gary Nieboer
> 
> 
> 877-763-1014 Toll Free  |  801-657-5484 Utah  |  615-800-6946 Tennessee 
> | 801-694-6106 Mobile
> gary at netdiverse.com <mailto:gary at netdiverse.com>  |   www.netdiverse.com
> <http://www.netdiverse.com/>
> 
> 
> On Fri, Aug 1, 2014 at 2:55 PM, Gary Nieboer <gary at netdiverse.com
> <mailto:gary at netdiverse.com>> wrote:
> 
> 
>     We have experienced a few issues with our "Peering Rules" on SPCE,
>     3.3.1.
> 
>     A created rule exists in the GUI, but when routing a call through
>     the SBC, the call follows a route to a default peer rather than the
>     peer indicated in the GUI.
> 
>     We recently did a comparison of what is shown in the database:
>      lcr_rules
> 
>                                 select * from lcr_rule;
> 
> 
>     Here are a few lines from the database:   Some numbers are replaced
>     with "`" and not fully shown:
> 
>     Note:  Rule 102 is missing from the database
> 
> 
>     | id  | lcr_id | prefix | request_uri | from_uri | stopper | enabled
>     | group_id |
>     +-----+--------+--------+-------------+----------+---------+---------+----------+
>     | 101 |      1 |        | ~~~~~20088  | NULL     |       0 |       1
>     |       23 |
>     | 105 |      1 |        | ~~~~~20186  | NULL     |       0 |       1
>     |       23 |
>     | 106 |      1 |        | ~~~~~74891  | NULL     |       0 |       1
>     |       23 |
> 
> 
> 
>     Now, here is a screenshot of the GUI for the same rules:
>     Note:  Rule 102 exists under peer group 23 for the GUI.
>     Inline image 1
> 
> 
> 
>     It appears we should trust the data in the database and not the GUI,
>     but I'm assuming it is not desired behavior for the GUI and database
>     to reflect different info.
> 
>     If you would like more information, we can share it.
> 
>     Please let me know if there is anything we can do to ensure the GUI
>     reflects the actual activity of the database and ngcp/kamailio.
> 
>     Thanks,
> 
>     Gary
> 
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From rabs at dimension-virtual.com  Mon Aug 11 09:37:47 2014
From: rabs at dimension-virtual.com (=?iso-8859-1?B?UmHDumw=?= Alexis Betancor Santana)
Date: Mon, 11 Aug 2014 14:37:47 +0100
Subject: [Spce-user] MySQL errors
In-Reply-To: <20140807121952.GA23093@salma.divi.prv>
References: <20140807121952.GA23093@salma.divi.prv>
Message-ID: <20140811133747.GA4724@salma.divi.prv>

On Thu, Aug 07, 2014 at 01:19:53PM +0100, (UNTRUSTED, sender <spce-user-bounces at lists.sipwise.com> is not authenticated) wrote:
> Hi all, since we upgrades a test system from 3.2 to mr3.3 and
> yesterday to mr3.4.1 this is getting worst:

Everyone on holidays? ...

Best regards


From dgrotti at sipwise.com  Mon Aug 11 11:22:15 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Mon, 11 Aug 2014 17:22:15 +0200
Subject: [Spce-user] MySQL errors
In-Reply-To: <20140811133747.GA4724@salma.divi.prv>
References: <20140807121952.GA23093@salma.divi.prv>
 <20140811133747.GA4724@salma.divi.prv>
Message-ID: <53E8DFA7.3010308@sipwise.com>

Hi,
it's hard to say. Mysql sometime get unreachable.
What is the state of your system usage ? Load, CPU, Mem ?

Daniel




On 08/11/2014 03:37 PM, Ra?l Alexis Betancor Santana wrote:
> On Thu, Aug 07, 2014 at 01:19:53PM +0100, (UNTRUSTED, sender <spce-user-bounces at lists.sipwise.com> is not authenticated) wrote:
>> Hi all, since we upgrades a test system from 3.2 to mr3.3 and
>> yesterday to mr3.4.1 this is getting worst:
> Everyone on holidays? ...
>
> Best regards
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user



From arpagon+sipwise at gmail.com  Mon Aug 11 12:51:09 2014
From: arpagon+sipwise at gmail.com (sebastian rojo)
Date: Mon, 11 Aug 2014 11:51:09 -0500
Subject: [Spce-user]  SBC is broken in mr3.4.1
Message-ID: <CAH7ArYweLeq=dSxXcTN6nEDJxXGC75FCkvumqpdgJd4Wioxieg@mail.gmail.com>

HI All,

Currently I have on SPCE in SBC mode, In version

cat /etc/sipwise_ngcp_version
> System installed. NGCP version mr3.3.2 on 2014-07-23 11:12:57


Everything is OK.

Since we upgrades a test system from 3.4.1. The SPCE got a problem whit the
Suscriber *Remote Authentication. *


   - Problem with the incoming Calls.
   - Problem with the remote register.


I decided to try a fresh installation


>
* root at sbc:~# cat /etc/sipwise_ngcp_version System installed. NGCP version
mr3.4.1 on 2014-08-06 12:05:52*
I got the same issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140811/59dda8f9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log.tar.gz
Type: application/x-gzip
Size: 1821190 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140811/59dda8f9/attachment.gz>

From agranig at sipwise.com  Mon Aug 11 16:36:20 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Mon, 11 Aug 2014 22:36:20 +0200
Subject: [Spce-user] SBC is broken in mr3.4.1
In-Reply-To: <CAH7ArYweLeq=dSxXcTN6nEDJxXGC75FCkvumqpdgJd4Wioxieg@mail.gmail.com>
References: <CAH7ArYweLeq=dSxXcTN6nEDJxXGC75FCkvumqpdgJd4Wioxieg@mail.gmail.com>
Message-ID: <53E92944.1050409@sipwise.com>

Hi,

On 08/11/2014 06:51 PM, sebastian rojo wrote:
> Since we upgrades a test system from 3.4.1. The SPCE got a problem whit
> the Suscriber *Remote Authentication. *
> *
> 
>   * Problem with the incoming Calls.

Which problems?

>   * Problem with the remote register.

Again, which problems? What do the logs say for the particular scenarios
(e.g. for one particular failing incoming call, or one particular
failing outbound registration)?

Please don't expect anyone to look at 1.7MB log files without any hints.

Andreas


From agranig at sipwise.com  Mon Aug 11 16:37:53 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Mon, 11 Aug 2014 22:37:53 +0200
Subject: [Spce-user] MySQL errors
In-Reply-To: <20140811133747.GA4724@salma.divi.prv>
References: <20140807121952.GA23093@salma.divi.prv>
 <20140811133747.GA4724@salma.divi.prv>
Message-ID: <53E929A1.6010906@sipwise.com>



On 08/11/2014 03:37 PM, Ra?l Alexis Betancor Santana wrote:
> On Thu, Aug 07, 2014 at 01:19:53PM +0100, (UNTRUSTED, sender <spce-user-bounces at lists.sipwise.com> is not authenticated) wrote:
>> Hi all, since we upgrades a test system from 3.2 to mr3.3 and
>> yesterday to mr3.4.1 this is getting worst:
> 
> Everyone on holidays? ...

Probably nobody on the list has ever encountered the same problem? As
Daniel said, it's not really SPCE related, rather than a problem of your
MySQL db dying from time to time?

Andreas


From dgrotti at sipwise.com  Tue Aug 12 11:42:26 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Tue, 12 Aug 2014 17:42:26 +0200
Subject: [Spce-user] SBC is broken in mr3.4.1
In-Reply-To: <CAH7ArYweLeq=dSxXcTN6nEDJxXGC75FCkvumqpdgJd4Wioxieg@mail.gmail.com>
References: <CAH7ArYweLeq=dSxXcTN6nEDJxXGC75FCkvumqpdgJd4Wioxieg@mail.gmail.com>
Message-ID: <53EA35E2.1070704@sipwise.com>

Hi,

Aug 11 02:50:37 sbc proxy[5162]: NOTICE: <script>: New request -
M=INVITE R=sip:+972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:+972598431309 at 181.143.4.67 IP=31.223.182.35:24708 (127.0.0.1:5060)
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:37 sbc proxy[5162]: NOTICE: <script>: Authentication
failed, no credentials - R=sip:+972598431309 at 181.143.4.67
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:37 sbc proxy[5156]: NOTICE: <script>: New request -
M=INVITE R=sip:+972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:+972598431309 at 181.143.4.67 IP=31.223.182.35:24708 (127.0.0.1:5060)
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:37 sbc proxy[5156]: NOTICE: <script>: Authentication
failed, invalid user - R=sip:+972598431309 at 181.143.4.67
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:37 sbc proxy[5152]: NOTICE: <script>: New request -
M=INVITE R=sip:+972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:+972598431309 at 181.143.4.67 IP=31.223.182.35:24708 (127.0.0.1:5060)
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:37 sbc proxy[5152]: NOTICE: <script>: Authentication
failed, invalid user - R=sip:+972598431309 at 181.143.4.67
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:38 sbc proxy[5154]: NOTICE: <script>: New request -
M=INVITE R=sip:+972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:+972598431309 at 181.143.4.67 IP=31.223.182.35:24708 (127.0.0.1:5060)
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:38 sbc proxy[5154]: NOTICE: <script>: Authentication
failed, invalid user - R=sip:+972598431309 at 181.143.4.67
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:40 sbc proxy[5158]: NOTICE: <script>: New request -
M=INVITE R=sip:00972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:00972598431309 at 181.143.4.67 IP=31.223.182.35:24708
(127.0.0.1:5060) ID=45c99da5a926916337e849e4b7860f53
Aug 11 02:50:40 sbc proxy[5158]: NOTICE: <script>: Authentication
failed, no credentials - R=sip:00972598431309 at 181.143.4.67
ID=45c99da5a926916337e849e4b7860f53
Aug 11 02:50:43 sbc proxy[5153]: NOTICE: <script>: New request -
M=INVITE R=sip:000972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:000972598431309 at 181.143.4.67 IP=31.223.182.35:24708
(127.0.0.1:5060) ID=a18a4b57737466201e0528413cccb1ae
Aug 11 02:50:43 sbc proxy[5153]: NOTICE: <script>: Authentication
failed, no credentials - R=sip:000972598431309 at 181.143.4.67
ID=a18a4b57737466201e0528413cccb1ae
Aug 11 02:50:44 sbc proxy[5161]: NOTICE: <script>: New request -
M=INVITE R=sip:005972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:005972598431309 at 181.143.4.67 IP=31.223.182.35:24708
(127.0.0.1:5060) ID=b37a727b93c3521c2767e54b8946be44
Aug 11 02:50:44 sbc proxy[5161]: NOTICE: <script>: Authentication
failed, no credentials - R=sip:005972598431309 at 181.143.4.67
ID=b37a727b93c3521c2767e54b8946be44
Aug 11 02:50:45 sbc proxy[5155]: NOTICE: <script>: New request -
M=INVITE R=sip:007972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:007972598431309 at 181.143.4.67 IP=31.223.182.35:24708
(127.0.0.1:5060) ID=06c4713e873b39c43aa9087e50bea15c
Aug 11 02:50:45 sbc proxy[5155]: NOTICE: <script>: Authentication
failed, no credentials - R=sip:007972598431309 at 181.143.4.67
ID=06c4713e873b39c43aa9087e50bea15c
Aug 11 02:50:46 sbc proxy[5156]: NOTICE: <script>: New request -
M=INVITE R=sip:009972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:009972598431309 at 181.143.4.67 IP=31.223.182.35:24708
(127.0.0.1:5060) ID=06c4713e873b39c43aa9087e50bea15c
Aug 11 02:50:46 sbc proxy[5156]: NOTICE: <script>: Authentication
failed, no credentials - R=sip:009972598431309 at 181.143.4.67
ID=06c4713e873b39c43aa9087e50bea15c
Aug 11 02:50:47 sbc proxy[5161]: NOTICE: <script>: New request -
M=INVITE R=sip:0007972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:0007972598431309 at 181.143.4.67 IP=31.223.182.35:24708
(127.0.0.1:5060) ID=1ffd12f2d18170c4087d0262731ebfaf


INVITE doesn't contain credentials.
I can see also and "invalid user" message. Please check your INVITE
credentials.

Aug 11 00:09:13 sbc lb[6692]: NOTICE: <script>: New request - M=REGISTER
R=sip:sapian.com.co F=sip:217 at sapian.com.co T=sip:217 at sapian.com.co
IP=udp:181.143.4.66:5060 ID=40db1521-dcfbb9a1 at 172.16.252.238
Aug 11 00:09:13 sbc lb[6692]: NOTICE: <script>: Relaying request,
du='sip:127.0.0.1:5062', fs='udp:127.0.0.1:5060' - R=sip:sapian.com.co
ID=40db1521-dcfbb9a1 at 172.16.252.238
Aug 11 00:09:13 sbc lb[6699]: NOTICE: <script>: Reply from Inbound -
S=100 - Trying M=REGISTER IP=udp:127.0.0.1:5062
ID=40db1521-dcfbb9a1 at 172.16.252.238
Aug 11 00:09:13 sbc lb[6699]: NOTICE: <script>: Sending reply,
fs='udp:181.143.4.67:5060' - ID=40db1521-dcfbb9a1 at 172.16.252.238
Aug 11 00:09:13 sbc lb[6699]: NOTICE: <script>: Reply from Inbound -
S=403 - Domain not served here M=REGISTER IP=udp:127.0.0.1:5062
ID=40db1521-dcfbb9a1 at 172.16.252.238



Are you registering to a domain which doesn't exist ?



Again - as Andreas said - if you don't point us out to your problems we
can't support you.
Please provide information regarding your problem, exact CallID,
caller/callee, expected behaviour, current behaviour.


Regards,

Daniel




On 08/11/2014 06:51 PM, sebastian rojo wrote:
> HI All, 
>
> Currently I have on SPCE in SBC mode, In version  
>
>     cat /etc/sipwise_ngcp_version 
>     System installed. NGCP version mr3.3.2 on 2014-07-23 11:12:57
>
>
> Everything is OK.
>
> Since we upgrades a test system from 3.4.1. The SPCE got a problem
> whit the Suscriber *Remote Authentication. *
> *
> *
>
>   * Problem with the incoming Calls.
>   * Problem with the remote register.
>
>
> I decided to try a fresh installation
>
> *
>
>     root at sbc:~# cat /etc/sipwise_ngcp_version 
>     System installed. NGCP version mr3.4.1 on 2014-08-06 12:05:52
>
>
> *
> I got the same issues.
>
>
>
>
> _______________________________________________
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140812/e383847a/attachment.html>

From arpagon+sipwise at gmail.com  Tue Aug 12 11:52:46 2014
From: arpagon+sipwise at gmail.com (sebastian rojo)
Date: Tue, 12 Aug 2014 10:52:46 -0500
Subject: [Spce-user] SBC is broken in mr3.4.1
In-Reply-To: <53EA35E2.1070704@sipwise.com>
References: <CAH7ArYweLeq=dSxXcTN6nEDJxXGC75FCkvumqpdgJd4Wioxieg@mail.gmail.com>
 <53EA35E2.1070704@sipwise.com>
Message-ID: <CAH7ArYyeFk3bVqheZBnS6dh6b_Nzo2s_P2BGUg+7K_eeMUggsQ@mail.gmail.com>

Andreas, Daniel You are Rigth.

I'm currently compiling the most accurate information to properly report mi
case.

Thanks for the reply.

?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140812/e173d3ca/attachment.html>

From rabs at dimension-virtual.com  Thu Aug 14 07:22:50 2014
From: rabs at dimension-virtual.com (rabs at dimension-virtual.com)
Date: Thu, 14 Aug 2014 13:22:50 +0200 (CEST)
Subject: [Spce-user] MySQL errors
In-Reply-To: <53E8DFA7.3010308@sipwise.com>
References: <20140807121952.GA23093@salma.divi.prv>
 <20140811133747.GA4724@salma.divi.prv> <53E8DFA7.3010308@sipwise.com>
Message-ID: <55580.85.155.242.185.1408015370.squirrel@www.rodriguezfeo.es>

> Hi,
> it's hard to say. Mysql sometime get unreachable.
> What is the state of your system usage ? Load, CPU, Mem ?
>
> Daniel
>

Found the problem ... a collecd daemon doing strange things ... overloading the
system and putting IO soo high that MySQL fails randomly.

Now have to review what that collecd was doing wrong.

Best regards



From kmasse at questblue.com  Thu Aug 14 07:33:26 2014
From: kmasse at questblue.com (Kevin Masse)
Date: Thu, 14 Aug 2014 07:33:26 -0400
Subject: [Spce-user] Subscriber Alias Entries in Database
References: <CEEE718799582B47A55D7897DCB264FC3F5E18@bvusaex.bestvoipusa.local><53C652BD.7000707@sipwise.com>
 <CEEE718799582B47A55D7897DCB264FC3F5E65@bvusaex.bestvoipusa.local>
 <CEEE718799582B47A55D7897DCB264FC3F5F7F@bvusaex.bestvoipusa.local> 
Message-ID: <CEEE718799582B47A55D7897DCB264FC3F61AD@bvusaex.bestvoipusa.local>

Hello Andraes, have you had a chance to review the two questions stated
below?

Our dev team is seeking to close out this issue we are having.

Thank you
Kevin




-----Original Message-----
From: Kevin Masse 
Sent: Wednesday, August 06, 2014 7:55 AM
To: Kevin Masse; 'Andreas Granig'; 'spce-user at lists.sipwise.com'
Subject: RE: [Spce-user] Subscriber Alias Entries in Database

Hello, I was wondering if there was a response to this that I missed.
There are two specific questions we are trying to answer.


Thank you
Kevin



-----Original Message-----
From: Kevin Masse 
Sent: Thursday, July 24, 2014 10:02 AM
To: Kevin Masse; Andreas Granig; spce-user at lists.sipwise.com
Subject: RE: [Spce-user] Subscriber Alias Entries in Database

Andraes one additional scenario has come up based on our last thread:
I wanted to post to the group the question from our dev team:

****  Begin Comment ****
It is going to be a long post because I can't explain in a short
message. I'll provide some example to explain what I mean. 

We have SIP named QBATRUNK.  If you open administrator page
(https://DOMAIN:1443/subscriber/detail?subscriber_id=395) you can see
there following info:

Contract ID (405) - This is main ID which we store in (customer site -
not part of Sipwise it is our Database) . All operations like
lock/unlock SIP, add/remove DID using the ID in it request to API.

Subscriber ID (395) - I can call it internal info, it is not used in any
request to Sipwise API but to make direct request to Sipwise DB I have
to use it.

I routed 3384066 DID to the SIP to work with the example. 
According to previous instructions we use two databases to store
aliases. Now I'll show you request to retrieve the DID from Sipwise DB.

First I use billing DB. Let's retrieve Subscriber ID (we do not know it
when call DB directly). I use voip_subscribers table which stores the
info.

mysql> select * from voip_subscribers where contract_id = 405;
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+
| id | contract_id | uuid | username | domain_id | status |
primary_number_id | external_id |
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+
| 395 | 405 | 14a58c84-c83e-4673-9d10-361a1a6b990e | QBATRUNK | 1 |
active | NULL | NULL |
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+

OK you can see that I receive id 395. We need it.

 

Let's get DIDs info from voip_numbers, DB - 

mysql> select * from voip_numbers where subscriber_id = 395;
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+
| id | cc | ac | sn | reseller_id | subscriber_id | status | ported |
list_timestamp |
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+
| 2119 | 1 | 910 | 3384066 | NULL | 395 | active | 1 | 2014-07-22
18:32:16 |
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+

Everything is OK we got it as expected. Lets' get DID info from second
DB (provisioning) I'll do it using DID number

mysql> select * from voip_dbaliases where username like '%3384066%';
+------+-------------+-----------+---------------+
| id | username | domain_id | subscriber_id |
+------+-------------+-----------+---------------+
| 2821 | 19103384066 | 3 | 398 |

As you can see subscriber_id in the table does not corresponds to the
subscriber_id which we retrieve from billing DB. That is the question
for me.

I found that the subscriber_id is stored in voip_dbaliases table but the
ID does not corresponds to the subscriber_id from billing table.




************* 2 questions below ****************





Question 1
I do not understand how subscriber_id in billing DB (table voip_numbers)
related with subscriber_id in provisioning DB (table voip_dbaliases ).

Question 2
Another question. I found that DIDs info is stored in voip_dbaliases
table (provisioning) but I did not told to creae the record by VoIP
specialist.


mysql> select * from voip_dbaliases where username like '%3384066%';
+------+-------------+-----------+---------------+
| id | username | domain_id | subscriber_id |
+------+-------------+-----------+---------------+
| 2821 | 19103384066 | 3 | 398 |
+------+-------------+-----------+---------------+

Hopefully I explained my questions clear. If not please let me know

Thanks,
*** End Comment from DEV ***



In conclusion Andreas do you think there is a proper answer for the
above Question 1 and Question 2?
Thank you
Kevin 





-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Kevin Masse
Sent: Wednesday, July 16, 2014 8:56 AM
To: Andreas Granig; spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Subscriber Alias Entries in Database

Thank you Andreas, I appreciate the detailed response.  Works as
described.
Kevin



-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Andreas Granig
Sent: Wednesday, July 16, 2014 6:24 AM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Subscriber Alias Entries in Database

Hi,

On 07/15/2014 03:05 PM, Kevin Masse wrote:

> **  Current operation:   We use SOAP to add alias numbers to a
subscriber 
> 
> Requested operation:  We would like to write a new alias number for a 
> subscriber directly to the database.

As long as you make sure to write it to both billing.voip_numbers and
provisioning.voip_dbaliases, it should be fine.

Andreas

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/listinfo/spce-user

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/listinfo/spce-user


From jchism2 at gmail.com  Sun Aug 17 04:41:37 2014
From: jchism2 at gmail.com (Jeremie Chism)
Date: Sun, 17 Aug 2014 03:41:37 -0500
Subject: [Spce-user] Audio proxy
Message-ID: <CAG-pSSj1Q5rO0hx_VfQD2G+BoByZa3jrq1ANV3dZ0sOLkz2uSg@mail.gmail.com>

I know by default the audio proxy is set to always. Is there a setting that
would make the system automatically proxy the audio if the registration is
natted and not proxy if it is not?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140817/3bb80a8a/attachment.html>

From george.mason at xoomtalk.com  Sun Aug 17 17:29:43 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Sun, 17 Aug 2014 22:29:43 +0100
Subject: [Spce-user] Assistance getting set up on AWS
Message-ID: <53F11EC7.1050203@xoomtalk.com>

Hi,

Am new to Sip:provider but liking what I read so far. I've been trying
to get this working on AWS but struggling to do so, and have been
advised to post my experience here - so here goes:

I have been trying to build a Debian Squeeze AMI and install the stable
release of your product (v2.8) by following the quick install guide and
handbook. I have been building my EC2 instances using the following AMI:
ami-f0a97498. The install seems to run for some time, downloading
components etc. but it then stops without error, or saying that it has
successfully completed. I have attached the ngcp-installer.log as I
tried to install the software last time.

Would be grateful of any assistance or comment from the community.

Many thanks

George Mason
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ngcp-installer.log.zip
Type: application/zip
Size: 49216 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140817/5c321ee2/attachment.zip>

From jbonilla at sipwise.com  Sun Aug 17 19:07:16 2014
From: jbonilla at sipwise.com (Jon Bonilla (Manwe))
Date: Mon, 18 Aug 2014 01:07:16 +0200
Subject: [Spce-user] Assistance getting set up on AWS
In-Reply-To: <53F11EC7.1050203@xoomtalk.com>
References: <53F11EC7.1050203@xoomtalk.com>
Message-ID: <20140818010716.5fcd7689@multivac>

El Sun, 17 Aug 2014 22:29:43 +0100
George Mason <george.mason at xoomtalk.com> escribi?:

> Hi,
> 
> Am new to Sip:provider but liking what I read so far. I've been trying
> to get this working on AWS but struggling to do so, and have been
> advised to post my experience here - so here goes:
> 
> I have been trying to build a Debian Squeeze AMI and install the stable
> release of your product (v2.8) by following the quick install guide and
> handbook. I have been building my EC2 instances using the following AMI:
> ami-f0a97498. The install seems to run for some time, downloading
> components etc. but it then stops without error, or saying that it has
> successfully completed. I have attached the ngcp-installer.log as I
> tried to install the software last time.
> 
> Would be grateful of any assistance or comment from the community.
> 
> Many thanks
> 
> George Mason



You have the error and a suggested action at the end of the logfile:

Error: Generating /etc/asterisk/iax.conf based
on /etc/ngcp-config/templates//etc/asterisk/iax.conf.tt2: FAILED NOTE: Check
those files for valid syntax and
encoding: /etc/ngcp-config/templates//etc/asterisk/iax.conf.tt2 /etc/ngcp-config/config.yml
/etc/ngcp-config/network.yml
/etc/ngcp-config/constants.yml
Running /usr/share/ngcp-ngcpcfg/helper/tt2-wrapper <file> should provide more
details.


Looks like one of the configuration templates does not have a valid syntax and
it can't be created.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140818/0cf2604c/attachment.asc>

From mprokop at sipwise.com  Mon Aug 18 04:22:50 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Mon, 18 Aug 2014 10:22:50 +0200
Subject: [Spce-user] Assistance getting set up on AWS
In-Reply-To: <53F11EC7.1050203@xoomtalk.com>
References: <53F11EC7.1050203@xoomtalk.com>
Message-ID: <2014-08-18T10-18-23@devnull.michael-prokop.at>

* George Mason [Sun Aug 17, 2014 at 10:29:43PM +0100]:

> Am new to Sip:provider but liking what I read so far. I've been trying
> to get this working on AWS but struggling to do so, and have been
> advised to post my experience here - so here goes:

> I have been trying to build a Debian Squeeze AMI and install the stable
> release of your product (v2.8) by following the quick install guide and
> handbook. I have been building my EC2 instances using the following AMI:
> ami-f0a97498. The install seems to run for some time, downloading
> components etc. but it then stops without error, or saying that it has
> successfully completed. I have attached the ngcp-installer.log as I
> tried to install the software last time.

> Would be grateful of any assistance or comment from the community.

We don't provide AWS support for the 2.8 release, instead we
provide a supported AMI for our latest release, see
http://lists.sipwise.com/pipermail/spce-user/2014-August/007061.html
for further information. Please let us know if you should notice any
problems with it.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140818/25a09577/attachment.asc>

From george.mason at xoomtalk.com  Mon Aug 18 07:47:30 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Mon, 18 Aug 2014 12:47:30 +0100
Subject: [Spce-user] Assistance getting set up on AWS
In-Reply-To: <2014-08-18T10-18-23@devnull.michael-prokop.at>
References: <53F11EC7.1050203@xoomtalk.com>
 <2014-08-18T10-18-23@devnull.michael-prokop.at>
Message-ID: <53F1E7D2.900@xoomtalk.com>

On 18/08/14 09:22, Michael Prokop wrote:
> We don't provide AWS support for the 2.8 release, instead we
> provide a supported AMI for our latest release, see
> http://lists.sipwise.com/pipermail/spce-user/2014-August/007061.html
> for further information. Please let us know if you should notice any
> problems with it.
>
> regards,
> -mika-
Hi mika

Many thanks - problem is that I need to use this on the East Coast
availability zone - seems the AMI is only available on EU West?

Kind regards

George


From mprokop at sipwise.com  Mon Aug 18 08:33:01 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Mon, 18 Aug 2014 14:33:01 +0200
Subject: [Spce-user] Assistance getting set up on AWS
In-Reply-To: <53F1E7D2.900@xoomtalk.com>
References: <53F11EC7.1050203@xoomtalk.com>
 <2014-08-18T10-18-23@devnull.michael-prokop.at>
 <53F1E7D2.900@xoomtalk.com>
Message-ID: <2014-08-18T14-22-11@devnull.michael-prokop.at>

* George Mason [Mon Aug 18, 2014 at 12:47:30PM +0100]:
> On 18/08/14 09:22, Michael Prokop wrote:
> > We don't provide AWS support for the 2.8 release, instead we
> > provide a supported AMI for our latest release, see
> > http://lists.sipwise.com/pipermail/spce-user/2014-August/007061.html
> > for further information. Please let us know if you should notice any
> > problems with it.

> Many thanks - problem is that I need to use this on the East Coast
> availability zone - seems the AMI is only available on EU West?

We've just provided the ngcp-ce-mr3.4.1 AMI to the us-east-1 region,
it's available as AMI ID ami-c2ad72aa there now.

If anyone should need the AMI in yet another zone please let us
know, I'll discuss within our team how we plan to handle this in the
future.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140818/a81f431d/attachment.asc>

From george.mason at xoomtalk.com  Tue Aug 19 07:01:09 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Tue, 19 Aug 2014 12:01:09 +0100
Subject: [Spce-user] Calls drop after 30 secs
Message-ID: <53F32E75.7070700@xoomtalk.com>

Hi,

I am having an issue with the SPCE Amazon EC2 image. I have configured
the server to forward all calls to a SIP provider with a couple of IP
handsets registered as subscribers. I can get a call to go through to
the PSTN and audio in both directions, but the call appears to drop
after approx. 30 secs.

I have run a UDP trace of the signalling and it looks like SPCE drops
the call, I found the following in the logs:

rtp.log
Aug 19 10:54:53 ip-10-237-180-106 rtpengine[26167]: Got valid command
from 127.0.0.1:56413: delete - { "call-id":
"60174c70-66e7d6e1 at 192.168.100.136", "received-from": [ "IP4",
"127.0.0.1" ], "from-tag": "317FA286-53F32CDB000A6E08-C56FB700",
"to-tag": "2cfee724f53bdbbdo0", "command": "delete" }

sems.log
Aug 19 10:54:53 ip-10-237-180-106 ngcp-sems[26328]: [#7f11c4ef3700]
[update_uac_request, trans_layer.cpp:2047] WARNING:  While sending 200
ACK: no matching transaction

Looks like either Sems or Asterisk is telling Kamailio to drop the call
- not sure what's going on here? Grateful of any feedback.

Thanks

George


From apogrebennyk at sipwise.com  Tue Aug 19 07:11:01 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Tue, 19 Aug 2014 13:11:01 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F32E75.7070700@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com>
Message-ID: <53F330C5.1040404@sipwise.com>

Hi,
what does your /etc/ngcp-config/network.yml look like? You should use
your Elastic IP as advertised_address. I think AMI configures that by
default.

Could you provide the kamailio-proxy.log, kamailio-lb.log and complete
trace? I mean also messages inside spce (lb,proxy,sems).

Regards.
Andrew

On 08/19/2014 01:01 PM, George Mason wrote:
> Hi,
> 
> I am having an issue with the SPCE Amazon EC2 image. I have configured
> the server to forward all calls to a SIP provider with a couple of IP
> handsets registered as subscribers. I can get a call to go through to
> the PSTN and audio in both directions, but the call appears to drop
> after approx. 30 secs.
> 
> I have run a UDP trace of the signalling and it looks like SPCE drops
> the call, I found the following in the logs:
> 
> rtp.log
> Aug 19 10:54:53 ip-10-237-180-106 rtpengine[26167]: Got valid command
> from 127.0.0.1:56413: delete - { "call-id":
> "60174c70-66e7d6e1 at 192.168.100.136", "received-from": [ "IP4",
> "127.0.0.1" ], "from-tag": "317FA286-53F32CDB000A6E08-C56FB700",
> "to-tag": "2cfee724f53bdbbdo0", "command": "delete" }
> 
> sems.log
> Aug 19 10:54:53 ip-10-237-180-106 ngcp-sems[26328]: [#7f11c4ef3700]
> [update_uac_request, trans_layer.cpp:2047] WARNING:  While sending 200
> ACK: no matching transaction
> 
> Looks like either Sems or Asterisk is telling Kamailio to drop the call
> - not sure what's going on here? Grateful of any feedback.
> 
> Thanks
> 
> George
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


-- 
Andrew Pogrebennyk
Software Engineer
Sipwise GmbH, Campus 21/Europaring F15
A-2345 Brunn am Gebirge


From gary at netdiverse.com  Tue Aug 19 12:43:00 2014
From: gary at netdiverse.com (Gary Nieboer)
Date: Tue, 19 Aug 2014 10:43:00 -0600
Subject: [Spce-user] Peering Rules database vs. GUI Issue
In-Reply-To: <53E87A4E.7030207@sipwise.com>
References: <CAMXUi2ScE2u1tnGKSsbZUms+64yYTwAb-LsiKCfHJFAs1k7bsg@mail.gmail.com>
 <CAMXUi2S1DkXDE-EWG5N5UKxTqWLz19_T6iLV5mjj4sqU5K2u_g@mail.gmail.com>
 <53E87A4E.7030207@sipwise.com>
Message-ID: <CAMXUi2Q_9z5xD2nGV5=nq7BRFN_jcTXMh73f2wkUs7RGZvXyXg@mail.gmail.com>

Oops - I forgot to send this to the spce list.  So here it is again.

Andreas,

Thanks for the response.



*>>Can you share some information about the history of your setup?
Whichversion did you use for the initial setup? *

This box was a fresh install with version 3.1.1

We upgraded to 3.3.1  about a month ago.

We have increased the usage and complexity of the system, it is 100% "Peer
to Peer" with no subscribers.




*>>Any things you remember doing to your peerings, like deleting groups or
something?*

Yes, we have added, deleted, and edited many   Peering Groups, Peering
Rules and Rewrite Rules in the system through the GUI.

We have about 30 Peering Groups, 250 peering rules, 10 Rewrite Sets, and 25
Rewrite Rules.


Thanks in advance for any recommendations or feedback.

If we are able to update the database tables directly through mysql, and
then have the GUI reflect what is in the database tables, it would be our
ideal situation and resolution.

Thanks,

Gary



On Mon, Aug 11, 2014 at 2:09 AM, Andreas Granig <agranig at sipwise.com> wrote:

> Hi,
>
> Can you share some information about the history of your setup? Which
> version did you use for the initial setup? Any things you remember doing
> to your peerings, like deleting groups or something?
>
> There have been some issues with older versions couple of months ago in
> the triggers synchronizing the databases provisioning and kamailio, but
> they have been fixed in 3.1 already.
>
> Andreas
>
> On 08/11/2014 08:33 AM, Gary Nieboer wrote:
> > I have another instance of the GUI not matching the database.
> >
> > A peering rule ID 233 exists in the database & it was different than the
> > rule showing in the GUI.  Changing the rule in the GUI didn't adjust the
> > database.  Deleting the rule in the GUI didn't adjust the database.
> >
> > Is there anything that can be done to "refresh" the GUI to reflect what
> > is actually in the database.
> >
> > Also, is it safe to use mysql and delete the rule?
> >
> > Thanks,
> >
> > Gary
> >
> > The Example:   In
> >
> > --
> > Gary Nieboer
> >
> >
> > 877-763-1014 Toll Free  |  801-657-5484 Utah  |  615-800-6946 Tennessee
> > | 801-694-6106 Mobile
> > gary at netdiverse.com <mailto:gary at netdiverse.com>  |   www.netdiverse.com
> > <http://www.netdiverse.com/>
> >
> >
> > On Fri, Aug 1, 2014 at 2:55 PM, Gary Nieboer <gary at netdiverse.com
> > <mailto:gary at netdiverse.com>> wrote:
> >
> >
> >     We have experienced a few issues with our "Peering Rules" on SPCE,
> >     3.3.1.
> >
> >     A created rule exists in the GUI, but when routing a call through
> >     the SBC, the call follows a route to a default peer rather than the
> >     peer indicated in the GUI.
> >
> >     We recently did a comparison of what is shown in the database:
> >      lcr_rules
> >
> >                                 select * from lcr_rule;
> >
> >
> >     Here are a few lines from the database:   Some numbers are replaced
> >     with "`" and not fully shown:
> >
> >     Note:  Rule 102 is missing from the database
> >
> >
> >     | id  | lcr_id | prefix | request_uri | from_uri | stopper | enabled
> >     | group_id |
> >
>  +-----+--------+--------+-------------+----------+---------+---------+----------+
> >     | 101 |      1 |        | ~~~~~20088  | NULL     |       0 |       1
> >     |       23 |
> >     | 105 |      1 |        | ~~~~~20186  | NULL     |       0 |       1
> >     |       23 |
> >     | 106 |      1 |        | ~~~~~74891  | NULL     |       0 |       1
> >     |       23 |
> >
> >
> >
> >     Now, here is a screenshot of the GUI for the same rules:
> >     Note:  Rule 102 exists under peer group 23 for the GUI.
> >     Inline image 1
> >
> >
> >
> >     It appears we should trust the data in the database and not the GUI,
> >     but I'm assuming it is not desired behavior for the GUI and database
> >     to reflect different info.
> >
> >     If you would like more information, we can share it.
> >
> >     Please let me know if there is anything we can do to ensure the GUI
> >     reflects the actual activity of the database and ngcp/kamailio.
> >
> >     Thanks,
> >
> >     Gary
> >
> >
> >
> >
> > _______________________________________________
> > 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140819/565d5567/attachment.html>

From joel at vozelia.com  Wed Aug 20 04:49:30 2014
From: joel at vozelia.com (Joel S. | VOZELIA)
Date: Wed, 20 Aug 2014 10:49:30 +0200 (CEST)
Subject: [Spce-user] Prosody XMPP Server unable to store images
	to	offline users
In-Reply-To: <DUB127-W331F391ACF8682CBBB7EA88F9A0@phx.gbl>
References: <DUB127-W49876D8EACB701EFA562338F990@phx.gbl>
 <DUB127-W331F391ACF8682CBBB7EA88F9A0@phx.gbl>
Message-ID: <763259845.527256.1408524570568.JavaMail.zimbra@vozelia.com>

Hi, 

I am experiencing the same problem, did you manage to find a solution?

Best regards, 
Joel.



----- Original Message ----- 

> From: "andreas tseiko" <a.tseiko at hotmail.com>
> To: spce-user at lists.sipwise.com
> Sent: Thursday, February 20, 2014 12:01:46 PM
> Subject: Re: [Spce-user] Prosody XMPP Server unable to store images to
> offline users

> Dear All,

> Is there any update regarding this issue?

> Best regards.

> From: a.tseiko at hotmail.com
> To: spce-user at lists.sipwise.com
> Subject: Prosody XMPP Server unable to store images to offline users
> Date: Mon, 17 Feb 2014 15:46:25 +0200

> Dear All,

> We have installed CE3.1 and we are using Prosody XMPP server for IM.
> When users are on line sending text,images or chating works properly.
> On the other hand when users are offline only text messages are stored while
> images are not.
> Is this a configuration issue or not?
> If it is a configuration issue, could please provide any relevant info on how
> to proceed?

> Best regards.

> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user


From agranig at sipwise.com  Wed Aug 20 05:18:41 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Wed, 20 Aug 2014 11:18:41 +0200
Subject: [Spce-user] Prosody XMPP Server unable to store images
 to	offline users
In-Reply-To: <763259845.527256.1408524570568.JavaMail.zimbra@vozelia.com>
References: <DUB127-W49876D8EACB701EFA562338F990@phx.gbl>
 <DUB127-W331F391ACF8682CBBB7EA88F9A0@phx.gbl>
 <763259845.527256.1408524570568.JavaMail.zimbra@vozelia.com>
Message-ID: <53F467F1.6070305@sipwise.com>

Hi,

File transfer is going either end-to-end or via an external proxy
(whatever is configured in your xmpp client by default, probably some
public xep-0065 proxy, like proxy.eu.jabber.org). You can run your own
using https://prosody.im/doc/modules/mod_proxy65.

The SPCE doesn't have that proxy configured by default, and if it did,
it wouldn't support file transfer store-and-forward. I don't think
prosody supports something like this at all, so development for it would
need to be sponsored for the prosody devs.

Andreas

On 08/20/2014 10:49 AM, Joel S. | VOZELIA wrote:
> Hi, 
> 
> I am experiencing the same problem, did you manage to find a solution?
> 
> Best regards, 
> Joel.
> 
> 
> 
> ----- Original Message ----- 
> 
>> From: "andreas tseiko" <a.tseiko at hotmail.com>
>> To: spce-user at lists.sipwise.com
>> Sent: Thursday, February 20, 2014 12:01:46 PM
>> Subject: Re: [Spce-user] Prosody XMPP Server unable to store images to
>> offline users
> 
>> Dear All,
> 
>> Is there any update regarding this issue?
> 
>> Best regards.
> 
>> From: a.tseiko at hotmail.com
>> To: spce-user at lists.sipwise.com
>> Subject: Prosody XMPP Server unable to store images to offline users
>> Date: Mon, 17 Feb 2014 15:46:25 +0200
> 
>> Dear All,
> 
>> We have installed CE3.1 and we are using Prosody XMPP server for IM.
>> When users are on line sending text,images or chating works properly.
>> On the other hand when users are offline only text messages are stored while
>> images are not.
>> Is this a configuration issue or not?
>> If it is a configuration issue, could please provide any relevant info on how
>> to proceed?
> 
>> Best regards.
> 
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From sipwise at carriba.org  Wed Aug 20 05:29:00 2014
From: sipwise at carriba.org (Carriba UG - sip:wise)
Date: Wed, 20 Aug 2014 09:29:00 +0000
Subject: [Spce-user] Change Peering IP
Message-ID: <em1d137ec4-bd90-43fd-907e-7ae53a0a3026@ws-w7pro-03>

Hello,

I notice if we change the Peering IP without recration of the Peering 
Group, all Inbound calls will be rejected. This is with the last 3 pubic 
Releases.

Please check this Situation for futher releases.

Thanks, Ben.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140820/cd694f9a/attachment.html>

From george.mason at xoomtalk.com  Wed Aug 20 05:43:39 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Wed, 20 Aug 2014 10:43:39 +0100
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F330C5.1040404@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
Message-ID: <53F46DCB.60101@xoomtalk.com>

Hi,

Am using the elastic IP as the advertised address, beforehand for some
reason it had the wrong address in there (was an Amazon address though,
might have been the one assigned to the original AMI image? not sure). I
had calls complete but no audio until I fixed that.

Please find the logs attached (sorry for the large attachment - full UDP
pcap from eth0). Not sure where to look for the source of the issue so
interested to hear any comments.

Thanks

George

On 19/08/14 12:11, Andrew Pogrebennyk wrote:
> Hi,
> what does your /etc/ngcp-config/network.yml look like? You should use
> your Elastic IP as advertised_address. I think AMI configures that by
> default.
>
> Could you provide the kamailio-proxy.log, kamailio-lb.log and complete
> trace? I mean also messages inside spce (lb,proxy,sems).
>
> Regards.
> Andrew
>
> On 08/19/2014 01:01 PM, George Mason wrote:
>> Hi,
>>
>> I am having an issue with the SPCE Amazon EC2 image. I have configured
>> the server to forward all calls to a SIP provider with a couple of IP
>> handsets registered as subscribers. I can get a call to go through to
>> the PSTN and audio in both directions, but the call appears to drop
>> after approx. 30 secs.
>>
>> I have run a UDP trace of the signalling and it looks like SPCE drops
>> the call, I found the following in the logs:
>>
>> rtp.log
>> Aug 19 10:54:53 ip-10-237-180-106 rtpengine[26167]: Got valid command
>> from 127.0.0.1:56413: delete - { "call-id":
>> "60174c70-66e7d6e1 at 192.168.100.136", "received-from": [ "IP4",
>> "127.0.0.1" ], "from-tag": "317FA286-53F32CDB000A6E08-C56FB700",
>> "to-tag": "2cfee724f53bdbbdo0", "command": "delete" }
>>
>> sems.log
>> Aug 19 10:54:53 ip-10-237-180-106 ngcp-sems[26328]: [#7f11c4ef3700]
>> [update_uac_request, trans_layer.cpp:2047] WARNING:  While sending 200
>> ACK: no matching transaction
>>
>> Looks like either Sems or Asterisk is telling Kamailio to drop the call
>> - not sure what's going on here? Grateful of any feedback.
>>
>> Thanks
>>
>> George
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: spce-files.zip
Type: application/zip
Size: 782421 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140820/fd2c55b9/attachment.zip>

From alessandro.romano at rpeng.it  Wed Aug 20 05:40:58 2014
From: alessandro.romano at rpeng.it (Alessandro Romano - Rp engineering)
Date: Wed, 20 Aug 2014 11:40:58 +0200
Subject: [Spce-user] max-forward
Message-ID: <000a01cfbc5a$d95664b0$8c032e10$@rpeng.it>

Dear All,

the my voip service provider has asked me to set the max-forward to 70
instead of 10

 

what is the procedure ?

 

BR

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140820/43f15e63/attachment.html>

From agranig at sipwise.com  Wed Aug 20 06:00:16 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Wed, 20 Aug 2014 12:00:16 +0200
Subject: [Spce-user] Change Peering IP
In-Reply-To: <em1d137ec4-bd90-43fd-907e-7ae53a0a3026@ws-w7pro-03>
References: <em1d137ec4-bd90-43fd-907e-7ae53a0a3026@ws-w7pro-03>
Message-ID: <53F471B0.1050104@sipwise.com>

Hi,

The provisioning interface probably fails to reload your kamailio
dispatcher table. Check in provisioning.xmlhosts table if the IP and
port of your kamailio is correct (it's 127.0.0.1 with port 8000 and
5062. If you played around with changing internal IPs, this table might
have gotten messed up.

It'd also help to check your kamailio.dispatcher table to see if it's in
sync with your provisoning.voip_peer_hosts table. Could be some data
inconsistency caused in older versions.

Andreas

On 08/20/2014 11:29 AM, Carriba UG - sip:wise wrote:
> Hello,
>  
> I notice if we change the Peering IP without recration of the Peering
> Group, all Inbound calls will be rejected. This is with the last 3 pubic
> Releases.
>  
> Please check this Situation for futher releases.
>  
> Thanks, Ben.
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From apogrebennyk at sipwise.com  Wed Aug 20 06:01:31 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Wed, 20 Aug 2014 12:01:31 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F46DCB.60101@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com>
Message-ID: <53F471FB.1020109@sipwise.com>

Hi,
I believe I have found the problem. We have to reconsider contact
masking in kamailio-lb if adv address is set. I'll try to push an update
with the fix later today. Thanks for the bugreport.

BR,
Andrew

On 08/20/2014 11:43 AM, George Mason wrote:
> Hi,
> 
> Am using the elastic IP as the advertised address, beforehand for some
> reason it had the wrong address in there (was an Amazon address though,
> might have been the one assigned to the original AMI image? not sure). I
> had calls complete but no audio until I fixed that.
> 
> Please find the logs attached (sorry for the large attachment - full UDP
> pcap from eth0). Not sure where to look for the source of the issue so
> interested to hear any comments.
> 
> Thanks
> 
> George



From george.mason at xoomtalk.com  Wed Aug 20 06:16:50 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Wed, 20 Aug 2014 11:16:50 +0100
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F471FB.1020109@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
Message-ID: <53F47592.6040905@xoomtalk.com>

On 20/08/14 11:01, Andrew Pogrebennyk wrote:
> Hi,
> I believe I have found the problem. We have to reconsider contact
> masking in kamailio-lb if adv address is set. I'll try to push an update
> with the fix later today. Thanks for the bugreport.
>
> BR,
> Andrew
Excellent many thanks. Grateful if you could push to the East Coast AWS
zone when you do.

George


From apogrebennyk at sipwise.com  Wed Aug 20 09:13:02 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Wed, 20 Aug 2014 15:13:02 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F47592.6040905@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com>
Message-ID: <53F49EDE.301@sipwise.com>

George,

On 08/20/2014 12:16 PM, George Mason wrote:
> Excellent many thanks. Grateful if you could push to the East Coast AWS
> zone when you do.
> 
> George

alright, I have pushed the fix. Actually you don't need to re-create the
instance, just run the update:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

The problem was that the private IP of the instance was used as contact
in initial invite instead of the adv address and the dialog was changed
from private IP to adv address on the consequent in-dialog request,
which broke the signaling. I just fixed the contact masking.
Let me know if that fixes your issue.

Andrew



From george.mason at xoomtalk.com  Wed Aug 20 16:59:05 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Wed, 20 Aug 2014 21:59:05 +0100
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F49EDE.301@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
Message-ID: <53F50C19.2050807@xoomtalk.com>

 
> George,
>
> On 08/20/2014 12:16 PM, George Mason wrote:
>> > Excellent many thanks. Grateful if you could push to the East Coast AWS
>> > zone when you do.
>> > 
>> > George
> alright, I have pushed the fix. Actually you don't need to re-create the
> instance, just run the update:
>
>   apt-get update && apt-get upgrade && \
>   ngcp-update-db-schema && ngcp-update-cfg-schema && \
>   ngcpcfg apply
>
> The problem was that the private IP of the instance was used as contact
> in initial invite instead of the adv address and the dialog was changed
> from private IP to adv address on the consequent in-dialog request,
> which broke the signaling. I just fixed the contact masking.
> Let me know if that fixes your issue.
>
> Andrew
Thanks - ran the update and was all looking good, until:

Applying revision script
/usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: ERROR
1050 (42S01) at line 2: Table 'acc_backup' already exists
failed. :(

Not sure whether this is something to worry about? Looks like it's no
big deal but thought I would check.




From apogrebennyk at sipwise.com  Wed Aug 20 17:06:30 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Wed, 20 Aug 2014 23:06:30 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F50C19.2050807@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com>
Message-ID: <53F50DD6.7060203@sipwise.com>

On 20/08/14 22:59, George Mason wrote:
> Thanks - ran the update and was all looking good, until:
> 
> Applying revision script
> /usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: ERROR
> 1050 (42S01) at line 2: Table 'acc_backup' already exists
> failed. :(
> 
> Not sure whether this is something to worry about? Looks like it's no
> big deal but thought I would check.

I will check tomorrow if this is the AMI problem, meanwhile please
update your "node" column in the tables "db_schema" and "cfg_schema" in
database "ngcp" to the actual hostname of your machine.

Andrew



From mprokop at sipwise.com  Wed Aug 20 17:10:18 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Wed, 20 Aug 2014 23:10:18 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F46DCB.60101@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com>
Message-ID: <2014-08-20T22-48-29@devnull.michael-prokop.at>

* George Mason [Wed Aug 20, 2014 at 10:43:39AM +0100]:

> Am using the elastic IP as the advertised address, beforehand for some
> reason it had the wrong address in there (was an Amazon address though,
> might have been the one assigned to the original AMI image? not sure). I
> had calls complete but no audio until I fixed that.

Thanks for raising this issue, we just investigated and indeed the
advertised address doesn't get automatically updated yet - that's
why you got the IP address of the system we built the AMI on.

We've got a change in our release queue which addresses this issue.
Once this change gets released during (re)boot / network restart of
your system the advertised address gets automatically adjusted for
you, so this problem shouldn't exist any longer.

We also discussed the issue regarding our AMI in different regions
and decided to provide the sip:provider CE AMI in all EC2 regions.
The feature to automatically take care of that in our release cycle
was just implemented, so on our next public AMI build you'll have
AMIs in all regions available.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140820/376ae952/attachment.asc>

From mprokop at sipwise.com  Wed Aug 20 17:42:55 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Wed, 20 Aug 2014 23:42:55 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F50DD6.7060203@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com> <53F50DD6.7060203@sipwise.com>
Message-ID: <2014-08-20T23-37-43@devnull.michael-prokop.at>

* Andrii Pogrebennyk [Wed Aug 20, 2014 at 11:06:30PM +0200]:
> On 20/08/14 22:59, George Mason wrote:
> > Thanks - ran the update and was all looking good, until:

> > Applying revision script
> > /usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: ERROR
> > 1050 (42S01) at line 2: Table 'acc_backup' already exists
> > failed. :(

> > Not sure whether this is something to worry about? Looks like it's no
> > big deal but thought I would check.

> I will check tomorrow if this is the AMI problem, meanwhile please
> update your "node" column in the tables "db_schema" and "cfg_schema" in
> database "ngcp" to the actual hostname of your machine.

Without verifying on my own yet this could very well be cloud-init*
tools on EC2 taking care of automatically adjusting /etc/hostname -
therefore modifying the hostname and confusing ngcp-db-schema
scripts.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140820/b3b989a5/attachment.asc>

From gary at netdiverse.com  Wed Aug 20 22:45:56 2014
From: gary at netdiverse.com (Gary Nieboer)
Date: Wed, 20 Aug 2014 20:45:56 -0600
Subject: [Spce-user] max-forward
In-Reply-To: <000a01cfbc5a$d95664b0$8c032e10$@rpeng.it>
References: <000a01cfbc5a$d95664b0$8c032e10$@rpeng.it>
Message-ID: <CAMXUi2R4EnAfVS+kpe4Gs_A2r75jQCAn+mwicEw2D47-GbZq1Q@mail.gmail.com>

I did this by editing the variable in the kamailio section of:
 /etc/ngcp-config/config.yml file

kamailio:
  lb:
    debug: 'no'
    extra_sockets: ~
    *max_forwards: 70*


Don't forget to run:   "ngcpcfg apply"   when you're done so they are
applied to kamailio.

Good luck.

-Gary


--
Gary Nieboer


877-763-1014 Toll Free  |  801-657-5484 Utah  |  615-800-6946 Tennessee  |
801-694-6106 Mobile
gary at netdiverse.com  |   www.netdiverse.com


On Wed, Aug 20, 2014 at 3:40 AM, Alessandro Romano - Rp engineering <
alessandro.romano at rpeng.it> wrote:

> Dear All,
>
> the my voip service provider has asked me to set the max-forward to 70
> instead of 10
>
>
>
> what is the procedure ?
>
>
>
> BR
>
> _______________________________________________
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140820/f48fb470/attachment.html>

From mprokop at sipwise.com  Thu Aug 21 03:26:24 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Thu, 21 Aug 2014 09:26:24 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <2014-08-20T23-37-43@devnull.michael-prokop.at>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com> <53F50DD6.7060203@sipwise.com>
 <2014-08-20T23-37-43@devnull.michael-prokop.at>
Message-ID: <2014-08-21T09-22-43@devnull.michael-prokop.at>

* Michael Prokop [Wed Aug 20, 2014 at 11:42:55PM +0200]:
> * Andrii Pogrebennyk [Wed Aug 20, 2014 at 11:06:30PM +0200]:

> > I will check tomorrow if this is the AMI problem, meanwhile please
> > update your "node" column in the tables "db_schema" and "cfg_schema" in
> > database "ngcp" to the actual hostname of your machine.

> Without verifying on my own yet this could very well be cloud-init*
> tools on EC2 taking care of automatically adjusting /etc/hostname -
> therefore modifying the hostname and confusing ngcp-db-schema
> scripts.

Just verified this, it indeed is cloud-init tools which
automatically adjusts the hostname, causing problems with
{cfg,db}_schema:

| /var/log/user.log:Aug 21 06:50:37 ip-10-37-133-236 [CLOUDINIT] cc_update_hostname.py[DEBUG]: Updating hostname to ip-10-91-133-125.eu-west-1.compute.internal (ip-10-91-133-125)

I've opened a ticket in our BTS to address this problem (MT#8731 if
anyone wants to refer to it).

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140821/3e86cd3c/attachment.asc>

From george.mason at xoomtalk.com  Thu Aug 21 04:21:15 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Thu, 21 Aug 2014 09:21:15 +0100
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F50DD6.7060203@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com> <53F50DD6.7060203@sipwise.com>
Message-ID: <53F5ABFB.5070302@xoomtalk.com>


On 20/08/14 22:06, Andrew Pogrebennyk wrote:
> I will check tomorrow if this is the AMI problem, meanwhile please
> update your "node" column in the tables "db_schema" and "cfg_schema" in
> database "ngcp" to the actual hostname of your machine.
Does this address the issue I raised or is this just something I need to
do as part of a new install?


From george.mason at xoomtalk.com  Thu Aug 21 04:22:52 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Thu, 21 Aug 2014 09:22:52 +0100
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <2014-08-21T09-22-43@devnull.michael-prokop.at>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com> <53F50DD6.7060203@sipwise.com>
 <2014-08-20T23-37-43@devnull.michael-prokop.at>
 <2014-08-21T09-22-43@devnull.michael-prokop.at>
Message-ID: <53F5AC5C.9020301@xoomtalk.com>


On 21/08/14 08:26, Michael Prokop wrote:
> Just verified this, it indeed is cloud-init tools which
> automatically adjusts the hostname, causing problems with
> {cfg,db}_schema:
>
> | /var/log/user.log:Aug 21 06:50:37 ip-10-37-133-236 [CLOUDINIT] cc_update_hostname.py[DEBUG]: Updating hostname to ip-10-91-133-125.eu-west-1.compute.internal (ip-10-91-133-125)
>
> I've opened a ticket in our BTS to address this problem (MT#8731 if
> anyone wants to refer to it).
Is there a workaround for this until the patch is released? Presumably
if this hostname is incorrect then this is the root cause of the problem?


From apogrebennyk at sipwise.com  Thu Aug 21 04:25:21 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Thu, 21 Aug 2014 10:25:21 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F5ABFB.5070302@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com> <53F50DD6.7060203@sipwise.com>
 <53F5ABFB.5070302@xoomtalk.com>
Message-ID: <53F5ACF1.8090607@sipwise.com>

Hi,

On 08/21/2014 10:21 AM, George Mason wrote:
> 
> On 20/08/14 22:06, Andrew Pogrebennyk wrote:
>> I will check tomorrow if this is the AMI problem, meanwhile please
>> update your "node" column in the tables "db_schema" and "cfg_schema" in
>> database "ngcp" to the actual hostname of your machine.
> Does this address the issue I raised or is this just something I need to
> do as part of a new install?

This is the workaround for error on upgrade:

Applying revision script
/usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: ERROR
1050 (42S01) at line 2: Table 'acc_backup' already exists failed.

The issue here was that the scripts for updating db and yml configs rely
on the hostname, which is changing upon boot in the amazon ec2 instance.
Proper fix for it is under way.

Andrew


From george.mason at xoomtalk.com  Thu Aug 21 04:43:51 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Thu, 21 Aug 2014 09:43:51 +0100
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F5ACF1.8090607@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com> <53F50DD6.7060203@sipwise.com>
 <53F5ABFB.5070302@xoomtalk.com> <53F5ACF1.8090607@sipwise.com>
Message-ID: <53F5B147.1020709@xoomtalk.com>

On 21/08/14 09:25, Andrew Pogrebennyk wrote:
> The issue here was that the scripts for updating db and yml configs rely
> on the hostname, which is changing upon boot in the amazon ec2 instance.
> Proper fix for it is under way.

Understood, thanks for the clarification. Presumably this means that the
hostname in the DB would have to be updated (if the machine has been
rebooted) every time an update was run - until your patch at least?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140821/a4eca55c/attachment.html>

From mprokop at sipwise.com  Thu Aug 21 05:33:26 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Thu, 21 Aug 2014 11:33:26 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F5B147.1020709@xoomtalk.com>
References: <53F330C5.1040404@sipwise.com> <53F46DCB.60101@xoomtalk.com>
 <53F471FB.1020109@sipwise.com> <53F47592.6040905@xoomtalk.com>
 <53F49EDE.301@sipwise.com> <53F50C19.2050807@xoomtalk.com>
 <53F50DD6.7060203@sipwise.com> <53F5ABFB.5070302@xoomtalk.com>
 <53F5ACF1.8090607@sipwise.com> <53F5B147.1020709@xoomtalk.com>
Message-ID: <2014-08-21T11-31-41@devnull.michael-prokop.at>

* George Mason [Thu Aug 21, 2014 at 09:43:51AM +0100]:
> On 21/08/14 09:25, Andrew Pogrebennyk wrote:
> > The issue here was that the scripts for updating db and yml configs rely
> > on the hostname, which is changing upon boot in the amazon ec2 instance.
> > Proper fix for it is under way.

> Understood, thanks for the clarification. Presumably this means that the
> hostname in the DB would have to be updated (if the machine has been
> rebooted) every time an update was run - until your patch at least?

Modifications - at least until we released our fix - should be
necessary only if you're starting it as new instance, an already
running instance which just gets updated or rebooted shouldn't be
affected AFAICT.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140821/a3621041/attachment.asc>

From mprokop at sipwise.com  Thu Aug 21 10:04:10 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Thu, 21 Aug 2014 16:04:10 +0200
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1 (was: Re: Calls drop after
 30 secs)
In-Reply-To: <2014-08-20T22-48-29@devnull.michael-prokop.at>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com>
 <2014-08-20T22-48-29@devnull.michael-prokop.at>
Message-ID: <2014-08-21T15-52-10@devnull.michael-prokop.at>

* Michael Prokop [Wed Aug 20, 2014 at 11:10:18PM +0200]:
> * George Mason [Wed Aug 20, 2014 at 10:43:39AM +0100]:

> > Am using the elastic IP as the advertised address, beforehand for some
> > reason it had the wrong address in there (was an Amazon address though,
> > might have been the one assigned to the original AMI image? not sure). I
> > had calls complete but no audio until I fixed that.

> Thanks for raising this issue, we just investigated and indeed the
> advertised address doesn't get automatically updated yet - that's
> why you got the IP address of the system we built the AMI on.

> We've got a change in our release queue which addresses this issue.
> Once this change gets released during (re)boot / network restart of
> your system the advertised address gets automatically adjusted for
> you, so this problem shouldn't exist any longer.

Executing:

  apt-get update ; apt-get upgrade

on mr3.4.1 will provide the updated package ngcp-system-tools-ce
version 0.12.1.4+0~mr3.4.1.4 which includes this change to address
the automatic advertised address adjustment on EC2 systems.

> We also discussed the issue regarding our AMI in different regions
> and decided to provide the sip:provider CE AMI in all EC2 regions.
> The feature to automatically take care of that in our release cycle
> was just implemented, so on our next public AMI build you'll have
> AMIs in all regions available.

We just rebuilt the AMI for ngcp-ce-mr3.4.1 to include the
ngcp-system-tools-ce 0.12.1.4+0~mr3.4.1.4 package and this gave us
the option to release our AMI for all EC2 regions, so here we go:

  AMI ID for region us-east-1: ami-2268b64a
  AMI ID for region us-west-2: ami-256e2a15
  AMI ID for region us-west-1: ami-2bfcf06e
  AMI ID for region eu-west-1: ami-ead30d9d
  AMI ID for region ap-southeast-1: ami-222d7770
  AMI ID for region ap-southeast-2: ami-67aecf5d
  AMI ID for region ap-northeast-1: ami-67634766
  AMI ID for region sa-east-1: ami-f33199ee

If you should notice any further issues please let us know.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140821/e33370e5/attachment.asc>

From george.mason at xoomtalk.com  Thu Aug 21 13:09:44 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Thu, 21 Aug 2014 18:09:44 +0100
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <2014-08-21T15-52-10@devnull.michael-prokop.at>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
Message-ID: <53F627D8.7060702@xoomtalk.com>

On 21/08/14 15:04, Michael Prokop wrote:
> on mr3.4.1 will provide the updated package ngcp-system-tools-ce
> version 0.12.1.4+0~mr3.4.1.4 which includes this change to address
> the automatic advertised address adjustment on EC2 systems.

Have just updated my EC2 instance, can see that ngcp-system-tools-ce has
upgraded to 3.4.1.4 but calls still drop after 30s. Unless I'm
misunderstanding, that update should have cured the elastic IP issue,
which should have resolved this?

Thanks

George
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140821/4d25c437/attachment.html>

From mprokop at sipwise.com  Thu Aug 21 17:00:11 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Thu, 21 Aug 2014 23:00:11 +0200
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F627D8.7060702@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com>
 <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
Message-ID: <2014-08-21T22-45-52@devnull.michael-prokop.at>

* George Mason [Thu Aug 21, 2014 at 06:09:44PM +0100]:
> On 21/08/14 15:04, Michael Prokop wrote:
> > on mr3.4.1 will provide the updated package ngcp-system-tools-ce
> > version 0.12.1.4+0~mr3.4.1.4 which includes this change to address
> > the automatic advertised address adjustment on EC2 systems.

> Have just updated my EC2 instance, can see that ngcp-system-tools-ce has
> upgraded to 3.4.1.4 but calls still drop after 30s. Unless I'm
> misunderstanding, that update should have cured the elastic IP issue,
> which should have resolved this?

The ngcp-system-tools-ce update just ensures that the advertised IP
configuration in network.yml is OK in the classic EC2 scenario. You
can verify this on your own by checking whether the configuration in
/etc/ngcp-config/network.yml matches the IP address reported via
executing 'facter ec2_public_ipv4' on the command line.

What's still missing is the fix to make sure that db-schema and
cfg-schema work independent from the hostname (this is fixed in our
"trunk" already but is waiting for an according release yet).

But did you adjust the node name entries in the ngcp.cfg_schema and
ngcp.db_schema tables so you're fully up2date with:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

yet? Because if you've up2date db-schema and cfg-schema changes
applied that should be working fine AFAIK, if not please let us
know.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140821/dde2464e/attachment.asc>

From george.mason at xoomtalk.com  Thu Aug 21 18:37:25 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Thu, 21 Aug 2014 23:37:25 +0100
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <2014-08-21T22-45-52@devnull.michael-prokop.at>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
 <2014-08-21T22-45-52@devnull.michael-prokop.at>
Message-ID: <53F674A5.7080800@xoomtalk.com>


> * George Mason [Thu Aug 21, 2014 at 06:09:44PM +0100]:
>> On 21/08/14 15:04, Michael Prokop wrote:
>>> on mr3.4.1 will provide the updated package ngcp-system-tools-ce
>>> version 0.12.1.4+0~mr3.4.1.4 which includes this change to address
>>> the automatic advertised address adjustment on EC2 systems.
>
>> Have just updated my EC2 instance, can see that ngcp-system-tools-ce has
>> upgraded to 3.4.1.4 but calls still drop after 30s. Unless I'm
>> misunderstanding, that update should have cured the elastic IP issue,
>> which should have resolved this?
>
> The ngcp-system-tools-ce update just ensures that the advertised IP
> configuration in network.yml is OK in the classic EC2 scenario. You
> can verify this on your own by checking whether the configuration in
> /etc/ngcp-config/network.yml matches the IP address reported via
> executing 'facter ec2_public_ipv4' on the command line.
Thanks - yes this has worked fine, the two match up.
>
>
> What's still missing is the fix to make sure that db-schema and
> cfg-schema work independent from the hostname (this is fixed in our
> "trunk" already but is waiting for an according release yet).
>
> But did you adjust the node name entries in the ngcp.cfg_schema and
> ngcp.db_schema tables so you're fully up2date with:
>
>   apt-get update && apt-get upgrade && \
>   ngcp-update-db-schema && ngcp-update-cfg-schema && \
>   ngcpcfg apply
>
> yet? Because if you've up2date db-schema and cfg-schema changes
> applied that should be working fine AFAIK, if not please let us
> know.
Unfortunately not working for me. I updated the node (to the EC2
internal hostname - in this case ip-10-237-180-106) in both db_schema
and cfg_schema and re-ran the update as above, but still receive the
following error on upgrade:

Applying revision script
/usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: ERROR
1050 (42S01) at line 2: Table 'acc_backup' already exists
failed. :(





From apogrebennyk at sipwise.com  Fri Aug 22 04:34:43 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Fri, 22 Aug 2014 10:34:43 +0200
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F627D8.7060702@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
Message-ID: <53F700A3.2030401@sipwise.com>

George,

On 08/21/2014 07:09 PM, George Mason wrote:
> Have just updated my EC2 instance, can see that ngcp-system-tools-ce has
> upgraded to 3.4.1.4 but calls still drop after 30s. Unless I'm
> misunderstanding, that update should have cured the elastic IP issue,
> which should have resolved this?

What version of templates do you have, e.g. dpkg -l
ngcp-templates-ce-kamailio ? Should be mr3.4.1.4.

Did you execute ngcpcfg apply after the templates upgrade?

If so I would like to check the kamailio-lb.log and kamailio-proxy.log
again, this time please raise the debug level with:
ngcp-kamctl proxy fifo debug 2
ngcp-kamctl lb fifo debug 2

And a pcap trace or ngrep-sip output would be helpful too.

Andrew


From apogrebennyk at sipwise.com  Fri Aug 22 05:19:07 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Fri, 22 Aug 2014 11:19:07 +0200
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F674A5.7080800@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
 <2014-08-21T22-45-52@devnull.michael-prokop.at>
 <53F674A5.7080800@xoomtalk.com>
Message-ID: <53F70B0B.6010308@sipwise.com>

Hi,
regarding the hostname change:

On 08/22/2014 12:37 AM, George Mason wrote:
> Unfortunately not working for me. I updated the node (to the EC2
> internal hostname - in this case ip-10-237-180-106) in both db_schema
> and cfg_schema and re-ran the update as above, but still receive the
> following error on upgrade:
> 
> Applying revision script
> /usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: ERROR
> 1050 (42S01) at line 2: Table 'acc_backup' already exists
> failed. :(

please update the node in both db_schema and cfg_schema to "spce"
instead of the internal hostname. That should help. I latest mr3.4.1 we
do not rely on the hostname anymore, instead the update scripts look
into /etc/ngcp_nodename.

Andrew


From george.mason at xoomtalk.com  Fri Aug 22 05:26:43 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Fri, 22 Aug 2014 10:26:43 +0100
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F70B0B.6010308@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
 <2014-08-21T22-45-52@devnull.michael-prokop.at>
 <53F674A5.7080800@xoomtalk.com> <53F70B0B.6010308@sipwise.com>
Message-ID: <53F70CD3.5060406@xoomtalk.com>


On 22/08/14 10:19, Andrew Pogrebennyk wrote:
> please update the node in both db_schema and cfg_schema to "spce"
> instead of the internal hostname. That should help. I latest mr3.4.1 we
> do not rely on the hostname anymore, instead the update scripts look
> into /etc/ngcp_nodename.

Did this, and the upgrade ran fine. So that's good. Unfortunately calls
still drop after 30 secs so am in the process of taking another PCAP and
Kamailio logs.

> What version of templates do you have, e.g. dpkg -l
> ngcp-templates-ce-kamailio ? Should be mr3.4.1.4.
ii  ngcp-templates-ce-kamailio                3.4.1.4+0~mr3.4.1.4      
all                       Configuration templates for Kamailio
configuration in NGCP platforms





From george.mason at xoomtalk.com  Fri Aug 22 05:32:03 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Fri, 22 Aug 2014 10:32:03 +0100
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F70CD3.5060406@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
 <2014-08-21T22-45-52@devnull.michael-prokop.at>
 <53F674A5.7080800@xoomtalk.com> <53F70B0B.6010308@sipwise.com>
 <53F70CD3.5060406@xoomtalk.com>
Message-ID: <53F70E13.5010306@xoomtalk.com>


> On 22/08/14 10:19, Andrew Pogrebennyk wrote:
>> please update the node in both db_schema and cfg_schema to "spce"
>> instead of the internal hostname. That should help. I latest mr3.4.1 we
>> do not rely on the hostname anymore, instead the update scripts look
>> into /etc/ngcp_nodename.
> Did this, and the upgrade ran fine. So that's good. Unfortunately calls
> still drop after 30 secs so am in the process of taking another PCAP and
> Kamailio logs.
>
>> What version of templates do you have, e.g. dpkg -l
>> ngcp-templates-ce-kamailio ? Should be mr3.4.1.4.
> ii  ngcp-templates-ce-kamailio                3.4.1.4+0~mr3.4.1.4      
> all                       Configuration templates for Kamailio
> configuration in NGCP platforms
>

Logs + PCAPs attached

-------------- next part --------------
A non-text attachment was scrubbed...
Name: pcap.zip
Type: application/zip
Size: 171351 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140822/c3e86044/attachment.zip>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logs.zip
Type: application/zip
Size: 218440 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140822/c3e86044/attachment-0001.zip>

From apogrebennyk at sipwise.com  Fri Aug 22 06:27:11 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Fri, 22 Aug 2014 12:27:11 +0200
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F70E13.5010306@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
 <2014-08-21T22-45-52@devnull.michael-prokop.at>
 <53F674A5.7080800@xoomtalk.com> <53F70B0B.6010308@sipwise.com>
 <53F70CD3.5060406@xoomtalk.com> <53F70E13.5010306@xoomtalk.com>
Message-ID: <53F71AFF.5090108@sipwise.com>

On 08/22/2014 11:32 AM, George Mason wrote:
> Logs + PCAPs attached

Hm, I think the problem now lies with the callee with 169.* IP. It
should acknowledge 200 OK after re-INVITE in packet #31 (eth0.pcap) with
an ACK message. At a glance I don't see any problem in packets sent to
169.* IP. The route set and Contact are correct now. Could you ask that
carrier what is the problem with acknowledging on their side?

Andrew


From aclark at structuredcommunications.co.uk  Fri Aug 22 11:22:41 2014
From: aclark at structuredcommunications.co.uk (Adam Clark)
Date: Fri, 22 Aug 2014 15:22:41 +0000
Subject: [Spce-user] Billing Profile Web Error
Message-ID: <E80006BDE297C94AADE7963C138CC416D99EEC7F@SR-AD.structured.local>

Afternoon all,

We have just uploaded a large 9500 line CSV file with "purge" ticked.

The file uploaded, however that profile once selected via the admin interface gets the web error "(en) Please come back later"

The OSS.log reports:

Aug 22 16:16:07 sipwise /usr/sbin/apache2: Caught exception in admin::Controller::billing->search_fees "Can't escape \x{FEFF}, try uri_escape_utf8() instead at /usr/share/ngcp-www-admin/lib/admin/Controller/billing.pm line 530"

We have looked at the table in SQL and it only has 560 odd lines ?


1)  Does sipwise not handle a zone file this large?

2)  Can we delete the profile from SQL or restore a backup without destroying anything?

Any help would be grateful.


Kind regards,

[sig1]

This e-mail and any attachments transmitted with it, including replies and forwarded copies subsequently transmitted, contains information which may be confidential and which may also be legally privileged. The content of this e-mail is for the exclusive use of the individual(s) or entity named above, if you are not the intended recipient, please note that any form of distribution, copying or use of this e-mail or the information in it is strictly prohibited and may be unlawful. If you have received this e-mail in error please reply to the sender at Structured Communications Ltd and then delete the e-mail immediately. Any views or opinions presented are solely those of the author, and may not necessarily represent those of Structured Communications Ltd. Structured Communications Ltd is registered in England and Wales, registered no 07667451, and its registered office is 22 London Road, Horsham, West Sussex RH12 1AY. Registered VAT number GB116507336.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140822/07a586ea/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 12937 bytes
Desc: image001.png
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140822/07a586ea/attachment.png>

From joel at vozelia.com  Fri Aug 22 17:54:13 2014
From: joel at vozelia.com (Joel S. | VOZELIA)
Date: Fri, 22 Aug 2014 23:54:13 +0200 (CEST)
Subject: [Spce-user] Prosody XMPP Server unable to store images
	to	offline users
In-Reply-To: <53F467F1.6070305@sipwise.com>
References: <DUB127-W49876D8EACB701EFA562338F990@phx.gbl>
 <DUB127-W331F391ACF8682CBBB7EA88F9A0@phx.gbl>
 <763259845.527256.1408524570568.JavaMail.zimbra@vozelia.com>
 <53F467F1.6070305@sipwise.com>
Message-ID: <1461629263.605282.1408744453802.JavaMail.zimbra@vozelia.com>

Thank you Andreas.

I will give a try with mod_proxy65 :)

Best regards, 
Joel.


----- Original Message -----
> From: "Andreas Granig" <agranig at sipwise.com>
> To: spce-user at lists.sipwise.com
> Sent: Wednesday, August 20, 2014 11:18:41 AM
> Subject: Re: [Spce-user] Prosody XMPP Server unable to store images to	offline users
> 
> Hi,
> 
> File transfer is going either end-to-end or via an external proxy
> (whatever is configured in your xmpp client by default, probably some
> public xep-0065 proxy, like proxy.eu.jabber.org). You can run your own
> using https://prosody.im/doc/modules/mod_proxy65.
> 
> The SPCE doesn't have that proxy configured by default, and if it did,
> it wouldn't support file transfer store-and-forward. I don't think
> prosody supports something like this at all, so development for it would
> need to be sponsored for the prosody devs.
> 
> Andreas
> 
> On 08/20/2014 10:49 AM, Joel S. | VOZELIA wrote:
> > Hi,
> > 
> > I am experiencing the same problem, did you manage to find a solution?
> > 
> > Best regards,
> > Joel.
> > 
> > 
> > 
> > ----- Original Message -----
> > 
> >> From: "andreas tseiko" <a.tseiko at hotmail.com>
> >> To: spce-user at lists.sipwise.com
> >> Sent: Thursday, February 20, 2014 12:01:46 PM
> >> Subject: Re: [Spce-user] Prosody XMPP Server unable to store images to
> >> offline users
> > 
> >> Dear All,
> > 
> >> Is there any update regarding this issue?
> > 
> >> Best regards.
> > 
> >> From: a.tseiko at hotmail.com
> >> To: spce-user at lists.sipwise.com
> >> Subject: Prosody XMPP Server unable to store images to offline users
> >> Date: Mon, 17 Feb 2014 15:46:25 +0200
> > 
> >> Dear All,
> > 
> >> We have installed CE3.1 and we are using Prosody XMPP server for IM.
> >> When users are on line sending text,images or chating works properly.
> >> On the other hand when users are offline only text messages are stored
> >> while
> >> images are not.
> >> Is this a configuration issue or not?
> >> If it is a configuration issue, could please provide any relevant info on
> >> how
> >> to proceed?
> > 
> >> Best regards.
> > 
> >> _______________________________________________
> >> Spce-user mailing list
> >> Spce-user at lists.sipwise.com
> >> http://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
> 


From george.mason at xoomtalk.com  Sat Aug 23 05:07:54 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Sat, 23 Aug 2014 10:07:54 +0100
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F71AFF.5090108@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
 <2014-08-21T22-45-52@devnull.michael-prokop.at>
 <53F674A5.7080800@xoomtalk.com> <53F70B0B.6010308@sipwise.com>
 <53F70CD3.5060406@xoomtalk.com> <53F70E13.5010306@xoomtalk.com>
 <53F71AFF.5090108@sipwise.com>
Message-ID: <53F859EA.5010705@xoomtalk.com>


> On 08/22/2014 11:32 AM, George Mason wrote:
>> > Logs + PCAPs attached
> Hm, I think the problem now lies with the callee with 169.* IP. It
> should acknowledge 200 OK after re-INVITE in packet #31 (eth0.pcap) with
> an ACK message. At a glance I don't see any problem in packets sent to
> 169.* IP. The route set and Contact are correct now. Could you ask that
> carrier what is the problem with acknowledging on their side?
>
> Andrew

Thanks Andrew - will check and potentially route via a different carrier
and report back.

George


From agranig at sipwise.com  Sat Aug 23 06:56:06 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Sat, 23 Aug 2014 12:56:06 +0200
Subject: [Spce-user] Billing Profile Web Error
In-Reply-To: <E80006BDE297C94AADE7963C138CC416D99EEC7F@SR-AD.structured.local>
References: <E80006BDE297C94AADE7963C138CC416D99EEC7F@SR-AD.structured.local>
Message-ID: <53F87346.8080309@sipwise.com>

Hello,

Which version are you using? 2.8?

The issue is not the size, rather than a character in your file seems to
cause issues with utf-8 handling.

Can you provide the file (also in private, and with zeroed fees)?

Andreas

On 08/22/2014 05:22 PM, Adam Clark wrote:
> Afternoon all,
> 
>  
> 
> We have just uploaded a large 9500 line CSV file with ?purge? ticked.
> 
>  
> 
> The file uploaded, however that profile once selected via the admin
> interface gets the web error ?(en) Please come back later?
> 
>  
> 
> The OSS.log reports:
> 
>  
> 
> Aug 22 16:16:07 sipwise /usr/sbin/apache2: Caught exception in
> admin::Controller::billing->search_fees "Can't escape \x{FEFF}, try
> uri_escape_utf8() instead at
> /usr/share/ngcp-www-admin/lib/admin/Controller/billing.pm line 530"
> 
>  
> 
> We have looked at the table in SQL and it only has 560 odd lines ?
> 
>  
> 
> 1)  Does sipwise not handle a zone file this large?
> 
> 2)  Can we delete the profile from SQL or restore a backup without
> destroying anything?
> 
>  
> 
> Any help would be grateful.
> 
>  
> 
>  
> 
> Kind regards,
> 
>  
> 
> sig1
> 
>  
> 
> This e-mail and any attachments transmitted with it, including replies
> and forwarded copies subsequently transmitted, contains information
> which may be confidential and which may also be legally privileged. The
> content of this e-mail is for the exclusive use of the individual(s) or
> entity named above, if you are not the intended recipient, please note
> that any form of distribution, copying or use of this e-mail or the
> information in it is strictly prohibited and may be unlawful. If you
> have received this e-mail in error please reply to the sender at
> Structured Communications Ltd and then delete the e-mail immediately.
> Any views or opinions presented are solely those of the author, and may
> not necessarily represent those of Structured Communications Ltd.
> Structured Communications Ltd is registered in England and Wales,
> registered no 07667451, and its registered office is 22 London Road,
> Horsham, West Sussex RH12 1AY. Registered VAT number GB116507336.
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From aclark at structuredcommunications.co.uk  Sat Aug 23 11:05:36 2014
From: aclark at structuredcommunications.co.uk (Adam Clark)
Date: Sat, 23 Aug 2014 15:05:36 +0000
Subject: [Spce-user] Billing Profile Web Error
In-Reply-To: <53F87346.8080309@sipwise.com>
References: <E80006BDE297C94AADE7963C138CC416D99EEC7F@SR-AD.structured.local>,
 <53F87346.8080309@sipwise.com>
Message-ID: <E80006BDE297C94AADE7963C138CC416D99F0081@SR-AD.structured.local>

Hi Andreas,

Thanks for the reply.

Yes 2.8

The file was saved as UTF-8. I can send the file once I get to a pc :)

Kind Regards,

Adam Clark
Chief Network Engineer
Structured Communications

Sent via my HTC

----- Reply message -----
From: "Andreas Granig" <agranig at sipwise.com>
To: "spce-user at lists.sipwise.com" <spce-user at lists.sipwise.com>
Subject: [Spce-user] Billing Profile Web Error
Date: Sat, Aug 23, 2014 11:57

Hello,

Which version are you using? 2.8?

The issue is not the size, rather than a character in your file seems to
cause issues with utf-8 handling.

Can you provide the file (also in private, and with zeroed fees)?

Andreas

On 08/22/2014 05:22 PM, Adam Clark wrote:
> Afternoon all,
>
>
>
> We have just uploaded a large 9500 line CSV file with ?purge? ticked.
>
>
>
> The file uploaded, however that profile once selected via the admin
> interface gets the web error ?(en) Please come back later?
>
>
>
> The OSS.log reports:
>
>
>
> Aug 22 16:16:07 sipwise /usr/sbin/apache2: Caught exception in
> admin::Controller::billing->search_fees "Can't escape \x{FEFF}, try
> uri_escape_utf8() instead at
> /usr/share/ngcp-www-admin/lib/admin/Controller/billing.pm line 530"
>
>
>
> We have looked at the table in SQL and it only has 560 odd lines ?
>
>
>
> 1)  Does sipwise not handle a zone file this large?
>
> 2)  Can we delete the profile from SQL or restore a backup without
> destroying anything?
>
>
>
> Any help would be grateful.
>
>
>
>
>
> Kind regards,
>
>
>
> sig1
>
>
>
> This e-mail and any attachments transmitted with it, including replies
> and forwarded copies subsequently transmitted, contains information
> which may be confidential and which may also be legally privileged. The
> content of this e-mail is for the exclusive use of the individual(s) or
> entity named above, if you are not the intended recipient, please note
> that any form of distribution, copying or use of this e-mail or the
> information in it is strictly prohibited and may be unlawful. If you
> have received this e-mail in error please reply to the sender at
> Structured Communications Ltd and then delete the e-mail immediately.
> Any views or opinions presented are solely those of the author, and may
> not necessarily represent those of Structured Communications Ltd.
> Structured Communications Ltd is registered in England and Wales,
> registered no 07667451, and its registered office is 22 London Road,
> Horsham, West Sussex RH12 1AY. Registered VAT number GB116507336.
>
>
>
>
>
>
>
> _______________________________________________
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140823/c71b4041/attachment.html>

From arjan at hakwerk.com  Sun Aug 24 05:05:41 2014
From: arjan at hakwerk.com (Arjan Hakkesteegt)
Date: Sun, 24 Aug 2014 11:05:41 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered" /
 kamailio-lb contact (un)masking
Message-ID: <53F9AAE5.2090904@hakwerk.com>

Hi all,

I have a fresh install of mr3.4.1 (actually I messed up upgrading from 
3.3.1 on a mysql error and didn't have a proper backup; my bad. 
Completey wiped the VM and started from scratch).
SEMS is successfully registering with my SIP trunk provider, I can call 
to and be called from the PSTN.
However, looking at the sems logs ("debug: 'yes'" in config.yml, 
attached), it is re-registering every 10 seconds because of a "no 
matching Contact - deregistered" error.

Below is the output of ngrep-sip for one attempt. I'm no expert but it 
looks like the unmasking of the contact fails in kamailio-lb.
178.X.Y.Z = public IP address
12345 = didlogic user id

I'd appreciate any help.

Thanks,
Arjan



U 2014/08/24 09:39:43.210372 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: <sip:12345 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.X.Y.Z:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 09:39:43.211469 178.X.Y.Z:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 
178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: <sip:12345 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
Max-Forwards: 69'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.X.Y.Z:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 09:39:43.258182 72.251.241.166:5060 -> 178.X.Y.Z:5060
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 
178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: 
<sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6'
CSeq: 50 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", 
nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
Content-Length: 0'
'


U 2014/08/24 09:39:43.258552 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: 
<sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6'
CSeq: 50 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", 
nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 09:39:43.260249 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: <sip:12345 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
Authorization: Digest username="12345", realm="sip.nl.didlogic.net", 
nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", 
uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7", nc=00000001, 
response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
Contact: <sip:127.0.0.1:5080;transport=udp>'
Contact: <sip:178.X.Y.Z:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 09:39:43.260751 178.X.Y.Z:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 
178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: <sip:12345 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
Max-Forwards: 69'
Expires: 3600'
Authorization: Digest username="12345", realm="sip.nl.didlogic.net", 
nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", 
uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7", nc=00000001, 
response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
Content-Length: 0'
Contact: 
<sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
'


U 2014/08/24 09:39:43.288129 72.251.241.166:5060 -> 178.X.Y.Z:5060
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 
178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: 
<sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd'
CSeq: 51 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
Contact: 
<sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
'


U 2014/08/24 09:39:43.288567 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: 
<sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd'
CSeq: 51 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
Contact: 
<sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sems.log
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140824/3e498aed/attachment.log>

From dgrotti at sipwise.com  Sun Aug 24 08:26:12 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Sun, 24 Aug 2014 14:26:12 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53F9AAE5.2090904@hakwerk.com>
References: <53F9AAE5.2090904@hakwerk.com>
Message-ID: <53F9D9E4.40601@sipwise.com>

Hi,
sorry in the trace below I just see the registration process at 09:39:43.
Where do you see the second REGISTER after 10sec ? It should Re-REGISTER
again after 3600 sec.

Also I don't see the unREGISTER message (with Expires: 0).
Can you provide such messages ?

Daniel







On 08/24/2014 11:05 AM, Arjan Hakkesteegt wrote:
> Hi all,
>
> I have a fresh install of mr3.4.1 (actually I messed up upgrading from
> 3.3.1 on a mysql error and didn't have a proper backup; my bad.
> Completey wiped the VM and started from scratch).
> SEMS is successfully registering with my SIP trunk provider, I can
> call to and be called from the PSTN.
> However, looking at the sems logs ("debug: 'yes'" in config.yml,
> attached), it is re-registering every 10 seconds because of a "no
> matching Contact - deregistered" error.
>
> Below is the output of ngrep-sip for one attempt. I'm no expert but it
> looks like the unmasking of the contact fails in kamailio-lb.
> 178.X.Y.Z = public IP address
> 12345 = didlogic user id
>
> I'd appreciate any help.
>
> Thanks,
> Arjan
>
>
>
> U 2014/08/24 09:39:43.210372 127.0.0.1:5080 -> 127.0.0.1:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Route: <sip:127.0.0.1:5060;lr>'
> Max-Forwards: 70'
> Expires: 3600'
> User-Agent: Sipwise NGCP Application Server 3.X'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.211469 178.X.Y.Z:5060 -> 72.251.241.166:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP
> 178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Max-Forwards: 69'
> Expires: 3600'
> User-Agent: Sipwise NGCP Application Server 3.X'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.258182 72.251.241.166:5060 -> 178.X.Y.Z:5060
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP
> 178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0;rport=5060'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To:
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> WWW-Authenticate: Digest realm="sip.nl.didlogic.net",
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.258552 127.0.0.1:5060 -> 127.0.0.1:5080
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To:
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> WWW-Authenticate: Digest realm="sip.nl.didlogic.net",
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
> Content-Length: 0'
> P-NGCP-Src-Ip: 72.251.241.166'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> '
>
>
> U 2014/08/24 09:39:43.260249 127.0.0.1:5080 -> 127.0.0.1:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Route: <sip:127.0.0.1:5060;lr>'
> Max-Forwards: 70'
> Expires: 3600'
> Authorization: Digest username="12345", realm="sip.nl.didlogic.net",
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=",
> uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7",
> nc=00000001, response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
> Contact: <sip:127.0.0.1:5080;transport=udp>'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.260751 178.X.Y.Z:5060 -> 72.251.241.166:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP
> 178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Max-Forwards: 69'
> Expires: 3600'
> Authorization: Digest username="12345", realm="sip.nl.didlogic.net",
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=",
> uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7",
> nc=00000001, response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
> Content-Length: 0'
> Contact:
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
> '
>
>
> U 2014/08/24 09:39:43.288129 72.251.241.166:5060 -> 178.X.Y.Z:5060
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP
> 178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0;rport=5060'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To:
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Contact:
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.288567 127.0.0.1:5060 -> 127.0.0.1:5080
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To:
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Contact:
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
> Content-Length: 0'
> P-NGCP-Src-Ip: 72.251.241.166'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> '
>
>
>
> _______________________________________________
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140824/5185dede/attachment.html>

From arjan at hakwerk.com  Sun Aug 24 09:44:11 2014
From: arjan at hakwerk.com (Arjan Hakkesteegt)
Date: Sun, 24 Aug 2014 15:44:11 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53F9D9E4.40601@sipwise.com>
References: <53F9AAE5.2090904@hakwerk.com> <53F9D9E4.40601@sipwise.com>
Message-ID: <53F9EC2B.2090406@hakwerk.com>

I attached the output from "ngrep-sip didlogic" for a minute or so, 
showing the 10 sec interval. I also included the sems.log for that same 
period.

I did a grep on expire in all logfiles in /var/log/ngcp/ but there never 
is an expires: 0 in the logs, only 3600. Any other idea how to find such 
an unREGISTER?

Arjan
> Daniel Grotti <mailto:dgrotti at sipwise.com>
> Sunday, August 24, 2014 14:26
> Hi,
> sorry in the trace below I just see the registration process at 09:39:43.
> Where do you see the second REGISTER after 10sec ? It should 
> Re-REGISTER again after 3600 sec.
>
> Also I don't see the unREGISTER message (with Expires: 0).
> Can you provide such messages ?
>
> Daniel
>
>
>
>
>
>
>
> On 08/24/2014 11:05 AM, Arjan Hakkesteegt wrote:
>
> Arjan Hakkesteegt <mailto:arjan at hakwerk.com>
> Sunday, August 24, 2014 11:05
> Hi all,
>
> I have a fresh install of mr3.4.1 (actually I messed up upgrading from 
> 3.3.1 on a mysql error and didn't have a proper backup; my bad. 
> Completey wiped the VM and started from scratch).
> SEMS is successfully registering with my SIP trunk provider, I can 
> call to and be called from the PSTN.
> However, looking at the sems logs ("debug: 'yes'" in config.yml, 
> attached), it is re-registering every 10 seconds because of a "no 
> matching Contact - deregistered" error.
>
> Below is the output of ngrep-sip for one attempt. I'm no expert but it 
> looks like the unmasking of the contact fails in kamailio-lb.
> 178.X.Y.Z = public IP address
> 12345 = didlogic user id
>
> I'd appreciate any help.
>
> Thanks,
> Arjan
>
>
>
> U 2014/08/24 09:39:43.210372 127.0.0.1:5080 -> 127.0.0.1:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Route: <sip:127.0.0.1:5060;lr>'
> Max-Forwards: 70'
> Expires: 3600'
> User-Agent: Sipwise NGCP Application Server 3.X'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.211469 178.X.Y.Z:5060 -> 72.251.241.166:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Max-Forwards: 69'
> Expires: 3600'
> User-Agent: Sipwise NGCP Application Server 3.X'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.258182 72.251.241.166:5060 -> 178.X.Y.Z:5060
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0;rport=5060' 
>
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6' 
>
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> WWW-Authenticate: Digest realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.258552 127.0.0.1:5060 -> 127.0.0.1:5080
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6' 
>
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> WWW-Authenticate: Digest realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
> Content-Length: 0'
> P-NGCP-Src-Ip: 72.251.241.166'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> '
>
>
> U 2014/08/24 09:39:43.260249 127.0.0.1:5080 -> 127.0.0.1:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Route: <sip:127.0.0.1:5060;lr>'
> Max-Forwards: 70'
> Expires: 3600'
> Authorization: Digest username="12345", realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", 
> uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7", 
> nc=00000001, response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
> Contact: <sip:127.0.0.1:5080;transport=udp>'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.260751 178.X.Y.Z:5060 -> 72.251.241.166:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Max-Forwards: 69'
> Expires: 3600'
> Authorization: Digest username="12345", realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", 
> uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7", 
> nc=00000001, response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
> Content-Length: 0'
> Contact: 
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
> '
>
>
> U 2014/08/24 09:39:43.288129 72.251.241.166:5060 -> 178.X.Y.Z:5060
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0;rport=5060' 
>
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd' 
>
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Contact: 
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600' 
>
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.288567 127.0.0.1:5060 -> 127.0.0.1:5080
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd' 
>
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Contact: 
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600' 
>
> Content-Length: 0'
> P-NGCP-Src-Ip: 72.251.241.166'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> '
>
> _______________________________________________
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140824/976c583c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1214 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140824/976c583c/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1321 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140824/976c583c/attachment-0001.jpg>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ngrep-sip.txt
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140824/976c583c/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sems.log
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140824/976c583c/attachment.log>

From jbonilla at sipwise.com  Sun Aug 24 13:17:36 2014
From: jbonilla at sipwise.com (Jon Bonilla (Manwe))
Date: Sun, 24 Aug 2014 19:17:36 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53F9EC2B.2090406@hakwerk.com>
References: <53F9AAE5.2090904@hakwerk.com> <53F9D9E4.40601@sipwise.com>
 <53F9EC2B.2090406@hakwerk.com>
Message-ID: <20140824191736.08d81fc1@quenya>

El Sun, 24 Aug 2014 15:44:11 +0200
Arjan Hakkesteegt <arjan at hakwerk.com> escribi?:

> I attached the output from "ngrep-sip didlogic" for a minute or so, 
> showing the 10 sec interval. I also included the sems.log for that same 
> period.
> 
> I did a grep on expire in all logfiles in /var/log/ngcp/ but there never 
> is an expires: 0 in the logs, only 3600. Any other idea how to find such 
> an unREGISTER?
> 
> 

There was a bug regarding sems not matching contact last week. It was already
fixed in master but maybe it hasn't been released yet.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140824/a421011f/attachment.asc>

From arjan at hakwerk.com  Sun Aug 24 13:27:59 2014
From: arjan at hakwerk.com (Arjan Hakkesteegt)
Date: Sun, 24 Aug 2014 19:27:59 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53F9EC2B.2090406@hakwerk.com>
References: <53F9AAE5.2090904@hakwerk.com> <53F9D9E4.40601@sipwise.com>
 <53F9EC2B.2090406@hakwerk.com>
Message-ID: <53FA209F.4060908@hakwerk.com>

I have been playing around some more, and if I force the Contact header 
of the peer reply in my kamailio.cfg.customtt.tt2 (near the end in 
onreply_route():
     remove_hf("Contact");
     append_hf("Contact: <sip:127.0.0.1:5080>;expires=200\r\n");
), then it works (at least for this particular scenario, and it is 
ignored when handling the 401 unauthorized):

U 2014/08/24 16:21:10.488831 72.251.241.166:5060 -> 178.X.Y.Z:5060
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 
178.X.Y.Z;branch=z9hG4bK09ac.08655b889dff04f59a713f0f644d643d.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK2jcbeaSi;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=478F2D6E-53F9F40C000A5CB8-335A3700'
To: 
<sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.434f'
CSeq: 55 REGISTER'
Call-ID: 32D4C33B-53F9F40C000A5D59-336A4700'
Contact: 
<sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
'


U 2014/08/24 16:21:10.489967 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK2jcbeaSi;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=478F2D6E-53F9F40C000A5CB8-335A3700'
To: 
<sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.434f'
CSeq: 55 REGISTER'
Call-ID: 32D4C33B-53F9F40C000A5D59-336A4700'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
Contact: <sip:127.0.0.1:5080>;expires=200'
'

That is, then I see the SEMS registering the reply and counting down 
from 200sec (see attached SEMS log).
At 50% of the expires value it will reregister, as per the following 
method I guess:

bool AmSIPRegistration::timeToReregister(time_t now_sec) {
     return (((unsigned long)reg_begin+ reg_expires/2) < (unsigned 
long)now_sec);
}


I'm still trying to get the hang of all the logic in the kamailio.cfg 
routing and I have no idea of all the SIP scenarios involved, but in 
general I would expect that for incoming messages to the loadbalancer 
that have ngcpct set, kamailio should unmask the contact. Or is that too 
simplistic?


Regards,
Arjan


> Arjan Hakkesteegt <mailto:arjan at hakwerk.com>
> Sunday, August 24, 2014 15:44
> I attached the output from "ngrep-sip didlogic" for a minute or so, 
> showing the 10 sec interval. I also included the sems.log for that 
> same period.
>
> I did a grep on expire in all logfiles in /var/log/ngcp/ but there 
> never is an expires: 0 in the logs, only 3600. Any other idea how to 
> find such an unREGISTER?
>
> Arjan
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> Daniel Grotti <mailto:dgrotti at sipwise.com>
> Sunday, August 24, 2014 14:26
> Hi,
> sorry in the trace below I just see the registration process at 09:39:43.
> Where do you see the second REGISTER after 10sec ? It should 
> Re-REGISTER again after 3600 sec.
>
> Also I don't see the unREGISTER message (with Expires: 0).
> Can you provide such messages ?
>
> Daniel
>
>
>
>
>
>
>
> On 08/24/2014 11:05 AM, Arjan Hakkesteegt wrote:
>
> Arjan Hakkesteegt <mailto:arjan at hakwerk.com>
> Sunday, August 24, 2014 11:05
> Hi all,
>
> I have a fresh install of mr3.4.1 (actually I messed up upgrading from 
> 3.3.1 on a mysql error and didn't have a proper backup; my bad. 
> Completey wiped the VM and started from scratch).
> SEMS is successfully registering with my SIP trunk provider, I can 
> call to and be called from the PSTN.
> However, looking at the sems logs ("debug: 'yes'" in config.yml, 
> attached), it is re-registering every 10 seconds because of a "no 
> matching Contact - deregistered" error.
>
> Below is the output of ngrep-sip for one attempt. I'm no expert but it 
> looks like the unmasking of the contact fails in kamailio-lb.
> 178.X.Y.Z = public IP address
> 12345 = didlogic user id
>
> I'd appreciate any help.
>
> Thanks,
> Arjan
>
>
>
> U 2014/08/24 09:39:43.210372 127.0.0.1:5080 -> 127.0.0.1:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Route: <sip:127.0.0.1:5060;lr>'
> Max-Forwards: 70'
> Expires: 3600'
> User-Agent: Sipwise NGCP Application Server 3.X'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.211469 178.X.Y.Z:5060 -> 72.251.241.166:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Max-Forwards: 69'
> Expires: 3600'
> User-Agent: Sipwise NGCP Application Server 3.X'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.258182 72.251.241.166:5060 -> 178.X.Y.Z:5060
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0;rport=5060' 
>
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6' 
>
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> WWW-Authenticate: Digest realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.258552 127.0.0.1:5060 -> 127.0.0.1:5080
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6' 
>
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> WWW-Authenticate: Digest realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
> Content-Length: 0'
> P-NGCP-Src-Ip: 72.251.241.166'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> '
>
>
> U 2014/08/24 09:39:43.260249 127.0.0.1:5080 -> 127.0.0.1:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Route: <sip:127.0.0.1:5060;lr>'
> Max-Forwards: 70'
> Expires: 3600'
> Authorization: Digest username="12345", realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", 
> uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7", 
> nc=00000001, response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
> Contact: <sip:127.0.0.1:5080;transport=udp>'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.260751 178.X.Y.Z:5060 -> 72.251.241.166:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Max-Forwards: 69'
> Expires: 3600'
> Authorization: Digest username="12345", realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", 
> uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7", 
> nc=00000001, response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
> Content-Length: 0'
> Contact: 
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
> '
>
>
> U 2014/08/24 09:39:43.288129 72.251.241.166:5060 -> 178.X.Y.Z:5060
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0;rport=5060' 
>
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd' 
>
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Contact: 
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600' 
>
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.288567 127.0.0.1:5060 -> 127.0.0.1:5080
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd' 
>
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Contact: 
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600' 
>
> Content-Length: 0'
> P-NGCP-Src-Ip: 72.251.241.166'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> '
>
> _______________________________________________
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140824/6b96274b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1321 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140824/6b96274b/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1214 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140824/6b96274b/attachment-0001.jpg>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sems_ok.log
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140824/6b96274b/attachment.log>

From apogrebennyk at sipwise.com  Mon Aug 25 04:54:42 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Mon, 25 Aug 2014 10:54:42 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53FA209F.4060908@hakwerk.com>
References: <53F9AAE5.2090904@hakwerk.com> <53F9D9E4.40601@sipwise.com>
 <53F9EC2B.2090406@hakwerk.com> <53FA209F.4060908@hakwerk.com>
Message-ID: <53FAF9D2.3070702@sipwise.com>

Hi,

On 08/24/2014 07:27 PM, Arjan Hakkesteegt wrote:
> 
> I'm still trying to get the hang of all the logic in the kamailio.cfg
> routing and I have no idea of all the SIP scenarios involved, but in
> general I would expect that for incoming messages to the loadbalancer
> that have ngcpct set, kamailio should unmask the contact. Or is that too
> simplistic?

That's right, for incoming _requests_ with RURI: ngcpct@ kamailio should
unmask the contact URI from RURI. There is no such manipulation required
for the 200 OK response from the UA however.

The problem you are having really looks like the sems bug that Jon is
talking about. The fix however is only in our development trunk and not
in the mr3.4.1 release. I am going to backport it right now and will
reply again when we are good to test.

Andrew


From alutay at sipwise.com  Mon Aug 25 06:04:51 2014
From: alutay at sipwise.com (Alex Lutay)
Date: Mon, 25 Aug 2014 12:04:51 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53F9AAE5.2090904@hakwerk.com>
References: <53F9AAE5.2090904@hakwerk.com>
Message-ID: <53FB0A43.9080209@sipwise.com>

Dear Arjan!

I would like to inform you that ngcp-upgrade automatically
performs backup of all configs and DB snapshot to:
 > /var/backup/ngcp-${UPGRADE_VERSION}/
where UPGRADE_VERSION=mr3.4.1 in your case.

So, next time you can restore your data in case if something went wrong.

On 24/08/14 11:05, Arjan Hakkesteegt wrote:
> ... actually I messed up upgrading from 3.3.1 on a mysql error and didn't have a proper backup; my bad.  ...

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From apogrebennyk at sipwise.com  Mon Aug 25 07:40:19 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Mon, 25 Aug 2014 13:40:19 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53FAF9D2.3070702@sipwise.com>
References: <53F9AAE5.2090904@hakwerk.com> <53F9D9E4.40601@sipwise.com>
 <53F9EC2B.2090406@hakwerk.com> <53FA209F.4060908@hakwerk.com>
 <53FAF9D2.3070702@sipwise.com>
Message-ID: <53FB20A3.2000508@sipwise.com>

Arjan, we are going to create the new release mr3.4.2 with that fix.
While it may take a day or two to do so, please try this package:
https://www.dropbox.com/s/foou1ujlnofvb53/ngcp-sems_1.6.0~20140819~0b6d12-1%2B0~mr3.4.2.0%2B0~20140825092947.264%2Bwheezy~1.gbp4477f1_amd64.deb?dl=0
Install with dpkg -i and it should resolve your problem with upstream
registration.

On 08/25/2014 10:54 AM, Andrew Pogrebennyk wrote:
> On 08/24/2014 07:27 PM, Arjan Hakkesteegt wrote:
>> > 
>> > I'm still trying to get the hang of all the logic in the kamailio.cfg
>> > routing and I have no idea of all the SIP scenarios involved, but in
>> > general I would expect that for incoming messages to the loadbalancer
>> > that have ngcpct set, kamailio should unmask the contact. Or is that too
>> > simplistic?
> That's right, for incoming _requests_ with RURI: ngcpct@ kamailio should
> unmask the contact URI from RURI. There is no such manipulation required
> for the 200 OK response from the UA however.
> 
> The problem you are having really looks like the sems bug that Jon is
> talking about. The fix however is only in our development trunk and not
> in the mr3.4.1 release. I am going to backport it right now and will
> reply again when we are good to test.
> 
> Andrew



From arjan at hakwerk.com  Mon Aug 25 15:45:00 2014
From: arjan at hakwerk.com (Arjan Hakkesteegt)
Date: Mon, 25 Aug 2014 21:45:00 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53FB20A3.2000508@sipwise.com>
References: <53F9AAE5.2090904@hakwerk.com> <53F9D9E4.40601@sipwise.com>
 <53F9EC2B.2090406@hakwerk.com> <53FA209F.4060908@hakwerk.com>
 <53FAF9D2.3070702@sipwise.com> <53FB20A3.2000508@sipwise.com>
Message-ID: <53FB923C.7020701@hakwerk.com>

I can confirm that this new package solved the problem for me. Thanks 
for the excellent support!!
Also thank you Alex for the tip on the location of the backup for 
ngcp-upgrade :)

Regards,
Arjan


Andrew Pogrebennyk wrote:
> While it may take a day or two to do so, please try this package:
> https://www.dropbox.com/s/foou1ujlnofvb53/ngcp-sems_1.6.0~20140819~0b6d12-1%2B0~mr3.4.2.0%2B0~20140825092947.264%2Bwheezy~1.gbp4477f1_amd64.deb?dl=0
> Install with dpkg -i and it should resolve your problem with upstream
> registration.


From matthew at tenacit.net  Wed Aug 27 10:43:40 2014
From: matthew at tenacit.net (Matthew Ogden)
Date: Wed, 27 Aug 2014 16:43:40 +0200
Subject: [Spce-user] voip loopback test
Message-ID: <12f5e97bc390af65cbe042959eceacf0@mail.gmail.com>

Hi



Does spce have a number I can dial built-in that is a loopback test?



Regards





*Matthew Ogden*

Management

TenacIT







*Strategic IT Consulting *?* Advanced Networking *? *Virtualisation*

*Custom Development *? *Hosting *? *Syspro Support  *? *MS Licensing*

National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
matthew at tenacit.net

CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
http://www.tenacit.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4809 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 1031 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 1424 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 1287 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 3930 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 4536 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment-0001.png>

From tabi.tabe at gmail.com  Wed Aug 27 10:58:20 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Wed, 27 Aug 2014 16:58:20 +0200
Subject: [Spce-user] SPCE 3.2.1
Message-ID: <CAOibrm5-Z_bVq+=PeNkZGaY1bS_QsDDiKuNYhoSErnarBpQ-NA@mail.gmail.com>

Hi,

We have a strange issue with SPCE 3.2.1. It has stopped responding to SIP
request from other peers and from endpoints. Any ideas what could be wrong
and how to resolve it?

Much appreciated.


-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/e709f0bd/attachment.html>

From dgrotti at sipwise.com  Wed Aug 27 11:33:00 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Wed, 27 Aug 2014 17:33:00 +0200
Subject: [Spce-user] SPCE 3.2.1
Message-ID: <20140827153329.B99A9150209F@zimbra.sipwise.com>

Hi,
Did you check if those IP have been banned?
Is lb still listening on the shared IP?

Is the platform not responding at all or just to some ips?

Daniel

On 27 Aug 2014 16:58, Tabi Tabe Tabi <tabi.tabe at gmail.com> wrote:
>
> Hi,
>
> We have a strange issue with SPCE 3.2.1. It has stopped responding to SIP request from other peers and from endpoints. Any ideas what could be wrong and how to resolve it?
>
> Much appreciated.
>
>
> -- 
> ...Tabi
>

From tabi.tabe at gmail.com  Wed Aug 27 11:43:02 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Wed, 27 Aug 2014 17:43:02 +0200
Subject: [Spce-user] SPCE 3.2.1
In-Reply-To: <20140827153329.B99A9150209F@zimbra.sipwise.com>
References: <20140827153329.B99A9150209F@zimbra.sipwise.com>
Message-ID: <CAOibrm40hDOUYnRmcrBveb6FUaDEvfjHjGJt8xG0tsPs5Xk3yA@mail.gmail.com>

Hi Daniel,

Checked. No IP address is banned.

How do I check ls lb is it is listening on share IP?

It is not responding to all IP addresses. However I can access the web
portal


Regards,

Tabi


On Wed, Aug 27, 2014 at 5:33 PM, Daniel Grotti <dgrotti at sipwise.com> wrote:

> Hi,
> Did you check if those IP have been banned?
> Is lb still listening on the shared IP?
>
> Is the platform not responding at all or just to some ips?
>
> Daniel
>
> On 27 Aug 2014 16:58, Tabi Tabe Tabi <tabi.tabe at gmail.com> wrote:
> >
> > Hi,
> >
> > We have a strange issue with SPCE 3.2.1. It has stopped responding to
> SIP request from other peers and from endpoints. Any ideas what could be
> wrong and how to resolve it?
> >
> > Much appreciated.
> >
> >
> > --
> > ...Tabi
> >
>



-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/e660cd26/attachment.html>

From tabi.tabe at gmail.com  Wed Aug 27 11:53:18 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Wed, 27 Aug 2014 17:53:18 +0200
Subject: [Spce-user] SPCE 3.2.1
In-Reply-To: <CAOibrm40hDOUYnRmcrBveb6FUaDEvfjHjGJt8xG0tsPs5Xk3yA@mail.gmail.com>
References: <20140827153329.B99A9150209F@zimbra.sipwise.com>
 <CAOibrm40hDOUYnRmcrBveb6FUaDEvfjHjGJt8xG0tsPs5Xk3yA@mail.gmail.com>
Message-ID: <CAOibrm4Gu837p+u=qbgFsODtBmdbAhx-O68qZAcLR4Gn1BJ+7w@mail.gmail.com>

Hi Daniel,

I can see see traffic in kamailio-lb.log

Should I share that log with you?

Regards,

Tabi


On Wed, Aug 27, 2014 at 5:43 PM, Tabi Tabe Tabi <tabi.tabe at gmail.com> wrote:

> Hi Daniel,
>
> Checked. No IP address is banned.
>
> How do I check ls lb is it is listening on share IP?
>
> It is not responding to all IP addresses. However I can access the web
> portal
>
>
> Regards,
>
> Tabi
>
>
> On Wed, Aug 27, 2014 at 5:33 PM, Daniel Grotti <dgrotti at sipwise.com>
> wrote:
>
>> Hi,
>> Did you check if those IP have been banned?
>> Is lb still listening on the shared IP?
>>
>> Is the platform not responding at all or just to some ips?
>>
>> Daniel
>>
>> On 27 Aug 2014 16:58, Tabi Tabe Tabi <tabi.tabe at gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > We have a strange issue with SPCE 3.2.1. It has stopped responding to
>> SIP request from other peers and from endpoints. Any ideas what could be
>> wrong and how to resolve it?
>> >
>> > Much appreciated.
>> >
>> >
>> > --
>> > ...Tabi
>> >
>>
>
>
>
> --
> ...Tabi
>
>


-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/a14c494f/attachment.html>

From vseva at sipwise.com  Wed Aug 27 12:44:51 2014
From: vseva at sipwise.com (Victor Seva)
Date: Wed, 27 Aug 2014 18:44:51 +0200
Subject: [Spce-user] SPCE 3.2.1
Message-ID: <20140827164455.3E5C3150209F@zimbra.sipwise.com>

An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/d1adb9ef/attachment.html>

From dgrotti at sipwise.com  Wed Aug 27 12:59:49 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Wed, 27 Aug 2014 18:59:49 +0200
Subject: [Spce-user] voip loopback test
Message-ID: <20140827170018.42CEE150209E@zimbra.sipwise.com>

Hi,
We don't have a specific number.
It depends what you want to achieve, you can call the voicebox number for example or you can call another subscriber with a CF set to a mobile phone.
Again it depends what you mean with loopback test.

Daniel

On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
>
> Hi
>
> ?
>
> Does spce have a number I can dial built-in that is a loopback test?
>
> ?
>
> Regards
>
> ?
>
> ?
>
> Matthew Ogden
>
> Management
>
> TenacIT
>
> ?
>
> ?
>
> ?
>
> Strategic IT Consulting ? Advanced Networking ? Virtualisation
>
> Custom Development ? Hosting ? Syspro Support? ? MS Licensing
>
> National Tel: 041 10 10?100 | Cell: 084 205 4445 | Email: matthew at tenacit.net?
>
> CT Tel: 021?201 0333 | Skype Name: matthew.ogden | Web: http://www.tenacit.net
>
> ?
>
> ?????????
>
> ?

From jward01 at gmail.com  Wed Aug 27 15:20:03 2014
From: jward01 at gmail.com (Jeremy Ward)
Date: Wed, 27 Aug 2014 15:20:03 -0400
Subject: [Spce-user] voip loopback test
In-Reply-To: <20140827170018.42CEE150209E@zimbra.sipwise.com>
References: <20140827170018.42CEE150209E@zimbra.sipwise.com>
Message-ID: <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>

Not to stick my nose in something that it doesn't belong, but I think he is
referring to what asterisk calls an "echo test".

Its usually accessed via a star code (*31, if my memory serves me
correctly).

Hope this helps.

Jeremy D. Ward, CWNE
(954) 661-4965
On Aug 27, 2014 1:01 PM, "Daniel Grotti" <dgrotti at sipwise.com> wrote:

> Hi,
> We don't have a specific number.
> It depends what you want to achieve, you can call the voicebox number for
> example or you can call another subscriber with a CF set to a mobile phone.
> Again it depends what you mean with loopback test.
>
> Daniel
>
> On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
> >
> > Hi
> >
> >
> >
> > Does spce have a number I can dial built-in that is a loopback test?
> >
> >
> >
> > Regards
> >
> >
> >
> >
> >
> > Matthew Ogden
> >
> > Management
> >
> > TenacIT
> >
> >
> >
> >
> >
> >
> >
> > Strategic IT Consulting ? Advanced Networking ? Virtualisation
> >
> > Custom Development ? Hosting ? Syspro Support  ? MS Licensing
> >
> > National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
> matthew at tenacit.net
> >
> > CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
> http://www.tenacit.net
> >
> >
> >
> >
> >
> >
> _______________________________________________
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/a32c5662/attachment.html>

From matthew at tenacit.net  Wed Aug 27 17:24:12 2014
From: matthew at tenacit.net (Matthew Ogden)
Date: Wed, 27 Aug 2014 23:24:12 +0200
Subject: [Spce-user] voip loopback test
In-Reply-To: <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>
References: <20140827170018.42CEE150209E@zimbra.sipwise.com>
 <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>
Message-ID: <8fe5440a16db354e530e18b3f58879e1@mail.gmail.com>

Thanks Jeremy, that?s exactly what I mean!



Echo test.



*From:* Jeremy Ward [mailto:jward01 at gmail.com]
*Sent:* 27 August 2014 09:20 PM
*To:* Daniel Grotti
*Cc:* spce-user at lists.sipwise.com; Matthew Ogden
*Subject:* Re: [Spce-user] voip loopback test



Not to stick my nose in something that it doesn't belong, but I think he is
referring to what asterisk calls an "echo test".

Its usually accessed via a star code (*31, if my memory serves me
correctly).

Hope this helps.

Jeremy D. Ward, CWNE
(954) 661-4965

On Aug 27, 2014 1:01 PM, "Daniel Grotti" <dgrotti at sipwise.com> wrote:

Hi,
We don't have a specific number.
It depends what you want to achieve, you can call the voicebox number for
example or you can call another subscriber with a CF set to a mobile phone.
Again it depends what you mean with loopback test.

Daniel

On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
>
> Hi
>
>
>
> Does spce have a number I can dial built-in that is a loopback test?
>
>
>
> Regards
>
>
>
>
>
> Matthew Ogden
>
> Management
>
> TenacIT
>
>
>
>
>
>
>
> Strategic IT Consulting ? Advanced Networking ? Virtualisation
>
> Custom Development ? Hosting ? Syspro Support  ? MS Licensing
>
> National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
matthew at tenacit.net
>
> CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
http://www.tenacit.net
>
>
>
>
>
>
_______________________________________________
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/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/e141453a/attachment.html>

From george.mason at xoomtalk.com  Wed Aug 27 17:26:20 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Wed, 27 Aug 2014 22:26:20 +0100
Subject: [Spce-user] Problems getting calls rated v2.8
Message-ID: <53FE4CFC.5000307@xoomtalk.com>

Hi

Please forgive the question but am learning the ropes on SPCE and
struggling somewhat with billing.

I have created a billing fee which I am attempting to apply to a SIP
peering, such that call costs are included in the CDR table. I have
created a contract which references the fees and applied this to the
peering concerned. However when I place a call for which there should be
a cost, no cost is recorded in the CDR table, and the rated_at field is
NULL. This last detail is different if I use the default fee of zero,
rated_at then includes a date and time, which implies the fault is with
my fee config, but cannot see where.

I have attempted to match destination prefixes in the fees as follows
(presume a call to +441273123456 via peering with IP 2.2.2.2)

^44
^+44
^+44.
^+44.+
^+44.+$
^\+44.+\@.+$

None of these have the desired effect. What am I doing wrong/how can I
troubleshoot this process?

Thanks

George


From george.mason at xoomtalk.com  Wed Aug 27 18:10:27 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Wed, 27 Aug 2014 23:10:27 +0100
Subject: [Spce-user] Problems getting calls rated v2.8
In-Reply-To: <53FE4CFC.5000307@xoomtalk.com>
References: <53FE4CFC.5000307@xoomtalk.com>
Message-ID: <53FE5753.6070803@xoomtalk.com>



On 27/08/14 22:26, George Mason wrote:
> I have attempted to match destination prefixes in the fees as follows
> (presume a call to +441273123456 via peering with IP 2.2.2.2)
>
> ^44
> ^+44
> ^+44.
> ^+44.+
> ^+44.+$
> ^\+44.+\@.+$
>
> None of these have the desired effect. What am I doing wrong/how can I
> troubleshoot this process?

I should add that our carrier in this case requires international
numbers with the + prefix, hence these being in the billing fees. Calls
complete but are not rated.


From george.mason at xoomtalk.com  Wed Aug 27 18:50:03 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Wed, 27 Aug 2014 23:50:03 +0100
Subject: [Spce-user] Problems getting calls rated v2.8
In-Reply-To: <53FE5753.6070803@xoomtalk.com>
References: <53FE4CFC.5000307@xoomtalk.com> <53FE5753.6070803@xoomtalk.com>
Message-ID: <53FE609B.70301@xoomtalk.com>

 On 27/08/14 23:10, George Mason wrote:
> On 27/08/14 22:26, George Mason wrote:
>> > I have attempted to match destination prefixes in the fees as follows
>> > (presume a call to +441273123456 via peering with IP 2.2.2.2)
>> >
>> > ^44
>> > ^+44
>> > ^+44.
>> > ^+44.+
>> > ^+44.+$
>> > ^\+44.+\@.+$
>> >
>> > None of these have the desired effect. What am I doing wrong/how can I
>> > troubleshoot this process?
> I should add that our carrier in this case requires international
> numbers with the + prefix, hence these being in the billing fees. Calls
> complete but are not rated.

Further work on this reveals the following in rate-o-mat.log:

Aug 27 18:45:49 sip1 rate-o-mat[19269]: Error rating CDR batch: No
provider info for provider id 2 found

But cannot seem to find which "provider 2" is and why it has no info!


From barry at flanagan.ie  Thu Aug 28 04:48:28 2014
From: barry at flanagan.ie (Barry Flanagan)
Date: Thu, 28 Aug 2014 09:48:28 +0100
Subject: [Spce-user] voip loopback test
In-Reply-To: <8fe5440a16db354e530e18b3f58879e1@mail.gmail.com>
References: <20140827170018.42CEE150209E@zimbra.sipwise.com>
 <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>
 <8fe5440a16db354e530e18b3f58879e1@mail.gmail.com>
Message-ID: <CALJb548k2yjZOtLO6mXw5TG52woQ3ATgF0-wb63vz3xtPnsD3w@mail.gmail.com>

On 27 August 2014 22:24, Matthew Ogden <matthew at tenacit.net> wrote:

> Thanks Jeremy, that?s exactly what I mean!
>
>
>
> Echo test.
>

You could quite easily do this on the Asterisk server included with spce.
Just make a custom extensions.conf like so:

cd /etc/ngcp-config/templates/etc/asterisk/
cp extentions.conf.tt2 extensions.conf.customtt.tt2

Then edit extensions.conf.customtt.tt2 and add something like the following
at the bottom of the file:

### Echo Test Context ####
[echo-test]
exten => s,1,wait(2)
exten => s,n,Playback(demo-echotest)   ; Let them know what's going on
exten => s,n,Answer()
exten => s,n,Echo()                      ; Do the echo test
exten => s,n,Playback(demo-echodone)   ; Let them know it's over
exten => s,n,Hangup()
### End of Echo Test ###

Then, in the existing [sip-in] context, at the top, put in an extension for
the number you want to use for the echo test. For example, if you wanted to
use 500 as the number someone would dial to do the echo test, then you
would do:

[sip-in] <-- NOTE: this line exists already -  do not put it in, just look
for it in the file!
exten => 500,1,Goto(echo-test,s,1)

You then need to run 'ngcpcfg apply' so that Asterisk picks up the new
config.

Then what you need to do in order to get SPCE to actually send this number
- 500 - to the asterisk voicemail server, is to put a rule into your
subscribers rewrite rule set, under "Inbound Rewrite Rules for Callee":

Match Pattern: ^500$
Replace Pattern: 500 at voicebox.local
Description: Echo Test
Direction: Inbound
Field: Callee

So now, any call from the subscriber to 500 will get re-written to
500 at voicebox.local and sent to the Asterisk server where it should get the
echo test.

Hope this helps.

-Barry Flanagan



>
>
> *From:* Jeremy Ward [mailto:jward01 at gmail.com]
> *Sent:* 27 August 2014 09:20 PM
> *To:* Daniel Grotti
> *Cc:* spce-user at lists.sipwise.com; Matthew Ogden
> *Subject:* Re: [Spce-user] voip loopback test
>
>
>
> Not to stick my nose in something that it doesn't belong, but I think he
> is referring to what asterisk calls an "echo test".
>
> Its usually accessed via a star code (*31, if my memory serves me
> correctly).
>
> Hope this helps.
>
> Jeremy D. Ward, CWNE
> (954) 661-4965
>
> On Aug 27, 2014 1:01 PM, "Daniel Grotti" <dgrotti at sipwise.com> wrote:
>
> Hi,
> We don't have a specific number.
> It depends what you want to achieve, you can call the voicebox number for
> example or you can call another subscriber with a CF set to a mobile phone.
> Again it depends what you mean with loopback test.
>
> Daniel
>
> On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
> >
> > Hi
> >
> >
> >
> > Does spce have a number I can dial built-in that is a loopback test?
> >
> >
> >
> > Regards
> >
> >
> >
> >
> >
> > Matthew Ogden
> >
> > Management
> >
> > TenacIT
> >
> >
> >
> >
> >
> >
> >
> > Strategic IT Consulting ? Advanced Networking ? Virtualisation
> >
> > Custom Development ? Hosting ? Syspro Support  ? MS Licensing
> >
> > National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
> matthew at tenacit.net
> >
> > CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
> http://www.tenacit.net
> >
> >
> >
> >
> >
> >
> _______________________________________________
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140828/6575e9d8/attachment.html>

From matthew at tenacit.net  Thu Aug 28 04:55:55 2014
From: matthew at tenacit.net (Matthew Ogden)
Date: Thu, 28 Aug 2014 10:55:55 +0200
Subject: [Spce-user] voip loopback test
In-Reply-To: <CALJb548k2yjZOtLO6mXw5TG52woQ3ATgF0-wb63vz3xtPnsD3w@mail.gmail.com>
References: <20140827170018.42CEE150209E@zimbra.sipwise.com>
 <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>
 <8fe5440a16db354e530e18b3f58879e1@mail.gmail.com>
 <CALJb548k2yjZOtLO6mXw5TG52woQ3ATgF0-wb63vz3xtPnsD3w@mail.gmail.com>
Message-ID: <bae72fc8a9a5bbc431a5cd64bc5eb5f1@mail.gmail.com>

Neat!



I?ll try this out a bit later



*From:* Barry Flanagan [mailto:barry at flanagan.ie]
*Sent:* 28 August 2014 10:48 AM
*To:* Matthew Ogden
*Cc:* Jeremy Ward; Daniel Grotti; spce-user at lists.sipwise.com
*Subject:* Re: [Spce-user] voip loopback test



On 27 August 2014 22:24, Matthew Ogden <matthew at tenacit.net> wrote:

Thanks Jeremy, that?s exactly what I mean!



Echo test.



You could quite easily do this on the Asterisk server included with spce.
Just make a custom extensions.conf like so:



cd /etc/ngcp-config/templates/etc/asterisk/

cp extentions.conf.tt2 extensions.conf.customtt.tt2



Then edit extensions.conf.customtt.tt2 and add something like the following
at the bottom of the file:



### Echo Test Context ####

[echo-test]

exten => s,1,wait(2)

exten => s,n,Playback(demo-echotest)   ; Let them know what's going on

exten => s,n,Answer()

exten => s,n,Echo()                      ; Do the echo test

exten => s,n,Playback(demo-echodone)   ; Let them know it's over

exten => s,n,Hangup()

### End of Echo Test ###



Then, in the existing [sip-in] context, at the top, put in an extension for
the number you want to use for the echo test. For example, if you wanted to
use 500 as the number someone would dial to do the echo test, then you
would do:



[sip-in] <-- NOTE: this line exists already -  do not put it in, just look
for it in the file!

exten => 500,1,Goto(echo-test,s,1)



You then need to run 'ngcpcfg apply' so that Asterisk picks up the new
config.



Then what you need to do in order to get SPCE to actually send this number
- 500 - to the asterisk voicemail server, is to put a rule into your
subscribers rewrite rule set, under "Inbound Rewrite Rules for Callee":



Match Pattern: ^500$

Replace Pattern: 500 at voicebox.local

Description: Echo Test

Direction: Inbound

Field: Callee



So now, any call from the subscriber to 500 will get re-written to
500 at voicebox.local and sent to the Asterisk server where it should get the
echo test.



Hope this helps.



-Barry Flanagan







*From:* Jeremy Ward [mailto:jward01 at gmail.com]
*Sent:* 27 August 2014 09:20 PM
*To:* Daniel Grotti
*Cc:* spce-user at lists.sipwise.com; Matthew Ogden
*Subject:* Re: [Spce-user] voip loopback test



Not to stick my nose in something that it doesn't belong, but I think he is
referring to what asterisk calls an "echo test".

Its usually accessed via a star code (*31, if my memory serves me
correctly).

Hope this helps.

Jeremy D. Ward, CWNE
(954) 661-4965

On Aug 27, 2014 1:01 PM, "Daniel Grotti" <dgrotti at sipwise.com> wrote:

Hi,
We don't have a specific number.
It depends what you want to achieve, you can call the voicebox number for
example or you can call another subscriber with a CF set to a mobile phone.
Again it depends what you mean with loopback test.

Daniel

On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
>
> Hi
>
>
>
> Does spce have a number I can dial built-in that is a loopback test?
>
>
>
> Regards
>
>
>
>
>
> Matthew Ogden
>
> Management
>
> TenacIT
>
>
>
>
>
>
>
> Strategic IT Consulting ? Advanced Networking ? Virtualisation
>
> Custom Development ? Hosting ? Syspro Support  ? MS Licensing
>
> National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
matthew at tenacit.net
>
> CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
http://www.tenacit.net
>
>
>
>
>
>
_______________________________________________
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/mailman/private/spce-user_lists.sipwise.com/attachments/20140828/605c15a9/attachment.html>

From tabi.tabe at gmail.com  Thu Aug 28 08:11:50 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Thu, 28 Aug 2014 14:11:50 +0200
Subject: [Spce-user] SPCE 3.4.1 not showing call history in Web portal
Message-ID: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>

Hi,

I installed SPCE 3.4.1 and got is working fine. However it does not show
call history under call distribution or subscriber menu. Any idea what
could be the cause?

-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140828/1060baec/attachment.html>

From jward01 at gmail.com  Thu Aug 28 09:36:06 2014
From: jward01 at gmail.com (Jeremy Ward)
Date: Thu, 28 Aug 2014 09:36:06 -0400
Subject: [Spce-user] voip loopback test
In-Reply-To: <CALJb548k2yjZOtLO6mXw5TG52woQ3ATgF0-wb63vz3xtPnsD3w@mail.gmail.com>
References: <20140827170018.42CEE150209E@zimbra.sipwise.com>
 <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>
 <8fe5440a16db354e530e18b3f58879e1@mail.gmail.com>
 <CALJb548k2yjZOtLO6mXw5TG52woQ3ATgF0-wb63vz3xtPnsD3w@mail.gmail.com>
Message-ID: <CAFfjrWqriH0WQNgeoN24696wAQ229xm0Wp4khHtrjteWR9L9fg@mail.gmail.com>

Barry,

Would the same logic then apply to setup an ANAC code?

Some of my carrier clients have voice gateways that terminate to multiple
lines at 66-block like in a multitenant commercial building (MDU).

Many voice techs in the US are used to being able to check the telephone
number assigned to a pair by "ANACing" the line - dialing 2006666666.

This causes the switch to announce the associated telephone number with
that pair of wires.

I realize that the asterisk script would be different, but could it be
accomplished in the same manner? I would imagine asterisk would see the CLI
of the callee as its needed for voicemail access, correct?

Thanks,

Jeremy D. Ward, CWNE
(954) 661-4965
On Aug 28, 2014 4:48 AM, "Barry Flanagan" <barry at flanagan.ie> wrote:

> On 27 August 2014 22:24, Matthew Ogden <matthew at tenacit.net> wrote:
>
>> Thanks Jeremy, that?s exactly what I mean!
>>
>>
>>
>> Echo test.
>>
>
> You could quite easily do this on the Asterisk server included with spce.
> Just make a custom extensions.conf like so:
>
> cd /etc/ngcp-config/templates/etc/asterisk/
> cp extentions.conf.tt2 extensions.conf.customtt.tt2
>
> Then edit extensions.conf.customtt.tt2 and add something like the
> following at the bottom of the file:
>
> ### Echo Test Context ####
> [echo-test]
> exten => s,1,wait(2)
> exten => s,n,Playback(demo-echotest)   ; Let them know what's going on
> exten => s,n,Answer()
> exten => s,n,Echo()                      ; Do the echo test
> exten => s,n,Playback(demo-echodone)   ; Let them know it's over
> exten => s,n,Hangup()
> ### End of Echo Test ###
>
> Then, in the existing [sip-in] context, at the top, put in an extension
> for the number you want to use for the echo test. For example, if you
> wanted to use 500 as the number someone would dial to do the echo test,
> then you would do:
>
> [sip-in] <-- NOTE: this line exists already -  do not put it in, just look
> for it in the file!
> exten => 500,1,Goto(echo-test,s,1)
>
> You then need to run 'ngcpcfg apply' so that Asterisk picks up the new
> config.
>
> Then what you need to do in order to get SPCE to actually send this number
> - 500 - to the asterisk voicemail server, is to put a rule into your
> subscribers rewrite rule set, under "Inbound Rewrite Rules for Callee":
>
> Match Pattern: ^500$
> Replace Pattern: 500 at voicebox.local
> Description: Echo Test
> Direction: Inbound
> Field: Callee
>
> So now, any call from the subscriber to 500 will get re-written to
> 500 at voicebox.local and sent to the Asterisk server where it should get
> the echo test.
>
> Hope this helps.
>
> -Barry Flanagan
>
>
>
>>
>>
>> *From:* Jeremy Ward [mailto:jward01 at gmail.com]
>> *Sent:* 27 August 2014 09:20 PM
>> *To:* Daniel Grotti
>> *Cc:* spce-user at lists.sipwise.com; Matthew Ogden
>> *Subject:* Re: [Spce-user] voip loopback test
>>
>>
>>
>> Not to stick my nose in something that it doesn't belong, but I think he
>> is referring to what asterisk calls an "echo test".
>>
>> Its usually accessed via a star code (*31, if my memory serves me
>> correctly).
>>
>> Hope this helps.
>>
>> Jeremy D. Ward, CWNE
>> (954) 661-4965
>>
>> On Aug 27, 2014 1:01 PM, "Daniel Grotti" <dgrotti at sipwise.com> wrote:
>>
>> Hi,
>> We don't have a specific number.
>> It depends what you want to achieve, you can call the voicebox number for
>> example or you can call another subscriber with a CF set to a mobile phone.
>> Again it depends what you mean with loopback test.
>>
>> Daniel
>>
>> On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
>> >
>> > Hi
>> >
>> >
>> >
>> > Does spce have a number I can dial built-in that is a loopback test?
>> >
>> >
>> >
>> > Regards
>> >
>> >
>> >
>> >
>> >
>> > Matthew Ogden
>> >
>> > Management
>> >
>> > TenacIT
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > Strategic IT Consulting ? Advanced Networking ? Virtualisation
>> >
>> > Custom Development ? Hosting ? Syspro Support  ? MS Licensing
>> >
>> > National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
>> matthew at tenacit.net
>> >
>> > CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
>> http://www.tenacit.net
>> >
>> >
>> >
>> >
>> >
>> >
>> _______________________________________________
>> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140828/1001d20e/attachment.html>

From barry at flanagan.ie  Thu Aug 28 09:44:46 2014
From: barry at flanagan.ie (Barry Flanagan)
Date: Thu, 28 Aug 2014 14:44:46 +0100
Subject: [Spce-user] voip loopback test
In-Reply-To: <CAFfjrWqriH0WQNgeoN24696wAQ229xm0Wp4khHtrjteWR9L9fg@mail.gmail.com>
References: <20140827170018.42CEE150209E@zimbra.sipwise.com>
 <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>
 <8fe5440a16db354e530e18b3f58879e1@mail.gmail.com>
 <CALJb548k2yjZOtLO6mXw5TG52woQ3ATgF0-wb63vz3xtPnsD3w@mail.gmail.com>
 <CAFfjrWqriH0WQNgeoN24696wAQ229xm0Wp4khHtrjteWR9L9fg@mail.gmail.com>
Message-ID: <CALJb549hoBcwF-B1x5WVE9BpVQiePCXPM0DVZpcVS=OOaF8odA@mail.gmail.com>

On 28 August 2014 14:36, Jeremy Ward <jward01 at gmail.com> wrote:

> Barry,
>
> Would the same logic then apply to setup an ANAC code?
>
> Some of my carrier clients have voice gateways that terminate to multiple
> lines at 66-block like in a multitenant commercial building (MDU).
>
> Many voice techs in the US are used to being able to check the telephone
> number assigned to a pair by "ANACing" the line - dialing 2006666666.
>
> This causes the switch to announce the associated telephone number with
> that pair of wires.
>
> I realize that the asterisk script would be different, but could it be
> accomplished in the same manner? I would imagine asterisk would see the CLI
> of the callee as its needed for voicemail access, correct?
>
>
Yes, it should work the same for that. Same technique, just write an
Asterisk dialplan to speak back the numbers from the CALLERID(number).

If you were building lots of Asterisk applications I would suggest running
them on a separate * box than your voicemail but for just echo test and
ANAC I wouldn't worry too much.

Regards,

-Barry



> Thanks,
>
> Jeremy D. Ward, CWNE
> (954) 661-4965
> On Aug 28, 2014 4:48 AM, "Barry Flanagan" <barry at flanagan.ie> wrote:
>
>> On 27 August 2014 22:24, Matthew Ogden <matthew at tenacit.net> wrote:
>>
>>> Thanks Jeremy, that?s exactly what I mean!
>>>
>>>
>>>
>>> Echo test.
>>>
>>
>> You could quite easily do this on the Asterisk server included with spce.
>> Just make a custom extensions.conf like so:
>>
>> cd /etc/ngcp-config/templates/etc/asterisk/
>> cp extentions.conf.tt2 extensions.conf.customtt.tt2
>>
>> Then edit extensions.conf.customtt.tt2 and add something like the
>> following at the bottom of the file:
>>
>> ### Echo Test Context ####
>> [echo-test]
>> exten => s,1,wait(2)
>> exten => s,n,Playback(demo-echotest)   ; Let them know what's going on
>> exten => s,n,Answer()
>> exten => s,n,Echo()                      ; Do the echo test
>> exten => s,n,Playback(demo-echodone)   ; Let them know it's over
>> exten => s,n,Hangup()
>> ### End of Echo Test ###
>>
>> Then, in the existing [sip-in] context, at the top, put in an extension
>> for the number you want to use for the echo test. For example, if you
>> wanted to use 500 as the number someone would dial to do the echo test,
>> then you would do:
>>
>> [sip-in] <-- NOTE: this line exists already -  do not put it in, just
>> look for it in the file!
>> exten => 500,1,Goto(echo-test,s,1)
>>
>> You then need to run 'ngcpcfg apply' so that Asterisk picks up the new
>> config.
>>
>> Then what you need to do in order to get SPCE to actually send this
>> number - 500 - to the asterisk voicemail server, is to put a rule into your
>> subscribers rewrite rule set, under "Inbound Rewrite Rules for Callee":
>>
>> Match Pattern: ^500$
>> Replace Pattern: 500 at voicebox.local
>> Description: Echo Test
>> Direction: Inbound
>> Field: Callee
>>
>> So now, any call from the subscriber to 500 will get re-written to
>> 500 at voicebox.local and sent to the Asterisk server where it should get
>> the echo test.
>>
>> Hope this helps.
>>
>> -Barry Flanagan
>>
>>
>>
>>>
>>>
>>> *From:* Jeremy Ward [mailto:jward01 at gmail.com]
>>> *Sent:* 27 August 2014 09:20 PM
>>> *To:* Daniel Grotti
>>> *Cc:* spce-user at lists.sipwise.com; Matthew Ogden
>>> *Subject:* Re: [Spce-user] voip loopback test
>>>
>>>
>>>
>>> Not to stick my nose in something that it doesn't belong, but I think he
>>> is referring to what asterisk calls an "echo test".
>>>
>>> Its usually accessed via a star code (*31, if my memory serves me
>>> correctly).
>>>
>>> Hope this helps.
>>>
>>> Jeremy D. Ward, CWNE
>>> (954) 661-4965
>>>
>>> On Aug 27, 2014 1:01 PM, "Daniel Grotti" <dgrotti at sipwise.com> wrote:
>>>
>>> Hi,
>>> We don't have a specific number.
>>> It depends what you want to achieve, you can call the voicebox number
>>> for example or you can call another subscriber with a CF set to a mobile
>>> phone.
>>> Again it depends what you mean with loopback test.
>>>
>>> Daniel
>>>
>>> On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
>>> >
>>> > Hi
>>> >
>>> >
>>> >
>>> > Does spce have a number I can dial built-in that is a loopback test?
>>> >
>>> >
>>> >
>>> > Regards
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Matthew Ogden
>>> >
>>> > Management
>>> >
>>> > TenacIT
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Strategic IT Consulting ? Advanced Networking ? Virtualisation
>>> >
>>> > Custom Development ? Hosting ? Syspro Support  ? MS Licensing
>>> >
>>> > National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
>>> matthew at tenacit.net
>>> >
>>> > CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
>>> http://www.tenacit.net
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> _______________________________________________
>>> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140828/22e860ae/attachment.html>

From mat at solutionskubix.com  Wed Aug 27 15:55:33 2014
From: mat at solutionskubix.com (Marc-Antoine Talbot)
Date: Wed, 27 Aug 2014 19:55:33 +0000
Subject: [Spce-user] SipProvider as switch
Message-ID: <75FB62B18A57A9478C294EF5484725EF01E570E8@SERVER.kubix.local>

Hi,
I would like to use SipProvider CE to connect all my PBXs so that I can have only one trunk at my provider, and share the channels between the PBXs.

I created my provider peering, and I created a subscriber for each one of my PBX.

The problem is that I need to put my phone number in the subscriber username, otherwise the calls can't be route (404) to my PBX.

Second problem, when I call, the Caller ID is my provider username, and I haven't found any way to bypass it, other than making it hidden.


Is there something I did wrong ?

Thank you !



Marc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140827/97c99efa/attachment.html>

From sebas_elprimo at hotmail.com  Thu Aug 28 10:52:32 2014
From: sebas_elprimo at hotmail.com (sebastian rojo)
Date: Thu, 28 Aug 2014 09:52:32 -0500
Subject: [Spce-user]  [kamailio] Usrloc: cache vs database inconsistencies
Message-ID: <CAH7ArYyyWxHHXW8C2cm=EEOa-GFy3dVPON8Vbi9_NVxyPdA=aQ@mail.gmail.com>

I have noticed a consistent difference between the location records in DB.
and those stored in kamailio chache.


root at sbc:~# ngcp-kamctl proxy ul show |grep Contact

         Contact::
sip:2422 at X.16.10.221:54733;rinstance=48d7e73f599c5826;transport=TCP Q=

         Contact:: sip:2422 at x.1.1.180:36404;rinstance=691517d9fa77703f Q=

         Contact:: sip:4202 at x.1.2.79:43802;rinstance=cd4779b1598d1beb Q=

         Contact:: sip:4202 at x.48.236.198:40862;rinstance=487d6d482fd2cb5f Q=

         Contact:: sip:2420 at x.1.0.175:5060;transport=udp Q=

         Contact::
sip:2420 at x.x.11.213:34945;rinstance=aba2923ddadb6b56;transport=TCP Q=

         Contact:: sip:2420 at x.1.1.12:18584;rinstance=7c30d5a446902dd0 Q=

         Contact:: sip:2421 at x.1.0.232:60492;rinstance=62e978f706b850cd Q=

         Contact:: sip:2417 at x.1.0.180:4750;rinstance=1969d005d5cfd371 Q=

         Contact:: sip:2410 at x.1.0.236:17688;rinstance=bacd6921e1c49d12 Q=

         Contact::
sip:2410 at x.16.10.208:55658;rinstance=0768359aed20d852;transport=UDP Q=

         Contact::
sip:3501 at x.157.133.229:33857;rinstance=36c7a54559d5147a;transport=TCP
Q=

         Contact:: sip:3501 at x.1.0.119:9470;rinstance=7bdf7c5e0c70a752 Q=

         Contact:: sip:s at x.1.0.4:5060 Q=

14 records

On DB see this records.

SELECT username, contact, expires - NOW() FROM kamailio.location;

   username contact expires - NOW()  *3501*
*sip:3501 at X.16.10.243:34959;rinstance=7933832f47243e95;transport=UDP*
*-1918864*  *4202*
*sip:4202 at X.14.26.12:35400;rinstance=9dbc8f7e36af6250;transport=TCP*
*-959457*  *2422*
*sip:2422 at X.16.10.221:47987;rinstance=275352713d6a6325;transport=TCP*
*-958275*  dialcast sip:s at X.1.0.4:5060 29  2410 sip:2410 at X.16.10.208
:55658;rinstance=0768359aed20d852;transport=UDP 95  3501
sip:3501 at X.157.133.229:33857;rinstance=36c7a54559d5147a;transport=TCP 213
4202 Sip:4202 at X.1.2.79:43802;rinstance=cd4779b1598d1beb 240  2420
sip:2420 at X.16.11.213:34945;rinstance=aba2923ddadb6b56;transport=TCP 527
2422 sip:2422 at X.16.10.221:54733;rinstance=48d7e73f599c5826;transport=TCP 715
2417 sip:2417 at X.1.0.180:4750;rinstance=1969d005d5cfd371 1799  2420
sip:2420 at X.1.1.12:18584;rinstance=7c30d5a446902dd0 2298  3501
sip:3501 at X.1.0.119:9470;rinstance=7bdf7c5e0c70a752 7920  2421
sip:2421 at X.1.0.232:60492;rinstance=62e978f706b850cd 8019  2422
sip:2422 at X.1.1.180:36404;rinstance=691517d9fa77703f 8293  4202
sip:4202 at X.48.236.198:40862;rinstance=487d6d482fd2cb5f 8514  2410
sip:2410 at X.1.0.236:17688;rinstance=bacd6921e1c49d12 8925  2420
sip:2420 at X.1.0.175:5060;transport=udp 9927

see this records. already expired records that are not in the cache. but
still the DB

SELECT username, contact, expires FROM kamailio.location WHERE expires <= NOW();

   username contact expires  3501 sip:3501 at 172.16.10.243:34959
;rinstance=7933832f47243e95;transport=UDP 2014-08-26 17:36:44  4202
sip:4202 at 179.14.26.12:35400;rinstance=9dbc8f7e36af6250;transport=TCP 2014-08-27
13:30:51  2422 sip:2422 at 172.16.10.221:47987
;rinstance=275352713d6a6325;transport=TCP 2014-08-27 13:42:33
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140828/9630b360/attachment.html>

From dgrotti at sipwise.com  Thu Aug 28 12:13:46 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Thu, 28 Aug 2014 18:13:46 +0200
Subject: [Spce-user] SipProvider as switch
In-Reply-To: <75FB62B18A57A9478C294EF5484725EF01E570E8@SERVER.kubix.local>
References: <75FB62B18A57A9478C294EF5484725EF01E570E8@SERVER.kubix.local>
Message-ID: <53FF553A.1010305@sipwise.com>

Hi,


On 08/27/2014 09:55 PM, Marc-Antoine Talbot wrote:
>
> Hi,
>
> I would like to use SipProvider CE to connect all my PBXs so that I
> can have only one trunk at my provider, and share the channels between
> the PBXs.
>
>
> I created my provider peering, and I created a subscriber for each one
> of my PBX.
>
>  
>
> The problem is that I need to put my phone number in the subscriber
> username, otherwise the calls can?t be route (404) to my PBX.
>


What you would like to achieve here ?
you need to register you PBXs as a subscriber. Subscriber has a E164
number associated, in order to be called.



>  
>
> Second problem, when I call, the Caller ID is my provider username,
> and I haven?t found any way to bypass it, other than making it hidden.
>


In order to keep the PBX caller ID, you should add the "allowed_clis"
list in your subscriber's preferences.
You can put there an "*" in order to match every number

>  
>
>  
>
> Is there something I did wrong ?
>
>  
>
> Thank you !
>
>  
>
>  
>
>  
>
> *Marc*
>


*Regards,
Daniel


*
>
>  
>
>
>
> _______________________________________________
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140828/f836c563/attachment.html>

From jbonilla at sipwise.com  Thu Aug 28 14:35:25 2014
From: jbonilla at sipwise.com (Jon Bonilla (Manwe))
Date: Thu, 28 Aug 2014 20:35:25 +0200
Subject: [Spce-user] SipProvider as switch
In-Reply-To: <75FB62B18A57A9478C294EF5484725EF01E570E8@SERVER.kubix.local>
References: <75FB62B18A57A9478C294EF5484725EF01E570E8@SERVER.kubix.local>
Message-ID: <20140828203525.7ab7d14c@quenya>

El Wed, 27 Aug 2014 19:55:33 +0000
Marc-Antoine Talbot <mat at solutionskubix.com> escribi?:

> Hi,
> I would like to use SipProvider CE to connect all my PBXs so that I can have
> only one trunk at my provider, and share the channels between the PBXs.
> 
> I created my provider peering, and I created a subscriber for each one of my
> PBX.
> 
> The problem is that I need to put my phone number in the subscriber username,
> otherwise the calls can't be route (404) to my PBX.

Yes thye can. If you enable "e164_to_ruri" option in the subscriber preference
the number will be sent to the pbx instead of the sip username.


> 
> Second problem, when I call, the Caller ID is my provider username, and I
> haven't found any way to bypass it, other than making it hidden.
> 

It depends on your provider. If it validates the callerid you send in the From
header it can rewrite it with the one it provided to you.

Maybe you need to send the callerid in another header or in another format.
That will depend on your peer and you should discuss it with your support.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140828/4eb0b7b7/attachment.asc>

From vseva at sipwise.com  Fri Aug 29 05:18:15 2014
From: vseva at sipwise.com (Victor Seva)
Date: Fri, 29 Aug 2014 11:18:15 +0200
Subject: [Spce-user] [kamailio] Usrloc: cache vs database inconsistencies
In-Reply-To: <CAH7ArYyyWxHHXW8C2cm=EEOa-GFy3dVPON8Vbi9_NVxyPdA=aQ@mail.gmail.com>
References: <CAH7ArYyyWxHHXW8C2cm=EEOa-GFy3dVPON8Vbi9_NVxyPdA=aQ@mail.gmail.com>
Message-ID: <54004557.6070707@sipwise.com>

On 08/28/2014 04:52 PM, sebastian rojo wrote:
> I have noticed a consistent difference between the location records in
> DB. and those stored in kamailio chache.

Knowing the version you are running could be helpful.
Please post the output of "dpkg -l ngcp-kamailio || dpkg -l kamailio"

Cheers,
Victor

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140829/2b81d9e9/attachment.asc>

From cervajs at fpf.slu.cz  Fri Aug 29 07:15:44 2014
From: cervajs at fpf.slu.cz (Marek Cervenka)
Date: Fri, 29 Aug 2014 13:15:44 +0200
Subject: [Spce-user] spce ip aliases
Message-ID: <540060E0.9000409@fpf.slu.cz>

hi,

is it possible use spce with multiple aliased ips?

like
eth0 192.168.100.1
eth0:1 192.168.100.20
eth0:2 192.168.100.30

and register endpoints to i.e. 192.168.100.30 and answer from spce will 
have src ip 192.168.100.30
thanks

-- 
---------------------------------------
Marek Cervenka
=======================================




From agranig at sipwise.com  Fri Aug 29 07:27:58 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Fri, 29 Aug 2014 13:27:58 +0200
Subject: [Spce-user] spce ip aliases
In-Reply-To: <540060E0.9000409@fpf.slu.cz>
References: <540060E0.9000409@fpf.slu.cz>
Message-ID: <540063BE.3040003@sipwise.com>

Hi,

You might want to check
https://www.sipwise.com/doc/mr3.4.1/spce/ar01s05.html#_extra_sip_listening_ports
for that. You can't just add other ports, but should be able to add
different IPs too.

Andreas

On 08/29/2014 01:15 PM, Marek Cervenka wrote:
> hi,
> 
> is it possible use spce with multiple aliased ips?
> 
> like
> eth0 192.168.100.1
> eth0:1 192.168.100.20
> eth0:2 192.168.100.30
> 
> and register endpoints to i.e. 192.168.100.30 and answer from spce will
> have src ip 192.168.100.30
> thanks
> 


From alutay at sipwise.com  Fri Aug 29 09:03:32 2014
From: alutay at sipwise.com (Alex Lutay)
Date: Fri, 29 Aug 2014 15:03:32 +0200
Subject: [Spce-user] SPCE 3.4.1 not showing call history in Web portal
In-Reply-To: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>
References: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>
Message-ID: <54007A24.2000308@sipwise.com>

Dear Tabi!

On 28/08/14 14:11, Tabi Tabe Tabi wrote:
> I installed SPCE 3.4.1 and got is working fine. However it does not show
> call history under call distribution or subscriber menu. Any idea what
> could be the cause?

Can you try this fix:
> https://github.com/sipwise/ngcp-panel/commit/cf93f0bf63dca1b66775feb5c7622af0c4d4cae6
if it helps you we will include it in next build mr3.4.2.
Thank you!

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From arpagon+sipwise at gmail.com  Fri Aug 29 10:43:25 2014
From: arpagon+sipwise at gmail.com (sebastian rojo)
Date: Fri, 29 Aug 2014 09:43:25 -0500
Subject: [Spce-user] [kamailio] Usrloc: cache vs database inconsistencies
In-Reply-To: <54004557.6070707@sipwise.com>
References: <CAH7ArYyyWxHHXW8C2cm=EEOa-GFy3dVPON8Vbi9_NVxyPdA=aQ@mail.gmail.com>
 <54004557.6070707@sipwise.com>
Message-ID: <CAH7ArYyLm1W4g1tCCWHPzUX-YgNxg_CGO=8A=X83zmfNxcpAsw@mail.gmail.com>

Hi,

root at sbc:~# cat /etc/sipwise_ngcp_version
System installed. NGCP version mr3.3.2 on 2014-07-23 11:12:57

root at sbc:~# dpkg -l ngcp-kamailio || dpkg -l kamailio
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                Version        Architecture   Description
+++-===================-==============-==============-===========================================
ii  ngcp-kamailio       4.1.3-1+0~mr3. amd64          very fast and
configurable SIP proxy



On Fri, Aug 29, 2014 at 4:18 AM, Victor Seva <vseva at sipwise.com> wrote:

> On 08/28/2014 04:52 PM, sebastian rojo wrote:
> > I have noticed a consistent difference between the location records in
> > DB. and those stored in kamailio chache.
>
> Knowing the version you are running could be helpful.
> Please post the output of "dpkg -l ngcp-kamailio || dpkg -l kamailio"
>
> Cheers,
> Victor
>
>
> _______________________________________________
> 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/mailman/private/spce-user_lists.sipwise.com/attachments/20140829/d426c8d9/attachment.html>

From tabi.tabe at gmail.com  Fri Aug 29 12:15:00 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Fri, 29 Aug 2014 18:15:00 +0200
Subject: [Spce-user] SPCE 3.4.1 not showing call history in Web portal
In-Reply-To: <54007A24.2000308@sipwise.com>
References: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>
 <54007A24.2000308@sipwise.com>
Message-ID: <CAOibrm52FOQ6CNaR0aLbm6TS0=VVemKtnA1hoby+ME66YtR2wA@mail.gmail.com>

Will do. After updating the .tt file, do I need to run any command to
update the system?

Regards,

Tabi


On Fri, Aug 29, 2014 at 3:03 PM, Alex Lutay <alutay at sipwise.com> wrote:

> Dear Tabi!
>
>
> On 28/08/14 14:11, Tabi Tabe Tabi wrote:
>
>> I installed SPCE 3.4.1 and got is working fine. However it does not show
>> call history under call distribution or subscriber menu. Any idea what
>> could be the cause?
>>
>
> Can you try this fix:
>
>> https://github.com/sipwise/ngcp-panel/commit/
>> cf93f0bf63dca1b66775feb5c7622af0c4d4cae6
>>
> if it helps you we will include it in next build mr3.4.2.
> Thank you!
>
> --
> Alexander Lutay
> Head of Quality Assurance
> Sipwise GmbH, Campus 21/Europaring F15
> AT-2345 Brunn am Gebirge
>
> Office: +43(0)13012036
> Email: alutay at sipwise.com
> Website: http://www.sipwise.com
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>



-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140829/b9c92c96/attachment.html>

From george.mason at xoomtalk.com  Fri Aug 29 12:18:57 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Fri, 29 Aug 2014 17:18:57 +0100
Subject: [Spce-user] LCR in SPCE?
Message-ID: <5400A7F1.6060208@xoomtalk.com>

Hi,

I have been looking around SPCE and like what I see. One element that I
cannot see anywhere, which is useful on other systems, is LCR. Namely
the ability to route a call to a given carrier based on the price for
that call.

As far as I can see, rate-o-mat rates the calls after they have
completed, so there is no account taken of what the cheapest route might
have been. This is a shame as it requires more complex routes to get
traffic over the best-costing carrier.

On that subject - is there a way to bulk import callee patterns against
a SIP peering? I am trying to configure a channel to only route the best
priced destinations and this involves lots (over 60K) of patterns. Will
this kill the routing engine? How can I import these, presume they need
to go straight into the DB?

Thanks

George


From tabi.tabe at gmail.com  Fri Aug 29 12:39:31 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Fri, 29 Aug 2014 18:39:31 +0200
Subject: [Spce-user] SPCE 3.4.1 not showing call history in Web portal
In-Reply-To: <CAOibrm52FOQ6CNaR0aLbm6TS0=VVemKtnA1hoby+ME66YtR2wA@mail.gmail.com>
References: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>
 <54007A24.2000308@sipwise.com>
 <CAOibrm52FOQ6CNaR0aLbm6TS0=VVemKtnA1hoby+ME66YtR2wA@mail.gmail.com>
Message-ID: <CAOibrm4w8u7WJF3eogS0Dk8jkp38yEJcbv8Jak-2630h9d4D2Q@mail.gmail.com>

Hi Alex,

An interesting observation. I checked Kamailio.log and found this errors:

Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database
Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database
Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database
Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database
Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database
Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database
Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database



Also checked the CDR table in MySQL and found zero record. Can't connect
MySQL. MySQL is running. What parameters should I check? All serv

Regards,

Tabi


On Fri, Aug 29, 2014 at 6:15 PM, Tabi Tabe Tabi <tabi.tabe at gmail.com> wrote:

> Will do. After updating the .tt file, do I need to run any command to
> update the system?
>
> Regards,
>
> Tabi
>
>
> On Fri, Aug 29, 2014 at 3:03 PM, Alex Lutay <alutay at sipwise.com> wrote:
>
>> Dear Tabi!
>>
>>
>> On 28/08/14 14:11, Tabi Tabe Tabi wrote:
>>
>>> I installed SPCE 3.4.1 and got is working fine. However it does not show
>>> call history under call distribution or subscriber menu. Any idea what
>>> could be the cause?
>>>
>>
>> Can you try this fix:
>>
>>> https://github.com/sipwise/ngcp-panel/commit/
>>> cf93f0bf63dca1b66775feb5c7622af0c4d4cae6
>>>
>> if it helps you we will include it in next build mr3.4.2.
>> Thank you!
>>
>> --
>> Alexander Lutay
>> Head of Quality Assurance
>> Sipwise GmbH, Campus 21/Europaring F15
>> AT-2345 Brunn am Gebirge
>>
>> Office: +43(0)13012036
>> Email: alutay at sipwise.com
>> Website: http://www.sipwise.com
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>>
>
>
>
> --
> ...Tabi
>
>


-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140829/00928f4b/attachment.html>

From tabi.tabe at gmail.com  Fri Aug 29 13:04:17 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Fri, 29 Aug 2014 19:04:17 +0200
Subject: [Spce-user] SPCE 3.4.1 not showing call history in Web portal
In-Reply-To: <CAOibrm4w8u7WJF3eogS0Dk8jkp38yEJcbv8Jak-2630h9d4D2Q@mail.gmail.com>
References: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>
 <54007A24.2000308@sipwise.com>
 <CAOibrm52FOQ6CNaR0aLbm6TS0=VVemKtnA1hoby+ME66YtR2wA@mail.gmail.com>
 <CAOibrm4w8u7WJF3eogS0Dk8jkp38yEJcbv8Jak-2630h9d4D2Q@mail.gmail.com>
Message-ID: <CAOibrm4SqsbnjoUVRp8sXWiWM8uciBTHrDWCURbUmWKNo3_SDw@mail.gmail.com>

Please ignore the email on the .tt template. Was not awake :-)

Problem still with database connection though. Any ideas?

Regards,

Tabi


On Fri, Aug 29, 2014 at 6:39 PM, Tabi Tabe Tabi <tabi.tabe at gmail.com> wrote:

> Hi Alex,
>
> An interesting observation. I checked Kamailio.log and found this errors:
>
> Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
> Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
> Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
> Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
> Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
> Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
> Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
>
>
>
> Also checked the CDR table in MySQL and found zero record. Can't connect
> MySQL. MySQL is running. What parameters should I check? All serv
>
> Regards,
>
> Tabi
>
>
> On Fri, Aug 29, 2014 at 6:15 PM, Tabi Tabe Tabi <tabi.tabe at gmail.com>
> wrote:
>
>> Will do. After updating the .tt file, do I need to run any command to
>> update the system?
>>
>> Regards,
>>
>> Tabi
>>
>>
>> On Fri, Aug 29, 2014 at 3:03 PM, Alex Lutay <alutay at sipwise.com> wrote:
>>
>>> Dear Tabi!
>>>
>>>
>>> On 28/08/14 14:11, Tabi Tabe Tabi wrote:
>>>
>>>> I installed SPCE 3.4.1 and got is working fine. However it does not show
>>>> call history under call distribution or subscriber menu. Any idea what
>>>> could be the cause?
>>>>
>>>
>>> Can you try this fix:
>>>
>>>> https://github.com/sipwise/ngcp-panel/commit/
>>>> cf93f0bf63dca1b66775feb5c7622af0c4d4cae6
>>>>
>>> if it helps you we will include it in next build mr3.4.2.
>>> Thank you!
>>>
>>> --
>>> Alexander Lutay
>>> Head of Quality Assurance
>>> Sipwise GmbH, Campus 21/Europaring F15
>>> AT-2345 Brunn am Gebirge
>>>
>>> Office: +43(0)13012036
>>> Email: alutay at sipwise.com
>>> Website: http://www.sipwise.com
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>
>>
>>
>> --
>> ...Tabi
>>
>>
>
>
> --
> ...Tabi
>
>


-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140829/6ff27278/attachment.html>

From kmasse at questblue.com  Fri Aug 29 15:52:50 2014
From: kmasse at questblue.com (Kevin Masse)
Date: Fri, 29 Aug 2014 15:52:50 -0400
Subject: [Spce-user] Subscriber Alias Entries in Database
References: <CEEE718799582B47A55D7897DCB264FC3F5E18@bvusaex.bestvoipusa.local><53C652BD.7000707@sipwise.com>
 <CEEE718799582B47A55D7897DCB264FC3F5E65@bvusaex.bestvoipusa.local>
 <CEEE718799582B47A55D7897DCB264FC3F5F7F@bvusaex.bestvoipusa.local>
 <CEEE718799582B47A55D7897DCB264FC3F61AD@bvusaex.bestvoipusa.local>
Message-ID: <CEEE718799582B47A55D7897DCB264FC3F62FD@bvusaex.bestvoipusa.local>

Greetings group:

I was hoping that someone might have had some thought on the two
questions below or perhaps it got buried.

\\ locate the 
************* 2 questions below ****************
\\ below

Thanks
Kevin



-----Original Message-----
From: Kevin Masse 
Sent: Thursday, August 14, 2014 7:33 AM
To: Kevin Masse; 'Andreas Granig'; 'spce-user at lists.sipwise.com'
Subject: RE: [Spce-user] Subscriber Alias Entries in Database

Hello Andraes, have you had a chance to review the two questions stated
below?

Our dev team is seeking to close out this issue we are having.

Thank you
Kevin




-----Original Message-----
From: Kevin Masse
Sent: Wednesday, August 06, 2014 7:55 AM
To: Kevin Masse; 'Andreas Granig'; 'spce-user at lists.sipwise.com'
Subject: RE: [Spce-user] Subscriber Alias Entries in Database

Hello, I was wondering if there was a response to this that I missed.
There are two specific questions we are trying to answer.


Thank you
Kevin



-----Original Message-----
From: Kevin Masse
Sent: Thursday, July 24, 2014 10:02 AM
To: Kevin Masse; Andreas Granig; spce-user at lists.sipwise.com
Subject: RE: [Spce-user] Subscriber Alias Entries in Database

Andraes one additional scenario has come up based on our last thread:
I wanted to post to the group the question from our dev team:

****  Begin Comment ****
It is going to be a long post because I can't explain in a short
message. I'll provide some example to explain what I mean. 

We have SIP named QBATRUNK.  If you open administrator page
(https://DOMAIN:1443/subscriber/detail?subscriber_id=395) you can see
there following info:

Contract ID (405) - This is main ID which we store in (customer site -
not part of Sipwise it is our Database) . All operations like
lock/unlock SIP, add/remove DID using the ID in it request to API.

Subscriber ID (395) - I can call it internal info, it is not used in any
request to Sipwise API but to make direct request to Sipwise DB I have
to use it.

I routed 3384066 DID to the SIP to work with the example. 
According to previous instructions we use two databases to store
aliases. Now I'll show you request to retrieve the DID from Sipwise DB.

First I use billing DB. Let's retrieve Subscriber ID (we do not know it
when call DB directly). I use voip_subscribers table which stores the
info.

mysql> select * from voip_subscribers where contract_id = 405;
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+
| id | contract_id | uuid | username | domain_id | status | 
| primary_number_id | external_id |
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+
| 395 | 405 | 14a58c84-c83e-4673-9d10-361a1a6b990e | QBATRUNK | 1 | 
| active | NULL | NULL |
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+

OK you can see that I receive id 395. We need it.

 

Let's get DIDs info from voip_numbers, DB - 

mysql> select * from voip_numbers where subscriber_id = 395;
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+
| id | cc | ac | sn | reseller_id | subscriber_id | status | ported | 
| list_timestamp |
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+
| 2119 | 1 | 910 | 3384066 | NULL | 395 | active | 1 | 2014-07-22 
| 18:32:16 |
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+

Everything is OK we got it as expected. Lets' get DID info from second
DB (provisioning) I'll do it using DID number

mysql> select * from voip_dbaliases where username like '%3384066%';
+------+-------------+-----------+---------------+
| id | username | domain_id | subscriber_id |
+------+-------------+-----------+---------------+
| 2821 | 19103384066 | 3 | 398 |

As you can see subscriber_id in the table does not corresponds to the
subscriber_id which we retrieve from billing DB. That is the question
for me.

I found that the subscriber_id is stored in voip_dbaliases table but the
ID does not corresponds to the subscriber_id from billing table.




************* 2 questions below ****************





Question 1
I do not understand how subscriber_id in billing DB (table voip_numbers)
related with subscriber_id in provisioning DB (table voip_dbaliases ).

Question 2
Another question. I found that DIDs info is stored in voip_dbaliases
table (provisioning) but I did not told to creae the record by VoIP
specialist.


mysql> select * from voip_dbaliases where username like '%3384066%';
+------+-------------+-----------+---------------+
| id | username | domain_id | subscriber_id |
+------+-------------+-----------+---------------+
| 2821 | 19103384066 | 3 | 398 |
+------+-------------+-----------+---------------+

Hopefully I explained my questions clear. If not please let me know

Thanks,
*** End Comment from DEV ***



In conclusion Andreas do you think there is a proper answer for the
above Question 1 and Question 2?
Thank you
Kevin 





-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Kevin Masse
Sent: Wednesday, July 16, 2014 8:56 AM
To: Andreas Granig; spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Subscriber Alias Entries in Database

Thank you Andreas, I appreciate the detailed response.  Works as
described.
Kevin



-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Andreas Granig
Sent: Wednesday, July 16, 2014 6:24 AM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Subscriber Alias Entries in Database

Hi,

On 07/15/2014 03:05 PM, Kevin Masse wrote:

> **  Current operation:   We use SOAP to add alias numbers to a
subscriber 
> 
> Requested operation:  We would like to write a new alias number for a 
> subscriber directly to the database.

As long as you make sure to write it to both billing.voip_numbers and
provisioning.voip_dbaliases, it should be fine.

Andreas

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/listinfo/spce-user

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/listinfo/spce-user


From agranig at sipwise.com  Fri Aug 29 18:09:45 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Sat, 30 Aug 2014 00:09:45 +0200
Subject: [Spce-user] SPCE 3.4.1 not showing call history in Web portal
In-Reply-To: <CAOibrm4SqsbnjoUVRp8sXWiWM8uciBTHrDWCURbUmWKNo3_SDw@mail.gmail.com>
References: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>
 <54007A24.2000308@sipwise.com>
 <CAOibrm52FOQ6CNaR0aLbm6TS0=VVemKtnA1hoby+ME66YtR2wA@mail.gmail.com>
 <CAOibrm4w8u7WJF3eogS0Dk8jkp38yEJcbv8Jak-2630h9d4D2Q@mail.gmail.com>
 <CAOibrm4SqsbnjoUVRp8sXWiWM8uciBTHrDWCURbUmWKNo3_SDw@mail.gmail.com>
Message-ID: <5400FA29.4050908@sipwise.com>

Hi,

You need to check if mysqld is running and if you can connect to it via
command line.

Usual suspects for such issues are running out of memory (check dmesg
for OOM messages) and running out of disk space.

Andreas

On 08/29/2014 07:04 PM, Tabi Tabe Tabi wrote:
> Please ignore the email on the .tt template. Was not awake :-)
> 
> Problem still with database connection though. Any ideas?
> 
> Regards,
> 
> Tabi
> 
> 
> On Fri, Aug 29, 2014 at 6:39 PM, Tabi Tabe Tabi <tabi.tabe at gmail.com
> <mailto:tabi.tabe at gmail.com>> wrote:
> 
>     Hi Alex,
> 
>     An interesting observation. I checked Kamailio.log and found this
>     errors:
> 
>     Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
>     Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
>     Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
>     Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
>     Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
>     Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
>     Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
> 
> 
> 
>     Also checked the CDR table in MySQL and found zero record. Can't
>     connect MySQL. MySQL is running. What parameters should I check? All
>     serv
> 
>     Regards,
> 
>     Tabi
> 
> 
>     On Fri, Aug 29, 2014 at 6:15 PM, Tabi Tabe Tabi <tabi.tabe at gmail.com
>     <mailto:tabi.tabe at gmail.com>> wrote:
> 
>         Will do. After updating the .tt file, do I need to run any
>         command to update the system?
> 
>         Regards,
> 
>         Tabi
> 
> 
>         On Fri, Aug 29, 2014 at 3:03 PM, Alex Lutay <alutay at sipwise.com
>         <mailto:alutay at sipwise.com>> wrote:
> 
>             Dear Tabi!
> 
> 
>             On 28/08/14 14:11, Tabi Tabe Tabi wrote:
> 
>                 I installed SPCE 3.4.1 and got is working fine. However
>                 it does not show
>                 call history under call distribution or subscriber menu.
>                 Any idea what
>                 could be the cause?
> 
> 
>             Can you try this fix:
> 
>                 https://github.com/sipwise/__ngcp-panel/commit/__cf93f0bf63dca1b66775feb5c7622a__f0c4d4cae6
>                 <https://github.com/sipwise/ngcp-panel/commit/cf93f0bf63dca1b66775feb5c7622af0c4d4cae6>
> 
>             if it helps you we will include it in next build mr3.4.2.
>             Thank you!
> 
>             -- 
>             Alexander Lutay
>             Head of Quality Assurance
>             Sipwise GmbH, Campus 21/Europaring F15
>             AT-2345 Brunn am Gebirge
> 
>             Office: +43(0)13012036 <tel:%2B43%280%2913012036>
>             Email: alutay at sipwise.com <mailto:alutay at sipwise.com>
>             Website: http://www.sipwise.com
>             _________________________________________________
>             Spce-user mailing list
>             Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>             https://lists.sipwise.com/__listinfo/spce-user
>             <https://lists.sipwise.com/listinfo/spce-user>
> 
> 
> 
> 
>         -- 
>         ...Tabi
> 
> 
> 
> 
>     -- 
>     ...Tabi
> 
> 
> 
> 
> -- 
> ...Tabi
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From agranig at sipwise.com  Fri Aug 29 18:16:52 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Sat, 30 Aug 2014 00:16:52 +0200
Subject: [Spce-user] LCR in SPCE?
In-Reply-To: <5400A7F1.6060208@xoomtalk.com>
References: <5400A7F1.6060208@xoomtalk.com>
Message-ID: <5400FBD4.2020506@sipwise.com>

Hi,

You can bulk-upload a CSV via the panel (since pretty much from the
start) or via REST API (since mr3.4).

You can then enable LCR for peerings by setting "perform_peer_lcr" to
"yes" in config.yml (off by default).

Andreas

On 08/29/2014 06:18 PM, George Mason wrote:
> Hi,
> 
> I have been looking around SPCE and like what I see. One element that I
> cannot see anywhere, which is useful on other systems, is LCR. Namely
> the ability to route a call to a given carrier based on the price for
> that call.
> 
> As far as I can see, rate-o-mat rates the calls after they have
> completed, so there is no account taken of what the cheapest route might
> have been. This is a shame as it requires more complex routes to get
> traffic over the best-costing carrier.
> 
> On that subject - is there a way to bulk import callee patterns against
> a SIP peering? I am trying to configure a channel to only route the best
> priced destinations and this involves lots (over 60K) of patterns. Will
> this kill the routing engine? How can I import these, presume they need
> to go straight into the DB?
> 
> Thanks
> 
> George
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From jbonilla at sipwise.com  Sat Aug 30 03:25:47 2014
From: jbonilla at sipwise.com (Jon Bonilla (Manwe))
Date: Sat, 30 Aug 2014 09:25:47 +0200
Subject: [Spce-user] LCR in SPCE?
In-Reply-To: <5400A7F1.6060208@xoomtalk.com>
References: <5400A7F1.6060208@xoomtalk.com>
Message-ID: <20140830092547.76a3abb4@quenya>

El Fri, 29 Aug 2014 17:18:57 +0100
George Mason <george.mason at xoomtalk.com> escribi?:

> Hi,
> 
> I have been looking around SPCE and like what I see. One element that I
> cannot see anywhere, which is useful on other systems, is LCR. Namely
> the ability to route a call to a given carrier based on the price for
> that call.
> 
> As far as I can see, rate-o-mat rates the calls after they have
> completed, so there is no account taken of what the cheapest route might
> have been. This is a shame as it requires more complex routes to get
> traffic over the best-costing carrier.
> 
> On that subject - is there a way to bulk import callee patterns against
> a SIP peering? I am trying to configure a channel to only route the best
> priced destinations and this involves lots (over 60K) of patterns. Will
> this kill the routing engine? How can I import these, presume they need
> to go straight into the DB?
> 
>

Hi George

You can enable lcr in config.yml, in the proxy section.




 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140830/c4436726/attachment.asc>

From aalejandro at alliedtechnologygrouppr.com  Sun Aug 31 03:05:11 2014
From: aalejandro at alliedtechnologygrouppr.com (Abel Alejandro)
Date: Sun, 31 Aug 2014 03:05:11 -0400
Subject: [Spce-user] invoke-rc.d: policy-rc.d denied execution of stop.
Message-ID: <CAKiNg21vn2UqtTBvjpEW9jxTt41UYL-rcAzUeOS-Va085q=yrg@mail.gmail.com>

Hello,

Upgrading from mr3.3.1 to mr3.4.1 I got a few of those errors and it seems
the upgrade tried to stop a few demons but got stuck when it couldnt stop
mysql.

Just stopped the mysql daemon manually and the upgraded continued fine.

Everything seems to be working after upgrade just wanted to report in case.

Thanks.

-- 
*Abel Alejandro*

787 586 8313 | 787 705 0555
<joquendo at alliedtechnologygrouppr.com>

400 Calle Calaf 477
San Juan, PR 00918
aalejandro at alliedtechnologygrouppr.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140831/8a0bcab3/attachment.html>

From mprokop at sipwise.com  Sun Aug 31 03:29:31 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Sun, 31 Aug 2014 09:29:31 +0200
Subject: [Spce-user] invoke-rc.d: policy-rc.d denied execution of stop.
In-Reply-To: <CAKiNg21vn2UqtTBvjpEW9jxTt41UYL-rcAzUeOS-Va085q=yrg@mail.gmail.com>
References: <CAKiNg21vn2UqtTBvjpEW9jxTt41UYL-rcAzUeOS-Va085q=yrg@mail.gmail.com>
Message-ID: <2014-08-31T09-27-06@devnull.michael-prokop.at>

* Abel Alejandro [Sun Aug 31, 2014 at 03:05:11AM -0400]:

> Upgrading from mr3.3.1 to mr3.4.1 I got a few of those errors and it seems
> the upgrade tried to stop a few demons but got stuck when it couldnt stop
> mysql.

> Just stopped the mysql daemon manually and the upgraded continued fine.

> Everything seems to be working after upgrade just wanted to report in case.

Did your upgrade actually really interrupt/abort? If so do you have
any error logs available for us?

The 'invoke-rc.d: policy-rc.d denied execution of stop' are only
warnings and no error messages, that setup is by intention and
should be working just fine.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140831/7e263ad6/attachment.asc>

From aalejandro at alliedtechnologygrouppr.com  Sun Aug 31 03:38:37 2014
From: aalejandro at alliedtechnologygrouppr.com (Abel Alejandro)
Date: Sun, 31 Aug 2014 03:38:37 -0400
Subject: [Spce-user] invoke-rc.d: policy-rc.d denied execution of stop.
In-Reply-To: <2014-08-31T09-27-06@devnull.michael-prokop.at>
References: <CAKiNg21vn2UqtTBvjpEW9jxTt41UYL-rcAzUeOS-Va085q=yrg@mail.gmail.com>
 <2014-08-31T09-27-06@devnull.michael-prokop.at>
Message-ID: <CAKiNg23G0-S2V4PCzgK2pSOHD0i+iU0+M3pEkyJRV0=zTNZg2w@mail.gmail.com>

While the upgrade got stuck I ran this:

root at sip:/var/log# tail /tmp/upgrade.log
Unpacking replacement mysql-client-5.5 ...
Preparing to replace mysql-server-core-5.5 5.5.37-0+wheezy1 (using
.../mysql-server-core-5.5_5.5.38-0+wheezy1_amd64.deb) ...
Unpacking replacement mysql-server-core-5.5 ...
Preparing to replace ngcp-installer-ce 0.14.1.3+0~mr3.3.1.3 (using
.../ngcp-installer-ce_0.15.1.2+0~mr3.4.1.2_all.deb) ...
Unpacking replacement ngcp-installer-ce ...
Processing triggers for man-db ...
Setting up mysql-client-5.5 (5.5.38-0+wheezy1) ...
Setting up mysql-server-core-5.5 (5.5.38-0+wheezy1) ...
Setting up mysql-server-5.5 (5.5.38-0+wheezy1) ...
invoke-rc.d: policy-rc.d denied execution of stop.
root at sip:/var/log#

I had two instances of mysqld trying to come up, the last one kept changing
process id, so I just killed the old one

root at sip:/var/log# ps -aux
warning: bad ps syntax, perhaps a bogus '-'?
See http://gitorious.org/procps/procps/blobs/master/Documentation/FAQ
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0  10648   696 ?        Ss   Jul19   1:23 init [2]
root         2  0.0  0.0      0     0 ?        S    Jul19   0:00 [kthreadd]
root         3  0.0  0.0      0     0 ?        S    Jul19   0:19
[ksoftirqd/0]
root         5  0.0  0.0      0     0 ?        S    Jul19   0:26
[kworker/u:0]
root         6  0.0  0.0      0     0 ?        S    Jul19   0:00
[migration/0]
root         7  0.0  0.0      0     0 ?        S    Jul19   0:08
[watchdog/0]
root         8  0.0  0.0      0     0 ?        S    Jul19   0:00
[migration/1]
root         9  0.0  0.0      0     0 ?        S    Jul19   1:11
[kworker/1:0]
root        10  0.0  0.0      0     0 ?        S    Jul19   0:15
[ksoftirqd/1]
root        11  0.0  0.0      0     0 ?        S    Jul19   1:34
[kworker/0:1]
root        12  0.0  0.0      0     0 ?        S    Jul19   0:06
[watchdog/1]
root        13  0.0  0.0      0     0 ?        S    Jul19   0:00
[migration/2]
root        14  0.0  0.0      0     0 ?        S    Jul19   1:22
[kworker/2:0]
root        15  0.0  0.0      0     0 ?        S    Jul19   0:15
[ksoftirqd/2]
root        16  0.0  0.0      0     0 ?        S    Jul19   0:07
[watchdog/2]
root        17  0.0  0.0      0     0 ?        S    Jul19   0:00
[migration/3]
root        19  0.0  0.0      0     0 ?        S    Jul19   0:16
[ksoftirqd/3]
root        20  0.0  0.0      0     0 ?        S    Jul19   0:06
[watchdog/3]
root        21  0.0  0.0      0     0 ?        S    Jul19   0:17
[migration/4]
root        23  0.0  0.0      0     0 ?        S    Jul19   0:20
[ksoftirqd/4]
root        24  0.0  0.0      0     0 ?        S    Jul19   0:06
[watchdog/4]
root        25  0.0  0.0      0     0 ?        S    Jul19   0:17
[migration/5]
root        27  0.0  0.0      0     0 ?        S    Jul19   0:18
[ksoftirqd/5]
root        28  0.0  0.0      0     0 ?        S    Jul19   0:06
[watchdog/5]
root        29  0.0  0.0      0     0 ?        S    Jul19   0:17
[migration/6]
root        31  0.0  0.0      0     0 ?        S    Jul19   0:16
[ksoftirqd/6]
root        32  0.0  0.0      0     0 ?        S    Jul19   0:06
[watchdog/6]
root        33  0.0  0.0      0     0 ?        S    Jul19   0:17
[migration/7]
root        35  0.0  0.0      0     0 ?        S    Jul19   0:15
[ksoftirqd/7]
root        36  0.0  0.0      0     0 ?        S    Jul19   0:06
[watchdog/7]
root        37  0.0  0.0      0     0 ?        S<   Jul19   0:00 [cpuset]
root        38  0.0  0.0      0     0 ?        S<   Jul19   0:00 [khelper]
root        39  0.0  0.0      0     0 ?        S    Jul19   0:00 [kdevtmpfs]
root        40  0.0  0.0      0     0 ?        S<   Jul19   0:00 [netns]
root        41  0.0  0.0      0     0 ?        S    Jul19   0:06
[sync_supers]
root        42  0.0  0.0      0     0 ?        S    Jul19   0:00
[bdi-default]
root        43  0.0  0.0      0     0 ?        S<   Jul19   0:00
[kintegrityd]
root        44  0.0  0.0      0     0 ?        S<   Jul19   0:00 [kblockd]
root        45  0.0  0.0      0     0 ?        S    Jul19   1:25
[kworker/1:1]
root        46  0.0  0.0      0     0 ?        S    Jul19   1:18
[kworker/2:1]
root        47  0.0  0.0      0     0 ?        S    Jul19   2:21
[kworker/3:1]
root        48  0.0  0.0      0     0 ?        S    Jul19   1:21
[kworker/4:1]
root        49  0.0  0.0      0     0 ?        S    Jul19   0:58
[kworker/5:1]
root        51  0.0  0.0      0     0 ?        S    Jul19   0:34
[kworker/7:1]
root        52  0.0  0.0      0     0 ?        S    Jul19   0:02
[khungtaskd]
root        53  0.0  0.0      0     0 ?        S    Jul19   0:00 [kswapd0]
root        54  0.0  0.0      0     0 ?        SN   Jul19   0:00 [ksmd]
root        55  0.0  0.0      0     0 ?        SN   Jul19   0:00
[khugepaged]
root        56  0.0  0.0      0     0 ?        S    Jul19   0:00
[fsnotify_mark]
root        57  0.0  0.0      0     0 ?        S<   Jul19   0:00 [crypto]
root       183  0.0  0.0      0     0 ?        S    Jul19   0:00 [khubd]
root       184  0.0  0.0      0     0 ?        S    Jul19   0:00
[cciss_scan]
root       185  0.0  0.0      0     0 ?        S<   Jul19   0:00 [ata_sff]
root       186  0.0  0.0      0     0 ?        S    Jul19   0:00 [scsi_eh_0]
root       187  0.0  0.0      0     0 ?        S    Jul19   0:00 [scsi_eh_1]
root       189  0.0  0.0      0     0 ?        S    Jul19   0:00 [scsi_eh_2]
root       191  0.0  0.0      0     0 ?        S    Jul19   0:30
[kworker/u:1]
root       200  0.0  0.0      0     0 ?        S    Jul19   1:15
[kworker/7:2]
root       205  0.0  0.0      0     0 ?        S    Jul19   0:29
[kworker/4:2]
root       207  0.0  0.0      0     0 ?        S    Jul19   2:14
[kworker/3:2]
root       229  0.0  0.0      0     0 ?        S    Jul19  11:13
[jbd2/cciss!c0d0]
root       230  0.0  0.0      0     0 ?        S<   Jul19   0:00
[ext4-dio-unwrit]
root       370  0.0  0.0  21380  1376 ?        Ss   Jul19   0:00 udevd
--daemon
root       481  0.0  0.0  21376   908 ?        S    Jul19   0:00 udevd
--daemon
root       483  0.0  0.0  21376   908 ?        S    Jul19   0:00 udevd
--daemon
root       523  0.0  0.0      0     0 ?        S    Jul19   1:49
[kworker/0:2]
root       534  0.0  0.0      0     0 ?        S<   Jul19   0:00 [kpsmoused]
root       537  0.0  0.0      0     0 ?        S<   Jul19   0:00
[edac-poller]
root       544  0.0  0.0      0     0 ?        S<   Jul19   0:00 [ttm_swap]
root      1901  0.0  0.0      0     0 ?        S    Jul19   1:19
[kworker/5:2]
root      1978  0.1  0.0 257932  2168 ?        Sl   Jul19  78:58
/usr/sbin/rsyslogd -c5
root      2165  0.0  0.0   4116   652 ?        Ss   Jul19   0:00
/usr/sbin/acpid
root      2183  0.0  0.0  20412   704 ?        Ss   Jul19   2:30
/usr/sbin/irqbalance
root      2206  0.0  0.0  20408  1084 ?        Ss   Jul19   0:20
/usr/sbin/cron
root      2235  0.0  0.0  14860   152 ?        Ss   Jul19   0:00
/usr/sbin/in.tftpd --listen --user tftp --address 0.0.0.0:69 --secure
/srv/tftp
ntp       2263  0.0  0.0  39072  2392 ?        Ss   Jul19   2:01
/usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 105:107
root      2281  0.0  0.0      0     0 ?        S    Jul19  23:39
[flush-104:0]
root      2344  0.0  0.0  49932  1256 ?        Ss   Jul19   0:54
/usr/sbin/sshd
root      3210  0.0  0.0      0     0 ?        S    Aug30   0:12
[kworker/6:2]
root      3325  0.0  0.0  12364   324 ?        Ss   Jul19   0:00
/usr/sbin/collectdmon -P /var/run/collectdmon.pid -- -C
/etc/collectd/collectd.conf
root      3326  0.7  0.1 533100 28296 ?        SLl  Jul19 451:48 collectd
-C /etc/collectd/collectd.conf -f
101       4415  0.0  0.0  46804  1064 ?        Ss   Jul19   0:00
/usr/sbin/exim4 -bd -q30m
root      4610  0.0  0.0  16256   960 tty1     Ss+  Jul19   0:00
/sbin/getty 38400 tty1
root      4611  0.0  0.0  16256   960 tty2     Ss+  Jul19   0:00
/sbin/getty 38400 tty2
root      4612  0.0  0.0  16256   952 tty3     Ss+  Jul19   0:00
/sbin/getty 38400 tty3
root      4613  0.0  0.0  16256   956 tty4     Ss+  Jul19   0:00
/sbin/getty 38400 tty4
root      4614  0.0  0.0  16256   964 tty5     Ss+  Jul19   0:00
/sbin/getty 38400 tty5
root      4615  0.0  0.0  16256   960 tty6     Ss+  Jul19   0:00
/sbin/getty 38400 tty6
root      4616  0.0  0.0  14576   876 ttyS1    Ss+  Jul19   0:00
/sbin/agetty 9600 ttyS1 vt100
root      8860  0.0  0.0  71292  3688 ?        Ss   02:22   0:00 sshd:
root at pts/2
root      8920  0.0  0.0  20652  3548 pts/2    Ss   02:22   0:00 -bash
root     11355  0.0  0.0  10784  1508 pts/2    S+   02:28   0:00 /bin/bash
/usr/sbin/ngcp-upgrade
root     11388  0.0  0.0  16052   844 pts/2    S+   02:28   0:00 script
-fqc '/usr/sbin/ngcp-upgrade' '--inside-log' /tmp/upgrade.log
root     11389  0.0  0.0  16056   528 pts/2    S+   02:28   0:00 script
-fqc '/usr/sbin/ngcp-upgrade' '--inside-log' /tmp/upgrade.log
root     11390  0.0  0.0  10780  1528 pts/3    Ss+  02:28   0:00 /bin/bash
/usr/sbin/ngcp-upgrade --inside-log
root     11394  0.0  0.0  39460  8832 pts/3    S+   02:28   0:00 python -m
SimpleHTTPServer 4242
root     11408  0.0  0.0  10776  1512 pts/3    S+   02:28   0:00 /bin/bash
/usr/share/ngcp-upgrade-mr3.4.1/upgrade-mr3.3.1-to-mr3.4.1
root     11807  0.0  0.0   4180   712 pts/3    S+   02:28   0:00 /bin/sh
/usr/bin/mysqld_safe
root     12302  0.0  0.0      0     0 ?        S    Aug26   0:30
[kworker/6:0]
mysql    12742  2.1  6.6 9527732 1099144 pts/3 Sl+  02:28   0:13
/usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql
--plugin-dir=/usr/lib/mysql/plugin --user=mysql
--log-error=/var/log/mysql/mysqld.err --pid-f
root     13384  0.0  0.1  58476 25800 pts/3    S+   02:29   0:00 apt-get -y
--force-yes -o DPkg::Options::=--force-confnew dist-upgrade
root     15334  0.0  0.0  12252  3900 pts/0    Ss+  02:31   0:00
/usr/bin/dpkg --force-confnew --status-fd 16 --configure
mysql-client-5.5:amd64 mysql-server-core-5.5:amd64 mysql-server-5.5:amd64
root     15381  0.0  0.0  58488 12852 pts/0    S+   02:31   0:00
/usr/bin/perl -w /usr/share/debconf/frontend
/var/lib/dpkg/info/mysql-server-5.5.postinst configure 5.5.37-0+wheezy1
root     15387  0.0  0.0   9364  1540 pts/0    S+   02:31   0:00 /bin/bash
/var/lib/dpkg/info/mysql-server-5.5.postinst configure 5.5.37-0+wheezy1
root     16673  0.0  0.0  71292  3692 ?        Ss   02:35   0:00 sshd:
root at pts/4
root     16725  0.0  0.0  20636  3544 pts/4    Ss   02:36   0:00 -bash
mysql    17483  4.3  4.0 9386576 661012 pts/0  Sl+  02:38   0:00
/usr/sbin/mysqld --bootstrap --user=mysql --skip-grant-tables
root     17554  0.0  0.0   4096   324 ?        S    02:38   0:00 sleep 10
root     17572  0.0  0.0   4096   324 ?        S    02:38   0:00 sleep 10
root     17588  0.0  0.0  16836  1288 pts/4    R+   02:38   0:00 ps -aux
root     18616  0.0  0.0  39424  5080 ?        Sl   Jul20  31:46 captagent
-d




On Sun, Aug 31, 2014 at 3:29 AM, Michael Prokop <mprokop at sipwise.com> wrote:

> * Abel Alejandro [Sun Aug 31, 2014 at 03:05:11AM -0400]:
>
> > Upgrading from mr3.3.1 to mr3.4.1 I got a few of those errors and it
> seems
> > the upgrade tried to stop a few demons but got stuck when it couldnt stop
> > mysql.
>
> > Just stopped the mysql daemon manually and the upgraded continued fine.
>
> > Everything seems to be working after upgrade just wanted to report in
> case.
>
> Did your upgrade actually really interrupt/abort? If so do you have
> any error logs available for us?
>
> The 'invoke-rc.d: policy-rc.d denied execution of stop' are only
> warnings and no error messages, that setup is by intention and
> should be working just fine.
>
> regards,
> -mika-
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAlQCztsACgkQ2N9T+zficuhBHACfexNoI4e9u2puc+kbmSe4Y3x/
> aO8AnjmXnkmde5TZFqibgULZ1kpiUDlN
> =UbCF
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>


-- 
*Abel Alejandro*

787 586 8313 | 787 705 0555
<joquendo at alliedtechnologygrouppr.com>

400 Calle Calaf 477
San Juan, PR 00918
aalejandro at alliedtechnologygrouppr.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140831/48eccb5f/attachment.html>

From jbonilla at sipwise.com  Sun Aug 31 04:24:26 2014
From: jbonilla at sipwise.com (Jon Bonilla (Manwe))
Date: Sun, 31 Aug 2014 10:24:26 +0200
Subject: [Spce-user] invoke-rc.d: policy-rc.d denied execution of stop.
In-Reply-To: <CAKiNg23G0-S2V4PCzgK2pSOHD0i+iU0+M3pEkyJRV0=zTNZg2w@mail.gmail.com>
References: <CAKiNg21vn2UqtTBvjpEW9jxTt41UYL-rcAzUeOS-Va085q=yrg@mail.gmail.com>
 <2014-08-31T09-27-06@devnull.michael-prokop.at>
 <CAKiNg23G0-S2V4PCzgK2pSOHD0i+iU0+M3pEkyJRV0=zTNZg2w@mail.gmail.com>
Message-ID: <20140831102426.0736cb0a@quenya>

El Sun, 31 Aug 2014 03:38:37 -0400
Abel Alejandro <aalejandro at alliedtechnologygrouppr.com> escribi?:

> While the upgrade got stuck I ran this:
> 
> root at sip:/var/log# tail /tmp/upgrade.log
> Unpacking replacement mysql-client-5.5 ...
> Preparing to replace mysql-server-core-5.5 5.5.37-0+wheezy1 (using
> .../mysql-server-core-5.5_5.5.38-0+wheezy1_amd64.deb) ...
> Unpacking replacement mysql-server-core-5.5 ...
> Preparing to replace ngcp-installer-ce 0.14.1.3+0~mr3.3.1.3 (using
> .../ngcp-installer-ce_0.15.1.2+0~mr3.4.1.2_all.deb) ...
> Unpacking replacement ngcp-installer-ce ...
> Processing triggers for man-db ...
> Setting up mysql-client-5.5 (5.5.38-0+wheezy1) ...
> Setting up mysql-server-core-5.5 (5.5.38-0+wheezy1) ...
> Setting up mysql-server-5.5 (5.5.38-0+wheezy1) ...
> invoke-rc.d: policy-rc.d denied execution of stop.
> root at sip:/var/log#
>

I recently experienced the problem during the upgrade and had to kill mysql
processes to allow the upgrade process to continue.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140831/574746e4/attachment.asc>

From marek.cervenka at fpf.slu.cz  Fri Aug 29 06:56:19 2014
From: marek.cervenka at fpf.slu.cz (=?UTF-8?B?TWFyZWsgxIxlcnZlbmth?=)
Date: Fri, 29 Aug 2014 10:56:19 -0000
Subject: [Spce-user] spce ip aliases
Message-ID: <54005A50.3040206@fpf.slu.cz>

hi,

is it possible use spce with multiple aliased ips?

like
eth0 192.168.100.1
eth0:1 192.168.100.20
eth0:2 192.168.100.30

and register endpoints to i.e. 192.168.100.30 and answer from spce will 
have src ip 192.168.100.30
thanks

-- 
---------------------------------------
Marek Cervenka
=======================================



From noreply at sipwise.com  Fri Aug  1 04:08:06 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 01 Aug 2014 08:08:06 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1406880480.756988.585.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.7+0~mr3.3.2.7 to version 1.3.2.8+0~mr3.3.2.8
* ngcp-panel-tools was updated from version 1.3.2.7+0~mr3.3.2.7 to version 1.3.2.8+0~mr3.3.2.8

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug  1 04:37:58 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 01 Aug 2014 08:37:58 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1406882272.737715.7090.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.8+0~mr3.3.2.8 to version 1.3.2.9+0~mr3.3.2.9
* ngcp-panel-tools was updated from version 1.3.2.8+0~mr3.3.2.8 to version 1.3.2.9+0~mr3.3.2.9

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Sun Aug  3 20:38:55 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 04 Aug 2014 00:38:55 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1407112725.689451.13182.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-db-schema was updated from version 3.3.3.2+0~mr3.3.2.2 to version 3.3.3.3+0~mr3.3.2.3

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Sun Aug  3 20:41:29 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 04 Aug 2014 00:41:29 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1407112882.807813.16593.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-schema was updated from version 3.1.2.1+0~mr3.3.2.1 to version 3.1.2.2+0~mr3.3.2.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug  5 01:18:50 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 05 Aug 2014 05:18:50 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1407215924.972116.6498.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.9+0~mr3.3.2.9 to version 1.3.2.10+0~mr3.3.2.10
* ngcp-panel-tools was updated from version 1.3.2.9+0~mr3.3.2.9 to version 1.3.2.10+0~mr3.3.2.10

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Sat Aug  9 22:55:09 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Sun, 10 Aug 2014 02:55:09 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1407639304.052809.12176.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.10+0~mr3.3.2.10 to version 1.3.2.11+0~mr3.3.2.11
* ngcp-panel-tools was updated from version 1.3.2.10+0~mr3.3.2.10 to version 1.3.2.11+0~mr3.3.2.11

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug 12 10:48:21 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 12 Aug 2014 14:48:21 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1407854896.027288.13608.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.11+0~mr3.3.2.11 to version 1.3.2.12+0~mr3.3.2.12
* ngcp-panel-tools was updated from version 1.3.2.11+0~mr3.3.2.11 to version 1.3.2.12+0~mr3.3.2.12

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Wed Aug 13 18:05:16 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Wed, 13 Aug 2014 22:05:16 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1407967510.346840.19837.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.12+0~mr3.3.2.12 to version 1.3.2.13+0~mr3.3.2.13
* ngcp-panel-tools was updated from version 1.3.2.12+0~mr3.3.2.12 to version 1.3.2.13+0~mr3.3.2.13

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Aug 14 06:58:05 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 14 Aug 2014 10:58:05 -0000
Subject: [Spce-user] FYI: Package update(s) in release 2.8
Message-ID: <1408013880.010662.2242.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 2.8:

* ngcp-db-schema was updated from version 2.8.5 to version 2.8.6
* ngcp-handbook-ce was updated from version 2.8.6 to version 2.8.7
* ngcp-handbook-pro was updated from version 2.8.6 to version 2.8.7
* ngcp-libswrate-dev was updated from version 1.1.6 to version 1.1.7
* ngcp-libswrate0 was updated from version 1.1.6 to version 1.1.7

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Aug 14 07:34:43 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 14 Aug 2014 11:34:43 -0000
Subject: [Spce-user] FYI: Package update(s) in release 2.8
Message-ID: <1408016078.095405.9059.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 2.8:

* ngcp-db-schema was updated from version 2.8.6 to version 2.8.7

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Aug 14 09:32:58 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 14 Aug 2014 13:32:58 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408023172.740440.20421.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.13+0~mr3.3.2.13 to version 1.3.2.14+0~mr3.3.2.14
* ngcp-panel-tools was updated from version 1.3.2.13+0~mr3.3.2.13 to version 1.3.2.14+0~mr3.3.2.14

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Aug 14 12:21:45 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 14 Aug 2014 16:21:45 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408033300.747504.23259.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-db-schema was updated from version 3.3.3.3+0~mr3.3.2.3 to version 3.3.3.4+0~mr3.3.2.4

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Aug 14 13:15:00 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 14 Aug 2014 17:15:00 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408036493.194163.15496.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.14+0~mr3.3.2.14 to version 1.3.2.15+0~mr3.3.2.15
* ngcp-panel-tools was updated from version 1.3.2.14+0~mr3.3.2.14 to version 1.3.2.15+0~mr3.3.2.15

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Aug 14 17:18:49 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 14 Aug 2014 21:18:49 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408051124.097466.15979.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.15+0~mr3.3.2.15 to version 1.3.2.16+0~mr3.3.2.16
* ngcp-panel-tools was updated from version 1.3.2.15+0~mr3.3.2.15 to version 1.3.2.16+0~mr3.3.2.16

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Aug 18 13:57:55 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 18 Aug 2014 17:57:55 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408384669.586131.24700.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.16+0~mr3.3.2.16 to version 1.3.2.17+0~mr3.3.2.17
* ngcp-panel-tools was updated from version 1.3.2.16+0~mr3.3.2.16 to version 1.3.2.17+0~mr3.3.2.17

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug 19 11:58:43 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 19 Aug 2014 15:58:43 -0000
Subject: [Spce-user] FYI: Package update(s) in release 3.0
Message-ID: <1408463920.314711.30200.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 3.0:

* ngcp-libswrate-dev was updated from version 1.1.6 to version 1.1.7
* ngcp-libswrate0 was updated from version 1.1.6 to version 1.1.7

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug 19 12:16:00 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 19 Aug 2014 16:16:00 -0000
Subject: [Spce-user] FYI: Package update(s) in release 3.1
Message-ID: <1408464957.243005.32207.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 3.1:

* ngcp-libswrate-dev was updated from version 1.1.6 to version 1.1.7
* ngcp-libswrate0 was updated from version 1.1.6 to version 1.1.7
* ngcp-panel was updated from version 1.1.16 to version 1.1.17

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug 19 12:58:49 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 19 Aug 2014 16:58:49 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.2.1
Message-ID: <1408467523.789979.3789.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.2.1:

* ngcp-libswrate-dev was updated from version 1.1.6.1+0~mr3.2.1.1 to version 1.1.7.1+0~mr3.2.1.2
* ngcp-libswrate0 was updated from version 1.1.6.1+0~mr3.2.1.1 to version 1.1.7.1+0~mr3.2.1.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Wed Aug 20 05:48:43 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Wed, 20 Aug 2014 09:48:43 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408528117.364976.9228.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.17+0~mr3.3.2.17 to version 1.3.2.18+0~mr3.3.2.18
* ngcp-panel-tools was updated from version 1.3.2.17+0~mr3.3.2.17 to version 1.3.2.18+0~mr3.3.2.18

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 06:51:22 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 10:51:22 -0000
Subject: [Spce-user] FYI: Package update(s) in release 2.8
Message-ID: <1408704676.701742.26194.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 2.8:

* ngcp-backup-tools was updated from version 0.1.1 to version 0.1.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 06:56:43 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 10:56:43 -0000
Subject: [Spce-user] FYI: Package update(s) in release 3.0
Message-ID: <1408704998.315949.27128.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 3.0:

* ngcp-backup-tools was updated from version 0.2.0 to version 0.2.1

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 06:58:10 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 10:58:10 -0000
Subject: [Spce-user] FYI: Package update(s) in release 3.1
Message-ID: <1408705085.177531.27383.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 3.1:

* ngcp-backup-tools was updated from version 0.2.0 to version 0.2.1

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 07:15:53 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 11:15:53 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.2.1
Message-ID: <1408706148.493018.3202.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.2.1:

* ngcp-backup-tools was updated from version 0.2.0.1+0~mr3.2.1.1 to version 0.2.0.2+0~mr3.2.1.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 07:16:43 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 11:16:43 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.2.2
Message-ID: <1408706198.076724.3302.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.2.2:

* ngcp-backup-tools was updated from version 0.2.1.1+0~mr3.2.2.1 to version 0.2.1.2+0~mr3.2.2.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 07:19:43 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 11:19:43 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.1
Message-ID: <1408706378.501945.3644.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.1:

* ngcp-backup-tools was updated from version 0.3.1.2+0~mr3.3.1.2 to version 0.3.1.3+0~mr3.3.1.3

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 07:22:41 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 11:22:41 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408706556.214057.7583.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-backup-tools was updated from version 0.3.2.1+0~mr3.3.2.1 to version 0.3.2.2+0~mr3.3.2.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug 26 06:53:14 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 26 Aug 2014 10:53:14 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.2.1
Message-ID: <1409050387.571493.12561.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.2.1:

* ngcp-backup-tools was updated from version 0.2.0.2+0~mr3.2.1.2 to version 0.2.1.3+0~mr3.2.1.3

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug 26 06:54:00 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 26 Aug 2014 10:54:00 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.2.2
Message-ID: <1409050435.587701.12736.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.2.2:

* ngcp-backup-tools was updated from version 0.2.1.2+0~mr3.2.2.2 to version 0.2.2.3+0~mr3.2.2.3

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From ms at pluteus.at  Fri Aug  1 03:39:18 2014
From: ms at pluteus.at (Martin Stix)
Date: Fri, 1 Aug 2014 07:39:18 +0000
Subject: [Spce-user] Right way to move existing CE install to a fresh
 new install
In-Reply-To: <53DA241C.2050602@sipwise.com>
References: <60b3724110ea4e4b8bd646b7387789ed@post.familie.local>
 <53DA1930.70207@sipwise.com>
 <0885a4afd51343ae9e837a27b64f54be@post.familie.local>
 <53DA241C.2050602@sipwise.com>
Message-ID: <7f88d426a39e4f03b44323e2c36279c8@post.familie.local>

Hi!

Thanks, renaming the host did the trick.

Works fine now.


mit freundlichen Gr??en
best regards
Martin Stix
CEO
pluteus communication solutions
ms at pluteus.at
www.pluteus.at
Dampfs?gestra?e 17
3300 Amstetten
Austria
tel.: +43 7472 28165 20
fax.: +43 7472 28165 22

-----Urspr?ngliche Nachricht-----
Von: Alex Lutay [mailto:alutay at sipwise.com] 
Gesendet: Donnerstag, 31. Juli 2014 13:10
An: spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Right way to move existing CE install to a fresh new install

Hi,

0070 is very old statement and you should have it already.
Probably you have installed the server using new hostname, while the information about the host and executed statements are stored in MySQL (please check column "node" for tables "ngcp.cfg_schema" and "ngcp.db_schema").

I would suggest you to use the same hostname or update the tables ngcp.cfg_schema and ngcp.db_schema with new/proper value and repeat ngcp-update-{db|cfg}-schema.

On 31/07/14 12:53, Martin Stix wrote:
> Yes I forgot, it states:
> Applying revision script 
> /usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: 
> ERROR 1050 (42S01) at line 2: Table 'acc_backup' already exists

--
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user


From liglesia at por-aire.es  Fri Aug  1 07:50:50 2014
From: liglesia at por-aire.es (Leopoldo Iglesia)
Date: Fri, 01 Aug 2014 13:50:50 +0200
Subject: [Spce-user] Call hangs at about 15 seconds
Message-ID: <53DB7F1A.9030900@por-aire.es>

If i call, from a suscriber to a foreign number,  via peering, or to 
other suscriber it hangs at about 15 secs.

I send a wireshark capture and proxy log.


Aug  1 13:13:37 sipwise proxy[4400]: NOTICE: <script>: Authentication 
failed, no credentials - R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: New request - 
M=INVITE R=sip:606105877 at 154.58.3.135 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=154.58.3.158:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-Provided CLI 
'x1009' taken from From-User as fallback, should be from 'rpid_user' - 
R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-provided CLI 
'x1009' rejected, using network-provided CLI '34984099519' - 
R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
'34984099519 at 154.58.3.135' as initiating user-provided CLI - 
R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
'34984099519 at 154.58.3.135' as initiating network-provided CLI - 
R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting called 
party '606105877' to '34606105877' - R=sip:606105877 at 154.58.3.135 
ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Callee is not 
local - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Call to SIP 
Peering - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Load gws matching 
calling part 'sip:34984099519 at 154.58.3.135' and called user 
'34606105877' and called part 'sip:34606105877 at 154.58.3.135' - 
R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc 
source-leg for uuid 'c2731ab4-e7f5-4440-a821-d95c5d94eeac': 
'c2731ab4-e7f5-4440-a821-d95c5d94eeac|x1009|154.58.3.135|34984099519|||2|||0|call|154.58.3.158|1406891617.480275' 
- R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc 
destination-leg for uuid '0': 
'0|||0|606105877|0|34606105877|212.231.4.206|34606105877|154.58.3.135' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: ERROR: rtpengine 
[rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
Failed to parse SDP
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting first 
user-provided CLI '34984099519' to '984099519' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting first 
network-provided CLI '34984099519' to '984099519' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for 
npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for 
npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting From to 
'984099519 <sip:984099519 at 154.58.3.135>' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for 
npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting PAI to 
'<sip:984099519 at 154.58.3.135>' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
P-Called-Party-ID '<sip:34606105877 at 212.231.4.206>' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
'sip:212.231.4.206:5060' taken from R-URI as next hop after lb for PSTN 
call - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Appending P-D-URI 
'sip:127.0.0.1:5060;received='sip:212.231.4.206:5060;lr;transport=udp'' 
- R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Forcing request 
via B2BUA 'sip:127.0.0.1:5080' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Request leaving 
server, D-URI='sip:127.0.0.1:5080' - 
R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
Aug  1 13:13:37 sipwise proxy[4404]: NOTICE: <script>: NAT-Reply - S=100 
- Connecting M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) 
ID=16888 at 154.58.3.158
Aug  1 13:13:38 sipwise proxy[4408]: NOTICE: <script>: NAT-Reply - S=183 
- Session Progress M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) 
ID=16888 at 154.58.3.158
Aug  1 13:13:38 sipwise proxy[4408]: ERROR: rtpengine 
[rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
Unknown call-id
Aug  1 13:13:48 sipwise proxy[4400]: NOTICE: <script>: NAT-Reply - S=200 
- OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) ID=16888 at 154.58.3.158
Aug  1 13:13:48 sipwise proxy[4400]: ERROR: rtpengine 
[rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
Unknown call-id
Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
Aug  1 13:13:48 sipwise proxy[4412]: ERROR: db_mysql [km_dbase.c:122]: 
db_mysql_submit_query(): driver error on query: Duplicate entry 
'uloc-53db7100-112e-1' for key 'ruid_idx'
Aug  1 13:13:48 sipwise proxy[4412]: ERROR: <core> [db_query.c:235]: 
db_do_insert_cmd(): error while submitting query
Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [ucontact.c:627]: 
db_insert_ucontact(): inserting contact in db failed
Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [urecord.c:386]: 
wb_timer(): inserting contact into database failed (aor: 
x984099517 at 154.58.3.135)
Aug  1 13:13:48 sipwise proxy[4402]: NOTICE: <script>: NAT-Reply - S=200 
- OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) ID=16888 at 154.58.3.158
Aug  1 13:13:48 sipwise proxy[4402]: ERROR: rtpengine 
[rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
Unknown call-id
Aug  1 13:13:48 sipwise proxy[4404]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:13:49 sipwise proxy[4404]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: New request - 
M=REGISTER R=sip:154.58.3.135 F=sip:x1010 at 154.58.3.135 
T=sip:x1010 at 154.58.3.135 IP=154.58.3.149:5060 (127.0.0.1:5060) 
ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: Authentication 
failed, no credentials - R=sip:154.58.3.135 
ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
Aug  1 13:13:49 sipwise proxy[4410]: NOTICE: <script>: NAT-Reply - S=200 
- OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) ID=16888 at 154.58.3.158
Aug  1 13:13:49 sipwise proxy[4410]: ERROR: rtpengine 
[rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
Unknown call-id
Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
Aug  1 13:14:03 sipwise proxy[4406]: NOTICE: <script>: New request - 
M=BYE R=sip:x1009 at 154.58.3.158:5060 F=sip:606105877 at 154.58.3.135 
T=sip:984099519 at 154.58.3.135 IP=127.0.0.1:5080 (127.0.0.1:5080) 
ID=16888 at 154.58.3.158
Aug  1 13:14:03 sipwise proxy[4398]: NOTICE: <script>: NAT-Reply - S=200 
- OK M=BYE IP=127.0.0.1:5080 (127.0.0.1:5060) ID=16888 at 154.58.3.158
Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: New request - 
M=ACK R=sip:127.0.0.1:5080 F=sip:984099519 at 154.58.3.135 
T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
ID=16888 at 154.58.3.158
Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: Dropping 
mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
root at sipwise:/var/log/ngcp# tail -n 1000 kamailio-proxy.log

-------------- next part --------------
A non-text attachment was scrubbed...
Name: telefoniae5.cap
Type: application/octet-stream
Size: 635978 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140801/45ae5595/attachment-0001.cap>

From mstorck at voipgate.com  Fri Aug  1 07:20:38 2014
From: mstorck at voipgate.com (Marc Storck)
Date: Fri, 1 Aug 2014 11:20:38 +0000
Subject: [Spce-user] Web Password requirements
Message-ID: <EF586431-A929-4490-9A8E-673D51C3D6D5@voipgate.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Good afternoon,

it seems that the customer can change his web password to an all numeric password. However this makes it impossible for an admin to change any of the settings in Master Data, because the NGCP complains that the web password ?must contain lower-case characters?.

Also, although it say characterS (plural), 1 single lower-case character (singular) is actually required. :-D

Best regards,

Marc
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJT23h3AAoJEBqZdpQUXtTC99MP/28HJBg7HBJCxzqZ1yCHHC0D
tPze0SJo8h4fW4W9hCCAQoUsboeQdDcTFynI6Xac1si/pqCjzT5E71ZTTGf2njDI
FvEm/uN3598FN6Uat6KKJDILBhJfq+Ilm8qbfJERiUmpv5v7RHtCqSJmCkbcZclS
UkUk2BqjOnfe2L07Q0zVMoViVOV/RxZ07yNyawIDIVnNtqm81aG+ScYsn5gtakY4
nSLPFf7xTY8Mi9V+hksogIHDQKgHtQnvorpWisMT5QMZ6v020Aqx0lt3lBtjTULw
yNsXiQ/y/C+QsZxHd5GpbLae+r53fhhJDdDLyOq3QNrdtz4xDdTy9zHP1eXMFDIP
JZ8BiSQGg47Etm0bWOIVS6YAx6fFXPSt65QiSMj/rZd6V5OGayRXmA4lXfrWJeQF
6BnSNRcxlI1f/p0SGsPPIYcSiV8T6lrJyXrvzPdyy6Kwld29TWMWZ8r3WEHDg/eH
0rUn4jDg2f6oX3JNwN25dAWW03KdvcEjt3dr0psPofL6I6TvX0/600Do6156IdVS
msZK2jyEShp4HCYrsYBDPkmrMdQByo80ucFtHV0l2KJwZXhNiclVC0qEOOht1GVH
NmU9HMNxx2fOJTJW2vCbLCb1usA/VPnK5AoMUx3m1nBtlGeKG2TR++BUGCTcorGn
vxRJZpUDzRJXpRctF4iG
=GCXg
-----END PGP SIGNATURE-----

From dgrotti at sipwise.com  Fri Aug  1 08:13:04 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 14:13:04 +0200
Subject: [Spce-user] Web Password requirements
In-Reply-To: <EF586431-A929-4490-9A8E-673D51C3D6D5@voipgate.com>
References: <EF586431-A929-4490-9A8E-673D51C3D6D5@voipgate.com>
Message-ID: <53DB8450.5000708@sipwise.com>

Thanks Marc,
which version are you using ?

Daniel



On 08/01/2014 01:20 PM, Marc Storck wrote:
> Good afternoon,
>
> it seems that the customer can change his web password to an all
> numeric password. However this makes it impossible for an admin to
> change any of the settings in Master Data, because the NGCP complains
> that the web password ?must contain lower-case characters?.
>
> Also, although it say characterS (plural), 1 single lower-case
> character (singular) is actually required. :-D
>
> Best regards,
>
> Marc
> _______________________________________________
> 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/20140801/6ef2b72d/attachment-0001.html>

From dgrotti at sipwise.com  Fri Aug  1 08:18:15 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 14:18:15 +0200
Subject: [Spce-user] Call hangs at about 15 seconds
In-Reply-To: <53DB7F1A.9030900@por-aire.es>
References: <53DB7F1A.9030900@por-aire.es>
Message-ID: <53DB8587.3060407@sipwise.com>

Hi,
there is no such call (ID=16888 at 154.58.3.158) in the trace attached.

Also you have a lot of ERROR:

ERROR: rtpengine [rtpengine.c:1491]: rtpp_function_call(): proxy replied
with error: Failed to parse SDP

But the reason why the call is drop is because the ACK is wrong and it
is not delivered:

NOTICE: <script>: New request - M=ACK R=sip:127.0.0.1:5080
F=sip:x1009 at 154.58.3.135 T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060
(127.0.0.1:5060) ID=16888 at 154.58.3.158
NOTICE: <script>: Dropping mis-routed request - R=sip:127.0.0.1:5080
ID=16888 at 154.58.3.158


Can't check the ACK inside cause there is no trace for that callid
16888 at 154.58.3.158.


Daniel



On 08/01/2014 01:50 PM, Leopoldo Iglesia wrote:
> If i call, from a suscriber to a foreign number,  via peering, or to
> other suscriber it hangs at about 15 secs.
>
> I send a wireshark capture and proxy log.
>
>
> Aug  1 13:13:37 sipwise proxy[4400]: NOTICE: <script>: Authentication
> failed, no credentials - R=sip:606105877 at 154.58.3.135
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: New request -
> M=INVITE R=sip:606105877 at 154.58.3.135 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=154.58.3.158:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-Provided
> CLI 'x1009' taken from From-User as fallback, should be from
> 'rpid_user' - R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-provided
> CLI 'x1009' rejected, using network-provided CLI '34984099519' -
> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> '34984099519 at 154.58.3.135' as initiating user-provided CLI -
> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> '34984099519 at 154.58.3.135' as initiating network-provided CLI -
> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting
> called party '606105877' to '34606105877' -
> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Callee is not
> local - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Call to SIP
> Peering - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Load gws
> matching calling part 'sip:34984099519 at 154.58.3.135' and called user
> '34606105877' and called part 'sip:34606105877 at 154.58.3.135' -
> R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc
> source-leg for uuid 'c2731ab4-e7f5-4440-a821-d95c5d94eeac':
> 'c2731ab4-e7f5-4440-a821-d95c5d94eeac|x1009|154.58.3.135|34984099519|||2|||0|call|154.58.3.158|1406891617.480275'
> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc
> destination-leg for uuid '0':
> '0|||0|606105877|0|34606105877|212.231.4.206|34606105877|154.58.3.135'
> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: ERROR: rtpengine
> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
> Failed to parse SDP
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting first
> user-provided CLI '34984099519' to '984099519' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting first
> network-provided CLI '34984099519' to '984099519' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for
> npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for
> npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting From to
> '984099519 <sip:984099519 at 154.58.3.135>' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for
> npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting PAI to
> '<sip:984099519 at 154.58.3.135>' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> P-Called-Party-ID '<sip:34606105877 at 212.231.4.206>' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
> 'sip:212.231.4.206:5060' taken from R-URI as next hop after lb for
> PSTN call - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
> ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Appending
> P-D-URI
> 'sip:127.0.0.1:5060;received='sip:212.231.4.206:5060;lr;transport=udp'' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Forcing request
> via B2BUA 'sip:127.0.0.1:5080' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Request leaving
> server, D-URI='sip:127.0.0.1:5080' -
> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
> Aug  1 13:13:37 sipwise proxy[4404]: NOTICE: <script>: NAT-Reply -
> S=100 - Connecting M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:38 sipwise proxy[4408]: NOTICE: <script>: NAT-Reply -
> S=183 - Session Progress M=INVITE IP=154.58.3.158:5060
> (127.0.0.1:5080) ID=16888 at 154.58.3.158
> Aug  1 13:13:38 sipwise proxy[4408]: ERROR: rtpengine
> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
> Unknown call-id
> Aug  1 13:13:48 sipwise proxy[4400]: NOTICE: <script>: NAT-Reply -
> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:48 sipwise proxy[4400]: ERROR: rtpengine
> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
> Unknown call-id
> Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Duplicate entry
> 'uloc-53db7100-112e-1' for key 'ruid_idx'
> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [ucontact.c:627]:
> db_insert_ucontact(): inserting contact in db failed
> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [urecord.c:386]:
> wb_timer(): inserting contact into database failed (aor:
> x984099517 at 154.58.3.135)
> Aug  1 13:13:48 sipwise proxy[4402]: NOTICE: <script>: NAT-Reply -
> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:48 sipwise proxy[4402]: ERROR: rtpengine
> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
> Unknown call-id
> Aug  1 13:13:48 sipwise proxy[4404]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:49 sipwise proxy[4404]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: New request -
> M=REGISTER R=sip:154.58.3.135 F=sip:x1010 at 154.58.3.135
> T=sip:x1010 at 154.58.3.135 IP=154.58.3.149:5060 (127.0.0.1:5060)
> ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
> Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: Authentication
> failed, no credentials - R=sip:154.58.3.135
> ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
> Aug  1 13:13:49 sipwise proxy[4410]: NOTICE: <script>: NAT-Reply -
> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:49 sipwise proxy[4410]: ERROR: rtpengine
> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
> Unknown call-id
> Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> Aug  1 13:14:03 sipwise proxy[4406]: NOTICE: <script>: New request -
> M=BYE R=sip:x1009 at 154.58.3.158:5060 F=sip:606105877 at 154.58.3.135
> T=sip:984099519 at 154.58.3.135 IP=127.0.0.1:5080 (127.0.0.1:5080)
> ID=16888 at 154.58.3.158
> Aug  1 13:14:03 sipwise proxy[4398]: NOTICE: <script>: NAT-Reply -
> S=200 - OK M=BYE IP=127.0.0.1:5080 (127.0.0.1:5060) ID=16888 at 154.58.3.158
> Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: New request -
> M=ACK R=sip:127.0.0.1:5080 F=sip:984099519 at 154.58.3.135
> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
> ID=16888 at 154.58.3.158
> Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
> root at sipwise:/var/log/ngcp# tail -n 1000 kamailio-proxy.log
>
>
>
> _______________________________________________
> 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/20140801/40946250/attachment-0001.html>

From mstorck at voipgate.com  Fri Aug  1 08:18:13 2014
From: mstorck at voipgate.com (Marc Storck)
Date: Fri, 1 Aug 2014 12:18:13 +0000
Subject: [Spce-user] Web Password requirements
In-Reply-To: <53DB8450.5000708@sipwise.com>
References: <EF586431-A929-4490-9A8E-673D51C3D6D5@voipgate.com>
 <53DB8450.5000708@sipwise.com>
Message-ID: <4F0D0E0B-B64C-482F-BADA-E5E79476E613@voipgate.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry forgot to mention:

cat /etc/ngcp_version 
mr3.3.1

Regards,

Marc

On Aug 1, 2014, at 2:13 PM, Daniel Grotti <dgrotti at sipwise.com> wrote:

Thanks Marc,
which version are you using ?

Daniel



On 08/01/2014 01:20 PM, Marc Storck wrote:
Good afternoon,

it seems that the customer can change his web password to an all numeric password. However this makes it impossible for an admin to change any of the settings in Master Data, because the NGCP complains that the web password ?must contain lower-case characters?.

Also, although it say characterS (plural), 1 single lower-case character (singular) is actually required. :-D

Best regards,

Marc
>
      _______________________________________________

      > 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

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJT24X3AAoJEBqZdpQUXtTCy5QP/048q1hiPLArDDu83JYPtvN9
hOQZTbUTOguKH0+9HO3K5L3A7pMVWVHlkcmxrM8wboKsQrAvRscL+jTfE1CPZG/d
qKYyZEoCsBKU6yImUoWlYzdn3vNyPcsaVIBcjndFBEJmy4fAOp1SRumaoMzn4NHu
N3Cx47DV77BzY7KHVze2kmugBpkdfOwZcq5HfA811IkRa369pq8gQ50R69xqDk9o
EHJRcuFVxPERxz2/3QAk7Xgkn09kXiW9GINDSG9yNuyye1UJbpjqGPWpug1BHU2V
ycWJCkfJbQVsqh9nLWZ1EayH8tfP4mLwdRdysmIw6VR/v5tdu1ZWnEPFkB9Oi2VV
9OW8wPG7v1H9wWdza0CLkhvJtMLNT+ZyaJce627L5Dlrd5usA0hAIDGSiFJXWN6E
JFq/NQSqv81afy+zu/HI02+cRfnFhki19xsRx6kjWdIGtRnruBjtMV78Yj3vi/Tj
ZJjquMOND5syUc41x9xQ3xEijcG5J4OBZSGyZgkK5ng/PyM8vUQuGIPRVlt8qGuU
UC5XYDTYiFHhgQEIpQSKMObi7wuNSHvbsXPF8jYj+MrCYUyCxwuz19uObn9cemP5
t35qpgRFf8S/Q12aodMJeAC1OlprvXnzIPZvEw0xmYLKrl3Hoi7CHt7+D1TT2ZUv
k465QCqQRK6Up3/nw9Zx
=t2EC
-----END PGP SIGNATURE-----

From dgrotti at sipwise.com  Fri Aug  1 08:25:08 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 14:25:08 +0200
Subject: [Spce-user] Web Password requirements
In-Reply-To: <4F0D0E0B-B64C-482F-BADA-E5E79476E613@voipgate.com>
References: <EF586431-A929-4490-9A8E-673D51C3D6D5@voipgate.com>
 <53DB8450.5000708@sipwise.com>
 <4F0D0E0B-B64C-482F-BADA-E5E79476E613@voipgate.com>
Message-ID: <53DB8724.1090000@sipwise.com>

Hi,
opened an internal ticket for this.

Daniel



On 08/01/2014 02:18 PM, Marc Storck wrote:
> it seems that the customer can change his web password to an all numeric password. However this makes it impossible for an admin to change any of the settings in Master Data, because the NGCP complains that the web password ?must contain lower-case characters?.
>
> Also, although it say characterS (plural), 1 single lower-case character (singular) is actually required.



From liglesia at por-aire.es  Fri Aug  1 08:27:46 2014
From: liglesia at por-aire.es (Leopoldo Iglesia)
Date: Fri, 01 Aug 2014 14:27:46 +0200
Subject: [Spce-user] Call hangs at about 15 seconds
In-Reply-To: <53DB8587.3060407@sipwise.com>
References: <53DB7F1A.9030900@por-aire.es> <53DB8587.3060407@sipwise.com>
Message-ID: <53DB87C2.6020105@por-aire.es>

Check this call in the pervious trace,   is the same call but 2 minutes 
before

6869 at 154.58.3.158

El 01/08/2014 14:18, Daniel Grotti escribi?:
> Hi,
> there is no such call (ID=16888 at 154.58.3.158) in the trace attached.
>
> Also you have a lot of ERROR:
>
> ERROR: rtpengine [rtpengine.c:1491]: rtpp_function_call(): proxy 
> replied with error: Failed to parse SDP
>
> But the reason why the call is drop is because the ACK is wrong and it 
> is not delivered:
>
> NOTICE: <script>: New request - M=ACK R=sip:127.0.0.1:5080 
> F=sip:x1009 at 154.58.3.135 T=sip:606105877 at 154.58.3.135 
> IP=127.0.0.1:5060 (127.0.0.1:5060) ID=16888 at 154.58.3.158
> NOTICE: <script>: Dropping mis-routed request - R=sip:127.0.0.1:5080 
> ID=16888 at 154.58.3.158
>
>
> Can't check the ACK inside cause there is no trace for that callid 
> 16888 at 154.58.3.158.
>
>
> Daniel
>
>
>
> On 08/01/2014 01:50 PM, Leopoldo Iglesia wrote:
>> If i call, from a suscriber to a foreign number,  via peering, or to 
>> other suscriber it hangs at about 15 secs.
>>
>> I send a wireshark capture and proxy log.
>>
>>
>> Aug  1 13:13:37 sipwise proxy[4400]: NOTICE: <script>: Authentication 
>> failed, no credentials - R=sip:606105877 at 154.58.3.135 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: New request - 
>> M=INVITE R=sip:606105877 at 154.58.3.135 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=154.58.3.158:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-Provided 
>> CLI 'x1009' taken from From-User as fallback, should be from 
>> 'rpid_user' - R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-provided 
>> CLI 'x1009' rejected, using network-provided CLI '34984099519' - 
>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> '34984099519 at 154.58.3.135' as initiating user-provided CLI - 
>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> '34984099519 at 154.58.3.135' as initiating network-provided CLI - 
>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting 
>> called party '606105877' to '34606105877' - 
>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Callee is not 
>> local - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Call to SIP 
>> Peering - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Load gws 
>> matching calling part 'sip:34984099519 at 154.58.3.135' and called user 
>> '34606105877' and called part 'sip:34606105877 at 154.58.3.135' - 
>> R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc 
>> source-leg for uuid 'c2731ab4-e7f5-4440-a821-d95c5d94eeac': 
>> 'c2731ab4-e7f5-4440-a821-d95c5d94eeac|x1009|154.58.3.135|34984099519|||2|||0|call|154.58.3.158|1406891617.480275' 
>> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc 
>> destination-leg for uuid '0': 
>> '0|||0|606105877|0|34606105877|212.231.4.206|34606105877|154.58.3.135' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: ERROR: rtpengine 
>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
>> Failed to parse SDP
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting 
>> first user-provided CLI '34984099519' to '984099519' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting 
>> first network-provided CLI '34984099519' to '984099519' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for 
>> npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for 
>> npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting From 
>> to '984099519 <sip:984099519 at 154.58.3.135>' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135' for 
>> npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting PAI to 
>> '<sip:984099519 at 154.58.3.135>' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> P-Called-Party-ID '<sip:34606105877 at 212.231.4.206>' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting 
>> 'sip:212.231.4.206:5060' taken from R-URI as next hop after lb for 
>> PSTN call - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Appending 
>> P-D-URI 
>> 'sip:127.0.0.1:5060;received='sip:212.231.4.206:5060;lr;transport=udp'' 
>> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Forcing 
>> request via B2BUA 'sip:127.0.0.1:5080' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Request 
>> leaving server, D-URI='sip:127.0.0.1:5080' - 
>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp ID=16888 at 154.58.3.158
>> Aug  1 13:13:37 sipwise proxy[4404]: NOTICE: <script>: NAT-Reply - 
>> S=100 - Connecting M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:38 sipwise proxy[4408]: NOTICE: <script>: NAT-Reply - 
>> S=183 - Session Progress M=INVITE IP=154.58.3.158:5060 
>> (127.0.0.1:5080) ID=16888 at 154.58.3.158
>> Aug  1 13:13:38 sipwise proxy[4408]: ERROR: rtpengine 
>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
>> Unknown call-id
>> Aug  1 13:13:48 sipwise proxy[4400]: NOTICE: <script>: NAT-Reply - 
>> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:48 sipwise proxy[4400]: ERROR: rtpengine 
>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
>> Unknown call-id
>> Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: db_mysql 
>> [km_dbase.c:122]: db_mysql_submit_query(): driver error on query: 
>> Duplicate entry 'uloc-53db7100-112e-1' for key 'ruid_idx'
>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: <core> [db_query.c:235]: 
>> db_do_insert_cmd(): error while submitting query
>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [ucontact.c:627]: 
>> db_insert_ucontact(): inserting contact in db failed
>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [urecord.c:386]: 
>> wb_timer(): inserting contact into database failed (aor: 
>> x984099517 at 154.58.3.135)
>> Aug  1 13:13:48 sipwise proxy[4402]: NOTICE: <script>: NAT-Reply - 
>> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:48 sipwise proxy[4402]: ERROR: rtpengine 
>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
>> Unknown call-id
>> Aug  1 13:13:48 sipwise proxy[4404]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:49 sipwise proxy[4404]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: New request - 
>> M=REGISTER R=sip:154.58.3.135 F=sip:x1010 at 154.58.3.135 
>> T=sip:x1010 at 154.58.3.135 IP=154.58.3.149:5060 (127.0.0.1:5060) 
>> ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
>> Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: Authentication 
>> failed, no credentials - R=sip:154.58.3.135 
>> ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
>> Aug  1 13:13:49 sipwise proxy[4410]: NOTICE: <script>: NAT-Reply - 
>> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:49 sipwise proxy[4410]: ERROR: rtpengine 
>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error: 
>> Unknown call-id
>> Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> Aug  1 13:14:03 sipwise proxy[4406]: NOTICE: <script>: New request - 
>> M=BYE R=sip:x1009 at 154.58.3.158:5060 F=sip:606105877 at 154.58.3.135 
>> T=sip:984099519 at 154.58.3.135 IP=127.0.0.1:5080 (127.0.0.1:5080) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:14:03 sipwise proxy[4398]: NOTICE: <script>: NAT-Reply - 
>> S=200 - OK M=BYE IP=127.0.0.1:5080 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: New request - 
>> M=ACK R=sip:127.0.0.1:5080 F=sip:984099519 at 154.58.3.135 
>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060) 
>> ID=16888 at 154.58.3.158
>> Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: Dropping 
>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>> root at sipwise:/var/log/ngcp# tail -n 1000 kamailio-proxy.log
>>
>>
>>
>> _______________________________________________
>> 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/20140801/15b36893/attachment-0001.html>

From dgrotti at sipwise.com  Fri Aug  1 08:52:09 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 14:52:09 +0200
Subject: [Spce-user] Call hangs at about 15 seconds
In-Reply-To: <53DB87C2.6020105@por-aire.es>
References: <53DB7F1A.9030900@por-aire.es> <53DB8587.3060407@sipwise.com>
 <53DB87C2.6020105@por-aire.es>
Message-ID: <53DB8D79.2000508@sipwise.com>

Hi,
looks like in the ACK the port 5062 is missing from one of the Route header.
Do you have all the trace ? I mean also messages inside spce
(lb,proxy,sems).

Daniel




On 08/01/2014 02:27 PM, Leopoldo Iglesia wrote:
> Check this call in the pervious trace,   is the same call but 2
> minutes before
>
> 6869 at 154.58.3.158
>
> El 01/08/2014 14:18, Daniel Grotti escribi?:
>> Hi,
>> there is no such call (ID=16888 at 154.58.3.158) in the trace attached.
>>
>> Also you have a lot of ERROR:
>>
>> ERROR: rtpengine [rtpengine.c:1491]: rtpp_function_call(): proxy
>> replied with error: Failed to parse SDP
>>
>> But the reason why the call is drop is because the ACK is wrong and
>> it is not delivered:
>>
>> NOTICE: <script>: New request - M=ACK R=sip:127.0.0.1:5080
>> F=sip:x1009 at 154.58.3.135 T=sip:606105877 at 154.58.3.135
>> IP=127.0.0.1:5060 (127.0.0.1:5060) ID=16888 at 154.58.3.158
>> NOTICE: <script>: Dropping mis-routed request - R=sip:127.0.0.1:5080
>> ID=16888 at 154.58.3.158
>>
>>
>> Can't check the ACK inside cause there is no trace for that callid
>> 16888 at 154.58.3.158.
>>
>>
>> Daniel
>>
>>
>>
>> On 08/01/2014 01:50 PM, Leopoldo Iglesia wrote:
>>> If i call, from a suscriber to a foreign number,  via peering, or to
>>> other suscriber it hangs at about 15 secs.
>>>
>>> I send a wireshark capture and proxy log.
>>>
>>>
>>> Aug  1 13:13:37 sipwise proxy[4400]: NOTICE: <script>:
>>> Authentication failed, no credentials - R=sip:606105877 at 154.58.3.135
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: New request -
>>> M=INVITE R=sip:606105877 at 154.58.3.135 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=154.58.3.158:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-Provided
>>> CLI 'x1009' taken from From-User as fallback, should be from
>>> 'rpid_user' - R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: User-provided
>>> CLI 'x1009' rejected, using network-provided CLI '34984099519' -
>>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> '34984099519 at 154.58.3.135' as initiating user-provided CLI -
>>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> '34984099519 at 154.58.3.135' as initiating network-provided CLI -
>>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting
>>> called party '606105877' to '34606105877' -
>>> R=sip:606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Callee is not
>>> local - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Call to SIP
>>> Peering - R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Load gws
>>> matching calling part 'sip:34984099519 at 154.58.3.135' and called user
>>> '34606105877' and called part 'sip:34606105877 at 154.58.3.135' -
>>> R=sip:34606105877 at 154.58.3.135 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc
>>> source-leg for uuid 'c2731ab4-e7f5-4440-a821-d95c5d94eeac':
>>> 'c2731ab4-e7f5-4440-a821-d95c5d94eeac|x1009|154.58.3.135|34984099519|||2|||0|call|154.58.3.158|1406891617.480275'
>>> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting acc
>>> destination-leg for uuid '0':
>>> '0|||0|606105877|0|34606105877|212.231.4.206|34606105877|154.58.3.135'
>>> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: ERROR: rtpengine
>>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
>>> Failed to parse SDP
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting
>>> first user-provided CLI '34984099519' to '984099519' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Rewriting
>>> first network-provided CLI '34984099519' to '984099519' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135'
>>> for npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135'
>>> for npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting From
>>> to '984099519 <sip:984099519 at 154.58.3.135>' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> caller_cli_netprov/caller_domain_netprov '984099519 at 154.58.3.135'
>>> for npn - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting PAI
>>> to '<sip:984099519 at 154.58.3.135>' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> P-Called-Party-ID '<sip:34606105877 at 212.231.4.206>' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Setting
>>> 'sip:212.231.4.206:5060' taken from R-URI as next hop after lb for
>>> PSTN call - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Appending
>>> P-D-URI
>>> 'sip:127.0.0.1:5060;received='sip:212.231.4.206:5060;lr;transport=udp''
>>> - R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Forcing
>>> request via B2BUA 'sip:127.0.0.1:5080' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4402]: NOTICE: <script>: Request
>>> leaving server, D-URI='sip:127.0.0.1:5080' -
>>> R=sip:34606105877 at 212.231.4.206:5060;transport=udp
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:37 sipwise proxy[4404]: NOTICE: <script>: NAT-Reply -
>>> S=100 - Connecting M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:38 sipwise proxy[4408]: NOTICE: <script>: NAT-Reply -
>>> S=183 - Session Progress M=INVITE IP=154.58.3.158:5060
>>> (127.0.0.1:5080) ID=16888 at 154.58.3.158
>>> Aug  1 13:13:38 sipwise proxy[4408]: ERROR: rtpengine
>>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
>>> Unknown call-id
>>> Aug  1 13:13:48 sipwise proxy[4400]: NOTICE: <script>: NAT-Reply -
>>> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:48 sipwise proxy[4400]: ERROR: rtpengine
>>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
>>> Unknown call-id
>>> Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:48 sipwise proxy[4398]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: db_mysql
>>> [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>>> Duplicate entry 'uloc-53db7100-112e-1' for key 'ruid_idx'
>>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: <core> [db_query.c:235]:
>>> db_do_insert_cmd(): error while submitting query
>>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [ucontact.c:627]:
>>> db_insert_ucontact(): inserting contact in db failed
>>> Aug  1 13:13:48 sipwise proxy[4412]: ERROR: usrloc [urecord.c:386]:
>>> wb_timer(): inserting contact into database failed (aor:
>>> x984099517 at 154.58.3.135)
>>> Aug  1 13:13:48 sipwise proxy[4402]: NOTICE: <script>: NAT-Reply -
>>> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:48 sipwise proxy[4402]: ERROR: rtpengine
>>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
>>> Unknown call-id
>>> Aug  1 13:13:48 sipwise proxy[4404]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:49 sipwise proxy[4404]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>: New request -
>>> M=REGISTER R=sip:154.58.3.135 F=sip:x1010 at 154.58.3.135
>>> T=sip:x1010 at 154.58.3.135 IP=154.58.3.149:5060 (127.0.0.1:5060)
>>> ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
>>> Aug  1 13:13:49 sipwise proxy[4408]: NOTICE: <script>:
>>> Authentication failed, no credentials - R=sip:154.58.3.135
>>> ID=cx0.Aa34erSB8FN6X7KRy.pHLfN3V9Y-
>>> Aug  1 13:13:49 sipwise proxy[4410]: NOTICE: <script>: NAT-Reply -
>>> S=200 - OK M=INVITE IP=154.58.3.158:5060 (127.0.0.1:5080)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:49 sipwise proxy[4410]: ERROR: rtpengine
>>> [rtpengine.c:1491]: rtpp_function_call(): proxy replied with error:
>>> Unknown call-id
>>> Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:50 sipwise proxy[4397]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:53 sipwise proxy[4400]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:13:57 sipwise proxy[4404]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:x1009 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:14:01 sipwise proxy[4410]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> Aug  1 13:14:03 sipwise proxy[4406]: NOTICE: <script>: New request -
>>> M=BYE R=sip:x1009 at 154.58.3.158:5060 F=sip:606105877 at 154.58.3.135
>>> T=sip:984099519 at 154.58.3.135 IP=127.0.0.1:5080 (127.0.0.1:5080)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:14:03 sipwise proxy[4398]: NOTICE: <script>: NAT-Reply -
>>> S=200 - OK M=BYE IP=127.0.0.1:5080 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: New request -
>>> M=ACK R=sip:127.0.0.1:5080 F=sip:984099519 at 154.58.3.135
>>> T=sip:606105877 at 154.58.3.135 IP=127.0.0.1:5060 (127.0.0.1:5060)
>>> ID=16888 at 154.58.3.158
>>> Aug  1 13:14:05 sipwise proxy[4402]: NOTICE: <script>: Dropping
>>> mis-routed request - R=sip:127.0.0.1:5080 ID=16888 at 154.58.3.158
>>> root at sipwise:/var/log/ngcp# tail -n 1000 kamailio-proxy.log
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20140801/18a418e8/attachment-0001.html>

From sipwise.support at mtkom.de  Fri Aug  1 09:41:14 2014
From: sipwise.support at mtkom.de (Pascal Schwarz)
Date: Fri, 1 Aug 2014 15:41:14 +0200 (CEST)
Subject: [Spce-user] security bans / 403 Errror
Message-ID: <alpine.DEB.2.10.1408011514080.32451@gucky>

Hy All,

i have setup a sip_provider_CE_mr3.3.2_virtualbox.ova .
i have configured 616 Subscribers.
All 616 Subscribers are automatic configured from me so the username and 
password of client and Server 100% the same and works.
All 616 Subscribers ar FritzBox from AVM mostly 7360 7270 and 7390 .

every h i can check the security bans and see that there are  Subscribers.
I now that at FritzBox and and the spce the same password and username so 
i don't understand why so mutch Subscribers will bee there .

i i delete them from security bans the fritbox works fine but without any
changes some of this Subscribers will bee back some houre later to ban.

At the logile of the AVM FritzBOx7270 i see there are often problems:

  date:
  29.07.14      27 x 403 error
  30.07.14     164 x 403 error
  01.08.14      35 x 403 error

bevor i use sip_provider_CE_mr3.3.2_virtualbox.ova i use asterisks there
i have no problems with the FritzBod autorisation.
Thas not only one fritzbox . I see this Problem at alle FritzBox .

Any One any Idee what i can do to fix this problem ?

regards
Pascal Schwarz




From dgrotti at sipwise.com  Fri Aug  1 10:05:40 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 16:05:40 +0200
Subject: [Spce-user] security bans / 403 Errror
In-Reply-To: <alpine.DEB.2.10.1408011514080.32451@gucky>
References: <alpine.DEB.2.10.1408011514080.32451@gucky>
Message-ID: <53DB9EB4.2090803@sipwise.com>

Hi,
please grep your kamailio-lb.log file with:

grep "Consecutive Authentication Failure" kamailio-lb.log

And check why you get some users banned.

An option is to increase the number of attempt from 3 to 6 for ex.

Daniel




On 08/01/2014 03:41 PM, Pascal Schwarz wrote:
> Hy All,
>
> i have setup a sip_provider_CE_mr3.3.2_virtualbox.ova .
> i have configured 616 Subscribers.
> All 616 Subscribers are automatic configured from me so the username
> and password of client and Server 100% the same and works.
> All 616 Subscribers ar FritzBox from AVM mostly 7360 7270 and 7390 .
>
> every h i can check the security bans and see that there are 
> Subscribers.
> I now that at FritzBox and and the spce the same password and username
> so i don't understand why so mutch Subscribers will bee there .
>
> i i delete them from security bans the fritbox works fine but without any
> changes some of this Subscribers will bee back some houre later to ban.
>
> At the logile of the AVM FritzBOx7270 i see there are often problems:
>
>  date:
>  29.07.14      27 x 403 error
>  30.07.14     164 x 403 error
>  01.08.14      35 x 403 error
>
> bevor i use sip_provider_CE_mr3.3.2_virtualbox.ova i use asterisks there
> i have no problems with the FritzBod autorisation.
> Thas not only one fritzbox . I see this Problem at alle FritzBox .
>
> Any One any Idee what i can do to fix this problem ?
>
> regards
> Pascal Schwarz
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user



From paul.belanger at polybeacon.com  Fri Aug  1 10:22:56 2014
From: paul.belanger at polybeacon.com (Paul Belanger)
Date: Fri, 1 Aug 2014 10:22:56 -0400
Subject: [Spce-user] fresh install debian 7 not web access
Message-ID: <CALLKq0SFYGHf5eCna7UpeDPaq=+=dw6Y2txmKUGs9MDmNcuu5A@mail.gmail.com>

I've just done a fresh install on debian 7 using the follow
directions[1] but for some reason it doesn't appear the web interface
is working correctly.  Any attempt to access the system results in no
web pages being loaded.

Is it possible the system did not properly configure itself?

[1] https://www.sipwise.com/doc/mr3.3.2/spce/ar01s04.html#_installing_the_sip_provider_ce

-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger


From dgrotti at sipwise.com  Fri Aug  1 10:33:50 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 16:33:50 +0200
Subject: [Spce-user] fresh install debian 7 not web access
Message-ID: <20140801143415.B61A81502088@zimbra.sipwise.com>

Are you accessing port 1443?
Is that port listening on your system?

Daniel

On 1 Aug 2014 16:22, Paul Belanger <paul.belanger at polybeacon.com> wrote:
>
> I've just done a fresh install on debian 7 using the follow 
> directions[1] but for some reason it doesn't appear the web interface 
> is working correctly.? Any attempt to access the system results in no 
> web pages being loaded. 
>
> Is it possible the system did not properly configure itself? 
>
> [1] https://www.sipwise.com/doc/mr3.3.2/spce/ar01s04.html#_installing_the_sip_provider_ce 
>
> -- 
> Paul Belanger | PolyBeacon, Inc. 
> Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode) 
> Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger 
> _______________________________________________ 
> Spce-user mailing list 
> Spce-user at lists.sipwise.com 
> https://lists.sipwise.com/listinfo/spce-user 

From gsims94 at gmail.com  Fri Aug  1 10:39:37 2014
From: gsims94 at gmail.com (Gordon Sims)
Date: Fri, 01 Aug 2014 09:39:37 -0500
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <CALLKq0SFYGHf5eCna7UpeDPaq=+=dw6Y2txmKUGs9MDmNcuu5A@mail.gmail.com>
Message-ID: <D00110A2.1D695%gsims94@gmail.com>

I had the same thing happen on fresh install.  Check to make sure iptables
are not enabled and then do a reboot.  Usually after the reboot,
everything works just fine.

Gordon

On 8/1/14, 9:22 AM, "Paul Belanger" <paul.belanger at polybeacon.com> wrote:

>I've just done a fresh install on debian 7 using the follow
>directions[1] but for some reason it doesn't appear the web interface
>is working correctly.  Any attempt to access the system results in no
>web pages being loaded.
>
>Is it possible the system did not properly configure itself?
>
>[1] 
>https://www.sipwise.com/doc/mr3.3.2/spce/ar01s04.html#_installing_the_sip_
>provider_ce
>
>-- 
>Paul Belanger | PolyBeacon, Inc.
>Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
>Github: https://github.com/pabelanger | Twitter:
>https://twitter.com/pabelanger
>_______________________________________________
>Spce-user mailing list
>Spce-user at lists.sipwise.com
>https://lists.sipwise.com/listinfo/spce-user




From j.fresneda at ibersontel.com  Fri Aug  1 10:39:17 2014
From: j.fresneda at ibersontel.com (Jorge Fresneda - Ibersontel)
Date: Fri, 01 Aug 2014 16:39:17 +0200
Subject: [Spce-user] Session-timers
In-Reply-To: <53DA2B75.2000703@sipwise.com>
References: <53D90E1B.6090701@ibersontel.com> <53DA20A5.20109@ibersontel.com>
 <53DA2B75.2000703@sipwise.com>
Message-ID: <53DBA695.7000607@ibersontel.com>

Hi,

One question, When I change the sst_enable to "yes", is need execute 
"ngcpcfg apply"?????

Thanks so much
Regards,
Jorge



El 31/07/2014 13:41, Daniel Grotti escribi?:
> Hi,
> you can enable/disable session-timers on peer/subscribers preferences.
>
> Daniel
>
>
>
> On 07/31/2014 12:55 PM, Jorge Fresneda - Ibersontel wrote:
>> Hello,
>>
>>
>> I have a problem with session-timers. A carrier send me a
>> "session-expire=1800;refresher=uac" header at 30 minutes and he say me
>> that I have enable the session-timer option. How I can do? I would like
>> to that session-option are enable on end-point and not in sipwise.
>>
>> Thank you so much,
>> Regards
>> Jorge
>>
>>
>> _______________________________________________
>> 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



From sipwise.support at mtkom.de  Fri Aug  1 10:54:30 2014
From: sipwise.support at mtkom.de (Pascal Schwarz)
Date: Fri, 1 Aug 2014 16:54:30 +0200 (CEST)
Subject: [Spce-user] security bans / 403 Errror
In-Reply-To: <53DB9EB4.2090803@sipwise.com>
References: <alpine.DEB.2.10.1408011514080.32451@gucky>
 <53DB9EB4.2090803@sipwise.com>
Message-ID: <alpine.DEB.2.10.1408011647570.32451@gucky>

Hallo Daniel,

> grep "Consecutive Authentication Failure" kamailio-lb.log

root at viax00:/var/log/ngcp# grep "Consecutive Authentication Failure" 
kamailio-lb.log | wc -l
1249
root at viax00:/var/log/ngcp#

thats only entry from 01.08.2014
it all the same ia change the username to XXXXXXXXXXX

Jul 31 23:59:51 viax00 lb[6845]: WARNING: <script>: Consecutive 
Authentication Failure for 'XXXXXXXXXXX at voice.mtkom.de' UA='AVM FRITZ!Box 
7272 120.06.03 TAL (Feb  7 2014)' IP='82.206.74.185' -  R=<null> 
ID=AAEF7C33E85B415F at 82.206.74.185

Aug  1 00:00:33 viax00 lb[6845]: WARNING: <script>: Consecutive 
Authentication Failure for 'XXXXXXXXXXX at voice.mtkom.de' UA='AVM FRITZ!Box 
Fon WLAN 7390 84.06.04 TAL (Feb 10 2014)' IP='82.206.74.227' -  R=<null> 
ID=BBCBCEA04C88306F at 82.206.74.227

Aug  1 00:16:35 viax00 lb[6845]: WARNING: <script>: Consecutive 
Authentication Failure for 'XXXXXXXXXX at voice.mtkom.de' UA='Grandstream 
GXP2000 1.2.4.3' IP='217.140.73.162' -  R=<null> 
ID=16ad51adde8014d2 at 192.168.253.106

Aug  1 00:24:22 viax00 lb[6845]: WARNING: <script>: Consecutive 
Authentication Failure for 'XXXXXXXXXXX at voice.mtkom.de' 
UA='Linksys/SPA2102-3.3.6' IP='93.194.37.194' -  R=<null> 
ID=81840f46-eea3fc72 at 93.194.37.194

you see this problem is with other Hardware too.
we block the config-change at AVM so nobody can change username
and password and that user that here will be ban works afte delet ban 
entry some times fine .

> An option is to increase the number of attempt from 3 to 6 for ex.
but the user ask why more times every day he see 403 at the logile
auf his AVM . So thats must fix.


regards
pascal



From dgrotti at sipwise.com  Fri Aug  1 10:57:03 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 01 Aug 2014 16:57:03 +0200
Subject: [Spce-user] Session-timers
Message-ID: <20140801145727.3EE911502088@zimbra.sipwise.com>

You can change it from web interface.
No apply is needed.

On 1 Aug 2014 16:39, Jorge Fresneda - Ibersontel <j.fresneda at ibersontel.com> wrote:
>
> Hi, 
>
> One question, When I change the sst_enable to "yes", is need execute 
> "ngcpcfg apply"????? 
>
> Thanks so much 
> Regards, 
> Jorge 
>
>
>
> El 31/07/2014 13:41, Daniel Grotti escribi?: 
> > Hi, 
> > you can enable/disable session-timers on peer/subscribers preferences. 
> > 
> > Daniel 
> > 
> > 
> > 
> > On 07/31/2014 12:55 PM, Jorge Fresneda - Ibersontel wrote: 
> >> Hello, 
> >> 
> >> 
> >> I have a problem with session-timers. A carrier send me a 
> >> "session-expire=1800;refresher=uac" header at 30 minutes and he say me 
> >> that I have enable the session-timer option. How I can do? I would like 
> >> to that session-option are enable on end-point and not in sipwise. 
> >> 
> >> Thank you so much, 
> >> Regards 
> >> Jorge 
> >> 
> >> 
> >> _______________________________________________ 
> >> 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 

From j.fresneda at ibersontel.com  Fri Aug  1 11:04:38 2014
From: j.fresneda at ibersontel.com (Jorge Fresneda - Ibersontel)
Date: Fri, 01 Aug 2014 17:04:38 +0200
Subject: [Spce-user] Session-timers
In-Reply-To: <20140801145727.3EE911502088@zimbra.sipwise.com>
References: <20140801145727.3EE911502088@zimbra.sipwise.com>
Message-ID: <53DBAC86.6070304@ibersontel.com>

Hi,

He cambiado el sst_enable, pero cuando reciben un INVITE del portador 
con "session-expire = 1,800; refresca = uac", la respuesta sipwise con 
200 OK. Me gustar?a que la respuesta sipwise con "session-expira = 7200".

Thanks
Regards


El 01/08/2014 16:57, Daniel Grotti escribi?:
> You can change it from web interface.
> No apply is needed.
>
> On 1 Aug 2014 16:39, Jorge Fresneda - Ibersontel <j.fresneda at ibersontel.com> wrote:
>> Hi,
>>
>> One question, When I change the sst_enable to "yes", is need execute
>> "ngcpcfg apply"?????
>>
>> Thanks so much
>> Regards,
>> Jorge
>>
>>
>>
>> El 31/07/2014 13:41, Daniel Grotti escribi?:
>>> Hi,
>>> you can enable/disable session-timers on peer/subscribers preferences.
>>>
>>> Daniel
>>>
>>>
>>>
>>> On 07/31/2014 12:55 PM, Jorge Fresneda - Ibersontel wrote:
>>>> Hello,
>>>>
>>>>
>>>> I have a problem with session-timers. A carrier send me a
>>>> "session-expire=1800;refresher=uac" header at 30 minutes and he say me
>>>> that I have enable the session-timer option. How I can do? I would like
>>>> to that session-option are enable on end-point and not in sipwise.
>>>>
>>>> Thank you so much,
>>>> Regards
>>>> Jorge
>>>>
>>>>
>>>> _______________________________________________
>>>> 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



From j.fresneda at ibersontel.com  Fri Aug  1 11:08:14 2014
From: j.fresneda at ibersontel.com (Jorge Fresneda - Ibersontel)
Date: Fri, 01 Aug 2014 17:08:14 +0200
Subject: [Spce-user] Session-timers
In-Reply-To: <20140801145727.3EE911502088@zimbra.sipwise.com>
References: <20140801145727.3EE911502088@zimbra.sipwise.com>
Message-ID: <53DBAD5E.6090901@ibersontel.com>

Oh, I'm sorry:

I'm changed the sst_enable, but when receive a INVITE from carrier with 
"session-expire=1800;refreshes=uac", the answer of sipwise is 200 ok. I 
would like that answer of sipwise with "session-expire=7200"

Thanks,
Regards


El 01/08/2014 16:57, Daniel Grotti escribi?:
> You can change it from web interface.
> No apply is needed.
>
> On 1 Aug 2014 16:39, Jorge Fresneda - Ibersontel <j.fresneda at ibersontel.com> wrote:
>> Hi,
>>
>> One question, When I change the sst_enable to "yes", is need execute
>> "ngcpcfg apply"?????
>>
>> Thanks so much
>> Regards,
>> Jorge
>>
>>
>>
>> El 31/07/2014 13:41, Daniel Grotti escribi?:
>>> Hi,
>>> you can enable/disable session-timers on peer/subscribers preferences.
>>>
>>> Daniel
>>>
>>>
>>>
>>> On 07/31/2014 12:55 PM, Jorge Fresneda - Ibersontel wrote:
>>>> Hello,
>>>>
>>>>
>>>> I have a problem with session-timers. A carrier send me a
>>>> "session-expire=1800;refresher=uac" header at 30 minutes and he say me
>>>> that I have enable the session-timer option. How I can do? I would like
>>>> to that session-option are enable on end-point and not in sipwise.
>>>>
>>>> Thank you so much,
>>>> Regards
>>>> Jorge
>>>>
>>>>
>>>> _______________________________________________
>>>> 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



From alutay at sipwise.com  Fri Aug  1 11:26:43 2014
From: alutay at sipwise.com (Alex Lutay)
Date: Fri, 01 Aug 2014 17:26:43 +0200
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <D00110A2.1D695%gsims94@gmail.com>
References: <D00110A2.1D695%gsims94@gmail.com>
Message-ID: <53DBB1B3.2000305@sipwise.com>

Dear Gordon!

First of all thank you for the bug report.

It is known CE problem, at the moment you have to reboot the server 
after fresh installation or start nginx manually.
You can use MT#6369 for further references to bugreport.

It happens because we install both Apache and Nginx WEB servers
(we are on a way of migration to Nginx). Both are default debian 
packages and install default configs, which are fighting for default 
ports... Apache won in your case while we need nginx.

At the end of installation "ngcpcfg apply" generate correct/new apache 
and nginx configs and remove port conflicts, but it tries to start 
ngingx before stopping apache:

> Restarting nginx: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
> nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
> ...
> nginx: [emerg] still could not bind()
> nginx.
> Restarting web server: apache2
> ...

I hope this information helped you understand the issue.
It will be automatically disappear as soon as we remove Apache,
also we are planning to add "Reboot (Y/N)?" hint for users,
but currently occupied with important new features ;-)

JFYI, Also we almost released mr3.4.1 with new CE install CD (which 
reboot the server after the installation):
> https://www.sipwise.com/doc/mr3.4.1/spce/ar01s04.html#_using_the_ngcp_install_cd_recommended
but it is a secret for now, don't tell anybody! :-)

Thank you for your bugreport one more time!

On 01/08/14 16:39, Gordon Sims wrote:
> I had the same thing happen on fresh install.  Check to make sure iptables
> are not enabled and then do a reboot.  Usually after the reboot,
> everything works just fine.

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From paul.belanger at polybeacon.com  Fri Aug  1 11:34:34 2014
From: paul.belanger at polybeacon.com (Paul Belanger)
Date: Fri, 1 Aug 2014 11:34:34 -0400
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <53DBB1B3.2000305@sipwise.com>
References: <D00110A2.1D695%gsims94@gmail.com> <53DBB1B3.2000305@sipwise.com>
Message-ID: <CALLKq0QSAORFnrXfk84GvPC7qMBvNPoo+3kktLmyAp8AgJhC2A@mail.gmail.com>

On Fri, Aug 1, 2014 at 11:26 AM, Alex Lutay <alutay at sipwise.com> wrote:
> Dear Gordon!
>
> First of all thank you for the bug report.
>
> It is known CE problem, at the moment you have to reboot the server after
> fresh installation or start nginx manually.
> You can use MT#6369 for further references to bugreport.
>
> It happens because we install both Apache and Nginx WEB servers
> (we are on a way of migration to Nginx). Both are default debian packages
> and install default configs, which are fighting for default ports... Apache
> won in your case while we need nginx.
>
> At the end of installation "ngcpcfg apply" generate correct/new apache and
> nginx configs and remove port conflicts, but it tries to start ngingx before
> stopping apache:
>
>> Restarting nginx: nginx: [emerg] bind() to [::]:80 failed (98: Address
>> already in use)
>> nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
>> ...
>> nginx: [emerg] still could not bind()
>> nginx.
>> Restarting web server: apache2
>> ...
>
>
> I hope this information helped you understand the issue.
> It will be automatically disappear as soon as we remove Apache,
> also we are planning to add "Reboot (Y/N)?" hint for users,
> but currently occupied with important new features ;-)
>
> JFYI, Also we almost released mr3.4.1 with new CE install CD (which reboot
> the server after the installation):
>>
>>
>> https://www.sipwise.com/doc/mr3.4.1/spce/ar01s04.html#_using_the_ngcp_install_cd_recommended
>
> but it is a secret for now, don't tell anybody! :-)
>
> Thank you for your bugreport one more time!
>
Okay, rebooting has gotten me a step closer. Aside from loosing ssh
access, I now get '502 Bad Gateway' from the web interface.  Looking
at the ngcp-panel error logs, I see the following:

2014/08/01 15:29:01 [error] 4046#0: *131 connect() to
unix:/var/run/fastcgi/ngcp-panel.sock failed (111: Connection refused)
while connecting to upstream, client: ::ffff:209.87.224.9, server: ,
request: "GET /login/admin HTTP/1.1", upstream:
"fastcgi://unix:/var/run/fastcgi/ngcp-panel.sock:", host:
"104.130.128.104:1443"

-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger


From gsims94 at gmail.com  Fri Aug  1 11:46:06 2014
From: gsims94 at gmail.com (Gordon Sims)
Date: Fri, 01 Aug 2014 10:46:06 -0500
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <14670942.9974.1406908190405.JavaMail.root@NXSSFUDF1.Nexepe.com>
Message-ID: <D0011E5D.1D6C3%GSims@Nexepe.com>

Is this server directly connected to the Internet? If not, check to make
sure that port 1443 is open on your firewall. As for SSH, you should be
able to check the status of sshd and make sure it is running with a
service sshd status .

-Gordon

On 8/1/14, 10:34 AM, "Paul Belanger" <paul.belanger at polybeacon.com> wrote:

>On Fri, Aug 1, 2014 at 11:26 AM, Alex Lutay <alutay at sipwise.com> wrote:
>> Dear Gordon!
>>
>> First of all thank you for the bug report.
>>
>> It is known CE problem, at the moment you have to reboot the server
>>after
>> fresh installation or start nginx manually.
>> You can use MT#6369 for further references to bugreport.
>>
>> It happens because we install both Apache and Nginx WEB servers
>> (we are on a way of migration to Nginx). Both are default debian
>>packages
>> and install default configs, which are fighting for default ports...
>>Apache
>> won in your case while we need nginx.
>>
>> At the end of installation "ngcpcfg apply" generate correct/new apache
>>and
>> nginx configs and remove port conflicts, but it tries to start ngingx
>>before
>> stopping apache:
>>
>>> Restarting nginx: nginx: [emerg] bind() to [::]:80 failed (98: Address
>>> already in use)
>>> nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
>>> ...
>>> nginx: [emerg] still could not bind()
>>> nginx.
>>> Restarting web server: apache2
>>> ...
>>
>>
>> I hope this information helped you understand the issue.
>> It will be automatically disappear as soon as we remove Apache,
>> also we are planning to add "Reboot (Y/N)?" hint for users,
>> but currently occupied with important new features ;-)
>>
>> JFYI, Also we almost released mr3.4.1 with new CE install CD (which
>>reboot
>> the server after the installation):
>>>
>>>
>>> 
>>>https://www.sipwise.com/doc/mr3.4.1/spce/ar01s04.html#_using_the_ngcp_in
>>>stall_cd_recommended
>>
>> but it is a secret for now, don't tell anybody! :-)
>>
>> Thank you for your bugreport one more time!
>>
>Okay, rebooting has gotten me a step closer. Aside from loosing ssh
>access, I now get '502 Bad Gateway' from the web interface.  Looking
>at the ngcp-panel error logs, I see the following:
>
>2014/08/01 15:29:01 [error] 4046#0: *131 connect() to
>unix:/var/run/fastcgi/ngcp-panel.sock failed (111: Connection refused)
>while connecting to upstream, client: ::ffff:209.87.224.9, server: ,
>request: "GET /login/admin HTTP/1.1", upstream:
>"fastcgi://unix:/var/run/fastcgi/ngcp-panel.sock:", host:
>"104.130.128.104:1443"
>
>-- 
>Paul Belanger | PolyBeacon, Inc.
>Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
>Github: https://github.com/pabelanger | Twitter:
>https://twitter.com/pabelanger
>_______________________________________________
>Spce-user mailing list
>Spce-user at lists.sipwise.com
>https://lists.sipwise.com/listinfo/spce-user
>
>
>-------------------------------------------------------------
>This email was processed through Nexepe Spam filter to filter junk
>messages.
>If you feel this message has been tagged incorrectly, you can
>change its category by clicking the link below.
>Click here 
>http://10.0.9.41:5272/FrontController?operation=mbeu&f=00001_-2300_2014080
>1_70980.eml&chkBayesian=1&pr=1&mt=1&ma=s to mark email as junk.
>-------------------------------------------------------------




From paul.belanger at polybeacon.com  Fri Aug  1 11:50:50 2014
From: paul.belanger at polybeacon.com (Paul Belanger)
Date: Fri, 1 Aug 2014 11:50:50 -0400
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <D0011E5D.1D6C3%GSims@Nexepe.com>
References: <14670942.9974.1406908190405.JavaMail.root@NXSSFUDF1.Nexepe.com>
 <D0011E5D.1D6C3%GSims@Nexepe.com>
Message-ID: <CALLKq0QQgqWdapCXALBOmCmPwthQkso5ShC6F3F6TZu+PZg82g@mail.gmail.com>

On Fri, Aug 1, 2014 at 11:46 AM, Gordon Sims <gsims94 at gmail.com> wrote:
> Is this server directly connected to the Internet? If not, check to make
> sure that port 1443 is open on your firewall. As for SSH, you should be
> able to check the status of sshd and make sure it is running with a
> service sshd status .
>
Yes, public web (rackspace instance for testing). No firewall is
running. This looks to be a provision error by looking at the logging
however, I don't have the knowledge yet to debug it.  This is also my
4 times re-provisioning the system so I suspect there is a bug in the
installer.

-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger


From gsims94 at gmail.com  Fri Aug  1 11:54:22 2014
From: gsims94 at gmail.com (Gordon Sims)
Date: Fri, 01 Aug 2014 10:54:22 -0500
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <CALLKq0QQgqWdapCXALBOmCmPwthQkso5ShC6F3F6TZu+PZg82g@mail.gmail.com>
Message-ID: <D00121B6.1D6E1%gsims94@gmail.com>

Did you do the net-installer and minimal install?  I?ve had issues before
using the standard install.  The only way that I got it to work was to not
install anything additional, including ssh.  The SPCE installer will
install all the appropriate packages and set it up the proper way.  Just
reboot after complete is all.

-Gordon

On 8/1/14, 10:50 AM, "Paul Belanger" <paul.belanger at polybeacon.com> wrote:

>On Fri, Aug 1, 2014 at 11:46 AM, Gordon Sims <gsims94 at gmail.com> wrote:
>> Is this server directly connected to the Internet? If not, check to make
>> sure that port 1443 is open on your firewall. As for SSH, you should be
>> able to check the status of sshd and make sure it is running with a
>> service sshd status .
>>
>Yes, public web (rackspace instance for testing). No firewall is
>running. This looks to be a provision error by looking at the logging
>however, I don't have the knowledge yet to debug it.  This is also my
>4 times re-provisioning the system so I suspect there is a bug in the
>installer.
>
>-- 
>Paul Belanger | PolyBeacon, Inc.
>Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
>Github: https://github.com/pabelanger | Twitter:
>https://twitter.com/pabelanger




From agranig at sipwise.com  Fri Aug  1 12:02:04 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Fri, 01 Aug 2014 18:02:04 +0200
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <CALLKq0QQgqWdapCXALBOmCmPwthQkso5ShC6F3F6TZu+PZg82g@mail.gmail.com>
References: <14670942.9974.1406908190405.JavaMail.root@NXSSFUDF1.Nexepe.com>
 <D0011E5D.1D6C3%GSims@Nexepe.com>
 <CALLKq0QQgqWdapCXALBOmCmPwthQkso5ShC6F3F6TZu+PZg82g@mail.gmail.com>
Message-ID: <53DBB9FC.8010108@sipwise.com>

Hi,

On 08/01/2014 05:50 PM, Paul Belanger wrote:
> Yes, public web (rackspace instance for testing). No firewall is
> running. This looks to be a provision error by looking at the logging
> however, I don't have the knowledge yet to debug it.  This is also my
> 4 times re-provisioning the system so I suspect there is a bug in the
> installer.

How much memory does your machine have? You'd need at least 2GB, more is
better.

What's the output when executing "/etc/init.d/ngcp-panel restart"
manually, and is there anything in /var/log/ngcp/oss.log?

Andreas


From alutay at sipwise.com  Fri Aug  1 12:28:33 2014
From: alutay at sipwise.com (Alex Lutay)
Date: Fri, 01 Aug 2014 18:28:33 +0200
Subject: [Spce-user] fresh install debian 7 not web access
In-Reply-To: <CALLKq0QSAORFnrXfk84GvPC7qMBvNPoo+3kktLmyAp8AgJhC2A@mail.gmail.com>
References: <D00110A2.1D695%gsims94@gmail.com>	<53DBB1B3.2000305@sipwise.com>
 <CALLKq0QSAORFnrXfk84GvPC7qMBvNPoo+3kktLmyAp8AgJhC2A@mail.gmail.com>
Message-ID: <53DBC031.7010807@sipwise.com>

Dear Paul,

NGCP has a configuration file /etc/ngcp-config/network.yml which
contains IPs/service/roles attached to server/service.

For mr3.3 we improved security configuration, allowing to listen SSH
on specified interfaces only. Please find type ssh_ext into network.yml

So, we might have some issues there, lets try to debug.
Please check the list of IPs sshd currently listening:
 > netstat -anp | grep sshd

Does sshd listen IP(s) you are trying to reach?

If NO: please check that all interfaces in network.yml has type ssh_ext.
Update network.yml if necessary and run "ngcpcfg apply" to apply config
changes. Recheck the ssh connection.

If YES: it is local networking issue.

If you have no luck, please share:
1) netstat -anp | grep sshd
2) cat /etc/ngcp-config/network.yml
3) grep ListenAddress /etc/ssh/sshd_config

Tnx!

On 01/08/14 17:34, Paul Belanger wrote:
> Okay, rebooting has gotten me a step closer. Aside from loosing ssh
> access, I now get '502 Bad Gateway' from the web interface.  Looking
> at the ngcp-panel error logs, I see the following:

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From gary at netdiverse.com  Fri Aug  1 16:55:28 2014
From: gary at netdiverse.com (Gary Nieboer)
Date: Fri, 1 Aug 2014 14:55:28 -0600
Subject: [Spce-user] Peering Rules database vs. GUI Issue
Message-ID: <CAMXUi2ScE2u1tnGKSsbZUms+64yYTwAb-LsiKCfHJFAs1k7bsg@mail.gmail.com>

We have experienced a few issues with our "Peering Rules" on SPCE, 3.3.1.

A created rule exists in the GUI, but when routing a call through the SBC,
the call follows a route to a default peer rather than the peer indicated
in the GUI.

We recently did a comparison of what is shown in the database:  lcr_rules

                            select * from lcr_rule;


Here are a few lines from the database:   Some numbers are replaced with
"`" and not fully shown:

Note:  Rule 102 is missing from the database


| id  | lcr_id | prefix | request_uri | from_uri | stopper | enabled |
group_id |
+-----+--------+--------+-------------+----------+---------+---------+----------+
| 101 |      1 |        | ~~~~~20088  | NULL     |       0 |       1 |
  23 |
| 105 |      1 |        | ~~~~~20186  | NULL     |       0 |       1 |
  23 |
| 106 |      1 |        | ~~~~~74891  | NULL     |       0 |       1 |
  23 |



Now, here is a screenshot of the GUI for the same rules:
Note:  Rule 102 exists under peer group 23 for the GUI.
[image: Inline image 1]



It appears we should trust the data in the database and not the GUI, but
I'm assuming it is not desired behavior for the GUI and database to reflect
different info.

If you would like more information, we can share it.

Please let me know if there is anything we can do to ensure the GUI
reflects the actual activity of the database and ngcp/kamailio.

Thanks,

Gary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140801/6d896dc7/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 30444 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140801/6d896dc7/attachment-0001.png>

From sipwise.support at mtkom.de  Sat Aug  2 04:01:54 2014
From: sipwise.support at mtkom.de (Pascal Schwarz)
Date: Sat, 2 Aug 2014 10:01:54 +0200 (CEST)
Subject: [Spce-user] security bans / 403 Errror
In-Reply-To: <53DB9EB4.2090803@sipwise.com>
References: <alpine.DEB.2.10.1408011514080.32451@gucky>
 <53DB9EB4.2090803@sipwise.com>
Message-ID: <alpine.DEB.2.10.1408020959340.14896@jumpy>

Hello Daniel,

> An option is to increase the number of attempt from 3 to 6 for ex.
where can i change it ?

regards
Pascal



From dgrotti at sipwise.com  Sat Aug  2 04:06:05 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Sat, 02 Aug 2014 10:06:05 +0200
Subject: [Spce-user] security bans / 403 Errror
Message-ID: <20140802080631.1BC121502093@zimbra.sipwise.com>

Hi,
You can find ban configuration in the config.yml file.
After that run ngcpcfg apply.

Daniel

On 2 Aug 2014 10:01, Pascal Schwarz <sipwise.support at mtkom.de> wrote:
>
> Hello Daniel, 
>
> > An option is to increase the number of attempt from 3 to 6 for ex. 
> where can i change it ? 
>
> regards 
> Pascal 
>

From sipwise.support at mtkom.de  Sat Aug  2 04:16:32 2014
From: sipwise.support at mtkom.de (Pascal Schwarz)
Date: Sat, 2 Aug 2014 10:16:32 +0200 (CEST)
Subject: [Spce-user] default Ringtone
Message-ID: <alpine.DEB.2.10.1408021002340.14896@jumpy>

Hy All,

when I call on cell phone from the PSTN to spce Subscribers
then I get a rington with a frequency which is not common for Germany

can anyone explain where i can change this default Ringtone ?.

thanks
regards
pascal


From dgrotti at sipwise.com  Sat Aug  2 04:34:54 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Sat, 02 Aug 2014 10:34:54 +0200
Subject: [Spce-user] default Ringtone
Message-ID: <20140802083520.90D6A1502093@zimbra.sipwise.com>

Hi,
Spce doesn't generate any ringtones.
It could be generated by the called party inband or by the pstn provider.

Daniel

On 2 Aug 2014 10:16, Pascal Schwarz <sipwise.support at mtkom.de> wrote:
>
> Hy All, 
>
> when I call on cell phone from the PSTN to spce Subscribers 
> then I get a rington with a frequency which is not common for Germany 
>
> can anyone explain where i can change this default Ringtone ?. 
>
> thanks 
> regards 
> pascal 
> _______________________________________________ 
> Spce-user mailing list 
> Spce-user at lists.sipwise.com 
> https://lists.sipwise.com/listinfo/spce-user 

From sipwise.support at mtkom.de  Sat Aug  2 04:36:09 2014
From: sipwise.support at mtkom.de (Pascal Schwarz)
Date: Sat, 2 Aug 2014 10:36:09 +0200 (CEST)
Subject: [Spce-user] security bans / 403 Errror
In-Reply-To: <20140802080631.1BC121502093@zimbra.sipwise.com>
References: <20140802080631.1BC121502093@zimbra.sipwise.com>
Message-ID: <alpine.DEB.2.10.1408021029440.14896@jumpy>

Hy

>>> An option is to increase the number of attempt from 3 to 6 for ex.
>> where can i change it ?
@daniel thanks i changed it.

i don't understand why the authentifikation fails.
there is no changens on boths systems. so there is no reason
for authentifikation trouble .

regards
Pascal



From dgrotti at sipwise.com  Sat Aug  2 04:44:47 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Sat, 02 Aug 2014 10:44:47 +0200
Subject: [Spce-user] security bans / 403 Errror
Message-ID: <20140802084513.E8D031502093@zimbra.sipwise.com>

If you check the kamailio-proxy.log you can see the reason.

Daniel

On 2 Aug 2014 10:36, Pascal Schwarz <sipwise.support at mtkom.de> wrote:
>
> Hy 
>
> >>> An option is to increase the number of attempt from 3 to 6 for ex. 
> >> where can i change it ? 
> @daniel thanks i changed it. 
>
> i don't understand why the authentifikation fails. 
> there is no changens on boths systems. so there is no reason 
> for authentifikation trouble . 
>
> regards 
> Pascal 
>

From jward01 at gmail.com  Sat Aug  2 13:36:16 2014
From: jward01 at gmail.com (Jeremy Ward)
Date: Sat, 2 Aug 2014 13:36:16 -0400
Subject: [Spce-user] Question About Third-Party Asterisk Applications
In-Reply-To: <CAFfjrWp-wEUtbKXVn+31zN5v9Tyx1wMzJciv2dvVSfh8FRKQ0g@mail.gmail.com>
References: <CAFfjrWp-wEUtbKXVn+31zN5v9Tyx1wMzJciv2dvVSfh8FRKQ0g@mail.gmail.com>
Message-ID: <CAFfjrWrYzmbKtm7u6rbq-u+e=r1kEKj3dD7wiTOa5C4Gu6DFgQ@mail.gmail.com>

Greetings,

Is it possible to add third-party asterisk applications to SPCE? I ask
because we would like to add ACD/Queueing to the system.

Perhaps I missed this in the feature list, but does the system provide IVR
capabilities?

Thanks,

Jeremy D. Ward, CWNE
Neteligence Comnunications, Inc
(212) 901-5288
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140802/13d89777/attachment-0001.html>

From paul.belanger at polybeacon.com  Sat Aug  2 14:10:29 2014
From: paul.belanger at polybeacon.com (Paul Belanger)
Date: Sat, 2 Aug 2014 14:10:29 -0400
Subject: [Spce-user] Question About Third-Party Asterisk Applications
In-Reply-To: <CAFfjrWrYzmbKtm7u6rbq-u+e=r1kEKj3dD7wiTOa5C4Gu6DFgQ@mail.gmail.com>
References: <CAFfjrWp-wEUtbKXVn+31zN5v9Tyx1wMzJciv2dvVSfh8FRKQ0g@mail.gmail.com>
 <CAFfjrWrYzmbKtm7u6rbq-u+e=r1kEKj3dD7wiTOa5C4Gu6DFgQ@mail.gmail.com>
Message-ID: <CALLKq0QWv0Zud_LarTdPtn4e89mti0zpxCX9jt7H6eSrX_PbpA@mail.gmail.com>

On Sat, Aug 2, 2014 at 1:36 PM, Jeremy Ward <jward01 at gmail.com> wrote:
> Greetings,
>
> Is it possible to add third-party asterisk applications to SPCE? I ask
> because we would like to add ACD/Queueing to the system.
>
> Perhaps I missed this in the feature list, but does the system provide IVR
> capabilities?
>
The issue you will have is because the phone are registered into
kamailio, app_queue will not be able to directly use their device
state.  The only way you could do something would be to write a bridge
between kamailio and asterisk to publish the state information about
the subscribers.  You'd use func_devicestate within asterisk.

-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger


From dgrotti at sipwise.com  Sat Aug  2 15:52:31 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Sat, 02 Aug 2014 21:52:31 +0200
Subject: [Spce-user] Question About Third-Party Asterisk Applications
Message-ID: <20140802195254.970AF1502098@zimbra.sipwise.com>

Hi Jeremy,
Ivr is a PBX feature and not a class 5.
Spce doesn't support a native ivr.
What you can do is to build your asterisk ivr outside ngcp and connect each others via sip trunk.

Otherwise you can move to our sip PRO version support a so called CloudPBX module, allowing you to handle pbx feature inside ngcp, such as ivr.

Regards,

Daniel

On 2 Aug 2014 19:36, Jeremy Ward <jward01 at gmail.com> wrote:
>
> Greetings,
>
> Is it possible to add third-party asterisk applications to SPCE? I ask because we would like to add ACD/Queueing to the system.
>
> Perhaps I missed this in the feature list, but does the system provide IVR capabilities?
>
> Thanks,
>
> Jeremy D. Ward, CWNE
> Neteligence Comnunications, Inc
> (212) 901-5288

From agranig at sipwise.com  Sat Aug  2 16:51:38 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Sat, 02 Aug 2014 22:51:38 +0200
Subject: [Spce-user] default Ringtone
In-Reply-To: <alpine.DEB.2.10.1408021002340.14896@jumpy>
References: <alpine.DEB.2.10.1408021002340.14896@jumpy>
Message-ID: <53DD4F5A.5040003@sipwise.com>

Hi,

On 08/02/2014 10:16 AM, Pascal Schwarz wrote:
> when I call on cell phone from the PSTN to spce Subscribers
> then I get a rington with a frequency which is not common for Germany
> 
> can anyone explain where i can change this default Ringtone ?.

You can't (on the server). Either your subscriber sends a 180 without
media, so the SPCE forwards the 180 to the gateway/peering-server, which
generates a ringtone (so if you have that gateway under your control,
you might be able to configure it there), or it sends a 183 with
early-media, which again (both in terms of signalling and media) is
forwarded to your gateway/peer, which play it to the caller as-is, so in
that case you might want to change your device your subscriber is using.

Andreas


From dgrotti at sipwise.com  Mon Aug  4 06:16:57 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Mon, 04 Aug 2014 12:16:57 +0200
Subject: [Spce-user] security bans / 403 Errror
In-Reply-To: <20140802084513.E8D031502093@zimbra.sipwise.com>
References: <20140802084513.E8D031502093@zimbra.sipwise.com>
Message-ID: <53DF5D99.9040508@sipwise.com>

Hi,
as I said in private, problem is that your user is trying to
authenticate with an old 'nonce'.
If you see "stale nonce" in the kamailio-proxy.log means, indeed, your
user is not using in the authenticate process the nonce provided by the
server.

This is a client issue.

Daniel




On 08/02/2014 10:44 AM, Daniel Grotti wrote:
> If you check the kamailio-proxy.log you can see the reason.
>
> Daniel
>
> On 2 Aug 2014 10:36, Pascal Schwarz <sipwise.support at mtkom.de> wrote:
>> Hy 
>>
>>>>> An option is to increase the number of attempt from 3 to 6 for ex. 
>>>> where can i change it ? 
>> @daniel thanks i changed it. 
>>
>> i don't understand why the authentifikation fails. 
>> there is no changens on boths systems. so there is no reason 
>> for authentifikation trouble . 
>>
>> regards 
>> Pascal 
>>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user



From j.fresneda at ibersontel.com  Mon Aug  4 06:29:33 2014
From: j.fresneda at ibersontel.com (Jorge Fresneda - Ibersontel)
Date: Mon, 04 Aug 2014 12:29:33 +0200
Subject: [Spce-user] Session-timers
In-Reply-To: <53DBAD5E.6090901@ibersontel.com>
References: <20140801145727.3EE911502088@zimbra.sipwise.com>
 <53DBAD5E.6090901@ibersontel.com>
Message-ID: <53DF608D.5090604@ibersontel.com>

Hello,
>
> I'm changed the sst_enable, but when receive a INVITE from carrier 
> with "session-expire=1800;refreshes=uac", the answer of sipwise is 200 
> ok. I would like that answer of sipwise with "session-expire=7200"
>
> Thanks,
> Regards
>
>
> El 01/08/2014 16:57, Daniel Grotti escribi?:
>> You can change it from web interface.
>> No apply is needed.
>>
>> On 1 Aug 2014 16:39, Jorge Fresneda - Ibersontel 
>> <j.fresneda at ibersontel.com> wrote:
>>> Hi,
>>>
>>> One question, When I change the sst_enable to "yes", is need execute
>>> "ngcpcfg apply"?????
>>>
>>> Thanks so much
>>> Regards,
>>> Jorge
>>>
>>>
>>>
>>> El 31/07/2014 13:41, Daniel Grotti escribi?:
>>>> Hi,
>>>> you can enable/disable session-timers on peer/subscribers preferences.
>>>>
>>>> Daniel
>>>>
>>>>
>>>>
>>>> On 07/31/2014 12:55 PM, Jorge Fresneda - Ibersontel wrote:
>>>>> Hello,
>>>>>
>>>>>
>>>>> I have a problem with session-timers. A carrier send me a
>>>>> "session-expire=1800;refresher=uac" header at 30 minutes and he 
>>>>> say me
>>>>> that I have enable the session-timer option. How I can do? I would 
>>>>> like
>>>>> to that session-option are enable on end-point and not in sipwise.
>>>>>
>>>>> Thank you so much,
>>>>> Regards
>>>>> Jorge
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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



From jbonilla at sipwise.com  Mon Aug  4 06:42:16 2014
From: jbonilla at sipwise.com (Jon Bonilla (Manwe))
Date: Mon, 4 Aug 2014 12:42:16 +0200
Subject: [Spce-user] Session-timers
In-Reply-To: <53DBAD5E.6090901@ibersontel.com>
References: <20140801145727.3EE911502088@zimbra.sipwise.com>
 <53DBAD5E.6090901@ibersontel.com>
Message-ID: <20140804124216.0f8701ab@quenya>

El Fri, 01 Aug 2014 17:08:14 +0200
Jorge Fresneda - Ibersontel <j.fresneda at ibersontel.com> escribi?:

> Oh, I'm sorry:
> 
> I'm changed the sst_enable, but when receive a INVITE from carrier with 
> "session-expire=1800;refreshes=uac", the answer of sipwise is 200 ok. I 
> would like that answer of sipwise with "session-expire=7200"
> 
> 

Then you need to set min_se to something higher. 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140804/1d6a5b1c/attachment-0001.asc>

From matthew at tenacit.net  Mon Aug  4 07:48:49 2014
From: matthew at tenacit.net (Matthew Ogden)
Date: Mon, 4 Aug 2014 13:48:49 +0200
Subject: [Spce-user] security bans / 403 Errror
In-Reply-To: <53DF5D99.9040508@sipwise.com>
References: <20140802084513.E8D031502093@zimbra.sipwise.com>
 <53DF5D99.9040508@sipwise.com>
Message-ID: <d85d4c7d6795addecfe54b5f317e24bf@mail.gmail.com>

Hi Daniel,

You guys gave me a workaround for the stalenonce on the lists as well:
http://lists.sipwise.com/pipermail/spce-user/2014-January/005712.html

(Asterisk bug in my case).

Regards

-----Original Message-----
From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of
Daniel Grotti
Sent: 04 August 2014 12:17 PM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] security bans / 403 Errror

Hi,
as I said in private, problem is that your user is trying to authenticate
with an old 'nonce'.
If you see "stale nonce" in the kamailio-proxy.log means, indeed, your
user is not using in the authenticate process the nonce provided by the
server.

This is a client issue.

Daniel




On 08/02/2014 10:44 AM, Daniel Grotti wrote:
> If you check the kamailio-proxy.log you can see the reason.
>
> Daniel
>
> On 2 Aug 2014 10:36, Pascal Schwarz <sipwise.support at mtkom.de> wrote:
>> Hy
>>
>>>>> An option is to increase the number of attempt from 3 to 6 for ex.
>>>> where can i change it ?
>> @daniel thanks i changed it.
>>
>> i don't understand why the authentifikation fails.
>> there is no changens on boths systems. so there is no reason for
>> authentifikation trouble .
>>
>> regards
>> Pascal
>>
> _______________________________________________
> 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


From alutay at sipwise.com  Tue Aug  5 12:05:34 2014
From: alutay at sipwise.com (Alex Lutay)
Date: Tue, 05 Aug 2014 18:05:34 +0200
Subject: [Spce-user] New sip:provider CE mr3.4.1 available
Message-ID: <53E100CE.30609@sipwise.com>

Hi all,

This is to inform community about availability of the new spce mr3.4.1:

Please check the release notes here:
https://www.sipwise.com/news/announcements/sipprovider-mr3-4-1-released/

Thanks for your bugreports and feedback!

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From mprokop at sipwise.com  Tue Aug  5 15:24:11 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Tue, 5 Aug 2014 21:24:11 +0200
Subject: [Spce-user] New sip:provider CE features: install CD,
	EC2 AMI + Docker support
Message-ID: <2014-08-05T21-14-20@devnull.michael-prokop.at>

Hi,

our release notes for sip:provider CE mr3.4.1 at
https://www.sipwise.com/news/announcements/sipprovider-mr3-4-1-released/
already mention it, but I'd like to highlight three features where
we're especially interested in community feedback.

1) Sipwise NGCP install CD
https://www.sipwise.com/doc/mr3.4.1/spce/ar01s04.html#_using_the_ngcp_install_cd_recommended

This is the initial public release of our deployment system, being
based on what we use internally since several years. It's based on
the Grml live system (<http://grml.org/>) and provides a straight
forward way to install sip:provider CE in an automated fashion (or
also just plain Debian, and while at it you also get the option to
use a full featured live rescue system with it too).

2) Amazon EC2 AMI

The creation of sip:provider CE AMIs for usage on Amazon EC2 is
fully automated in our release process and we plan to provide
updated AMIs with each new sip:provider CE release. We even made
some of the scripts we use for AMI generation available to the
public: https://github.com/sipwise/ec2-tools

We plan to provide some more documentation about usage of our AMIs
on EC2 soon, in the meanwhile just launch the latest mr3.4.1 release
via https://console.aws.amazon.com/ec2/v2/home?region=eu-west-1#LaunchInstanceWizard:ami=ami-0bb6657c

3) Docker support

Starting with the mr3.4.1 release we provide initial docker support
for sip:provider CE. Generating the docker images is also part of
our automated release process, so we plan to provide updated docker
images for each new sip:provider CE release too. The documentation
is still on our agenda, but if you are familiar with docker or feel
like you'd like to play with it anyway please feel invited to do so:
https://registry.hub.docker.com/repos/sipwise/

If you should notice *any* problems with the install CD, the AMI(s)
or the Docker images please let us know, we appreciate any feedback.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140805/2e3ea7e4/attachment-0001.asc>

From aalejandro at alliedtechnologygrouppr.com  Wed Aug  6 01:58:34 2014
From: aalejandro at alliedtechnologygrouppr.com (Abel Alejandro)
Date: Wed, 6 Aug 2014 01:58:34 -0400
Subject: [Spce-user] No PSTN gateways available when using *31* to hide CLIR
Message-ID: <CAKiNg22=aFv6KTYoPRK45yighLrS3Gfci4jBYKzftA67=Sgx5Q@mail.gmail.com>

Hello,

I am testing using *31* to hide the CLIR. However any number I call
(subscriber or peer) it gives me the same error. Is there something I
need to enable to use this code?


Aug  6 01:54:22 sip proxy[4231]: NOTICE: <script>: Contacts
successfully updated, expires in 60s - R=sip:sip.fusetelecom.com
ID=14269cb16fb84fda790fb6d1011c2899 at 127.0.0.1
Aug  6 01:54:27 sip proxy[4231]: NOTICE: <script>: New request -
M=REGISTER R=sip:sip.alliedtechpr.com
F=sip:alliedtech at sip.alliedtechpr.com
T=sip:alliedtech at sip.alliedtechpr.com IP=38.87.235.182:5060
(127.0.0.1:5060) ID=29fc3e6f7e7b02af4cc2c5b201a895f1 at 127.0.0.1
Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: New request -
M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
F=sip:aalejandro at sip.alliedtechpr.com:5060
T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
(127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: Authentication
failed, no credentials -
R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: New request -
M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
F=sip:aalejandro at sip.alliedtechpr.com:5060
T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
(127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-Provided CLI
'aalejandro' taken from From-User -
R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-provided CLI
'aalejandro' rejected, using network-provided CLI '17879190810' -
R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
'17879190810 at sip.alliedtechpr.com' as initiating user-provided CLI -
R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
'17879190810 at sip.alliedtechpr.com' as initiating network-provided CLI
- R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Per-call CLIR
enabled - R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Callee is not local
- R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Call to SIP Peering
- R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Load gws matching
calling part 'sip:17879190810 at sip.alliedtechpr.com' and called user
'7877050555' and called part
'sip:7877050555 at sip.alliedtechpr.com:5060' -
R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: ERROR: <script>: No PSTN gateways
available - R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
source-leg for uuid '1c62f6c2-cc4e-41a3-b0f2-140ead720f14':
'1c62f6c2-cc4e-41a3-b0f2-140ead720f14|aalejandro|sip.alliedtechpr.com|17879190810|17879190810|Allied
Technology|10|||1|call|24.55.105.153|1407304467.351906' -
R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
destination-leg for uuid '0':
'0|||0|*31*7877050555|0|7877050555|sip.alliedtechpr.com|7877050555|sip.alliedtechpr.com'
- R=sip:7877050555 at sip.alliedtechpr.com:5060
ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.


-- 
Abel Alejandro

787 586 8313 | 787 705 0555

400 Calle Calaf 477
San Juan, PR 00918
aalejandro at alliedtechnologygrouppr.com


From dgrotti at sipwise.com  Wed Aug  6 02:11:29 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Wed, 06 Aug 2014 08:11:29 +0200
Subject: [Spce-user] No PSTN gateways available when using *31* to hide
 CLIR
Message-ID: <20140806061158.B2E72150208F@zimbra.sipwise.com>

Hi,
Problem is you don't have any peering rules matching the number 7877050555.

Daniel

On 6 Aug 2014 07:58, Abel Alejandro <aalejandro at alliedtechnologygrouppr.com> wrote:
>
> Hello, 
>
> I am testing using *31* to hide the CLIR. However any number I call 
> (subscriber or peer) it gives me the same error. Is there something I 
> need to enable to use this code? 
>
>
> Aug? 6 01:54:22 sip proxy[4231]: NOTICE: <script>: Contacts 
> successfully updated, expires in 60s - R=sip:sip.fusetelecom.com 
> ID=14269cb16fb84fda790fb6d1011c2899 at 127.0.0.1 
> Aug? 6 01:54:27 sip proxy[4231]: NOTICE: <script>: New request - 
> M=REGISTER R=sip:sip.alliedtechpr.com 
> F=sip:alliedtech at sip.alliedtechpr.com 
> T=sip:alliedtech at sip.alliedtechpr.com IP=38.87.235.182:5060 
> (127.0.0.1:5060) ID=29fc3e6f7e7b02af4cc2c5b201a895f1 at 127.0.0.1 
> Aug? 6 01:54:27 sip proxy[4217]: NOTICE: <script>: New request - 
> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> F=sip:aalejandro at sip.alliedtechpr.com:5060 
> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494 
> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4217]: NOTICE: <script>: Authentication 
> failed, no credentials - 
> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: New request - 
> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> F=sip:aalejandro at sip.alliedtechpr.com:5060 
> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494 
> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-Provided CLI 
> 'aalejandro' taken from From-User - 
> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-provided CLI 
> 'aalejandro' rejected, using network-provided CLI '17879190810' - 
> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting 
> '17879190810 at sip.alliedtechpr.com' as initiating user-provided CLI - 
> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting 
> '17879190810 at sip.alliedtechpr.com' as initiating network-provided CLI 
> - R=sip:*31*7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Per-call CLIR 
> enabled - R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Callee is not local 
> - R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Call to SIP Peering 
> - R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Load gws matching 
> calling part 'sip:17879190810 at sip.alliedtechpr.com' and called user 
> '7877050555' and called part 
> 'sip:7877050555 at sip.alliedtechpr.com:5060' - 
> R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: ERROR: <script>: No PSTN gateways 
> available - R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc 
> source-leg for uuid '1c62f6c2-cc4e-41a3-b0f2-140ead720f14': 
> '1c62f6c2-cc4e-41a3-b0f2-140ead720f14|aalejandro|sip.alliedtechpr.com|17879190810|17879190810|Allied 
> Technology|10|||1|call|24.55.105.153|1407304467.351906' - 
> R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
> Aug? 6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc 
> destination-leg for uuid '0': 
> '0|||0|*31*7877050555|0|7877050555|sip.alliedtechpr.com|7877050555|sip.alliedtechpr.com' 
> - R=sip:7877050555 at sip.alliedtechpr.com:5060 
> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ. 
>
>
> -- 
> Abel Alejandro 
>
> 787 586 8313 | 787 705 0555 
>
> 400 Calle Calaf 477 
> San Juan, PR 00918 
> aalejandro at alliedtechnologygrouppr.com 
> _______________________________________________ 
> Spce-user mailing list 
> Spce-user at lists.sipwise.com 
> https://lists.sipwise.com/listinfo/spce-user 

From aalejandro at alliedtechnologygrouppr.com  Wed Aug  6 07:32:15 2014
From: aalejandro at alliedtechnologygrouppr.com (Abel Alejandro)
Date: Wed, 6 Aug 2014 07:32:15 -0400
Subject: [Spce-user] No PSTN gateways available when using *31* to hide
	CLIR
In-Reply-To: <20140806061158.B2E72150208F@zimbra.sipwise.com>
References: <20140806061158.B2E72150208F@zimbra.sipwise.com>
Message-ID: <CAKiNg22g5qJ3zXp+oJ7R_Z+Z37J=20Z7gW7QDz-pjsu+F=tpzw@mail.gmail.com>

Hello,

Thats actually a subscriber. If I dial 7877050555 it works fine.
However if I dial *31*7877050555 it doesn't work.
The same thing happens with a number that goes thru a peer.

Abel.


On Wed, Aug 6, 2014 at 2:11 AM, Daniel Grotti <dgrotti at sipwise.com> wrote:
> Hi,
> Problem is you don't have any peering rules matching the number 7877050555.
>
> Daniel
>
> On 6 Aug 2014 07:58, Abel Alejandro <aalejandro at alliedtechnologygrouppr.com> wrote:
>>
>> Hello,
>>
>> I am testing using *31* to hide the CLIR. However any number I call
>> (subscriber or peer) it gives me the same error. Is there something I
>> need to enable to use this code?
>>
>>
>> Aug  6 01:54:22 sip proxy[4231]: NOTICE: <script>: Contacts
>> successfully updated, expires in 60s - R=sip:sip.fusetelecom.com
>> ID=14269cb16fb84fda790fb6d1011c2899 at 127.0.0.1
>> Aug  6 01:54:27 sip proxy[4231]: NOTICE: <script>: New request -
>> M=REGISTER R=sip:sip.alliedtechpr.com
>> F=sip:alliedtech at sip.alliedtechpr.com
>> T=sip:alliedtech at sip.alliedtechpr.com IP=38.87.235.182:5060
>> (127.0.0.1:5060) ID=29fc3e6f7e7b02af4cc2c5b201a895f1 at 127.0.0.1
>> Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: New request -
>> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> F=sip:aalejandro at sip.alliedtechpr.com:5060
>> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
>> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: Authentication
>> failed, no credentials -
>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: New request -
>> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> F=sip:aalejandro at sip.alliedtechpr.com:5060
>> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
>> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-Provided CLI
>> 'aalejandro' taken from From-User -
>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-provided CLI
>> 'aalejandro' rejected, using network-provided CLI '17879190810' -
>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
>> '17879190810 at sip.alliedtechpr.com' as initiating user-provided CLI -
>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
>> '17879190810 at sip.alliedtechpr.com' as initiating network-provided CLI
>> - R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Per-call CLIR
>> enabled - R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Callee is not local
>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Call to SIP Peering
>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Load gws matching
>> calling part 'sip:17879190810 at sip.alliedtechpr.com' and called user
>> '7877050555' and called part
>> 'sip:7877050555 at sip.alliedtechpr.com:5060' -
>> R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: ERROR: <script>: No PSTN gateways
>> available - R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
>> source-leg for uuid '1c62f6c2-cc4e-41a3-b0f2-140ead720f14':
>> '1c62f6c2-cc4e-41a3-b0f2-140ead720f14|aalejandro|sip.alliedtechpr.com|17879190810|17879190810|Allied
>> Technology|10|||1|call|24.55.105.153|1407304467.351906' -
>> R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
>> destination-leg for uuid '0':
>> '0|||0|*31*7877050555|0|7877050555|sip.alliedtechpr.com|7877050555|sip.alliedtechpr.com'
>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>
>>
>> --
>> Abel Alejandro
>>
>> 787 586 8313 | 787 705 0555
>>
>> 400 Calle Calaf 477
>> San Juan, PR 00918
>> aalejandro at alliedtechnologygrouppr.com
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user



-- 
Abel Alejandro

787 586 8313 | 787 705 0555

400 Calle Calaf 477
San Juan, PR 00918
aalejandro at alliedtechnologygrouppr.com


From kmasse at questblue.com  Wed Aug  6 07:54:41 2014
From: kmasse at questblue.com (Kevin Masse)
Date: Wed, 6 Aug 2014 07:54:41 -0400
Subject: [Spce-user] Subscriber Alias Entries in Database
References: <CEEE718799582B47A55D7897DCB264FC3F5E18@bvusaex.bestvoipusa.local><53C652BD.7000707@sipwise.com>
 <CEEE718799582B47A55D7897DCB264FC3F5E65@bvusaex.bestvoipusa.local>
 <CEEE718799582B47A55D7897DCB264FC3F5F7F@bvusaex.bestvoipusa.local>
Message-ID: <CEEE718799582B47A55D7897DCB264FC3F60D6@bvusaex.bestvoipusa.local>

Hello, I was wondering if there was a response to this that I missed.
There are two specific questions we are trying to answer.


Thank you
Kevin



-----Original Message-----
From: Kevin Masse 
Sent: Thursday, July 24, 2014 10:02 AM
To: Kevin Masse; Andreas Granig; spce-user at lists.sipwise.com
Subject: RE: [Spce-user] Subscriber Alias Entries in Database

Andraes one additional scenario has come up based on our last thread:
I wanted to post to the group the question from our dev team:

****  Begin Comment ****
It is going to be a long post because I can't explain in a short
message. I'll provide some example to explain what I mean. 

We have SIP named QBATRUNK.  If you open administrator page
(https://DOMAIN:1443/subscriber/detail?subscriber_id=395) you can see
there following info:

Contract ID (405) - This is main ID which we store in (customer site -
not part of Sipwise it is our Database) . All operations like
lock/unlock SIP, add/remove DID using the ID in it request to API.

Subscriber ID (395) - I can call it internal info, it is not used in any
request to Sipwise API but to make direct request to Sipwise DB I have
to use it.

I routed 3384066 DID to the SIP to work with the example. 
According to previous instructions we use two databases to store
aliases. Now I'll show you request to retrieve the DID from Sipwise DB.

First I use billing DB. Let's retrieve Subscriber ID (we do not know it
when call DB directly). I use voip_subscribers table which stores the
info.

mysql> select * from voip_subscribers where contract_id = 405;
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+
| id | contract_id | uuid | username | domain_id | status |
primary_number_id | external_id |
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+
| 395 | 405 | 14a58c84-c83e-4673-9d10-361a1a6b990e | QBATRUNK | 1 |
active | NULL | NULL |
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+

OK you can see that I receive id 395. We need it.

 

Let's get DIDs info from voip_numbers, DB - 

mysql> select * from voip_numbers where subscriber_id = 395;
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+
| id | cc | ac | sn | reseller_id | subscriber_id | status | ported |
list_timestamp |
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+
| 2119 | 1 | 910 | 3384066 | NULL | 395 | active | 1 | 2014-07-22
18:32:16 |
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+

Everything is OK we got it as expected. Lets' get DID info from second
DB (provisioning) I'll do it using DID number

mysql> select * from voip_dbaliases where username like '%3384066%';
+------+-------------+-----------+---------------+
| id | username | domain_id | subscriber_id |
+------+-------------+-----------+---------------+
| 2821 | 19103384066 | 3 | 398 |

As you can see subscriber_id in the table does not corresponds to the
subscriber_id which we retrieve from billing DB. That is the question
for me.

I found that the subscriber_id is stored in voip_dbaliases table but the
ID does not corresponds to the subscriber_id from billing table.

Question 1
I do not understand how subscriber_id in billing DB (table voip_numbers)
related with subscriber_id in provisioning DB (table voip_dbaliases ).

Question 2
Another question. I found that DIDs info is stored in voip_dbaliases
table (provisioning) but I did not told to creae the record by VoIP
specialist.

mysql> select * from voip_dbaliases where username like '%3384066%';
+------+-------------+-----------+---------------+
| id | username | domain_id | subscriber_id |
+------+-------------+-----------+---------------+
| 2821 | 19103384066 | 3 | 398 |
+------+-------------+-----------+---------------+

Hopefully I explained my questions clear. If not please let me know

Thanks,
*** End Comment from DEV ***



In conclusion Andreas do you think there is a proper answer for the
above Question 1 and Question 2?
Thank you
Kevin 





-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Kevin Masse
Sent: Wednesday, July 16, 2014 8:56 AM
To: Andreas Granig; spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Subscriber Alias Entries in Database

Thank you Andreas, I appreciate the detailed response.  Works as
described.
Kevin



-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Andreas Granig
Sent: Wednesday, July 16, 2014 6:24 AM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Subscriber Alias Entries in Database

Hi,

On 07/15/2014 03:05 PM, Kevin Masse wrote:

> **  Current operation:   We use SOAP to add alias numbers to a
subscriber 
> 
> Requested operation:  We would like to write a new alias number for a 
> subscriber directly to the database.

As long as you make sure to write it to both billing.voip_numbers and
provisioning.voip_dbaliases, it should be fine.

Andreas

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/listinfo/spce-user

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/listinfo/spce-user


From mstorck at voipgate.com  Wed Aug  6 08:02:12 2014
From: mstorck at voipgate.com (Marc Storck)
Date: Wed, 6 Aug 2014 12:02:12 +0000
Subject: [Spce-user] change of IP address
Message-ID: <44D6B68F-59E4-46E3-B2BD-65371E9220F7@voipgate.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Good afternoon,

I need to change the IP address of a system (*NOT* the domain name). I tried seraching for instruction but I wasn?t successful.

Could someone please point me into the right direction?

Best regards,

Marc
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJT4hnIAAoJEBqZdpQUXtTCvhAP/1qrA08tWkgjl+wKtOU3tBV2
vLo2uK9xX0guTbMiZ3rAAwZ2hmpqfsbZ8nAXj4+PLo6h7P5oM4boiiAWg6CGg4DM
XWgX9hEHIlvHF27OdOj/pmP2UfFC9MRfcKfIvU+7fCcGn9Mt+6WlfEHalbUOgbIq
XrTyWRAgob1WEwQnlpTz9fwzqQ+idUBdHheSa3r9LyabrCHktLx8nQA0ZxkH9AUR
kp5gbWRlAATPHqzGaSkbAy2CVFRmHGjc3ELG0d/1KbEgoz2BnWT3rX7yevnM7q7a
ZSVaIS85UdnnL1nBggSYk54H8ybF5wphN5746AYLh89jqbiqoRDooSAwAyUEvG0J
NYw7Ft0qSDCGaQb982zgOQbkZeG2Qv1j1sRpX6bZjfia+zLjZq8jVl+Aquzyaerm
9tOh/abxWymvXutnT0Begl+snWph94kQr+HFl3VnHeycd6HiaXh3jCSO1g00LxZu
W0OEgbvPjFanIm+qAzRFfBo+MuHkpXxhY19TlJRYP1k3aGBeiP+CxqAzH63mcOiE
Vf2rSaY0jYrc43P/cjaEEpe8drE47NRmCTgH5qR0nn2yh/vfYi6XI6tkc+aTeZ2F
KBjKt501DBDGfiEBT/qcC8ezb8KxB82qbSgMqxaY69oB7158uEnKURuW/zGgmh6c
i9zbbfSGr53Nf4YREP7F
=m8Fr
-----END PGP SIGNATURE-----

From vseva at sipwise.com  Wed Aug  6 08:12:38 2014
From: vseva at sipwise.com (Victor Seva)
Date: Wed, 06 Aug 2014 14:12:38 +0200
Subject: [Spce-user] change of IP address
In-Reply-To: <44D6B68F-59E4-46E3-B2BD-65371E9220F7@voipgate.com>
References: <44D6B68F-59E4-46E3-B2BD-65371E9220F7@voipgate.com>
Message-ID: <53E21BB6.4030701@sipwise.com>

On 08/06/2014 02:02 PM, Marc Storck wrote:
> Good afternoon,
> 
> I need to change the IP address of a system (*NOT* the domain name). I tried seraching for instruction but I wasn?t successful.
> 
> Could someone please point me into the right direction?

https://www.sipwise.com/doc/mr3.4.1/spce/ar01s05.html#_network_configuration



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140806/201a7302/attachment-0001.asc>

From aalejandro at alliedtechnologygrouppr.com  Wed Aug  6 08:26:19 2014
From: aalejandro at alliedtechnologygrouppr.com (Abel Alejandro)
Date: Wed, 6 Aug 2014 08:26:19 -0400
Subject: [Spce-user] No PSTN gateways available when using *31* to hide
	CLIR
In-Reply-To: <CAKiNg22g5qJ3zXp+oJ7R_Z+Z37J=20Z7gW7QDz-pjsu+F=tpzw@mail.gmail.com>
References: <20140806061158.B2E72150208F@zimbra.sipwise.com>
 <CAKiNg22g5qJ3zXp+oJ7R_Z+Z37J=20Z7gW7QDz-pjsu+F=tpzw@mail.gmail.com>
Message-ID: <CAKiNg201dJE1EfYnGbGpU5anTR-5JKgCQHKB6QL1tQGq_HVbfA@mail.gmail.com>

I see what happened now. If I use *31* the rewrite rules wont work. I
guess I need to account for the service codes in the rewrite rules as
well, yes?
I thought the *31* would be like a special code and hidden from the
system as soon as it entered.

Thanks.


On Wed, Aug 6, 2014 at 7:32 AM, Abel Alejandro
<aalejandro at alliedtechnologygrouppr.com> wrote:
> Hello,
>
> Thats actually a subscriber. If I dial 7877050555 it works fine.
> However if I dial *31*7877050555 it doesn't work.
> The same thing happens with a number that goes thru a peer.
>
> Abel.
>
>
> On Wed, Aug 6, 2014 at 2:11 AM, Daniel Grotti <dgrotti at sipwise.com> wrote:
>> Hi,
>> Problem is you don't have any peering rules matching the number 7877050555.
>>
>> Daniel
>>
>> On 6 Aug 2014 07:58, Abel Alejandro <aalejandro at alliedtechnologygrouppr.com> wrote:
>>>
>>> Hello,
>>>
>>> I am testing using *31* to hide the CLIR. However any number I call
>>> (subscriber or peer) it gives me the same error. Is there something I
>>> need to enable to use this code?
>>>
>>>
>>> Aug  6 01:54:22 sip proxy[4231]: NOTICE: <script>: Contacts
>>> successfully updated, expires in 60s - R=sip:sip.fusetelecom.com
>>> ID=14269cb16fb84fda790fb6d1011c2899 at 127.0.0.1
>>> Aug  6 01:54:27 sip proxy[4231]: NOTICE: <script>: New request -
>>> M=REGISTER R=sip:sip.alliedtechpr.com
>>> F=sip:alliedtech at sip.alliedtechpr.com
>>> T=sip:alliedtech at sip.alliedtechpr.com IP=38.87.235.182:5060
>>> (127.0.0.1:5060) ID=29fc3e6f7e7b02af4cc2c5b201a895f1 at 127.0.0.1
>>> Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: New request -
>>> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> F=sip:aalejandro at sip.alliedtechpr.com:5060
>>> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
>>> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: Authentication
>>> failed, no credentials -
>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: New request -
>>> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> F=sip:aalejandro at sip.alliedtechpr.com:5060
>>> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
>>> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-Provided CLI
>>> 'aalejandro' taken from From-User -
>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-provided CLI
>>> 'aalejandro' rejected, using network-provided CLI '17879190810' -
>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
>>> '17879190810 at sip.alliedtechpr.com' as initiating user-provided CLI -
>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
>>> '17879190810 at sip.alliedtechpr.com' as initiating network-provided CLI
>>> - R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Per-call CLIR
>>> enabled - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Callee is not local
>>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Call to SIP Peering
>>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Load gws matching
>>> calling part 'sip:17879190810 at sip.alliedtechpr.com' and called user
>>> '7877050555' and called part
>>> 'sip:7877050555 at sip.alliedtechpr.com:5060' -
>>> R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: ERROR: <script>: No PSTN gateways
>>> available - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
>>> source-leg for uuid '1c62f6c2-cc4e-41a3-b0f2-140ead720f14':
>>> '1c62f6c2-cc4e-41a3-b0f2-140ead720f14|aalejandro|sip.alliedtechpr.com|17879190810|17879190810|Allied
>>> Technology|10|||1|call|24.55.105.153|1407304467.351906' -
>>> R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
>>> destination-leg for uuid '0':
>>> '0|||0|*31*7877050555|0|7877050555|sip.alliedtechpr.com|7877050555|sip.alliedtechpr.com'
>>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>
>>>
>>> --
>>> Abel Alejandro
>>>
>>> 787 586 8313 | 787 705 0555
>>>
>>> 400 Calle Calaf 477
>>> San Juan, PR 00918
>>> aalejandro at alliedtechnologygrouppr.com
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>
>
>
> --
> Abel Alejandro
>
> 787 586 8313 | 787 705 0555
>
> 400 Calle Calaf 477
> San Juan, PR 00918
> aalejandro at alliedtechnologygrouppr.com



-- 
Abel Alejandro

787 586 8313 | 787 705 0555

400 Calle Calaf 477
San Juan, PR 00918
aalejandro at alliedtechnologygrouppr.com


From dgrotti at sipwise.com  Wed Aug  6 08:32:17 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Wed, 06 Aug 2014 14:32:17 +0200
Subject: [Spce-user] No PSTN gateways available when using *31* to hide
 CLIR
In-Reply-To: <CAKiNg201dJE1EfYnGbGpU5anTR-5JKgCQHKB6QL1tQGq_HVbfA@mail.gmail.com>
References: <20140806061158.B2E72150208F@zimbra.sipwise.com>	<CAKiNg22g5qJ3zXp+oJ7R_Z+Z37J=20Z7gW7QDz-pjsu+F=tpzw@mail.gmail.com>
 <CAKiNg201dJE1EfYnGbGpU5anTR-5JKgCQHKB6QL1tQGq_HVbfA@mail.gmail.com>
Message-ID: <53E22051.1020200@sipwise.com>

Hi,
yes you should rewrite the call first

*31*7877050555 ---> *31*e164-number


Daniel




On 08/06/2014 02:26 PM, Abel Alejandro wrote:
> I see what happened now. If I use *31* the rewrite rules wont work. I
> guess I need to account for the service codes in the rewrite rules as
> well, yes?
> I thought the *31* would be like a special code and hidden from the
> system as soon as it entered.
>
> Thanks.
>
>
> On Wed, Aug 6, 2014 at 7:32 AM, Abel Alejandro
> <aalejandro at alliedtechnologygrouppr.com> wrote:
>> Hello,
>>
>> Thats actually a subscriber. If I dial 7877050555 it works fine.
>> However if I dial *31*7877050555 it doesn't work.
>> The same thing happens with a number that goes thru a peer.
>>
>> Abel.
>>
>>
>> On Wed, Aug 6, 2014 at 2:11 AM, Daniel Grotti <dgrotti at sipwise.com> wrote:
>>> Hi,
>>> Problem is you don't have any peering rules matching the number 7877050555.
>>>
>>> Daniel
>>>
>>> On 6 Aug 2014 07:58, Abel Alejandro <aalejandro at alliedtechnologygrouppr.com> wrote:
>>>> Hello,
>>>>
>>>> I am testing using *31* to hide the CLIR. However any number I call
>>>> (subscriber or peer) it gives me the same error. Is there something I
>>>> need to enable to use this code?
>>>>
>>>>
>>>> Aug  6 01:54:22 sip proxy[4231]: NOTICE: <script>: Contacts
>>>> successfully updated, expires in 60s - R=sip:sip.fusetelecom.com
>>>> ID=14269cb16fb84fda790fb6d1011c2899 at 127.0.0.1
>>>> Aug  6 01:54:27 sip proxy[4231]: NOTICE: <script>: New request -
>>>> M=REGISTER R=sip:sip.alliedtechpr.com
>>>> F=sip:alliedtech at sip.alliedtechpr.com
>>>> T=sip:alliedtech at sip.alliedtechpr.com IP=38.87.235.182:5060
>>>> (127.0.0.1:5060) ID=29fc3e6f7e7b02af4cc2c5b201a895f1 at 127.0.0.1
>>>> Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: New request -
>>>> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> F=sip:aalejandro at sip.alliedtechpr.com:5060
>>>> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
>>>> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4217]: NOTICE: <script>: Authentication
>>>> failed, no credentials -
>>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: New request -
>>>> M=INVITE R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> F=sip:aalejandro at sip.alliedtechpr.com:5060
>>>> T=sip:*31*7877050555 at sip.alliedtechpr.com:5060 IP=24.55.105.153:51494
>>>> (127.0.0.1:5060) ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-Provided CLI
>>>> 'aalejandro' taken from From-User -
>>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: User-provided CLI
>>>> 'aalejandro' rejected, using network-provided CLI '17879190810' -
>>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
>>>> '17879190810 at sip.alliedtechpr.com' as initiating user-provided CLI -
>>>> R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting
>>>> '17879190810 at sip.alliedtechpr.com' as initiating network-provided CLI
>>>> - R=sip:*31*7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Per-call CLIR
>>>> enabled - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Callee is not local
>>>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Call to SIP Peering
>>>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Load gws matching
>>>> calling part 'sip:17879190810 at sip.alliedtechpr.com' and called user
>>>> '7877050555' and called part
>>>> 'sip:7877050555 at sip.alliedtechpr.com:5060' -
>>>> R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: ERROR: <script>: No PSTN gateways
>>>> available - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
>>>> source-leg for uuid '1c62f6c2-cc4e-41a3-b0f2-140ead720f14':
>>>> '1c62f6c2-cc4e-41a3-b0f2-140ead720f14|aalejandro|sip.alliedtechpr.com|17879190810|17879190810|Allied
>>>> Technology|10|||1|call|24.55.105.153|1407304467.351906' -
>>>> R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>> Aug  6 01:54:27 sip proxy[4218]: NOTICE: <script>: Setting acc
>>>> destination-leg for uuid '0':
>>>> '0|||0|*31*7877050555|0|7877050555|sip.alliedtechpr.com|7877050555|sip.alliedtechpr.com'
>>>> - R=sip:7877050555 at sip.alliedtechpr.com:5060
>>>> ID=NDlhN2I5YTI5ODkyNjUzMGRmMzdlODE5NWYxZWRmYTQ.
>>>>
>>>>
>>>> --
>>>> Abel Alejandro
>>>>
>>>> 787 586 8313 | 787 705 0555
>>>>
>>>> 400 Calle Calaf 477
>>>> San Juan, PR 00918
>>>> aalejandro at alliedtechnologygrouppr.com
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com
>>>> https://lists.sipwise.com/listinfo/spce-user
>>
>>
>> --
>> Abel Alejandro
>>
>> 787 586 8313 | 787 705 0555
>>
>> 400 Calle Calaf 477
>> San Juan, PR 00918
>> aalejandro at alliedtechnologygrouppr.com
>
>



From rabs at dimension-virtual.com  Thu Aug  7 08:19:53 2014
From: rabs at dimension-virtual.com (=?iso-8859-1?B?UmHDumw=?= Alexis Betancor Santana)
Date: Thu, 7 Aug 2014 13:19:53 +0100
Subject: [Spce-user] MySQL errors
Message-ID: <20140807121952.GA23093@salma.divi.prv>

Hi all, since we upgrades a test system from 3.2 to mr3.3 and
yesterday to mr3.4.1 this is getting worst:

Aug  7 14:18:56 sipapp01 proxy[16074]: ERROR: db_mysql
[km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Lost
connection to MySQL server during query
Aug  7 14:18:56 sipapp01 proxy[16074]: ERROR: <core> [db_query.c:337]:
db_do_update(): error while submitting query
Aug  7 14:18:56 sipapp01 proxy[16074]: ERROR: usrloc [ucontact.c:815]:
db_update_ucontact_addr(): updating database failed
Aug  7 14:18:56 sipapp01 proxy[16074]: ERROR: usrloc
[ucontact.c:1502]: update_ucontact(): failed to update database
Aug  7 14:18:56 sipapp01 proxy[16074]: ERROR: registrar [save.c:775]:
update_contacts(): failed to update contact
Aug  7 14:18:56 sipapp01 proxy[16077]: ERROR: db_mysql
[km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Lost
connection to MySQL server during query
Aug  7 14:18:56 sipapp01 proxy[16077]: ERROR: <core> [db_query.c:337]:
db_do_update(): error while submitting query
Aug  7 14:18:56 sipapp01 proxy[16077]: ERROR: usrloc [ucontact.c:815]:
db_update_ucontact_addr(): updating database failed
Aug  7 14:18:56 sipapp01 proxy[16077]: ERROR: usrloc
[ucontact.c:1502]: update_ucontact(): failed to update database
Aug  7 14:18:56 sipapp01 proxy[16077]: ERROR: registrar [save.c:775]:
update_contacts(): failed to update contact
Aug  7 14:18:57 sipapp01 proxy[16083]: ERROR: db_mysql
[km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Lost
connection to MySQL server during query
Aug  7 14:18:57 sipapp01 proxy[16083]: ERROR: <core> [db_query.c:337]:
db_do_update(): error while submitting query
Aug  7 14:18:57 sipapp01 proxy[16083]: ERROR: usrloc [ucontact.c:815]:
db_update_ucontact_addr(): updating database failed
Aug  7 14:18:57 sipapp01 proxy[16083]: ERROR: usrloc
[ucontact.c:1502]: update_ucontact(): failed to update database
Aug  7 14:18:57 sipapp01 proxy[16083]: ERROR: registrar [save.c:775]:
update_contacts(): failed to update contact


Also notice a lot of 'slow queries' on the logs of mysql.

Test system it's a  dual Intel(R) Xeon(R) CPU E5420  @ 2.50GHz, with 4
cores each CPU and 16Gb of RAM.

There is also errors about ACC inserts:

Aug  7 14:21:10 sipapp01 proxy[16085]: ERROR: db_mysql
[km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Lost
connection to MySQL server duri
ng query
Aug  7 14:21:10 sipapp01 proxy[16085]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug  7 14:21:10 sipapp01 proxy[16085]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database


Any hint about what could be wrong ?

Best regards


From jward01 at gmail.com  Fri Aug  8 02:58:49 2014
From: jward01 at gmail.com (Jeremy Ward)
Date: Fri, 8 Aug 2014 02:58:49 -0400
Subject: [Spce-user] Issues on Install
Message-ID: <CAFfjrWp=L=WgjHAyoAn8tjV8qr3nw6nUTsz3P0SgPjQ4ub_NPA@mail.gmail.com>

Greetings,

After two installation attempts, I have seen the installer appear to hang
(not complete) after several hours of execution.

System is a clean install of Linux debian 3.2.0-4-amd64 #1 SMP Debian
3.2.60-1+deb7u3 x86_64.

Below is the output of the installer script on the screen, and attached is
the ngcp-installer.log file.


######BEGIN SCREEN SCRAPE######
root at debian:~# dpkg -i ${PKG}
(Reading database ... 24568 files and directories currently installed.)
Preparing to replace ngcp-installer-ce 0.15.1.2+0~mr3.4.1.2 (using
ngcp-installer-latest.deb) ...
Unpacking replacement ngcp-installer-ce ...
Setting up ngcp-installer-ce (0.15.1.2+0~mr3.4.1.2) ...
root at debian:~# ngcp-installer
Welcome to Sipwise sip:provider installer.

This software comes WITH NO WARRANTY.
If you need SLA please consider upgrading to Sipwise sip:provider Pro
Edition.

This installation script is not intended to run in a shared system,
as it can add/delete/update existing configurations.
Please run this script only in a base install of 64 bit Debian 7.x on a
dedicated server.

Do you want to continue with the installation process? (y/n)y


Running as root... OK
Internet access... OK
Looks like a clean install... OK
Generate /etc/ngcp_nodename as spce
Check Debian version... OK
Check 64 bit capable system... OK
Updating package repository...OK
Installing ngcp-keyring package
OK
Installing package list. This might take several minutes depending on your
network connection...

######END SCREEN SCRAPE######

Any idea whats going on?

Thanks.

-- 
Jeremy D. Ward
Consulting Network Engineer
(954) 661-4965
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140808/476bbc6e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ngcp-installer.log
Type: application/octet-stream
Size: 6706 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140808/476bbc6e/attachment-0001.log>

From mprokop at sipwise.com  Fri Aug  8 04:19:29 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Fri, 8 Aug 2014 10:19:29 +0200
Subject: [Spce-user] Issues on Install
In-Reply-To: <CAFfjrWp=L=WgjHAyoAn8tjV8qr3nw6nUTsz3P0SgPjQ4ub_NPA@mail.gmail.com>
References: <CAFfjrWp=L=WgjHAyoAn8tjV8qr3nw6nUTsz3P0SgPjQ4ub_NPA@mail.gmail.com>
Message-ID: <2014-08-08T10-19-01@devnull.michael-prokop.at>

* Jeremy Ward [Fri Aug 08, 2014 at 02:58:49AM -0400]:

> After two installation attempts, I have seen the installer appear to hang
> (not complete) after several hours of execution.

> System is a clean install of Linux debian 3.2.0-4-amd64 #1 SMP Debian
> 3.2.60-1+deb7u3 x86_64.

> Below is the output of the installer script on the screen, and attached is
> the ngcp-installer.log file.

[...]
> Installing package list. This might take several minutes depending on your
> network connection...

What's inside /tmp/ngcp-installer.log?

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140808/a7923cfd/attachment-0001.asc>

From mstorck at voipgate.com  Fri Aug  8 07:02:57 2014
From: mstorck at voipgate.com (Marc Storck)
Date: Fri, 8 Aug 2014 11:02:57 +0000
Subject: [Spce-user] change of IP address
In-Reply-To: <53E21BB6.4030701@sipwise.com>
References: <44D6B68F-59E4-46E3-B2BD-65371E9220F7@voipgate.com>
 <53E21BB6.4030701@sipwise.com>
Message-ID: <C0469670-92EA-4786-B1E0-25749015DCE1@voipgate.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I tried that, but a few places still had the old IP address. Here is a list

/etc/default/ngcp-mediaproxy-ng-daemon
/etc/kamailio/lb/kamailio.cfg.custom
/etc/sems/etc/db_reg_agent.conf
/etc/sems/etc/reg_agent.conf
/etc/sems/sems.conf

Some of these files might be obsolete? as I have these system since version 2.8 and it is currently running 3.4.1

Can anybody advise on how to proceed?

Regards,

Marc

Do I have to 
On Aug 6, 2014, at 2:12 PM, Victor Seva <vseva at sipwise.com> wrote:

On 08/06/2014 02:02 PM, Marc Storck wrote:
Good afternoon,

I need to change the IP address of a system (*NOT* the domain name). I tried seraching for instruction but I wasn?t successful.

Could someone please point me into the right direction?

https://www.sipwise.com/doc/mr3.4.1/spce/ar01s05.html#_network_configuration



_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJT5K7rAAoJEBqZdpQUXtTCBckP/iwRVV4ZLNE2jKbqw+xwsOZ2
w+trGUAkxSqyYgw7OwYmfeV2tLWkaZrVozCB8130zEgqBvrWotpFr8AAIHNbcINs
RFepBlZa+LN86RxHeuxDpig3+wIZQRDDRbPjypsA5vM6bSP/0tfkvbp1GpcKE3/N
IjKxD/KQm872YV3s1NCj5RU4R2reeifID5nAog91mgPss8hlGovzRzVO/W1uDFHD
PqlMjuZ1CupWZ67t2cwyzrDac41BTTeFW2wIkEJSt6iS/+cB+4c+0csssDRU+FVR
ZbqFSN7fBkqbPCr4ZeAaedlAAzW4uNQuQ4ApHoetW/0KwpWvNlQjEv6PCMEgaZA8
vbEOXaCTcePCConQashDbjMBLh4HitE0awi0HVUO6MGZLsciun0gVYhemb/Dc9To
zGYjvD0KFGLT/oE0KJ/gF99jhmLZ+mtVMHRbnrIjf/tY5J0uRasB6Iw+cJ/NNoUF
LqtcjOrjmAy+tFkeQiHdMJJsCcEy8Q18Xatgxt9lGctKAm7iF8FrVLHr9mCWjafM
u5jKdhH0L1buxGr6nCorRFdGg8FOows9sBJl8bsdRP1AjM1/h05w7tzsRqGtrx+O
1pLHrqZT4JOurNuI6Hb8Rt3EwabMpM/xyj3XL8/cVr0T7VZMkyZEjN8ccdhW6pva
NdEGyyFvvtwNySpNESSa
=8Fw7
-----END PGP SIGNATURE-----

From dgrotti at sipwise.com  Fri Aug  8 09:07:46 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 08 Aug 2014 15:07:46 +0200
Subject: [Spce-user] change of IP address
In-Reply-To: <C0469670-92EA-4786-B1E0-25749015DCE1@voipgate.com>
References: <44D6B68F-59E4-46E3-B2BD-65371E9220F7@voipgate.com>
 <53E21BB6.4030701@sipwise.com>
 <C0469670-92EA-4786-B1E0-25749015DCE1@voipgate.com>
Message-ID: <53E4CBA2.4040801@sipwise.com>

Hi,
if you have to change the IP serving the Voip services, you just need to
change the shared_ip in your network.yml and then apply the changes.
The files you have mentioned are automatically generated by the ngcp
framework, and if you change the netwrok.yml, as soon as you apply the
changes those file will be regenerated.

Daniel






On 08/08/2014 01:02 PM, Marc Storck wrote:
> Hello,
>
> I tried that, but a few places still had the old IP address. Here is a
> list
>
> /etc/default/ngcp-mediaproxy-ng-daemon
> /etc/kamailio/lb/kamailio.cfg.custom
> /etc/sems/etc/db_reg_agent.conf
> /etc/sems/etc/reg_agent.conf
> /etc/sems/sems.conf
>
> Some of these files might be obsolete? as I have these system since
> version 2.8 and it is currently running 3.4.1
>
> Can anybody advise on how to proceed?
>
> Regards,
>
> Marc
>
> Do I have to
> On Aug 6, 2014, at 2:12 PM, Victor Seva <vseva at sipwise.com> wrote:
>
> On 08/06/2014 02:02 PM, Marc Storck wrote:
> Good afternoon,
>
> I need to change the IP address of a system (*NOT* the domain name). I
> tried seraching for instruction but I wasn?t successful.
>
> Could someone please point me into the right direction?
>
> https://www.sipwise.com/doc/mr3.4.1/spce/ar01s05.html#_network_configuration
>
>
>
> _______________________________________________
> 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/20140808/714b103d/attachment-0001.html>

From agranig at sipwise.com  Fri Aug  8 15:32:44 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Fri, 08 Aug 2014 21:32:44 +0200
Subject: [Spce-user] change of IP address
In-Reply-To: <53E4CBA2.4040801@sipwise.com>
References: <44D6B68F-59E4-46E3-B2BD-65371E9220F7@voipgate.com>
 <53E21BB6.4030701@sipwise.com>
 <C0469670-92EA-4786-B1E0-25749015DCE1@voipgate.com>
 <53E4CBA2.4040801@sipwise.com>
Message-ID: <53E525DC.5050900@sipwise.com>

Hi,

Newer version use /etc/ngcp-sems instead of /etc/sems, and they use
rtpengine instead if meadiaproxy-ng, and custom files are ignored
anyways, so all in all, you should be good.

Andreas

On 08/08/2014 03:07 PM, Daniel Grotti wrote:
> Hi,
> if you have to change the IP serving the Voip services, you just need to
> change the shared_ip in your network.yml and then apply the changes.
> The files you have mentioned are automatically generated by the ngcp
> framework, and if you change the netwrok.yml, as soon as you apply the
> changes those file will be regenerated.
> 
> Daniel
> 
> 
> 
> 
> 
> 
> On 08/08/2014 01:02 PM, Marc Storck wrote:
>> Hello,
>>
>> I tried that, but a few places still had the old IP address. Here is a
>> list
>>
>> /etc/default/ngcp-mediaproxy-ng-daemon
>> /etc/kamailio/lb/kamailio.cfg.custom
>> /etc/sems/etc/db_reg_agent.conf
>> /etc/sems/etc/reg_agent.conf
>> /etc/sems/sems.conf
>>
>> Some of these files might be obsolete? as I have these system since
>> version 2.8 and it is currently running 3.4.1
>>
>> Can anybody advise on how to proceed?
>>
>> Regards,
>>
>> Marc
>>
>> Do I have to
>> On Aug 6, 2014, at 2:12 PM, Victor Seva <vseva at sipwise.com> wrote:
>>
>> On 08/06/2014 02:02 PM, Marc Storck wrote:
>> Good afternoon,
>>
>> I need to change the IP address of a system (*NOT* the domain name). I
>> tried seraching for instruction but I wasn?t successful.
>>
>> Could someone please point me into the right direction?
>>
>> https://www.sipwise.com/doc/mr3.4.1/spce/ar01s05.html#_network_configuration
>>
>>
>>
>> _______________________________________________
>> 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
> 


From jchism2 at gmail.com  Fri Aug  8 15:36:43 2014
From: jchism2 at gmail.com (Jeremie Chism)
Date: Fri, 8 Aug 2014 14:36:43 -0500
Subject: [Spce-user] Block International Calls from Subscribers with US
	numbers
Message-ID: <CAG-pSShVobai8vRbFx5F-wKwCgKJTjwv0QsuXaL6CuPo740BWQ@mail.gmail.com>

I have some subscribers with US telephone numbers that I would like to
block calls to 011+ numbers.  I tried to use the NCOS with 011*  and it was
blocking other numbers that had 011 elsewhere in the number.  Is there a
definite way with either NCOS or rewrite rules that I can prevent
International calls from being sent to a peer from my US based customers.

Thanks

-- 
Jeremie Chism
Triton Communications
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140808/0652b963/attachment-0001.html>

From jward01 at gmail.com  Fri Aug  8 19:13:25 2014
From: jward01 at gmail.com (Jeremy Ward)
Date: Fri, 8 Aug 2014 19:13:25 -0400
Subject: [Spce-user] Fwd: Issues on Install
In-Reply-To: <2014-08-08T12-33-43@devnull.michael-prokop.at>
References: <CAFfjrWp=L=WgjHAyoAn8tjV8qr3nw6nUTsz3P0SgPjQ4ub_NPA@mail.gmail.com>
 <CAFfjrWq21g+OJ2GWMP+Uxw96-x=m6ZSEtBZL_2wz0X7wAhMv7Q@mail.gmail.com>
 <2014-08-08T12-07-06@devnull.michael-prokop.at>
 <CAFfjrWp07dnZo7EZEgLTzRPa8f6aM0YUcsT-Vg8ofFOaSfipOQ@mail.gmail.com>
 <2014-08-08T12-33-43@devnull.michael-prokop.at>
Message-ID: <CAFfjrWpYDk=QxJD8d8VL6TzO3ewo2J2W_0t2x0ff0Xz0DU5fDA@mail.gmail.com>

Hi Michael,

I performed a package installation test by running the apt-get install
[package]. I received the following prompt after instructing apt-get to
proceed (typing 'y'):

*Media change: please insert the disc labeled 'Debian GNU/Linux 7.6.0
_Wheezy_ - Official amd64 CD Binary-1 20140712-14:11' in the drive
'/media/cdrom/' and press enter*

I turns out that I had to remove the cdrom entry from the sources.list file
on the server. This was causing an issue on the system during spce
installation.

This is why the NetInstall CD is probably the best way to go, as sipwise
recommends ;-).


*But either way, here's how I fixed it*:

I removed the cdrom entry from sources.list by running the following:

sed -i '/cdrom/d' /etc/apt/sources.list

I then verified the removal of the cdrom entry from sourced.list and
verified the active repositories that were setup on the system by running
the following:

grep -v '#' /etc/apt/sources.list

This fixed the issues encountered during the previous two installation
attempts; install was completed in less than five minutes.


Hope that this is helpful to someone else.


Jeremy D. Ward, CWNE
(954) 661-4965
---------- Forwarded message ----------
From: "Michael Prokop" <mprokop at sipwise.com>
Date: Aug 8, 2014 6:34 AM
Subject: Re: Fwd: Issues on Install
To: "Jeremy Ward" <jward01 at gmail.com>
Cc:

Hi,

yes, the all-in-one ISO should be a good way, just let me know if
you should note any problems with it.

regards,
-mika-

* Jeremy Ward [Fri Aug 08, 2014 at 06:19:24AM -0400]:
> Thanks, Michael.

> It took approximately 20 mins to get to where the log ended, and waited
two
> hours longer. This is when I became concerned that there was an issue.

> I'm going to try the all-in-one ISO that you guys just released with
> version 3.4.1.

> Do you think that would that be the easiest way to do the installation at
> this point?

> Thanks Again,

> Jeremy D. Ward, CWNE
> (954) 661-4965
> On Aug 8, 2014 6:11 AM, "Michael Prokop" <mprokop at sipwise.com> wrote:

> > Hi,

> > there's nothing unusual in the log, besides that's it's truncated
> > before any actual issues arrised. ;)

> > It definitely takes some time to get past the package installation,
> > but while it's running you should see what's going on in
> > /tmp/ngcp-installer.log and by also checking process output (ps
> > auxwwww).

> > The CD issue *shouldn't* be a problem, but I can't answer that
> > without having further details about your system. As documented at
> > https://www.sipwise.com/doc/mr3.4.1/spce/ar01s04.html "Sipwise
> > recommends using the latest Netinstall ISO as installation medium."

> > So from my PoV rerun installer from a clean Debian system and if
> > stucks again share the installer logs to have a closer look. And use
> > the netinstall ISO instead this time. :)

> > regards,
> > -mika-

> > * Jeremy Ward [Fri Aug 08, 2014 at 05:57:15AM -0400]:
> > > Michael,

> > > Here's the original message with the log attached. I dont think it
made
> > it
> > > through the support list.

> > > I don't see anything other than packages being installed.

> > > The first log (truncated) had a few lines referring to the Debian
> > > installation CD (insert CD). Do you think its a repository issue?

> > > Its also worth mentioning that the first time I ran the installer, it
> > took
> > > awhile for it to eventually stall out... The operations underway
during
> > the
> > > install took much longer than I would have expected it to have taken
> > given
> > > server perfomance and Internet bandwidth (250Mbps).

> > > Thanks,

> > > Jeremy D. Ward, CWNE
> > > (954) 661-4965
> > > ---------- Forwarded message ----------
> > > From: "Jeremy Ward" <jward01 at gmail.com>
> > > Date: Aug 8, 2014 2:58 AM
> > > Subject: Issues on Install
> > > To: <spce-user at lists.sipwise.com>
> > > Cc:

> > > Greetings,

> > > After two installation attempts, I have seen the installer appear to
hang
> > > (not complete) after several hours of execution.

> > > System is a clean install of Linux debian 3.2.0-4-amd64 #1 SMP Debian
> > > 3.2.60-1+deb7u3 x86_64.

> > > Below is the output of the installer script on the screen, and
attached
> > is
> > > the ngcp-installer.log file.


> > > ######BEGIN SCREEN SCRAPE######
> > > root at debian:~# dpkg -i ${PKG}
> > > (Reading database ... 24568 files and directories currently
installed.)
> > > Preparing to replace ngcp-installer-ce 0.15.1.2+0~mr3.4.1.2 (using
> > > ngcp-installer-latest.deb) ...
> > > Unpacking replacement ngcp-installer-ce ...
> > > Setting up ngcp-installer-ce (0.15.1.2+0~mr3.4.1.2) ...
> > > root at debian:~# ngcp-installer
> > > Welcome to Sipwise sip:provider installer.

> > > This software comes WITH NO WARRANTY.
> > > If you need SLA please consider upgrading to Sipwise sip:provider Pro
> > > Edition.

> > > This installation script is not intended to run in a shared system,
> > > as it can add/delete/update existing configurations.
> > > Please run this script only in a base install of 64 bit Debian 7.x on
a
> > > dedicated server.

> > > Do you want to continue with the installation process? (y/n)y


> > > Running as root... OK
> > > Internet access... OK
> > > Looks like a clean install... OK
> > > Generate /etc/ngcp_nodename as spce
> > > Check Debian version... OK
> > > Check 64 bit capable system... OK
> > > Updating package repository...OK
> > > Installing ngcp-keyring package
> > > OK
> > > Installing package list. This might take several minutes depending on
> > your
> > > network connection...

> > > ######END SCREEN SCRAPE######

> > > Any idea whats going on?

> > > Thanks.

> > > --
> > > Jeremy D. Ward
> > > Consulting Network Engineer
> > > (954) 661-4965



> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.9 (GNU/Linux)

> > iEYEARECAAYFAlPkoi0ACgkQ2N9T+zficugbbwCeId4X/cFZRQZ4Lpg5vtWbEOxG
> > jgoAn3jEBDjhTmsUQZ3/CTMJ5/fXG1uR
> > =I5sR
> > -----END PGP SIGNATURE-----



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAlPkp54ACgkQ2N9T+zficujPogCePe4umPZeyElsUfl4WeyHgJW+
j5gAn1Ozgt/NxIgUXec5Ci0UZDf5YqZQ
=Cqs/
-----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140808/d501e9fe/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140808/d501e9fe/attachment-0001.asc>

From agranig at sipwise.com  Sat Aug  9 07:57:50 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Sat, 09 Aug 2014 13:57:50 +0200
Subject: [Spce-user] Block International Calls from Subscribers with US
 numbers
In-Reply-To: <CAG-pSShVobai8vRbFx5F-wKwCgKJTjwv0QsuXaL6CuPo740BWQ@mail.gmail.com>
References: <CAG-pSShVobai8vRbFx5F-wKwCgKJTjwv0QsuXaL6CuPo740BWQ@mail.gmail.com>
Message-ID: <53E60CBE.1020306@sipwise.com>

Hi,

NCOS use regular expressions, so you can create a blacklist and put ^011
there to block anything starting with 011. However, note that the ncos
check is done after incoming rewriting, so if you have rewrite rules in
place rewriting your 011, make sure to put the format into NCOS which
you expect after running through rewrite rules.

Andreas

On 08/08/2014 09:36 PM, Jeremie Chism wrote:
> I have some subscribers with US telephone numbers that I would like to
> block calls to 011+ numbers.  I tried to use the NCOS with 011*  and it
> was blocking other numbers that had 011 elsewhere in the number.  Is
> there a definite way with either NCOS or rewrite rules that I can
> prevent International calls from being sent to a peer from my US based
> customers.
> 
> Thanks
> 
> -- 
> Jeremie Chism
> Triton Communications
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From gary at netdiverse.com  Mon Aug 11 02:33:32 2014
From: gary at netdiverse.com (Gary Nieboer)
Date: Mon, 11 Aug 2014 00:33:32 -0600
Subject: [Spce-user] Peering Rules database vs. GUI Issue
In-Reply-To: <CAMXUi2ScE2u1tnGKSsbZUms+64yYTwAb-LsiKCfHJFAs1k7bsg@mail.gmail.com>
References: <CAMXUi2ScE2u1tnGKSsbZUms+64yYTwAb-LsiKCfHJFAs1k7bsg@mail.gmail.com>
Message-ID: <CAMXUi2S1DkXDE-EWG5N5UKxTqWLz19_T6iLV5mjj4sqU5K2u_g@mail.gmail.com>

I have another instance of the GUI not matching the database.

A peering rule ID 233 exists in the database & it was different than the
rule showing in the GUI.  Changing the rule in the GUI didn't adjust the
database.  Deleting the rule in the GUI didn't adjust the database.

Is there anything that can be done to "refresh" the GUI to reflect what is
actually in the database.

Also, is it safe to use mysql and delete the rule?

Thanks,

Gary

The Example:   In

--
Gary Nieboer


877-763-1014 Toll Free  |  801-657-5484 Utah  |  615-800-6946 Tennessee  |
801-694-6106 Mobile
gary at netdiverse.com  |   www.netdiverse.com


On Fri, Aug 1, 2014 at 2:55 PM, Gary Nieboer <gary at netdiverse.com> wrote:

>
> We have experienced a few issues with our "Peering Rules" on SPCE, 3.3.1.
>
> A created rule exists in the GUI, but when routing a call through the SBC,
> the call follows a route to a default peer rather than the peer indicated
> in the GUI.
>
> We recently did a comparison of what is shown in the database:  lcr_rules
>
>                             select * from lcr_rule;
>
>
> Here are a few lines from the database:   Some numbers are replaced with
> "`" and not fully shown:
>
> Note:  Rule 102 is missing from the database
>
>
> | id  | lcr_id | prefix | request_uri | from_uri | stopper | enabled |
> group_id |
>
> +-----+--------+--------+-------------+----------+---------+---------+----------+
> | 101 |      1 |        | ~~~~~20088  | NULL     |       0 |       1 |
>   23 |
> | 105 |      1 |        | ~~~~~20186  | NULL     |       0 |       1 |
>   23 |
> | 106 |      1 |        | ~~~~~74891  | NULL     |       0 |       1 |
>   23 |
>
>
>
> Now, here is a screenshot of the GUI for the same rules:
> Note:  Rule 102 exists under peer group 23 for the GUI.
> [image: Inline image 1]
>
>
>
> It appears we should trust the data in the database and not the GUI, but
> I'm assuming it is not desired behavior for the GUI and database to reflect
> different info.
>
> If you would like more information, we can share it.
>
> Please let me know if there is anything we can do to ensure the GUI
> reflects the actual activity of the database and ngcp/kamailio.
>
> Thanks,
>
> Gary
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140811/dce0f21a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 30444 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140811/dce0f21a/attachment-0001.png>

From agranig at sipwise.com  Mon Aug 11 04:09:50 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Mon, 11 Aug 2014 10:09:50 +0200
Subject: [Spce-user] Peering Rules database vs. GUI Issue
In-Reply-To: <CAMXUi2S1DkXDE-EWG5N5UKxTqWLz19_T6iLV5mjj4sqU5K2u_g@mail.gmail.com>
References: <CAMXUi2ScE2u1tnGKSsbZUms+64yYTwAb-LsiKCfHJFAs1k7bsg@mail.gmail.com>
 <CAMXUi2S1DkXDE-EWG5N5UKxTqWLz19_T6iLV5mjj4sqU5K2u_g@mail.gmail.com>
Message-ID: <53E87A4E.7030207@sipwise.com>

Hi,

Can you share some information about the history of your setup? Which
version did you use for the initial setup? Any things you remember doing
to your peerings, like deleting groups or something?

There have been some issues with older versions couple of months ago in
the triggers synchronizing the databases provisioning and kamailio, but
they have been fixed in 3.1 already.

Andreas

On 08/11/2014 08:33 AM, Gary Nieboer wrote:
> I have another instance of the GUI not matching the database.
> 
> A peering rule ID 233 exists in the database & it was different than the
> rule showing in the GUI.  Changing the rule in the GUI didn't adjust the
> database.  Deleting the rule in the GUI didn't adjust the database.
> 
> Is there anything that can be done to "refresh" the GUI to reflect what
> is actually in the database.
> 
> Also, is it safe to use mysql and delete the rule?
> 
> Thanks,
> 
> Gary
> 
> The Example:   In 
> 
> --
> Gary Nieboer
> 
> 
> 877-763-1014 Toll Free  |  801-657-5484 Utah  |  615-800-6946 Tennessee 
> | 801-694-6106 Mobile
> gary at netdiverse.com <mailto:gary at netdiverse.com>  |   www.netdiverse.com
> <http://www.netdiverse.com/>
> 
> 
> On Fri, Aug 1, 2014 at 2:55 PM, Gary Nieboer <gary at netdiverse.com
> <mailto:gary at netdiverse.com>> wrote:
> 
> 
>     We have experienced a few issues with our "Peering Rules" on SPCE,
>     3.3.1.
> 
>     A created rule exists in the GUI, but when routing a call through
>     the SBC, the call follows a route to a default peer rather than the
>     peer indicated in the GUI.
> 
>     We recently did a comparison of what is shown in the database:
>      lcr_rules
> 
>                                 select * from lcr_rule;
> 
> 
>     Here are a few lines from the database:   Some numbers are replaced
>     with "`" and not fully shown:
> 
>     Note:  Rule 102 is missing from the database
> 
> 
>     | id  | lcr_id | prefix | request_uri | from_uri | stopper | enabled
>     | group_id |
>     +-----+--------+--------+-------------+----------+---------+---------+----------+
>     | 101 |      1 |        | ~~~~~20088  | NULL     |       0 |       1
>     |       23 |
>     | 105 |      1 |        | ~~~~~20186  | NULL     |       0 |       1
>     |       23 |
>     | 106 |      1 |        | ~~~~~74891  | NULL     |       0 |       1
>     |       23 |
> 
> 
> 
>     Now, here is a screenshot of the GUI for the same rules:
>     Note:  Rule 102 exists under peer group 23 for the GUI.
>     Inline image 1
> 
> 
> 
>     It appears we should trust the data in the database and not the GUI,
>     but I'm assuming it is not desired behavior for the GUI and database
>     to reflect different info.
> 
>     If you would like more information, we can share it.
> 
>     Please let me know if there is anything we can do to ensure the GUI
>     reflects the actual activity of the database and ngcp/kamailio.
> 
>     Thanks,
> 
>     Gary
> 
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From rabs at dimension-virtual.com  Mon Aug 11 09:37:47 2014
From: rabs at dimension-virtual.com (=?iso-8859-1?B?UmHDumw=?= Alexis Betancor Santana)
Date: Mon, 11 Aug 2014 14:37:47 +0100
Subject: [Spce-user] MySQL errors
In-Reply-To: <20140807121952.GA23093@salma.divi.prv>
References: <20140807121952.GA23093@salma.divi.prv>
Message-ID: <20140811133747.GA4724@salma.divi.prv>

On Thu, Aug 07, 2014 at 01:19:53PM +0100, (UNTRUSTED, sender <spce-user-bounces at lists.sipwise.com> is not authenticated) wrote:
> Hi all, since we upgrades a test system from 3.2 to mr3.3 and
> yesterday to mr3.4.1 this is getting worst:

Everyone on holidays? ...

Best regards


From dgrotti at sipwise.com  Mon Aug 11 11:22:15 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Mon, 11 Aug 2014 17:22:15 +0200
Subject: [Spce-user] MySQL errors
In-Reply-To: <20140811133747.GA4724@salma.divi.prv>
References: <20140807121952.GA23093@salma.divi.prv>
 <20140811133747.GA4724@salma.divi.prv>
Message-ID: <53E8DFA7.3010308@sipwise.com>

Hi,
it's hard to say. Mysql sometime get unreachable.
What is the state of your system usage ? Load, CPU, Mem ?

Daniel




On 08/11/2014 03:37 PM, Ra?l Alexis Betancor Santana wrote:
> On Thu, Aug 07, 2014 at 01:19:53PM +0100, (UNTRUSTED, sender <spce-user-bounces at lists.sipwise.com> is not authenticated) wrote:
>> Hi all, since we upgrades a test system from 3.2 to mr3.3 and
>> yesterday to mr3.4.1 this is getting worst:
> Everyone on holidays? ...
>
> Best regards
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user



From arpagon+sipwise at gmail.com  Mon Aug 11 12:51:09 2014
From: arpagon+sipwise at gmail.com (sebastian rojo)
Date: Mon, 11 Aug 2014 11:51:09 -0500
Subject: [Spce-user]  SBC is broken in mr3.4.1
Message-ID: <CAH7ArYweLeq=dSxXcTN6nEDJxXGC75FCkvumqpdgJd4Wioxieg@mail.gmail.com>

HI All,

Currently I have on SPCE in SBC mode, In version

cat /etc/sipwise_ngcp_version
> System installed. NGCP version mr3.3.2 on 2014-07-23 11:12:57


Everything is OK.

Since we upgrades a test system from 3.4.1. The SPCE got a problem whit the
Suscriber *Remote Authentication. *


   - Problem with the incoming Calls.
   - Problem with the remote register.


I decided to try a fresh installation


>
* root at sbc:~# cat /etc/sipwise_ngcp_version System installed. NGCP version
mr3.4.1 on 2014-08-06 12:05:52*
I got the same issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140811/59dda8f9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log.tar.gz
Type: application/x-gzip
Size: 1821190 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140811/59dda8f9/attachment-0001.gz>

From agranig at sipwise.com  Mon Aug 11 16:36:20 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Mon, 11 Aug 2014 22:36:20 +0200
Subject: [Spce-user] SBC is broken in mr3.4.1
In-Reply-To: <CAH7ArYweLeq=dSxXcTN6nEDJxXGC75FCkvumqpdgJd4Wioxieg@mail.gmail.com>
References: <CAH7ArYweLeq=dSxXcTN6nEDJxXGC75FCkvumqpdgJd4Wioxieg@mail.gmail.com>
Message-ID: <53E92944.1050409@sipwise.com>

Hi,

On 08/11/2014 06:51 PM, sebastian rojo wrote:
> Since we upgrades a test system from 3.4.1. The SPCE got a problem whit
> the Suscriber *Remote Authentication. *
> *
> 
>   * Problem with the incoming Calls.

Which problems?

>   * Problem with the remote register.

Again, which problems? What do the logs say for the particular scenarios
(e.g. for one particular failing incoming call, or one particular
failing outbound registration)?

Please don't expect anyone to look at 1.7MB log files without any hints.

Andreas


From agranig at sipwise.com  Mon Aug 11 16:37:53 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Mon, 11 Aug 2014 22:37:53 +0200
Subject: [Spce-user] MySQL errors
In-Reply-To: <20140811133747.GA4724@salma.divi.prv>
References: <20140807121952.GA23093@salma.divi.prv>
 <20140811133747.GA4724@salma.divi.prv>
Message-ID: <53E929A1.6010906@sipwise.com>



On 08/11/2014 03:37 PM, Ra?l Alexis Betancor Santana wrote:
> On Thu, Aug 07, 2014 at 01:19:53PM +0100, (UNTRUSTED, sender <spce-user-bounces at lists.sipwise.com> is not authenticated) wrote:
>> Hi all, since we upgrades a test system from 3.2 to mr3.3 and
>> yesterday to mr3.4.1 this is getting worst:
> 
> Everyone on holidays? ...

Probably nobody on the list has ever encountered the same problem? As
Daniel said, it's not really SPCE related, rather than a problem of your
MySQL db dying from time to time?

Andreas


From dgrotti at sipwise.com  Tue Aug 12 11:42:26 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Tue, 12 Aug 2014 17:42:26 +0200
Subject: [Spce-user] SBC is broken in mr3.4.1
In-Reply-To: <CAH7ArYweLeq=dSxXcTN6nEDJxXGC75FCkvumqpdgJd4Wioxieg@mail.gmail.com>
References: <CAH7ArYweLeq=dSxXcTN6nEDJxXGC75FCkvumqpdgJd4Wioxieg@mail.gmail.com>
Message-ID: <53EA35E2.1070704@sipwise.com>

Hi,

Aug 11 02:50:37 sbc proxy[5162]: NOTICE: <script>: New request -
M=INVITE R=sip:+972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:+972598431309 at 181.143.4.67 IP=31.223.182.35:24708 (127.0.0.1:5060)
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:37 sbc proxy[5162]: NOTICE: <script>: Authentication
failed, no credentials - R=sip:+972598431309 at 181.143.4.67
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:37 sbc proxy[5156]: NOTICE: <script>: New request -
M=INVITE R=sip:+972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:+972598431309 at 181.143.4.67 IP=31.223.182.35:24708 (127.0.0.1:5060)
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:37 sbc proxy[5156]: NOTICE: <script>: Authentication
failed, invalid user - R=sip:+972598431309 at 181.143.4.67
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:37 sbc proxy[5152]: NOTICE: <script>: New request -
M=INVITE R=sip:+972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:+972598431309 at 181.143.4.67 IP=31.223.182.35:24708 (127.0.0.1:5060)
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:37 sbc proxy[5152]: NOTICE: <script>: Authentication
failed, invalid user - R=sip:+972598431309 at 181.143.4.67
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:38 sbc proxy[5154]: NOTICE: <script>: New request -
M=INVITE R=sip:+972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:+972598431309 at 181.143.4.67 IP=31.223.182.35:24708 (127.0.0.1:5060)
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:38 sbc proxy[5154]: NOTICE: <script>: Authentication
failed, invalid user - R=sip:+972598431309 at 181.143.4.67
ID=b7f41e099d1aeff3e8bde957b3d391f3
Aug 11 02:50:40 sbc proxy[5158]: NOTICE: <script>: New request -
M=INVITE R=sip:00972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:00972598431309 at 181.143.4.67 IP=31.223.182.35:24708
(127.0.0.1:5060) ID=45c99da5a926916337e849e4b7860f53
Aug 11 02:50:40 sbc proxy[5158]: NOTICE: <script>: Authentication
failed, no credentials - R=sip:00972598431309 at 181.143.4.67
ID=45c99da5a926916337e849e4b7860f53
Aug 11 02:50:43 sbc proxy[5153]: NOTICE: <script>: New request -
M=INVITE R=sip:000972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:000972598431309 at 181.143.4.67 IP=31.223.182.35:24708
(127.0.0.1:5060) ID=a18a4b57737466201e0528413cccb1ae
Aug 11 02:50:43 sbc proxy[5153]: NOTICE: <script>: Authentication
failed, no credentials - R=sip:000972598431309 at 181.143.4.67
ID=a18a4b57737466201e0528413cccb1ae
Aug 11 02:50:44 sbc proxy[5161]: NOTICE: <script>: New request -
M=INVITE R=sip:005972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:005972598431309 at 181.143.4.67 IP=31.223.182.35:24708
(127.0.0.1:5060) ID=b37a727b93c3521c2767e54b8946be44
Aug 11 02:50:44 sbc proxy[5161]: NOTICE: <script>: Authentication
failed, no credentials - R=sip:005972598431309 at 181.143.4.67
ID=b37a727b93c3521c2767e54b8946be44
Aug 11 02:50:45 sbc proxy[5155]: NOTICE: <script>: New request -
M=INVITE R=sip:007972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:007972598431309 at 181.143.4.67 IP=31.223.182.35:24708
(127.0.0.1:5060) ID=06c4713e873b39c43aa9087e50bea15c
Aug 11 02:50:45 sbc proxy[5155]: NOTICE: <script>: Authentication
failed, no credentials - R=sip:007972598431309 at 181.143.4.67
ID=06c4713e873b39c43aa9087e50bea15c
Aug 11 02:50:46 sbc proxy[5156]: NOTICE: <script>: New request -
M=INVITE R=sip:009972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:009972598431309 at 181.143.4.67 IP=31.223.182.35:24708
(127.0.0.1:5060) ID=06c4713e873b39c43aa9087e50bea15c
Aug 11 02:50:46 sbc proxy[5156]: NOTICE: <script>: Authentication
failed, no credentials - R=sip:009972598431309 at 181.143.4.67
ID=06c4713e873b39c43aa9087e50bea15c
Aug 11 02:50:47 sbc proxy[5161]: NOTICE: <script>: New request -
M=INVITE R=sip:0007972598431309 at 181.143.4.67 F=sip:100 at 181.143.4.67
T=sip:0007972598431309 at 181.143.4.67 IP=31.223.182.35:24708
(127.0.0.1:5060) ID=1ffd12f2d18170c4087d0262731ebfaf


INVITE doesn't contain credentials.
I can see also and "invalid user" message. Please check your INVITE
credentials.

Aug 11 00:09:13 sbc lb[6692]: NOTICE: <script>: New request - M=REGISTER
R=sip:sapian.com.co F=sip:217 at sapian.com.co T=sip:217 at sapian.com.co
IP=udp:181.143.4.66:5060 ID=40db1521-dcfbb9a1 at 172.16.252.238
Aug 11 00:09:13 sbc lb[6692]: NOTICE: <script>: Relaying request,
du='sip:127.0.0.1:5062', fs='udp:127.0.0.1:5060' - R=sip:sapian.com.co
ID=40db1521-dcfbb9a1 at 172.16.252.238
Aug 11 00:09:13 sbc lb[6699]: NOTICE: <script>: Reply from Inbound -
S=100 - Trying M=REGISTER IP=udp:127.0.0.1:5062
ID=40db1521-dcfbb9a1 at 172.16.252.238
Aug 11 00:09:13 sbc lb[6699]: NOTICE: <script>: Sending reply,
fs='udp:181.143.4.67:5060' - ID=40db1521-dcfbb9a1 at 172.16.252.238
Aug 11 00:09:13 sbc lb[6699]: NOTICE: <script>: Reply from Inbound -
S=403 - Domain not served here M=REGISTER IP=udp:127.0.0.1:5062
ID=40db1521-dcfbb9a1 at 172.16.252.238



Are you registering to a domain which doesn't exist ?



Again - as Andreas said - if you don't point us out to your problems we
can't support you.
Please provide information regarding your problem, exact CallID,
caller/callee, expected behaviour, current behaviour.


Regards,

Daniel




On 08/11/2014 06:51 PM, sebastian rojo wrote:
> HI All, 
>
> Currently I have on SPCE in SBC mode, In version  
>
>     cat /etc/sipwise_ngcp_version 
>     System installed. NGCP version mr3.3.2 on 2014-07-23 11:12:57
>
>
> Everything is OK.
>
> Since we upgrades a test system from 3.4.1. The SPCE got a problem
> whit the Suscriber *Remote Authentication. *
> *
> *
>
>   * Problem with the incoming Calls.
>   * Problem with the remote register.
>
>
> I decided to try a fresh installation
>
> *
>
>     root at sbc:~# cat /etc/sipwise_ngcp_version 
>     System installed. NGCP version mr3.4.1 on 2014-08-06 12:05:52
>
>
> *
> I got the same issues.
>
>
>
>
> _______________________________________________
> 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/20140812/e383847a/attachment-0001.html>

From arpagon+sipwise at gmail.com  Tue Aug 12 11:52:46 2014
From: arpagon+sipwise at gmail.com (sebastian rojo)
Date: Tue, 12 Aug 2014 10:52:46 -0500
Subject: [Spce-user] SBC is broken in mr3.4.1
In-Reply-To: <53EA35E2.1070704@sipwise.com>
References: <CAH7ArYweLeq=dSxXcTN6nEDJxXGC75FCkvumqpdgJd4Wioxieg@mail.gmail.com>
 <53EA35E2.1070704@sipwise.com>
Message-ID: <CAH7ArYyeFk3bVqheZBnS6dh6b_Nzo2s_P2BGUg+7K_eeMUggsQ@mail.gmail.com>

Andreas, Daniel You are Rigth.

I'm currently compiling the most accurate information to properly report mi
case.

Thanks for the reply.

?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140812/e173d3ca/attachment-0001.html>

From rabs at dimension-virtual.com  Thu Aug 14 07:22:50 2014
From: rabs at dimension-virtual.com (rabs at dimension-virtual.com)
Date: Thu, 14 Aug 2014 13:22:50 +0200 (CEST)
Subject: [Spce-user] MySQL errors
In-Reply-To: <53E8DFA7.3010308@sipwise.com>
References: <20140807121952.GA23093@salma.divi.prv>
 <20140811133747.GA4724@salma.divi.prv> <53E8DFA7.3010308@sipwise.com>
Message-ID: <55580.85.155.242.185.1408015370.squirrel@www.rodriguezfeo.es>

> Hi,
> it's hard to say. Mysql sometime get unreachable.
> What is the state of your system usage ? Load, CPU, Mem ?
>
> Daniel
>

Found the problem ... a collecd daemon doing strange things ... overloading the
system and putting IO soo high that MySQL fails randomly.

Now have to review what that collecd was doing wrong.

Best regards



From kmasse at questblue.com  Thu Aug 14 07:33:26 2014
From: kmasse at questblue.com (Kevin Masse)
Date: Thu, 14 Aug 2014 07:33:26 -0400
Subject: [Spce-user] Subscriber Alias Entries in Database
References: <CEEE718799582B47A55D7897DCB264FC3F5E18@bvusaex.bestvoipusa.local><53C652BD.7000707@sipwise.com>
 <CEEE718799582B47A55D7897DCB264FC3F5E65@bvusaex.bestvoipusa.local>
 <CEEE718799582B47A55D7897DCB264FC3F5F7F@bvusaex.bestvoipusa.local> 
Message-ID: <CEEE718799582B47A55D7897DCB264FC3F61AD@bvusaex.bestvoipusa.local>

Hello Andraes, have you had a chance to review the two questions stated
below?

Our dev team is seeking to close out this issue we are having.

Thank you
Kevin




-----Original Message-----
From: Kevin Masse 
Sent: Wednesday, August 06, 2014 7:55 AM
To: Kevin Masse; 'Andreas Granig'; 'spce-user at lists.sipwise.com'
Subject: RE: [Spce-user] Subscriber Alias Entries in Database

Hello, I was wondering if there was a response to this that I missed.
There are two specific questions we are trying to answer.


Thank you
Kevin



-----Original Message-----
From: Kevin Masse 
Sent: Thursday, July 24, 2014 10:02 AM
To: Kevin Masse; Andreas Granig; spce-user at lists.sipwise.com
Subject: RE: [Spce-user] Subscriber Alias Entries in Database

Andraes one additional scenario has come up based on our last thread:
I wanted to post to the group the question from our dev team:

****  Begin Comment ****
It is going to be a long post because I can't explain in a short
message. I'll provide some example to explain what I mean. 

We have SIP named QBATRUNK.  If you open administrator page
(https://DOMAIN:1443/subscriber/detail?subscriber_id=395) you can see
there following info:

Contract ID (405) - This is main ID which we store in (customer site -
not part of Sipwise it is our Database) . All operations like
lock/unlock SIP, add/remove DID using the ID in it request to API.

Subscriber ID (395) - I can call it internal info, it is not used in any
request to Sipwise API but to make direct request to Sipwise DB I have
to use it.

I routed 3384066 DID to the SIP to work with the example. 
According to previous instructions we use two databases to store
aliases. Now I'll show you request to retrieve the DID from Sipwise DB.

First I use billing DB. Let's retrieve Subscriber ID (we do not know it
when call DB directly). I use voip_subscribers table which stores the
info.

mysql> select * from voip_subscribers where contract_id = 405;
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+
| id | contract_id | uuid | username | domain_id | status |
primary_number_id | external_id |
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+
| 395 | 405 | 14a58c84-c83e-4673-9d10-361a1a6b990e | QBATRUNK | 1 |
active | NULL | NULL |
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+

OK you can see that I receive id 395. We need it.

 

Let's get DIDs info from voip_numbers, DB - 

mysql> select * from voip_numbers where subscriber_id = 395;
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+
| id | cc | ac | sn | reseller_id | subscriber_id | status | ported |
list_timestamp |
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+
| 2119 | 1 | 910 | 3384066 | NULL | 395 | active | 1 | 2014-07-22
18:32:16 |
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+

Everything is OK we got it as expected. Lets' get DID info from second
DB (provisioning) I'll do it using DID number

mysql> select * from voip_dbaliases where username like '%3384066%';
+------+-------------+-----------+---------------+
| id | username | domain_id | subscriber_id |
+------+-------------+-----------+---------------+
| 2821 | 19103384066 | 3 | 398 |

As you can see subscriber_id in the table does not corresponds to the
subscriber_id which we retrieve from billing DB. That is the question
for me.

I found that the subscriber_id is stored in voip_dbaliases table but the
ID does not corresponds to the subscriber_id from billing table.




************* 2 questions below ****************





Question 1
I do not understand how subscriber_id in billing DB (table voip_numbers)
related with subscriber_id in provisioning DB (table voip_dbaliases ).

Question 2
Another question. I found that DIDs info is stored in voip_dbaliases
table (provisioning) but I did not told to creae the record by VoIP
specialist.


mysql> select * from voip_dbaliases where username like '%3384066%';
+------+-------------+-----------+---------------+
| id | username | domain_id | subscriber_id |
+------+-------------+-----------+---------------+
| 2821 | 19103384066 | 3 | 398 |
+------+-------------+-----------+---------------+

Hopefully I explained my questions clear. If not please let me know

Thanks,
*** End Comment from DEV ***



In conclusion Andreas do you think there is a proper answer for the
above Question 1 and Question 2?
Thank you
Kevin 





-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Kevin Masse
Sent: Wednesday, July 16, 2014 8:56 AM
To: Andreas Granig; spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Subscriber Alias Entries in Database

Thank you Andreas, I appreciate the detailed response.  Works as
described.
Kevin



-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Andreas Granig
Sent: Wednesday, July 16, 2014 6:24 AM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Subscriber Alias Entries in Database

Hi,

On 07/15/2014 03:05 PM, Kevin Masse wrote:

> **  Current operation:   We use SOAP to add alias numbers to a
subscriber 
> 
> Requested operation:  We would like to write a new alias number for a 
> subscriber directly to the database.

As long as you make sure to write it to both billing.voip_numbers and
provisioning.voip_dbaliases, it should be fine.

Andreas

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/listinfo/spce-user

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/listinfo/spce-user


From jchism2 at gmail.com  Sun Aug 17 04:41:37 2014
From: jchism2 at gmail.com (Jeremie Chism)
Date: Sun, 17 Aug 2014 03:41:37 -0500
Subject: [Spce-user] Audio proxy
Message-ID: <CAG-pSSj1Q5rO0hx_VfQD2G+BoByZa3jrq1ANV3dZ0sOLkz2uSg@mail.gmail.com>

I know by default the audio proxy is set to always. Is there a setting that
would make the system automatically proxy the audio if the registration is
natted and not proxy if it is not?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140817/3bb80a8a/attachment-0001.html>

From george.mason at xoomtalk.com  Sun Aug 17 17:29:43 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Sun, 17 Aug 2014 22:29:43 +0100
Subject: [Spce-user] Assistance getting set up on AWS
Message-ID: <53F11EC7.1050203@xoomtalk.com>

Hi,

Am new to Sip:provider but liking what I read so far. I've been trying
to get this working on AWS but struggling to do so, and have been
advised to post my experience here - so here goes:

I have been trying to build a Debian Squeeze AMI and install the stable
release of your product (v2.8) by following the quick install guide and
handbook. I have been building my EC2 instances using the following AMI:
ami-f0a97498. The install seems to run for some time, downloading
components etc. but it then stops without error, or saying that it has
successfully completed. I have attached the ngcp-installer.log as I
tried to install the software last time.

Would be grateful of any assistance or comment from the community.

Many thanks

George Mason
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ngcp-installer.log.zip
Type: application/zip
Size: 49216 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140817/5c321ee2/attachment-0001.zip>

From jbonilla at sipwise.com  Sun Aug 17 19:07:16 2014
From: jbonilla at sipwise.com (Jon Bonilla (Manwe))
Date: Mon, 18 Aug 2014 01:07:16 +0200
Subject: [Spce-user] Assistance getting set up on AWS
In-Reply-To: <53F11EC7.1050203@xoomtalk.com>
References: <53F11EC7.1050203@xoomtalk.com>
Message-ID: <20140818010716.5fcd7689@multivac>

El Sun, 17 Aug 2014 22:29:43 +0100
George Mason <george.mason at xoomtalk.com> escribi?:

> Hi,
> 
> Am new to Sip:provider but liking what I read so far. I've been trying
> to get this working on AWS but struggling to do so, and have been
> advised to post my experience here - so here goes:
> 
> I have been trying to build a Debian Squeeze AMI and install the stable
> release of your product (v2.8) by following the quick install guide and
> handbook. I have been building my EC2 instances using the following AMI:
> ami-f0a97498. The install seems to run for some time, downloading
> components etc. but it then stops without error, or saying that it has
> successfully completed. I have attached the ngcp-installer.log as I
> tried to install the software last time.
> 
> Would be grateful of any assistance or comment from the community.
> 
> Many thanks
> 
> George Mason



You have the error and a suggested action at the end of the logfile:

Error: Generating /etc/asterisk/iax.conf based
on /etc/ngcp-config/templates//etc/asterisk/iax.conf.tt2: FAILED NOTE: Check
those files for valid syntax and
encoding: /etc/ngcp-config/templates//etc/asterisk/iax.conf.tt2 /etc/ngcp-config/config.yml
/etc/ngcp-config/network.yml
/etc/ngcp-config/constants.yml
Running /usr/share/ngcp-ngcpcfg/helper/tt2-wrapper <file> should provide more
details.


Looks like one of the configuration templates does not have a valid syntax and
it can't be created.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140818/0cf2604c/attachment-0001.asc>

From mprokop at sipwise.com  Mon Aug 18 04:22:50 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Mon, 18 Aug 2014 10:22:50 +0200
Subject: [Spce-user] Assistance getting set up on AWS
In-Reply-To: <53F11EC7.1050203@xoomtalk.com>
References: <53F11EC7.1050203@xoomtalk.com>
Message-ID: <2014-08-18T10-18-23@devnull.michael-prokop.at>

* George Mason [Sun Aug 17, 2014 at 10:29:43PM +0100]:

> Am new to Sip:provider but liking what I read so far. I've been trying
> to get this working on AWS but struggling to do so, and have been
> advised to post my experience here - so here goes:

> I have been trying to build a Debian Squeeze AMI and install the stable
> release of your product (v2.8) by following the quick install guide and
> handbook. I have been building my EC2 instances using the following AMI:
> ami-f0a97498. The install seems to run for some time, downloading
> components etc. but it then stops without error, or saying that it has
> successfully completed. I have attached the ngcp-installer.log as I
> tried to install the software last time.

> Would be grateful of any assistance or comment from the community.

We don't provide AWS support for the 2.8 release, instead we
provide a supported AMI for our latest release, see
http://lists.sipwise.com/pipermail/spce-user/2014-August/007061.html
for further information. Please let us know if you should notice any
problems with it.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140818/25a09577/attachment-0001.asc>

From george.mason at xoomtalk.com  Mon Aug 18 07:47:30 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Mon, 18 Aug 2014 12:47:30 +0100
Subject: [Spce-user] Assistance getting set up on AWS
In-Reply-To: <2014-08-18T10-18-23@devnull.michael-prokop.at>
References: <53F11EC7.1050203@xoomtalk.com>
 <2014-08-18T10-18-23@devnull.michael-prokop.at>
Message-ID: <53F1E7D2.900@xoomtalk.com>

On 18/08/14 09:22, Michael Prokop wrote:
> We don't provide AWS support for the 2.8 release, instead we
> provide a supported AMI for our latest release, see
> http://lists.sipwise.com/pipermail/spce-user/2014-August/007061.html
> for further information. Please let us know if you should notice any
> problems with it.
>
> regards,
> -mika-
Hi mika

Many thanks - problem is that I need to use this on the East Coast
availability zone - seems the AMI is only available on EU West?

Kind regards

George


From mprokop at sipwise.com  Mon Aug 18 08:33:01 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Mon, 18 Aug 2014 14:33:01 +0200
Subject: [Spce-user] Assistance getting set up on AWS
In-Reply-To: <53F1E7D2.900@xoomtalk.com>
References: <53F11EC7.1050203@xoomtalk.com>
 <2014-08-18T10-18-23@devnull.michael-prokop.at>
 <53F1E7D2.900@xoomtalk.com>
Message-ID: <2014-08-18T14-22-11@devnull.michael-prokop.at>

* George Mason [Mon Aug 18, 2014 at 12:47:30PM +0100]:
> On 18/08/14 09:22, Michael Prokop wrote:
> > We don't provide AWS support for the 2.8 release, instead we
> > provide a supported AMI for our latest release, see
> > http://lists.sipwise.com/pipermail/spce-user/2014-August/007061.html
> > for further information. Please let us know if you should notice any
> > problems with it.

> Many thanks - problem is that I need to use this on the East Coast
> availability zone - seems the AMI is only available on EU West?

We've just provided the ngcp-ce-mr3.4.1 AMI to the us-east-1 region,
it's available as AMI ID ami-c2ad72aa there now.

If anyone should need the AMI in yet another zone please let us
know, I'll discuss within our team how we plan to handle this in the
future.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140818/a81f431d/attachment-0001.asc>

From george.mason at xoomtalk.com  Tue Aug 19 07:01:09 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Tue, 19 Aug 2014 12:01:09 +0100
Subject: [Spce-user] Calls drop after 30 secs
Message-ID: <53F32E75.7070700@xoomtalk.com>

Hi,

I am having an issue with the SPCE Amazon EC2 image. I have configured
the server to forward all calls to a SIP provider with a couple of IP
handsets registered as subscribers. I can get a call to go through to
the PSTN and audio in both directions, but the call appears to drop
after approx. 30 secs.

I have run a UDP trace of the signalling and it looks like SPCE drops
the call, I found the following in the logs:

rtp.log
Aug 19 10:54:53 ip-10-237-180-106 rtpengine[26167]: Got valid command
from 127.0.0.1:56413: delete - { "call-id":
"60174c70-66e7d6e1 at 192.168.100.136", "received-from": [ "IP4",
"127.0.0.1" ], "from-tag": "317FA286-53F32CDB000A6E08-C56FB700",
"to-tag": "2cfee724f53bdbbdo0", "command": "delete" }

sems.log
Aug 19 10:54:53 ip-10-237-180-106 ngcp-sems[26328]: [#7f11c4ef3700]
[update_uac_request, trans_layer.cpp:2047] WARNING:  While sending 200
ACK: no matching transaction

Looks like either Sems or Asterisk is telling Kamailio to drop the call
- not sure what's going on here? Grateful of any feedback.

Thanks

George


From apogrebennyk at sipwise.com  Tue Aug 19 07:11:01 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Tue, 19 Aug 2014 13:11:01 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F32E75.7070700@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com>
Message-ID: <53F330C5.1040404@sipwise.com>

Hi,
what does your /etc/ngcp-config/network.yml look like? You should use
your Elastic IP as advertised_address. I think AMI configures that by
default.

Could you provide the kamailio-proxy.log, kamailio-lb.log and complete
trace? I mean also messages inside spce (lb,proxy,sems).

Regards.
Andrew

On 08/19/2014 01:01 PM, George Mason wrote:
> Hi,
> 
> I am having an issue with the SPCE Amazon EC2 image. I have configured
> the server to forward all calls to a SIP provider with a couple of IP
> handsets registered as subscribers. I can get a call to go through to
> the PSTN and audio in both directions, but the call appears to drop
> after approx. 30 secs.
> 
> I have run a UDP trace of the signalling and it looks like SPCE drops
> the call, I found the following in the logs:
> 
> rtp.log
> Aug 19 10:54:53 ip-10-237-180-106 rtpengine[26167]: Got valid command
> from 127.0.0.1:56413: delete - { "call-id":
> "60174c70-66e7d6e1 at 192.168.100.136", "received-from": [ "IP4",
> "127.0.0.1" ], "from-tag": "317FA286-53F32CDB000A6E08-C56FB700",
> "to-tag": "2cfee724f53bdbbdo0", "command": "delete" }
> 
> sems.log
> Aug 19 10:54:53 ip-10-237-180-106 ngcp-sems[26328]: [#7f11c4ef3700]
> [update_uac_request, trans_layer.cpp:2047] WARNING:  While sending 200
> ACK: no matching transaction
> 
> Looks like either Sems or Asterisk is telling Kamailio to drop the call
> - not sure what's going on here? Grateful of any feedback.
> 
> Thanks
> 
> George
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


-- 
Andrew Pogrebennyk
Software Engineer
Sipwise GmbH, Campus 21/Europaring F15
A-2345 Brunn am Gebirge


From gary at netdiverse.com  Tue Aug 19 12:43:00 2014
From: gary at netdiverse.com (Gary Nieboer)
Date: Tue, 19 Aug 2014 10:43:00 -0600
Subject: [Spce-user] Peering Rules database vs. GUI Issue
In-Reply-To: <53E87A4E.7030207@sipwise.com>
References: <CAMXUi2ScE2u1tnGKSsbZUms+64yYTwAb-LsiKCfHJFAs1k7bsg@mail.gmail.com>
 <CAMXUi2S1DkXDE-EWG5N5UKxTqWLz19_T6iLV5mjj4sqU5K2u_g@mail.gmail.com>
 <53E87A4E.7030207@sipwise.com>
Message-ID: <CAMXUi2Q_9z5xD2nGV5=nq7BRFN_jcTXMh73f2wkUs7RGZvXyXg@mail.gmail.com>

Oops - I forgot to send this to the spce list.  So here it is again.

Andreas,

Thanks for the response.



*>>Can you share some information about the history of your setup?
Whichversion did you use for the initial setup? *

This box was a fresh install with version 3.1.1

We upgraded to 3.3.1  about a month ago.

We have increased the usage and complexity of the system, it is 100% "Peer
to Peer" with no subscribers.




*>>Any things you remember doing to your peerings, like deleting groups or
something?*

Yes, we have added, deleted, and edited many   Peering Groups, Peering
Rules and Rewrite Rules in the system through the GUI.

We have about 30 Peering Groups, 250 peering rules, 10 Rewrite Sets, and 25
Rewrite Rules.


Thanks in advance for any recommendations or feedback.

If we are able to update the database tables directly through mysql, and
then have the GUI reflect what is in the database tables, it would be our
ideal situation and resolution.

Thanks,

Gary



On Mon, Aug 11, 2014 at 2:09 AM, Andreas Granig <agranig at sipwise.com> wrote:

> Hi,
>
> Can you share some information about the history of your setup? Which
> version did you use for the initial setup? Any things you remember doing
> to your peerings, like deleting groups or something?
>
> There have been some issues with older versions couple of months ago in
> the triggers synchronizing the databases provisioning and kamailio, but
> they have been fixed in 3.1 already.
>
> Andreas
>
> On 08/11/2014 08:33 AM, Gary Nieboer wrote:
> > I have another instance of the GUI not matching the database.
> >
> > A peering rule ID 233 exists in the database & it was different than the
> > rule showing in the GUI.  Changing the rule in the GUI didn't adjust the
> > database.  Deleting the rule in the GUI didn't adjust the database.
> >
> > Is there anything that can be done to "refresh" the GUI to reflect what
> > is actually in the database.
> >
> > Also, is it safe to use mysql and delete the rule?
> >
> > Thanks,
> >
> > Gary
> >
> > The Example:   In
> >
> > --
> > Gary Nieboer
> >
> >
> > 877-763-1014 Toll Free  |  801-657-5484 Utah  |  615-800-6946 Tennessee
> > | 801-694-6106 Mobile
> > gary at netdiverse.com <mailto:gary at netdiverse.com>  |   www.netdiverse.com
> > <http://www.netdiverse.com/>
> >
> >
> > On Fri, Aug 1, 2014 at 2:55 PM, Gary Nieboer <gary at netdiverse.com
> > <mailto:gary at netdiverse.com>> wrote:
> >
> >
> >     We have experienced a few issues with our "Peering Rules" on SPCE,
> >     3.3.1.
> >
> >     A created rule exists in the GUI, but when routing a call through
> >     the SBC, the call follows a route to a default peer rather than the
> >     peer indicated in the GUI.
> >
> >     We recently did a comparison of what is shown in the database:
> >      lcr_rules
> >
> >                                 select * from lcr_rule;
> >
> >
> >     Here are a few lines from the database:   Some numbers are replaced
> >     with "`" and not fully shown:
> >
> >     Note:  Rule 102 is missing from the database
> >
> >
> >     | id  | lcr_id | prefix | request_uri | from_uri | stopper | enabled
> >     | group_id |
> >
>  +-----+--------+--------+-------------+----------+---------+---------+----------+
> >     | 101 |      1 |        | ~~~~~20088  | NULL     |       0 |       1
> >     |       23 |
> >     | 105 |      1 |        | ~~~~~20186  | NULL     |       0 |       1
> >     |       23 |
> >     | 106 |      1 |        | ~~~~~74891  | NULL     |       0 |       1
> >     |       23 |
> >
> >
> >
> >     Now, here is a screenshot of the GUI for the same rules:
> >     Note:  Rule 102 exists under peer group 23 for the GUI.
> >     Inline image 1
> >
> >
> >
> >     It appears we should trust the data in the database and not the GUI,
> >     but I'm assuming it is not desired behavior for the GUI and database
> >     to reflect different info.
> >
> >     If you would like more information, we can share it.
> >
> >     Please let me know if there is anything we can do to ensure the GUI
> >     reflects the actual activity of the database and ngcp/kamailio.
> >
> >     Thanks,
> >
> >     Gary
> >
> >
> >
> >
> > _______________________________________________
> > 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/20140819/565d5567/attachment-0001.html>

From joel at vozelia.com  Wed Aug 20 04:49:30 2014
From: joel at vozelia.com (Joel S. | VOZELIA)
Date: Wed, 20 Aug 2014 10:49:30 +0200 (CEST)
Subject: [Spce-user] Prosody XMPP Server unable to store images
	to	offline users
In-Reply-To: <DUB127-W331F391ACF8682CBBB7EA88F9A0@phx.gbl>
References: <DUB127-W49876D8EACB701EFA562338F990@phx.gbl>
 <DUB127-W331F391ACF8682CBBB7EA88F9A0@phx.gbl>
Message-ID: <763259845.527256.1408524570568.JavaMail.zimbra@vozelia.com>

Hi, 

I am experiencing the same problem, did you manage to find a solution?

Best regards, 
Joel.



----- Original Message ----- 

> From: "andreas tseiko" <a.tseiko at hotmail.com>
> To: spce-user at lists.sipwise.com
> Sent: Thursday, February 20, 2014 12:01:46 PM
> Subject: Re: [Spce-user] Prosody XMPP Server unable to store images to
> offline users

> Dear All,

> Is there any update regarding this issue?

> Best regards.

> From: a.tseiko at hotmail.com
> To: spce-user at lists.sipwise.com
> Subject: Prosody XMPP Server unable to store images to offline users
> Date: Mon, 17 Feb 2014 15:46:25 +0200

> Dear All,

> We have installed CE3.1 and we are using Prosody XMPP server for IM.
> When users are on line sending text,images or chating works properly.
> On the other hand when users are offline only text messages are stored while
> images are not.
> Is this a configuration issue or not?
> If it is a configuration issue, could please provide any relevant info on how
> to proceed?

> Best regards.

> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user


From agranig at sipwise.com  Wed Aug 20 05:18:41 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Wed, 20 Aug 2014 11:18:41 +0200
Subject: [Spce-user] Prosody XMPP Server unable to store images
 to	offline users
In-Reply-To: <763259845.527256.1408524570568.JavaMail.zimbra@vozelia.com>
References: <DUB127-W49876D8EACB701EFA562338F990@phx.gbl>
 <DUB127-W331F391ACF8682CBBB7EA88F9A0@phx.gbl>
 <763259845.527256.1408524570568.JavaMail.zimbra@vozelia.com>
Message-ID: <53F467F1.6070305@sipwise.com>

Hi,

File transfer is going either end-to-end or via an external proxy
(whatever is configured in your xmpp client by default, probably some
public xep-0065 proxy, like proxy.eu.jabber.org). You can run your own
using https://prosody.im/doc/modules/mod_proxy65.

The SPCE doesn't have that proxy configured by default, and if it did,
it wouldn't support file transfer store-and-forward. I don't think
prosody supports something like this at all, so development for it would
need to be sponsored for the prosody devs.

Andreas

On 08/20/2014 10:49 AM, Joel S. | VOZELIA wrote:
> Hi, 
> 
> I am experiencing the same problem, did you manage to find a solution?
> 
> Best regards, 
> Joel.
> 
> 
> 
> ----- Original Message ----- 
> 
>> From: "andreas tseiko" <a.tseiko at hotmail.com>
>> To: spce-user at lists.sipwise.com
>> Sent: Thursday, February 20, 2014 12:01:46 PM
>> Subject: Re: [Spce-user] Prosody XMPP Server unable to store images to
>> offline users
> 
>> Dear All,
> 
>> Is there any update regarding this issue?
> 
>> Best regards.
> 
>> From: a.tseiko at hotmail.com
>> To: spce-user at lists.sipwise.com
>> Subject: Prosody XMPP Server unable to store images to offline users
>> Date: Mon, 17 Feb 2014 15:46:25 +0200
> 
>> Dear All,
> 
>> We have installed CE3.1 and we are using Prosody XMPP server for IM.
>> When users are on line sending text,images or chating works properly.
>> On the other hand when users are offline only text messages are stored while
>> images are not.
>> Is this a configuration issue or not?
>> If it is a configuration issue, could please provide any relevant info on how
>> to proceed?
> 
>> Best regards.
> 
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From sipwise at carriba.org  Wed Aug 20 05:29:00 2014
From: sipwise at carriba.org (Carriba UG - sip:wise)
Date: Wed, 20 Aug 2014 09:29:00 +0000
Subject: [Spce-user] Change Peering IP
Message-ID: <em1d137ec4-bd90-43fd-907e-7ae53a0a3026@ws-w7pro-03>

Hello,

I notice if we change the Peering IP without recration of the Peering 
Group, all Inbound calls will be rejected. This is with the last 3 pubic 
Releases.

Please check this Situation for futher releases.

Thanks, Ben.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140820/cd694f9a/attachment-0001.html>

From george.mason at xoomtalk.com  Wed Aug 20 05:43:39 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Wed, 20 Aug 2014 10:43:39 +0100
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F330C5.1040404@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
Message-ID: <53F46DCB.60101@xoomtalk.com>

Hi,

Am using the elastic IP as the advertised address, beforehand for some
reason it had the wrong address in there (was an Amazon address though,
might have been the one assigned to the original AMI image? not sure). I
had calls complete but no audio until I fixed that.

Please find the logs attached (sorry for the large attachment - full UDP
pcap from eth0). Not sure where to look for the source of the issue so
interested to hear any comments.

Thanks

George

On 19/08/14 12:11, Andrew Pogrebennyk wrote:
> Hi,
> what does your /etc/ngcp-config/network.yml look like? You should use
> your Elastic IP as advertised_address. I think AMI configures that by
> default.
>
> Could you provide the kamailio-proxy.log, kamailio-lb.log and complete
> trace? I mean also messages inside spce (lb,proxy,sems).
>
> Regards.
> Andrew
>
> On 08/19/2014 01:01 PM, George Mason wrote:
>> Hi,
>>
>> I am having an issue with the SPCE Amazon EC2 image. I have configured
>> the server to forward all calls to a SIP provider with a couple of IP
>> handsets registered as subscribers. I can get a call to go through to
>> the PSTN and audio in both directions, but the call appears to drop
>> after approx. 30 secs.
>>
>> I have run a UDP trace of the signalling and it looks like SPCE drops
>> the call, I found the following in the logs:
>>
>> rtp.log
>> Aug 19 10:54:53 ip-10-237-180-106 rtpengine[26167]: Got valid command
>> from 127.0.0.1:56413: delete - { "call-id":
>> "60174c70-66e7d6e1 at 192.168.100.136", "received-from": [ "IP4",
>> "127.0.0.1" ], "from-tag": "317FA286-53F32CDB000A6E08-C56FB700",
>> "to-tag": "2cfee724f53bdbbdo0", "command": "delete" }
>>
>> sems.log
>> Aug 19 10:54:53 ip-10-237-180-106 ngcp-sems[26328]: [#7f11c4ef3700]
>> [update_uac_request, trans_layer.cpp:2047] WARNING:  While sending 200
>> ACK: no matching transaction
>>
>> Looks like either Sems or Asterisk is telling Kamailio to drop the call
>> - not sure what's going on here? Grateful of any feedback.
>>
>> Thanks
>>
>> George
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: spce-files.zip
Type: application/zip
Size: 782421 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140820/fd2c55b9/attachment-0001.zip>

From alessandro.romano at rpeng.it  Wed Aug 20 05:40:58 2014
From: alessandro.romano at rpeng.it (Alessandro Romano - Rp engineering)
Date: Wed, 20 Aug 2014 11:40:58 +0200
Subject: [Spce-user] max-forward
Message-ID: <000a01cfbc5a$d95664b0$8c032e10$@rpeng.it>

Dear All,

the my voip service provider has asked me to set the max-forward to 70
instead of 10

 

what is the procedure ?

 

BR

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140820/43f15e63/attachment-0001.html>

From agranig at sipwise.com  Wed Aug 20 06:00:16 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Wed, 20 Aug 2014 12:00:16 +0200
Subject: [Spce-user] Change Peering IP
In-Reply-To: <em1d137ec4-bd90-43fd-907e-7ae53a0a3026@ws-w7pro-03>
References: <em1d137ec4-bd90-43fd-907e-7ae53a0a3026@ws-w7pro-03>
Message-ID: <53F471B0.1050104@sipwise.com>

Hi,

The provisioning interface probably fails to reload your kamailio
dispatcher table. Check in provisioning.xmlhosts table if the IP and
port of your kamailio is correct (it's 127.0.0.1 with port 8000 and
5062. If you played around with changing internal IPs, this table might
have gotten messed up.

It'd also help to check your kamailio.dispatcher table to see if it's in
sync with your provisoning.voip_peer_hosts table. Could be some data
inconsistency caused in older versions.

Andreas

On 08/20/2014 11:29 AM, Carriba UG - sip:wise wrote:
> Hello,
>  
> I notice if we change the Peering IP without recration of the Peering
> Group, all Inbound calls will be rejected. This is with the last 3 pubic
> Releases.
>  
> Please check this Situation for futher releases.
>  
> Thanks, Ben.
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From apogrebennyk at sipwise.com  Wed Aug 20 06:01:31 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Wed, 20 Aug 2014 12:01:31 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F46DCB.60101@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com>
Message-ID: <53F471FB.1020109@sipwise.com>

Hi,
I believe I have found the problem. We have to reconsider contact
masking in kamailio-lb if adv address is set. I'll try to push an update
with the fix later today. Thanks for the bugreport.

BR,
Andrew

On 08/20/2014 11:43 AM, George Mason wrote:
> Hi,
> 
> Am using the elastic IP as the advertised address, beforehand for some
> reason it had the wrong address in there (was an Amazon address though,
> might have been the one assigned to the original AMI image? not sure). I
> had calls complete but no audio until I fixed that.
> 
> Please find the logs attached (sorry for the large attachment - full UDP
> pcap from eth0). Not sure where to look for the source of the issue so
> interested to hear any comments.
> 
> Thanks
> 
> George



From george.mason at xoomtalk.com  Wed Aug 20 06:16:50 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Wed, 20 Aug 2014 11:16:50 +0100
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F471FB.1020109@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
Message-ID: <53F47592.6040905@xoomtalk.com>

On 20/08/14 11:01, Andrew Pogrebennyk wrote:
> Hi,
> I believe I have found the problem. We have to reconsider contact
> masking in kamailio-lb if adv address is set. I'll try to push an update
> with the fix later today. Thanks for the bugreport.
>
> BR,
> Andrew
Excellent many thanks. Grateful if you could push to the East Coast AWS
zone when you do.

George


From apogrebennyk at sipwise.com  Wed Aug 20 09:13:02 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Wed, 20 Aug 2014 15:13:02 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F47592.6040905@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com>
Message-ID: <53F49EDE.301@sipwise.com>

George,

On 08/20/2014 12:16 PM, George Mason wrote:
> Excellent many thanks. Grateful if you could push to the East Coast AWS
> zone when you do.
> 
> George

alright, I have pushed the fix. Actually you don't need to re-create the
instance, just run the update:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

The problem was that the private IP of the instance was used as contact
in initial invite instead of the adv address and the dialog was changed
from private IP to adv address on the consequent in-dialog request,
which broke the signaling. I just fixed the contact masking.
Let me know if that fixes your issue.

Andrew



From george.mason at xoomtalk.com  Wed Aug 20 16:59:05 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Wed, 20 Aug 2014 21:59:05 +0100
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F49EDE.301@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
Message-ID: <53F50C19.2050807@xoomtalk.com>

 
> George,
>
> On 08/20/2014 12:16 PM, George Mason wrote:
>> > Excellent many thanks. Grateful if you could push to the East Coast AWS
>> > zone when you do.
>> > 
>> > George
> alright, I have pushed the fix. Actually you don't need to re-create the
> instance, just run the update:
>
>   apt-get update && apt-get upgrade && \
>   ngcp-update-db-schema && ngcp-update-cfg-schema && \
>   ngcpcfg apply
>
> The problem was that the private IP of the instance was used as contact
> in initial invite instead of the adv address and the dialog was changed
> from private IP to adv address on the consequent in-dialog request,
> which broke the signaling. I just fixed the contact masking.
> Let me know if that fixes your issue.
>
> Andrew
Thanks - ran the update and was all looking good, until:

Applying revision script
/usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: ERROR
1050 (42S01) at line 2: Table 'acc_backup' already exists
failed. :(

Not sure whether this is something to worry about? Looks like it's no
big deal but thought I would check.




From apogrebennyk at sipwise.com  Wed Aug 20 17:06:30 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Wed, 20 Aug 2014 23:06:30 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F50C19.2050807@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com>
Message-ID: <53F50DD6.7060203@sipwise.com>

On 20/08/14 22:59, George Mason wrote:
> Thanks - ran the update and was all looking good, until:
> 
> Applying revision script
> /usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: ERROR
> 1050 (42S01) at line 2: Table 'acc_backup' already exists
> failed. :(
> 
> Not sure whether this is something to worry about? Looks like it's no
> big deal but thought I would check.

I will check tomorrow if this is the AMI problem, meanwhile please
update your "node" column in the tables "db_schema" and "cfg_schema" in
database "ngcp" to the actual hostname of your machine.

Andrew



From mprokop at sipwise.com  Wed Aug 20 17:10:18 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Wed, 20 Aug 2014 23:10:18 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F46DCB.60101@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com>
Message-ID: <2014-08-20T22-48-29@devnull.michael-prokop.at>

* George Mason [Wed Aug 20, 2014 at 10:43:39AM +0100]:

> Am using the elastic IP as the advertised address, beforehand for some
> reason it had the wrong address in there (was an Amazon address though,
> might have been the one assigned to the original AMI image? not sure). I
> had calls complete but no audio until I fixed that.

Thanks for raising this issue, we just investigated and indeed the
advertised address doesn't get automatically updated yet - that's
why you got the IP address of the system we built the AMI on.

We've got a change in our release queue which addresses this issue.
Once this change gets released during (re)boot / network restart of
your system the advertised address gets automatically adjusted for
you, so this problem shouldn't exist any longer.

We also discussed the issue regarding our AMI in different regions
and decided to provide the sip:provider CE AMI in all EC2 regions.
The feature to automatically take care of that in our release cycle
was just implemented, so on our next public AMI build you'll have
AMIs in all regions available.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140820/376ae952/attachment-0001.asc>

From mprokop at sipwise.com  Wed Aug 20 17:42:55 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Wed, 20 Aug 2014 23:42:55 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F50DD6.7060203@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com> <53F50DD6.7060203@sipwise.com>
Message-ID: <2014-08-20T23-37-43@devnull.michael-prokop.at>

* Andrii Pogrebennyk [Wed Aug 20, 2014 at 11:06:30PM +0200]:
> On 20/08/14 22:59, George Mason wrote:
> > Thanks - ran the update and was all looking good, until:

> > Applying revision script
> > /usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: ERROR
> > 1050 (42S01) at line 2: Table 'acc_backup' already exists
> > failed. :(

> > Not sure whether this is something to worry about? Looks like it's no
> > big deal but thought I would check.

> I will check tomorrow if this is the AMI problem, meanwhile please
> update your "node" column in the tables "db_schema" and "cfg_schema" in
> database "ngcp" to the actual hostname of your machine.

Without verifying on my own yet this could very well be cloud-init*
tools on EC2 taking care of automatically adjusting /etc/hostname -
therefore modifying the hostname and confusing ngcp-db-schema
scripts.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140820/b3b989a5/attachment-0001.asc>

From gary at netdiverse.com  Wed Aug 20 22:45:56 2014
From: gary at netdiverse.com (Gary Nieboer)
Date: Wed, 20 Aug 2014 20:45:56 -0600
Subject: [Spce-user] max-forward
In-Reply-To: <000a01cfbc5a$d95664b0$8c032e10$@rpeng.it>
References: <000a01cfbc5a$d95664b0$8c032e10$@rpeng.it>
Message-ID: <CAMXUi2R4EnAfVS+kpe4Gs_A2r75jQCAn+mwicEw2D47-GbZq1Q@mail.gmail.com>

I did this by editing the variable in the kamailio section of:
 /etc/ngcp-config/config.yml file

kamailio:
  lb:
    debug: 'no'
    extra_sockets: ~
    *max_forwards: 70*


Don't forget to run:   "ngcpcfg apply"   when you're done so they are
applied to kamailio.

Good luck.

-Gary


--
Gary Nieboer


877-763-1014 Toll Free  |  801-657-5484 Utah  |  615-800-6946 Tennessee  |
801-694-6106 Mobile
gary at netdiverse.com  |   www.netdiverse.com


On Wed, Aug 20, 2014 at 3:40 AM, Alessandro Romano - Rp engineering <
alessandro.romano at rpeng.it> wrote:

> Dear All,
>
> the my voip service provider has asked me to set the max-forward to 70
> instead of 10
>
>
>
> what is the procedure ?
>
>
>
> BR
>
> _______________________________________________
> 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/20140820/f48fb470/attachment-0001.html>

From mprokop at sipwise.com  Thu Aug 21 03:26:24 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Thu, 21 Aug 2014 09:26:24 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <2014-08-20T23-37-43@devnull.michael-prokop.at>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com> <53F50DD6.7060203@sipwise.com>
 <2014-08-20T23-37-43@devnull.michael-prokop.at>
Message-ID: <2014-08-21T09-22-43@devnull.michael-prokop.at>

* Michael Prokop [Wed Aug 20, 2014 at 11:42:55PM +0200]:
> * Andrii Pogrebennyk [Wed Aug 20, 2014 at 11:06:30PM +0200]:

> > I will check tomorrow if this is the AMI problem, meanwhile please
> > update your "node" column in the tables "db_schema" and "cfg_schema" in
> > database "ngcp" to the actual hostname of your machine.

> Without verifying on my own yet this could very well be cloud-init*
> tools on EC2 taking care of automatically adjusting /etc/hostname -
> therefore modifying the hostname and confusing ngcp-db-schema
> scripts.

Just verified this, it indeed is cloud-init tools which
automatically adjusts the hostname, causing problems with
{cfg,db}_schema:

| /var/log/user.log:Aug 21 06:50:37 ip-10-37-133-236 [CLOUDINIT] cc_update_hostname.py[DEBUG]: Updating hostname to ip-10-91-133-125.eu-west-1.compute.internal (ip-10-91-133-125)

I've opened a ticket in our BTS to address this problem (MT#8731 if
anyone wants to refer to it).

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140821/3e86cd3c/attachment-0001.asc>

From george.mason at xoomtalk.com  Thu Aug 21 04:21:15 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Thu, 21 Aug 2014 09:21:15 +0100
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F50DD6.7060203@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com> <53F50DD6.7060203@sipwise.com>
Message-ID: <53F5ABFB.5070302@xoomtalk.com>


On 20/08/14 22:06, Andrew Pogrebennyk wrote:
> I will check tomorrow if this is the AMI problem, meanwhile please
> update your "node" column in the tables "db_schema" and "cfg_schema" in
> database "ngcp" to the actual hostname of your machine.
Does this address the issue I raised or is this just something I need to
do as part of a new install?


From george.mason at xoomtalk.com  Thu Aug 21 04:22:52 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Thu, 21 Aug 2014 09:22:52 +0100
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <2014-08-21T09-22-43@devnull.michael-prokop.at>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com> <53F50DD6.7060203@sipwise.com>
 <2014-08-20T23-37-43@devnull.michael-prokop.at>
 <2014-08-21T09-22-43@devnull.michael-prokop.at>
Message-ID: <53F5AC5C.9020301@xoomtalk.com>


On 21/08/14 08:26, Michael Prokop wrote:
> Just verified this, it indeed is cloud-init tools which
> automatically adjusts the hostname, causing problems with
> {cfg,db}_schema:
>
> | /var/log/user.log:Aug 21 06:50:37 ip-10-37-133-236 [CLOUDINIT] cc_update_hostname.py[DEBUG]: Updating hostname to ip-10-91-133-125.eu-west-1.compute.internal (ip-10-91-133-125)
>
> I've opened a ticket in our BTS to address this problem (MT#8731 if
> anyone wants to refer to it).
Is there a workaround for this until the patch is released? Presumably
if this hostname is incorrect then this is the root cause of the problem?


From apogrebennyk at sipwise.com  Thu Aug 21 04:25:21 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Thu, 21 Aug 2014 10:25:21 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F5ABFB.5070302@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com> <53F50DD6.7060203@sipwise.com>
 <53F5ABFB.5070302@xoomtalk.com>
Message-ID: <53F5ACF1.8090607@sipwise.com>

Hi,

On 08/21/2014 10:21 AM, George Mason wrote:
> 
> On 20/08/14 22:06, Andrew Pogrebennyk wrote:
>> I will check tomorrow if this is the AMI problem, meanwhile please
>> update your "node" column in the tables "db_schema" and "cfg_schema" in
>> database "ngcp" to the actual hostname of your machine.
> Does this address the issue I raised or is this just something I need to
> do as part of a new install?

This is the workaround for error on upgrade:

Applying revision script
/usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: ERROR
1050 (42S01) at line 2: Table 'acc_backup' already exists failed.

The issue here was that the scripts for updating db and yml configs rely
on the hostname, which is changing upon boot in the amazon ec2 instance.
Proper fix for it is under way.

Andrew


From george.mason at xoomtalk.com  Thu Aug 21 04:43:51 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Thu, 21 Aug 2014 09:43:51 +0100
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F5ACF1.8090607@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <53F471FB.1020109@sipwise.com>
 <53F47592.6040905@xoomtalk.com> <53F49EDE.301@sipwise.com>
 <53F50C19.2050807@xoomtalk.com> <53F50DD6.7060203@sipwise.com>
 <53F5ABFB.5070302@xoomtalk.com> <53F5ACF1.8090607@sipwise.com>
Message-ID: <53F5B147.1020709@xoomtalk.com>

On 21/08/14 09:25, Andrew Pogrebennyk wrote:
> The issue here was that the scripts for updating db and yml configs rely
> on the hostname, which is changing upon boot in the amazon ec2 instance.
> Proper fix for it is under way.

Understood, thanks for the clarification. Presumably this means that the
hostname in the DB would have to be updated (if the machine has been
rebooted) every time an update was run - until your patch at least?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140821/a4eca55c/attachment-0001.html>

From mprokop at sipwise.com  Thu Aug 21 05:33:26 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Thu, 21 Aug 2014 11:33:26 +0200
Subject: [Spce-user] Calls drop after 30 secs
In-Reply-To: <53F5B147.1020709@xoomtalk.com>
References: <53F330C5.1040404@sipwise.com> <53F46DCB.60101@xoomtalk.com>
 <53F471FB.1020109@sipwise.com> <53F47592.6040905@xoomtalk.com>
 <53F49EDE.301@sipwise.com> <53F50C19.2050807@xoomtalk.com>
 <53F50DD6.7060203@sipwise.com> <53F5ABFB.5070302@xoomtalk.com>
 <53F5ACF1.8090607@sipwise.com> <53F5B147.1020709@xoomtalk.com>
Message-ID: <2014-08-21T11-31-41@devnull.michael-prokop.at>

* George Mason [Thu Aug 21, 2014 at 09:43:51AM +0100]:
> On 21/08/14 09:25, Andrew Pogrebennyk wrote:
> > The issue here was that the scripts for updating db and yml configs rely
> > on the hostname, which is changing upon boot in the amazon ec2 instance.
> > Proper fix for it is under way.

> Understood, thanks for the clarification. Presumably this means that the
> hostname in the DB would have to be updated (if the machine has been
> rebooted) every time an update was run - until your patch at least?

Modifications - at least until we released our fix - should be
necessary only if you're starting it as new instance, an already
running instance which just gets updated or rebooted shouldn't be
affected AFAICT.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140821/a3621041/attachment-0001.asc>

From mprokop at sipwise.com  Thu Aug 21 10:04:10 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Thu, 21 Aug 2014 16:04:10 +0200
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1 (was: Re: Calls drop after
 30 secs)
In-Reply-To: <2014-08-20T22-48-29@devnull.michael-prokop.at>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com>
 <2014-08-20T22-48-29@devnull.michael-prokop.at>
Message-ID: <2014-08-21T15-52-10@devnull.michael-prokop.at>

* Michael Prokop [Wed Aug 20, 2014 at 11:10:18PM +0200]:
> * George Mason [Wed Aug 20, 2014 at 10:43:39AM +0100]:

> > Am using the elastic IP as the advertised address, beforehand for some
> > reason it had the wrong address in there (was an Amazon address though,
> > might have been the one assigned to the original AMI image? not sure). I
> > had calls complete but no audio until I fixed that.

> Thanks for raising this issue, we just investigated and indeed the
> advertised address doesn't get automatically updated yet - that's
> why you got the IP address of the system we built the AMI on.

> We've got a change in our release queue which addresses this issue.
> Once this change gets released during (re)boot / network restart of
> your system the advertised address gets automatically adjusted for
> you, so this problem shouldn't exist any longer.

Executing:

  apt-get update ; apt-get upgrade

on mr3.4.1 will provide the updated package ngcp-system-tools-ce
version 0.12.1.4+0~mr3.4.1.4 which includes this change to address
the automatic advertised address adjustment on EC2 systems.

> We also discussed the issue regarding our AMI in different regions
> and decided to provide the sip:provider CE AMI in all EC2 regions.
> The feature to automatically take care of that in our release cycle
> was just implemented, so on our next public AMI build you'll have
> AMIs in all regions available.

We just rebuilt the AMI for ngcp-ce-mr3.4.1 to include the
ngcp-system-tools-ce 0.12.1.4+0~mr3.4.1.4 package and this gave us
the option to release our AMI for all EC2 regions, so here we go:

  AMI ID for region us-east-1: ami-2268b64a
  AMI ID for region us-west-2: ami-256e2a15
  AMI ID for region us-west-1: ami-2bfcf06e
  AMI ID for region eu-west-1: ami-ead30d9d
  AMI ID for region ap-southeast-1: ami-222d7770
  AMI ID for region ap-southeast-2: ami-67aecf5d
  AMI ID for region ap-northeast-1: ami-67634766
  AMI ID for region sa-east-1: ami-f33199ee

If you should notice any further issues please let us know.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140821/e33370e5/attachment-0001.asc>

From george.mason at xoomtalk.com  Thu Aug 21 13:09:44 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Thu, 21 Aug 2014 18:09:44 +0100
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <2014-08-21T15-52-10@devnull.michael-prokop.at>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
Message-ID: <53F627D8.7060702@xoomtalk.com>

On 21/08/14 15:04, Michael Prokop wrote:
> on mr3.4.1 will provide the updated package ngcp-system-tools-ce
> version 0.12.1.4+0~mr3.4.1.4 which includes this change to address
> the automatic advertised address adjustment on EC2 systems.

Have just updated my EC2 instance, can see that ngcp-system-tools-ce has
upgraded to 3.4.1.4 but calls still drop after 30s. Unless I'm
misunderstanding, that update should have cured the elastic IP issue,
which should have resolved this?

Thanks

George
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140821/4d25c437/attachment-0001.html>

From mprokop at sipwise.com  Thu Aug 21 17:00:11 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Thu, 21 Aug 2014 23:00:11 +0200
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F627D8.7060702@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com>
 <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
Message-ID: <2014-08-21T22-45-52@devnull.michael-prokop.at>

* George Mason [Thu Aug 21, 2014 at 06:09:44PM +0100]:
> On 21/08/14 15:04, Michael Prokop wrote:
> > on mr3.4.1 will provide the updated package ngcp-system-tools-ce
> > version 0.12.1.4+0~mr3.4.1.4 which includes this change to address
> > the automatic advertised address adjustment on EC2 systems.

> Have just updated my EC2 instance, can see that ngcp-system-tools-ce has
> upgraded to 3.4.1.4 but calls still drop after 30s. Unless I'm
> misunderstanding, that update should have cured the elastic IP issue,
> which should have resolved this?

The ngcp-system-tools-ce update just ensures that the advertised IP
configuration in network.yml is OK in the classic EC2 scenario. You
can verify this on your own by checking whether the configuration in
/etc/ngcp-config/network.yml matches the IP address reported via
executing 'facter ec2_public_ipv4' on the command line.

What's still missing is the fix to make sure that db-schema and
cfg-schema work independent from the hostname (this is fixed in our
"trunk" already but is waiting for an according release yet).

But did you adjust the node name entries in the ngcp.cfg_schema and
ngcp.db_schema tables so you're fully up2date with:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

yet? Because if you've up2date db-schema and cfg-schema changes
applied that should be working fine AFAIK, if not please let us
know.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140821/dde2464e/attachment-0001.asc>

From george.mason at xoomtalk.com  Thu Aug 21 18:37:25 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Thu, 21 Aug 2014 23:37:25 +0100
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <2014-08-21T22-45-52@devnull.michael-prokop.at>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
 <2014-08-21T22-45-52@devnull.michael-prokop.at>
Message-ID: <53F674A5.7080800@xoomtalk.com>


> * George Mason [Thu Aug 21, 2014 at 06:09:44PM +0100]:
>> On 21/08/14 15:04, Michael Prokop wrote:
>>> on mr3.4.1 will provide the updated package ngcp-system-tools-ce
>>> version 0.12.1.4+0~mr3.4.1.4 which includes this change to address
>>> the automatic advertised address adjustment on EC2 systems.
>
>> Have just updated my EC2 instance, can see that ngcp-system-tools-ce has
>> upgraded to 3.4.1.4 but calls still drop after 30s. Unless I'm
>> misunderstanding, that update should have cured the elastic IP issue,
>> which should have resolved this?
>
> The ngcp-system-tools-ce update just ensures that the advertised IP
> configuration in network.yml is OK in the classic EC2 scenario. You
> can verify this on your own by checking whether the configuration in
> /etc/ngcp-config/network.yml matches the IP address reported via
> executing 'facter ec2_public_ipv4' on the command line.
Thanks - yes this has worked fine, the two match up.
>
>
> What's still missing is the fix to make sure that db-schema and
> cfg-schema work independent from the hostname (this is fixed in our
> "trunk" already but is waiting for an according release yet).
>
> But did you adjust the node name entries in the ngcp.cfg_schema and
> ngcp.db_schema tables so you're fully up2date with:
>
>   apt-get update && apt-get upgrade && \
>   ngcp-update-db-schema && ngcp-update-cfg-schema && \
>   ngcpcfg apply
>
> yet? Because if you've up2date db-schema and cfg-schema changes
> applied that should be working fine AFAIK, if not please let us
> know.
Unfortunately not working for me. I updated the node (to the EC2
internal hostname - in this case ip-10-237-180-106) in both db_schema
and cfg_schema and re-ran the update as above, but still receive the
following error on upgrade:

Applying revision script
/usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: ERROR
1050 (42S01) at line 2: Table 'acc_backup' already exists
failed. :(





From apogrebennyk at sipwise.com  Fri Aug 22 04:34:43 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Fri, 22 Aug 2014 10:34:43 +0200
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F627D8.7060702@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
Message-ID: <53F700A3.2030401@sipwise.com>

George,

On 08/21/2014 07:09 PM, George Mason wrote:
> Have just updated my EC2 instance, can see that ngcp-system-tools-ce has
> upgraded to 3.4.1.4 but calls still drop after 30s. Unless I'm
> misunderstanding, that update should have cured the elastic IP issue,
> which should have resolved this?

What version of templates do you have, e.g. dpkg -l
ngcp-templates-ce-kamailio ? Should be mr3.4.1.4.

Did you execute ngcpcfg apply after the templates upgrade?

If so I would like to check the kamailio-lb.log and kamailio-proxy.log
again, this time please raise the debug level with:
ngcp-kamctl proxy fifo debug 2
ngcp-kamctl lb fifo debug 2

And a pcap trace or ngrep-sip output would be helpful too.

Andrew


From apogrebennyk at sipwise.com  Fri Aug 22 05:19:07 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Fri, 22 Aug 2014 11:19:07 +0200
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F674A5.7080800@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
 <2014-08-21T22-45-52@devnull.michael-prokop.at>
 <53F674A5.7080800@xoomtalk.com>
Message-ID: <53F70B0B.6010308@sipwise.com>

Hi,
regarding the hostname change:

On 08/22/2014 12:37 AM, George Mason wrote:
> Unfortunately not working for me. I updated the node (to the EC2
> internal hostname - in this case ip-10-237-180-106) in both db_schema
> and cfg_schema and re-ran the update as above, but still receive the
> following error on upgrade:
> 
> Applying revision script
> /usr/share/ngcp-db-schema/db_scripts/base/0070_not_replicated.up: ERROR
> 1050 (42S01) at line 2: Table 'acc_backup' already exists
> failed. :(

please update the node in both db_schema and cfg_schema to "spce"
instead of the internal hostname. That should help. I latest mr3.4.1 we
do not rely on the hostname anymore, instead the update scripts look
into /etc/ngcp_nodename.

Andrew


From george.mason at xoomtalk.com  Fri Aug 22 05:26:43 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Fri, 22 Aug 2014 10:26:43 +0100
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F70B0B.6010308@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
 <2014-08-21T22-45-52@devnull.michael-prokop.at>
 <53F674A5.7080800@xoomtalk.com> <53F70B0B.6010308@sipwise.com>
Message-ID: <53F70CD3.5060406@xoomtalk.com>


On 22/08/14 10:19, Andrew Pogrebennyk wrote:
> please update the node in both db_schema and cfg_schema to "spce"
> instead of the internal hostname. That should help. I latest mr3.4.1 we
> do not rely on the hostname anymore, instead the update scripts look
> into /etc/ngcp_nodename.

Did this, and the upgrade ran fine. So that's good. Unfortunately calls
still drop after 30 secs so am in the process of taking another PCAP and
Kamailio logs.

> What version of templates do you have, e.g. dpkg -l
> ngcp-templates-ce-kamailio ? Should be mr3.4.1.4.
ii  ngcp-templates-ce-kamailio                3.4.1.4+0~mr3.4.1.4      
all                       Configuration templates for Kamailio
configuration in NGCP platforms





From george.mason at xoomtalk.com  Fri Aug 22 05:32:03 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Fri, 22 Aug 2014 10:32:03 +0100
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F70CD3.5060406@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
 <2014-08-21T22-45-52@devnull.michael-prokop.at>
 <53F674A5.7080800@xoomtalk.com> <53F70B0B.6010308@sipwise.com>
 <53F70CD3.5060406@xoomtalk.com>
Message-ID: <53F70E13.5010306@xoomtalk.com>


> On 22/08/14 10:19, Andrew Pogrebennyk wrote:
>> please update the node in both db_schema and cfg_schema to "spce"
>> instead of the internal hostname. That should help. I latest mr3.4.1 we
>> do not rely on the hostname anymore, instead the update scripts look
>> into /etc/ngcp_nodename.
> Did this, and the upgrade ran fine. So that's good. Unfortunately calls
> still drop after 30 secs so am in the process of taking another PCAP and
> Kamailio logs.
>
>> What version of templates do you have, e.g. dpkg -l
>> ngcp-templates-ce-kamailio ? Should be mr3.4.1.4.
> ii  ngcp-templates-ce-kamailio                3.4.1.4+0~mr3.4.1.4      
> all                       Configuration templates for Kamailio
> configuration in NGCP platforms
>

Logs + PCAPs attached

-------------- next part --------------
A non-text attachment was scrubbed...
Name: pcap.zip
Type: application/zip
Size: 171351 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140822/c3e86044/attachment-0002.zip>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logs.zip
Type: application/zip
Size: 218440 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140822/c3e86044/attachment-0003.zip>

From apogrebennyk at sipwise.com  Fri Aug 22 06:27:11 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Fri, 22 Aug 2014 12:27:11 +0200
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F70E13.5010306@xoomtalk.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
 <2014-08-21T22-45-52@devnull.michael-prokop.at>
 <53F674A5.7080800@xoomtalk.com> <53F70B0B.6010308@sipwise.com>
 <53F70CD3.5060406@xoomtalk.com> <53F70E13.5010306@xoomtalk.com>
Message-ID: <53F71AFF.5090108@sipwise.com>

On 08/22/2014 11:32 AM, George Mason wrote:
> Logs + PCAPs attached

Hm, I think the problem now lies with the callee with 169.* IP. It
should acknowledge 200 OK after re-INVITE in packet #31 (eth0.pcap) with
an ACK message. At a glance I don't see any problem in packets sent to
169.* IP. The route set and Contact are correct now. Could you ask that
carrier what is the problem with acknowledging on their side?

Andrew


From aclark at structuredcommunications.co.uk  Fri Aug 22 11:22:41 2014
From: aclark at structuredcommunications.co.uk (Adam Clark)
Date: Fri, 22 Aug 2014 15:22:41 +0000
Subject: [Spce-user] Billing Profile Web Error
Message-ID: <E80006BDE297C94AADE7963C138CC416D99EEC7F@SR-AD.structured.local>

Afternoon all,

We have just uploaded a large 9500 line CSV file with "purge" ticked.

The file uploaded, however that profile once selected via the admin interface gets the web error "(en) Please come back later"

The OSS.log reports:

Aug 22 16:16:07 sipwise /usr/sbin/apache2: Caught exception in admin::Controller::billing->search_fees "Can't escape \x{FEFF}, try uri_escape_utf8() instead at /usr/share/ngcp-www-admin/lib/admin/Controller/billing.pm line 530"

We have looked at the table in SQL and it only has 560 odd lines ?


1)  Does sipwise not handle a zone file this large?

2)  Can we delete the profile from SQL or restore a backup without destroying anything?

Any help would be grateful.


Kind regards,

[sig1]

This e-mail and any attachments transmitted with it, including replies and forwarded copies subsequently transmitted, contains information which may be confidential and which may also be legally privileged. The content of this e-mail is for the exclusive use of the individual(s) or entity named above, if you are not the intended recipient, please note that any form of distribution, copying or use of this e-mail or the information in it is strictly prohibited and may be unlawful. If you have received this e-mail in error please reply to the sender at Structured Communications Ltd and then delete the e-mail immediately. Any views or opinions presented are solely those of the author, and may not necessarily represent those of Structured Communications Ltd. Structured Communications Ltd is registered in England and Wales, registered no 07667451, and its registered office is 22 London Road, Horsham, West Sussex RH12 1AY. Registered VAT number GB116507336.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140822/07a586ea/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 12937 bytes
Desc: image001.png
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140822/07a586ea/attachment-0001.png>

From joel at vozelia.com  Fri Aug 22 17:54:13 2014
From: joel at vozelia.com (Joel S. | VOZELIA)
Date: Fri, 22 Aug 2014 23:54:13 +0200 (CEST)
Subject: [Spce-user] Prosody XMPP Server unable to store images
	to	offline users
In-Reply-To: <53F467F1.6070305@sipwise.com>
References: <DUB127-W49876D8EACB701EFA562338F990@phx.gbl>
 <DUB127-W331F391ACF8682CBBB7EA88F9A0@phx.gbl>
 <763259845.527256.1408524570568.JavaMail.zimbra@vozelia.com>
 <53F467F1.6070305@sipwise.com>
Message-ID: <1461629263.605282.1408744453802.JavaMail.zimbra@vozelia.com>

Thank you Andreas.

I will give a try with mod_proxy65 :)

Best regards, 
Joel.


----- Original Message -----
> From: "Andreas Granig" <agranig at sipwise.com>
> To: spce-user at lists.sipwise.com
> Sent: Wednesday, August 20, 2014 11:18:41 AM
> Subject: Re: [Spce-user] Prosody XMPP Server unable to store images to	offline users
> 
> Hi,
> 
> File transfer is going either end-to-end or via an external proxy
> (whatever is configured in your xmpp client by default, probably some
> public xep-0065 proxy, like proxy.eu.jabber.org). You can run your own
> using https://prosody.im/doc/modules/mod_proxy65.
> 
> The SPCE doesn't have that proxy configured by default, and if it did,
> it wouldn't support file transfer store-and-forward. I don't think
> prosody supports something like this at all, so development for it would
> need to be sponsored for the prosody devs.
> 
> Andreas
> 
> On 08/20/2014 10:49 AM, Joel S. | VOZELIA wrote:
> > Hi,
> > 
> > I am experiencing the same problem, did you manage to find a solution?
> > 
> > Best regards,
> > Joel.
> > 
> > 
> > 
> > ----- Original Message -----
> > 
> >> From: "andreas tseiko" <a.tseiko at hotmail.com>
> >> To: spce-user at lists.sipwise.com
> >> Sent: Thursday, February 20, 2014 12:01:46 PM
> >> Subject: Re: [Spce-user] Prosody XMPP Server unable to store images to
> >> offline users
> > 
> >> Dear All,
> > 
> >> Is there any update regarding this issue?
> > 
> >> Best regards.
> > 
> >> From: a.tseiko at hotmail.com
> >> To: spce-user at lists.sipwise.com
> >> Subject: Prosody XMPP Server unable to store images to offline users
> >> Date: Mon, 17 Feb 2014 15:46:25 +0200
> > 
> >> Dear All,
> > 
> >> We have installed CE3.1 and we are using Prosody XMPP server for IM.
> >> When users are on line sending text,images or chating works properly.
> >> On the other hand when users are offline only text messages are stored
> >> while
> >> images are not.
> >> Is this a configuration issue or not?
> >> If it is a configuration issue, could please provide any relevant info on
> >> how
> >> to proceed?
> > 
> >> Best regards.
> > 
> >> _______________________________________________
> >> Spce-user mailing list
> >> Spce-user at lists.sipwise.com
> >> http://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
> 


From george.mason at xoomtalk.com  Sat Aug 23 05:07:54 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Sat, 23 Aug 2014 10:07:54 +0100
Subject: [Spce-user] Updated EC2 AMIs for mr3.4.1
In-Reply-To: <53F71AFF.5090108@sipwise.com>
References: <53F32E75.7070700@xoomtalk.com> <53F330C5.1040404@sipwise.com>
 <53F46DCB.60101@xoomtalk.com> <2014-08-20T22-48-29@devnull.michael-prokop.at>
 <2014-08-21T15-52-10@devnull.michael-prokop.at>
 <53F627D8.7060702@xoomtalk.com>
 <2014-08-21T22-45-52@devnull.michael-prokop.at>
 <53F674A5.7080800@xoomtalk.com> <53F70B0B.6010308@sipwise.com>
 <53F70CD3.5060406@xoomtalk.com> <53F70E13.5010306@xoomtalk.com>
 <53F71AFF.5090108@sipwise.com>
Message-ID: <53F859EA.5010705@xoomtalk.com>


> On 08/22/2014 11:32 AM, George Mason wrote:
>> > Logs + PCAPs attached
> Hm, I think the problem now lies with the callee with 169.* IP. It
> should acknowledge 200 OK after re-INVITE in packet #31 (eth0.pcap) with
> an ACK message. At a glance I don't see any problem in packets sent to
> 169.* IP. The route set and Contact are correct now. Could you ask that
> carrier what is the problem with acknowledging on their side?
>
> Andrew

Thanks Andrew - will check and potentially route via a different carrier
and report back.

George


From agranig at sipwise.com  Sat Aug 23 06:56:06 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Sat, 23 Aug 2014 12:56:06 +0200
Subject: [Spce-user] Billing Profile Web Error
In-Reply-To: <E80006BDE297C94AADE7963C138CC416D99EEC7F@SR-AD.structured.local>
References: <E80006BDE297C94AADE7963C138CC416D99EEC7F@SR-AD.structured.local>
Message-ID: <53F87346.8080309@sipwise.com>

Hello,

Which version are you using? 2.8?

The issue is not the size, rather than a character in your file seems to
cause issues with utf-8 handling.

Can you provide the file (also in private, and with zeroed fees)?

Andreas

On 08/22/2014 05:22 PM, Adam Clark wrote:
> Afternoon all,
> 
>  
> 
> We have just uploaded a large 9500 line CSV file with ?purge? ticked.
> 
>  
> 
> The file uploaded, however that profile once selected via the admin
> interface gets the web error ?(en) Please come back later?
> 
>  
> 
> The OSS.log reports:
> 
>  
> 
> Aug 22 16:16:07 sipwise /usr/sbin/apache2: Caught exception in
> admin::Controller::billing->search_fees "Can't escape \x{FEFF}, try
> uri_escape_utf8() instead at
> /usr/share/ngcp-www-admin/lib/admin/Controller/billing.pm line 530"
> 
>  
> 
> We have looked at the table in SQL and it only has 560 odd lines ?
> 
>  
> 
> 1)  Does sipwise not handle a zone file this large?
> 
> 2)  Can we delete the profile from SQL or restore a backup without
> destroying anything?
> 
>  
> 
> Any help would be grateful.
> 
>  
> 
>  
> 
> Kind regards,
> 
>  
> 
> sig1
> 
>  
> 
> This e-mail and any attachments transmitted with it, including replies
> and forwarded copies subsequently transmitted, contains information
> which may be confidential and which may also be legally privileged. The
> content of this e-mail is for the exclusive use of the individual(s) or
> entity named above, if you are not the intended recipient, please note
> that any form of distribution, copying or use of this e-mail or the
> information in it is strictly prohibited and may be unlawful. If you
> have received this e-mail in error please reply to the sender at
> Structured Communications Ltd and then delete the e-mail immediately.
> Any views or opinions presented are solely those of the author, and may
> not necessarily represent those of Structured Communications Ltd.
> Structured Communications Ltd is registered in England and Wales,
> registered no 07667451, and its registered office is 22 London Road,
> Horsham, West Sussex RH12 1AY. Registered VAT number GB116507336.
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From aclark at structuredcommunications.co.uk  Sat Aug 23 11:05:36 2014
From: aclark at structuredcommunications.co.uk (Adam Clark)
Date: Sat, 23 Aug 2014 15:05:36 +0000
Subject: [Spce-user] Billing Profile Web Error
In-Reply-To: <53F87346.8080309@sipwise.com>
References: <E80006BDE297C94AADE7963C138CC416D99EEC7F@SR-AD.structured.local>,
 <53F87346.8080309@sipwise.com>
Message-ID: <E80006BDE297C94AADE7963C138CC416D99F0081@SR-AD.structured.local>

Hi Andreas,

Thanks for the reply.

Yes 2.8

The file was saved as UTF-8. I can send the file once I get to a pc :)

Kind Regards,

Adam Clark
Chief Network Engineer
Structured Communications

Sent via my HTC

----- Reply message -----
From: "Andreas Granig" <agranig at sipwise.com>
To: "spce-user at lists.sipwise.com" <spce-user at lists.sipwise.com>
Subject: [Spce-user] Billing Profile Web Error
Date: Sat, Aug 23, 2014 11:57

Hello,

Which version are you using? 2.8?

The issue is not the size, rather than a character in your file seems to
cause issues with utf-8 handling.

Can you provide the file (also in private, and with zeroed fees)?

Andreas

On 08/22/2014 05:22 PM, Adam Clark wrote:
> Afternoon all,
>
>
>
> We have just uploaded a large 9500 line CSV file with ?purge? ticked.
>
>
>
> The file uploaded, however that profile once selected via the admin
> interface gets the web error ?(en) Please come back later?
>
>
>
> The OSS.log reports:
>
>
>
> Aug 22 16:16:07 sipwise /usr/sbin/apache2: Caught exception in
> admin::Controller::billing->search_fees "Can't escape \x{FEFF}, try
> uri_escape_utf8() instead at
> /usr/share/ngcp-www-admin/lib/admin/Controller/billing.pm line 530"
>
>
>
> We have looked at the table in SQL and it only has 560 odd lines ?
>
>
>
> 1)  Does sipwise not handle a zone file this large?
>
> 2)  Can we delete the profile from SQL or restore a backup without
> destroying anything?
>
>
>
> Any help would be grateful.
>
>
>
>
>
> Kind regards,
>
>
>
> sig1
>
>
>
> This e-mail and any attachments transmitted with it, including replies
> and forwarded copies subsequently transmitted, contains information
> which may be confidential and which may also be legally privileged. The
> content of this e-mail is for the exclusive use of the individual(s) or
> entity named above, if you are not the intended recipient, please note
> that any form of distribution, copying or use of this e-mail or the
> information in it is strictly prohibited and may be unlawful. If you
> have received this e-mail in error please reply to the sender at
> Structured Communications Ltd and then delete the e-mail immediately.
> Any views or opinions presented are solely those of the author, and may
> not necessarily represent those of Structured Communications Ltd.
> Structured Communications Ltd is registered in England and Wales,
> registered no 07667451, and its registered office is 22 London Road,
> Horsham, West Sussex RH12 1AY. Registered VAT number GB116507336.
>
>
>
>
>
>
>
> _______________________________________________
> 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/20140823/c71b4041/attachment-0001.html>

From arjan at hakwerk.com  Sun Aug 24 05:05:41 2014
From: arjan at hakwerk.com (Arjan Hakkesteegt)
Date: Sun, 24 Aug 2014 11:05:41 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered" /
 kamailio-lb contact (un)masking
Message-ID: <53F9AAE5.2090904@hakwerk.com>

Hi all,

I have a fresh install of mr3.4.1 (actually I messed up upgrading from 
3.3.1 on a mysql error and didn't have a proper backup; my bad. 
Completey wiped the VM and started from scratch).
SEMS is successfully registering with my SIP trunk provider, I can call 
to and be called from the PSTN.
However, looking at the sems logs ("debug: 'yes'" in config.yml, 
attached), it is re-registering every 10 seconds because of a "no 
matching Contact - deregistered" error.

Below is the output of ngrep-sip for one attempt. I'm no expert but it 
looks like the unmasking of the contact fails in kamailio-lb.
178.X.Y.Z = public IP address
12345 = didlogic user id

I'd appreciate any help.

Thanks,
Arjan



U 2014/08/24 09:39:43.210372 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: <sip:12345 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.X.Y.Z:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 09:39:43.211469 178.X.Y.Z:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 
178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: <sip:12345 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
Max-Forwards: 69'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.X.Y.Z:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 09:39:43.258182 72.251.241.166:5060 -> 178.X.Y.Z:5060
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 
178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: 
<sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6'
CSeq: 50 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", 
nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
Content-Length: 0'
'


U 2014/08/24 09:39:43.258552 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: 
<sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6'
CSeq: 50 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", 
nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 09:39:43.260249 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: <sip:12345 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
Authorization: Digest username="12345", realm="sip.nl.didlogic.net", 
nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", 
uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7", nc=00000001, 
response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
Contact: <sip:127.0.0.1:5080;transport=udp>'
Contact: <sip:178.X.Y.Z:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 09:39:43.260751 178.X.Y.Z:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 
178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: <sip:12345 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
Max-Forwards: 69'
Expires: 3600'
Authorization: Digest username="12345", realm="sip.nl.didlogic.net", 
nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", 
uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7", nc=00000001, 
response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
Content-Length: 0'
Contact: 
<sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
'


U 2014/08/24 09:39:43.288129 72.251.241.166:5060 -> 178.X.Y.Z:5060
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 
178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: 
<sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd'
CSeq: 51 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
Contact: 
<sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
'


U 2014/08/24 09:39:43.288567 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
To: 
<sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd'
CSeq: 51 REGISTER'
Call-ID: 015670DF-53F996BF00033117-60710700'
Contact: 
<sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'

-------------- next part --------------
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f406060f700] [run, RegistrationAgent.cpp:190] DEBUG:  Registration 0 does not exist or timeout. Creating registration.
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f406060f700] [create_registration, RegistrationAgent.cpp:131] DEBUG:  calling createRegistration
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [onNewRegistration, SIPRegistrarClient.cpp:200] DEBUG:  enabling UAC Auth for new registration.
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [onNewRegistration, SIPRegistrarClient.cpp:208] DEBUG:  arg type is 6
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [add_reg, SIPRegistrarClient.cpp:306] DEBUG:  adding registration '21D25CA9-53F98EB300019510-6060F700'  (this = 14359168)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 50 to list of sent requests.
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.X.Y.Z:5060>>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bK7QmZKaGG
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK7QmZKaGG;rport..From: <sip:12345 at sip.nl.didlogic.net>;tag=21D25CA9-53F98EB300019510-6060F700..To: <sip:12345 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 5F4AD48F-53F98EB300019611-60710700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.X.Y.Z:5060;transport=udp>..Content-Length: 0.......>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK7QmZKaGG;rport..From: <sip:12345 at sip.nl.didlogic.net>;tag=21D25CA9-53F98EB300019510-6060F700..To: <sip:12345 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 5F4AD48F-53F98EB300019611-60710700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.X.Y.Z:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0xe55a20)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=23122 (repeated=0)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=24697 (repeated=0)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK7QmZKaGG;rport=5080..From: <sip:12345 at sip.nl.didlogic.net>;tag=21D25CA9-53F98EB300019510-6060F700..To: <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.f2f8..CSeq: 50 REGISTER..Call-ID: 5F4AD48F-53F98EB300019611-60710700..WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/mP31P5jrPOoegNj2RD/SF0oElQvmBfKopG/4A=", qop="auth"..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bK7QmZKaGG
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 401, trans=0xe55a20)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0xe54bb0)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0xe56d90)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=23348 (repeated=0)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 401 Unauthorized
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <5F4AD48F-53F98EB300019611-60710700>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <21D25CA9-53F98EB300019510-6060F700>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.f2f8>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <50>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/mP31P5jrPOoegNj2RD/SF0oElQvmBfKopG/4A=", qop="auth"..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405ebac700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [5F4AD48F-53F98EB300019611-60710700|21D25CA9-53F98EB300019510-6060F700] ru SIP reply 401 Unauthorized handled ^^
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '21D25CA9-53F98EB300019510-6060F700'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '15036144' (this = 14359168)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 401 Unauthorized): transaction found!
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [onSipReply, UACAuth.cpp:165] DEBUG:  SIP reply with code 401 cseq 50 .
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [onSipReply, UACAuth.cpp:171] DEBUG:   UACAuth - processing with reply code 401
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [do_auth, UACAuth.cpp:401] DEBUG:  realm='sip.nl.didlogic.net', nonce='U/mP31P5jrPOoegNj2RD/SF0oElQvmBfKopG/4A=', qop='auth'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [do_auth, UACAuth.cpp:447] DEBUG:  calculated response = 1e41934ed262dea6922d0bfe48c804b0
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [do_auth, UACAuth.cpp:468] DEBUG:  Auth req hdr: 'Authorization: Digest username="12345", realm="sip.nl.didlogic.net", nonce="U/mP31P5jrPOoegNj2RD/SF0oElQvmBfKopG/4A=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="085a904f", nc=00000001, response="1e41934ed262dea6922d0bfe48c804b0", algorithm=MD5.'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 51 to list of sent requests.
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:127.0.0.1:5080>>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5080) to int (5080)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.X.Y.Z:5060>>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKHM2u0a2Z
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKHM2u0a2Z;rport..From: <sip:12345 at sip.nl.didlogic.net>;tag=21D25CA9-53F98EB300019510-6060F700..To: <sip:12345 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 5F4AD48F-53F98EB300019611-60710700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="12345", realm="sip.nl.didlogic.net", nonce="U/mP31P5jrPOoegNj2RD/SF0oElQvmBfKopG/4A=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="085a904f", nc=00000001, response="1e41934ed262dea6922d0bfe48c804b0", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.X.Y.Z:5060;transport=udp>..Content-Length: 0.......>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKHM2u0a2Z;rport..From: <sip:12345 at sip.nl.didlogic.net>;tag=21D25CA9-53F98EB300019510-6060F700..To: <sip:12345 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 5F4AD48F-53F98EB300019611-60710700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="12345", realm="sip.nl.didlogic.net", nonce="U/mP31P5jrPOoegNj2RD/SF0oElQvmBfKopG/4A=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="085a904f", nc=00000001, response="1e41934ed262dea6922d0bfe48c804b0", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.X.Y.Z:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0xe59040)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=23124 (repeated=0)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=24699 (repeated=0)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [onSipReply, UACAuth.cpp:234] DEBUG:  authenticated request successfully sent.
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 200 OK..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKHM2u0a2Z;rport=5080..From: <sip:12345 at sip.nl.didlogic.net>;tag=21D25CA9-53F98EB300019510-6060F700..To: <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.061b..CSeq: 51 REGISTER..Call-ID: 5F4AD48F-53F98EB300019611-60710700..Contact: <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKHM2u0a2Z
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 200, trans=0xe59040)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0xe57fd0)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0xe57f40)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=23350 (repeated=0)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 200 OK
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <5F4AD48F-53F98EB300019611-60710700>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <21D25CA9-53F98EB300019510-6060F700>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.061b>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <<sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <51>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f405edae700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [5F4AD48F-53F98EB300019611-60710700|21D25CA9-53F98EB300019510-6060F700] ru SIP reply 200 OK handled ^^
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '21D25CA9-53F98EB300019510-6060F700'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '15036144' (this = 14359168)
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 200 OK): transaction found!
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [onSipReply, AmSipRegistration.cpp:287] DEBUG:  positive reply to REGISTER!
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:127.0.0.1:5080>..'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  'Contact:'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      ''
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '127.0.0.1'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5080'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     ''
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  ''
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      'ngcp-lb'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '178.X.Y.Z'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5060'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     'ngcpct=7369703a3132372e302e302e313a35303830'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:493] DEBUG:   param     'expires'='3600'
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [onSipReply, AmSipRegistration.cpp:345] DEBUG:  no matching Contact - deregistered.
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [checkTimeouts, SIPRegistrarClient.cpp:123] DEBUG:  removing registration
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmBasicSipDialog.cpp:729] DEBUG:  callid = 5F4AD48F-53F98EB300019611-60710700
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmBasicSipDialog.cpp:730] DEBUG:  local_tag = 21D25CA9-53F98EB300019510-6060F700
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmBasicSipDialog.cpp:731] DEBUG:  uac_trans.size() = 0
Aug 24 09:05:23 sip ngcp-sems[4379]: [#7f4060710700] [dump, AmBasicSipDialog.cpp:739] DEBUG:  uas_trans.size() = 0


From dgrotti at sipwise.com  Sun Aug 24 08:26:12 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Sun, 24 Aug 2014 14:26:12 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53F9AAE5.2090904@hakwerk.com>
References: <53F9AAE5.2090904@hakwerk.com>
Message-ID: <53F9D9E4.40601@sipwise.com>

Hi,
sorry in the trace below I just see the registration process at 09:39:43.
Where do you see the second REGISTER after 10sec ? It should Re-REGISTER
again after 3600 sec.

Also I don't see the unREGISTER message (with Expires: 0).
Can you provide such messages ?

Daniel







On 08/24/2014 11:05 AM, Arjan Hakkesteegt wrote:
> Hi all,
>
> I have a fresh install of mr3.4.1 (actually I messed up upgrading from
> 3.3.1 on a mysql error and didn't have a proper backup; my bad.
> Completey wiped the VM and started from scratch).
> SEMS is successfully registering with my SIP trunk provider, I can
> call to and be called from the PSTN.
> However, looking at the sems logs ("debug: 'yes'" in config.yml,
> attached), it is re-registering every 10 seconds because of a "no
> matching Contact - deregistered" error.
>
> Below is the output of ngrep-sip for one attempt. I'm no expert but it
> looks like the unmasking of the contact fails in kamailio-lb.
> 178.X.Y.Z = public IP address
> 12345 = didlogic user id
>
> I'd appreciate any help.
>
> Thanks,
> Arjan
>
>
>
> U 2014/08/24 09:39:43.210372 127.0.0.1:5080 -> 127.0.0.1:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Route: <sip:127.0.0.1:5060;lr>'
> Max-Forwards: 70'
> Expires: 3600'
> User-Agent: Sipwise NGCP Application Server 3.X'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.211469 178.X.Y.Z:5060 -> 72.251.241.166:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP
> 178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Max-Forwards: 69'
> Expires: 3600'
> User-Agent: Sipwise NGCP Application Server 3.X'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.258182 72.251.241.166:5060 -> 178.X.Y.Z:5060
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP
> 178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0;rport=5060'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To:
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> WWW-Authenticate: Digest realm="sip.nl.didlogic.net",
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.258552 127.0.0.1:5060 -> 127.0.0.1:5080
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To:
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> WWW-Authenticate: Digest realm="sip.nl.didlogic.net",
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
> Content-Length: 0'
> P-NGCP-Src-Ip: 72.251.241.166'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> '
>
>
> U 2014/08/24 09:39:43.260249 127.0.0.1:5080 -> 127.0.0.1:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Route: <sip:127.0.0.1:5060;lr>'
> Max-Forwards: 70'
> Expires: 3600'
> Authorization: Digest username="12345", realm="sip.nl.didlogic.net",
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=",
> uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7",
> nc=00000001, response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
> Contact: <sip:127.0.0.1:5080;transport=udp>'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.260751 178.X.Y.Z:5060 -> 72.251.241.166:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP
> 178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Max-Forwards: 69'
> Expires: 3600'
> Authorization: Digest username="12345", realm="sip.nl.didlogic.net",
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=",
> uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7",
> nc=00000001, response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
> Content-Length: 0'
> Contact:
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
> '
>
>
> U 2014/08/24 09:39:43.288129 72.251.241.166:5060 -> 178.X.Y.Z:5060
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP
> 178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0;rport=5060'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To:
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Contact:
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.288567 127.0.0.1:5060 -> 127.0.0.1:5080
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From:
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To:
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Contact:
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
> Content-Length: 0'
> P-NGCP-Src-Ip: 72.251.241.166'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> '
>
>
>
> _______________________________________________
> 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/20140824/5185dede/attachment-0001.html>

From arjan at hakwerk.com  Sun Aug 24 09:44:11 2014
From: arjan at hakwerk.com (Arjan Hakkesteegt)
Date: Sun, 24 Aug 2014 15:44:11 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53F9D9E4.40601@sipwise.com>
References: <53F9AAE5.2090904@hakwerk.com> <53F9D9E4.40601@sipwise.com>
Message-ID: <53F9EC2B.2090406@hakwerk.com>

I attached the output from "ngrep-sip didlogic" for a minute or so, 
showing the 10 sec interval. I also included the sems.log for that same 
period.

I did a grep on expire in all logfiles in /var/log/ngcp/ but there never 
is an expires: 0 in the logs, only 3600. Any other idea how to find such 
an unREGISTER?

Arjan
> Daniel Grotti <mailto:dgrotti at sipwise.com>
> Sunday, August 24, 2014 14:26
> Hi,
> sorry in the trace below I just see the registration process at 09:39:43.
> Where do you see the second REGISTER after 10sec ? It should 
> Re-REGISTER again after 3600 sec.
>
> Also I don't see the unREGISTER message (with Expires: 0).
> Can you provide such messages ?
>
> Daniel
>
>
>
>
>
>
>
> On 08/24/2014 11:05 AM, Arjan Hakkesteegt wrote:
>
> Arjan Hakkesteegt <mailto:arjan at hakwerk.com>
> Sunday, August 24, 2014 11:05
> Hi all,
>
> I have a fresh install of mr3.4.1 (actually I messed up upgrading from 
> 3.3.1 on a mysql error and didn't have a proper backup; my bad. 
> Completey wiped the VM and started from scratch).
> SEMS is successfully registering with my SIP trunk provider, I can 
> call to and be called from the PSTN.
> However, looking at the sems logs ("debug: 'yes'" in config.yml, 
> attached), it is re-registering every 10 seconds because of a "no 
> matching Contact - deregistered" error.
>
> Below is the output of ngrep-sip for one attempt. I'm no expert but it 
> looks like the unmasking of the contact fails in kamailio-lb.
> 178.X.Y.Z = public IP address
> 12345 = didlogic user id
>
> I'd appreciate any help.
>
> Thanks,
> Arjan
>
>
>
> U 2014/08/24 09:39:43.210372 127.0.0.1:5080 -> 127.0.0.1:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Route: <sip:127.0.0.1:5060;lr>'
> Max-Forwards: 70'
> Expires: 3600'
> User-Agent: Sipwise NGCP Application Server 3.X'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.211469 178.X.Y.Z:5060 -> 72.251.241.166:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Max-Forwards: 69'
> Expires: 3600'
> User-Agent: Sipwise NGCP Application Server 3.X'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.258182 72.251.241.166:5060 -> 178.X.Y.Z:5060
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0;rport=5060' 
>
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6' 
>
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> WWW-Authenticate: Digest realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.258552 127.0.0.1:5060 -> 127.0.0.1:5080
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6' 
>
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> WWW-Authenticate: Digest realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
> Content-Length: 0'
> P-NGCP-Src-Ip: 72.251.241.166'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> '
>
>
> U 2014/08/24 09:39:43.260249 127.0.0.1:5080 -> 127.0.0.1:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Route: <sip:127.0.0.1:5060;lr>'
> Max-Forwards: 70'
> Expires: 3600'
> Authorization: Digest username="12345", realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", 
> uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7", 
> nc=00000001, response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
> Contact: <sip:127.0.0.1:5080;transport=udp>'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.260751 178.X.Y.Z:5060 -> 72.251.241.166:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Max-Forwards: 69'
> Expires: 3600'
> Authorization: Digest username="12345", realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", 
> uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7", 
> nc=00000001, response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
> Content-Length: 0'
> Contact: 
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
> '
>
>
> U 2014/08/24 09:39:43.288129 72.251.241.166:5060 -> 178.X.Y.Z:5060
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0;rport=5060' 
>
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd' 
>
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Contact: 
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600' 
>
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.288567 127.0.0.1:5060 -> 127.0.0.1:5080
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd' 
>
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Contact: 
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600' 
>
> Content-Length: 0'
> P-NGCP-Src-Ip: 72.251.241.166'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> '
>
> _______________________________________________
> 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/20140824/976c583c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1214 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140824/976c583c/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1321 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140824/976c583c/attachment-0003.jpg>
-------------- next part --------------
U 2014/08/24 15:20:58.454966 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKPqU3PamA;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:20:58.455690 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK563e.cdbf5a3f2e4f434a978784f169086726.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKPqU3PamA;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700'
Max-Forwards: 69'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:20:58.494001 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK563e.cdbf5a3f2e4f434a978784f169086726.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKPqU3PamA;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.140c'
CSeq: 50 REGISTER'
Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/nn5lP55roAniF7fJmwfG2t3yTZ4+hHKuQ1lIA=", qop="auth"'
Content-Length: 0'
'


U 2014/08/24 15:20:58.494545 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKPqU3PamA;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.140c'
CSeq: 50 REGISTER'
Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/nn5lP55roAniF7fJmwfG2t3yTZ4+hHKuQ1lIA=", qop="auth"'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:20:58.497208 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKBfUaFaU1;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn5lP55roAniF7fJmwfG2t3yTZ4+hHKuQ1lIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="64f1d6a4", nc=00000001, response="107fe88a2ab09de989de170457237e6f", algorithm=MD5'
Contact: <sip:127.0.0.1:5080;transport=udp>'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:20:58.497826 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK663e.373ed16eb4c2e7ab164bfb9122452df0.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKBfUaFaU1;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700'
Max-Forwards: 69'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn5lP55roAniF7fJmwfG2t3yTZ4+hHKuQ1lIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="64f1d6a4", nc=00000001, response="107fe88a2ab09de989de170457237e6f", algorithm=MD5'
Content-Length: 0'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
'


U 2014/08/24 15:20:58.524512 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK663e.373ed16eb4c2e7ab164bfb9122452df0.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKBfUaFaU1;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.2b72'
CSeq: 51 REGISTER'
Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
'


U 2014/08/24 15:20:58.525197 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKBfUaFaU1;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.2b72'
CSeq: 51 REGISTER'
Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:21:08.455405 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRLKvNab9;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:08.466395 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKab2d.b033854d2074bd11f8ebcf3c0406ead4.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRLKvNab9;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700'
Max-Forwards: 69'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:08.504690 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKab2d.b033854d2074bd11f8ebcf3c0406ead4.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRLKvNab9;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.62cb'
CSeq: 50 REGISTER'
Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/nn8FP55sSeO/HhT5qwR5O5XYv2SWpNKuQ6mYA=", qop="auth"'
Content-Length: 0'
'


U 2014/08/24 15:21:08.505058 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRLKvNab9;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.62cb'
CSeq: 50 REGISTER'
Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/nn8FP55sSeO/HhT5qwR5O5XYv2SWpNKuQ6mYA=", qop="auth"'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:21:08.508269 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKE8OukaNn;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn8FP55sSeO/HhT5qwR5O5XYv2SWpNKuQ6mYA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="4576ce26", nc=00000001, response="1def3161bcbd8883e48b875cc1d97672", algorithm=MD5'
Contact: <sip:127.0.0.1:5080;transport=udp>'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:08.508952 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKbb2d.16c4a336218f3bac1b21313265bdece5.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKE8OukaNn;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700'
Max-Forwards: 69'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn8FP55sSeO/HhT5qwR5O5XYv2SWpNKuQ6mYA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="4576ce26", nc=00000001, response="1def3161bcbd8883e48b875cc1d97672", algorithm=MD5'
Content-Length: 0'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
'


U 2014/08/24 15:21:08.536476 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKbb2d.16c4a336218f3bac1b21313265bdece5.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKE8OukaNn;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.0f7f'
CSeq: 51 REGISTER'
Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
'


U 2014/08/24 15:21:08.537255 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKE8OukaNn;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.0f7f'
CSeq: 51 REGISTER'
Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:21:18.455786 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKaVZfaaw2;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:18.456497 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKd07e.e8206774a0971e2772fe63421a3464f5.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKaVZfaaw2;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700'
Max-Forwards: 69'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:18.495314 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKd07e.e8206774a0971e2772fe63421a3464f5.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKaVZfaaw2;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.f36d'
CSeq: 50 REGISTER'
Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/nn+lP55s7NCpyvab2cwNW4rbgx1SDJKuRGpYA=", qop="auth"'
Content-Length: 0'
'


U 2014/08/24 15:21:18.495701 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKaVZfaaw2;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.f36d'
CSeq: 50 REGISTER'
Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/nn+lP55s7NCpyvab2cwNW4rbgx1SDJKuRGpYA=", qop="auth"'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:21:18.499902 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKKYtsiaGz;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn+lP55s7NCpyvab2cwNW4rbgx1SDJKuRGpYA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="6924719d", nc=00000001, response="653f353ef8e77154fd1bc762dd7ff2af", algorithm=MD5'
Contact: <sip:127.0.0.1:5080;transport=udp>'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:18.500478 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKe07e.79f5dff02df364d60b4a3542c54668b4.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKKYtsiaGz;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700'
Max-Forwards: 69'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn+lP55s7NCpyvab2cwNW4rbgx1SDJKuRGpYA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="6924719d", nc=00000001, response="653f353ef8e77154fd1bc762dd7ff2af", algorithm=MD5'
Content-Length: 0'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
'


U 2014/08/24 15:21:18.527457 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKe07e.79f5dff02df364d60b4a3542c54668b4.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKKYtsiaGz;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.232d'
CSeq: 51 REGISTER'
Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
'


U 2014/08/24 15:21:18.527987 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKKYtsiaGz;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.232d'
CSeq: 51 REGISTER'
Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:21:28.456005 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKwDPZOaCE;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:28.457083 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK373f.7c3ffbd284b0779074f9891b9e3f3a2b.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKwDPZOaCE;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700'
Max-Forwards: 69'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:28.495330 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK373f.7c3ffbd284b0779074f9891b9e3f3a2b.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKwDPZOaCE;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.98d4'
CSeq: 50 REGISTER'
Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noBFP55tjkuncjBQ1LstzIm7bX5h4UKuRNrIA=", qop="auth"'
Content-Length: 0'
'


U 2014/08/24 15:21:28.495743 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKwDPZOaCE;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.98d4'
CSeq: 50 REGISTER'
Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noBFP55tjkuncjBQ1LstzIm7bX5h4UKuRNrIA=", qop="auth"'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:21:28.498542 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKfaDfgaMU;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noBFP55tjkuncjBQ1LstzIm7bX5h4UKuRNrIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="73bd14fd", nc=00000001, response="6ae930ba0b9b6150dc146587ead4940a", algorithm=MD5'
Contact: <sip:127.0.0.1:5080;transport=udp>'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:28.499355 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK473f.79d3ac39bdd24b375ff55a37136df215.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKfaDfgaMU;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700'
Max-Forwards: 69'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noBFP55tjkuncjBQ1LstzIm7bX5h4UKuRNrIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="73bd14fd", nc=00000001, response="6ae930ba0b9b6150dc146587ead4940a", algorithm=MD5'
Content-Length: 0'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
'


U 2014/08/24 15:21:28.526214 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK473f.79d3ac39bdd24b375ff55a37136df215.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKfaDfgaMU;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.02b4'
CSeq: 51 REGISTER'
Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
'


U 2014/08/24 15:21:28.526985 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKfaDfgaMU;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.02b4'
CSeq: 51 REGISTER'
Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:21:38.456349 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKn4lvxaOR;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 69900D25-53F9E6E20006F41F-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:38.457863 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK7e22.b56ce2fb3a63833ea786c1dd3fb31665.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKn4lvxaOR;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 69900D25-53F9E6E20006F41F-336A4700'
Max-Forwards: 69'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:38.497247 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK7e22.b56ce2fb3a63833ea786c1dd3fb31665.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKn4lvxaOR;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.effa'
CSeq: 50 REGISTER'
Call-ID: 69900D25-53F9E6E20006F41F-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noDlP55uLBj5/xUNgN16TYkhU9KO28KuRXtoA=", qop="auth"'
Content-Length: 0'
'


U 2014/08/24 15:21:38.497699 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKn4lvxaOR;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.effa'
CSeq: 50 REGISTER'
Call-ID: 69900D25-53F9E6E20006F41F-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noDlP55uLBj5/xUNgN16TYkhU9KO28KuRXtoA=", qop="auth"'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:21:38.500039 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKGBcD~aYW;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 69900D25-53F9E6E20006F41F-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noDlP55uLBj5/xUNgN16TYkhU9KO28KuRXtoA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="05fab516", nc=00000001, response="e39a0e12e8a9cf26cbe0d8324f41302a", algorithm=MD5'
Contact: <sip:127.0.0.1:5080;transport=udp>'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:38.500774 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK8e22.a990f430ce1fc664566428ff307c4655.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKGBcD~aYW;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 69900D25-53F9E6E20006F41F-336A4700'
Max-Forwards: 69'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noDlP55uLBj5/xUNgN16TYkhU9KO28KuRXtoA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="05fab516", nc=00000001, response="e39a0e12e8a9cf26cbe0d8324f41302a", algorithm=MD5'
Content-Length: 0'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
'


U 2014/08/24 15:21:38.527769 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK8e22.a990f430ce1fc664566428ff307c4655.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKGBcD~aYW;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.c1fc'
CSeq: 51 REGISTER'
Call-ID: 69900D25-53F9E6E20006F41F-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
'


U 2014/08/24 15:21:38.528171 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKGBcD~aYW;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.c1fc'
CSeq: 51 REGISTER'
Call-ID: 69900D25-53F9E6E20006F41F-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:21:48.456844 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKbaHziaA7;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:48.458040 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKc0f.52a8a843a42bce1c1e70dabb36542143.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKbaHziaA7;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700'
Max-Forwards: 69'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:48.496384 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKc0f.52a8a843a42bce1c1e70dabb36542143.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKbaHziaA7;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.593c'
CSeq: 50 REGISTER'
Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noGFP55uzXlBDyjSfe/byaKGFpX8ftKuRdvIA=", qop="auth"'
Content-Length: 0'
'


U 2014/08/24 15:21:48.496882 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKbaHziaA7;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.593c'
CSeq: 50 REGISTER'
Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noGFP55uzXlBDyjSfe/byaKGFpX8ftKuRdvIA=", qop="auth"'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:21:48.499634 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKes8MGaO1;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noGFP55uzXlBDyjSfe/byaKGFpX8ftKuRdvIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="2fe95026", nc=00000001, response="6fedb095f14d0ea80d93de4d77c390f8", algorithm=MD5'
Contact: <sip:127.0.0.1:5080;transport=udp>'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:48.499988 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKd0f.7707358721801d5a97234bca5e249d8b.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKes8MGaO1;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700'
Max-Forwards: 69'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noGFP55uzXlBDyjSfe/byaKGFpX8ftKuRdvIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="2fe95026", nc=00000001, response="6fedb095f14d0ea80d93de4d77c390f8", algorithm=MD5'
Content-Length: 0'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
'


U 2014/08/24 15:21:48.526797 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKd0f.7707358721801d5a97234bca5e249d8b.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKes8MGaO1;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.22c2'
CSeq: 51 REGISTER'
Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
'


U 2014/08/24 15:21:48.527175 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKes8MGaO1;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.22c2'
CSeq: 51 REGISTER'
Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:21:58.457402 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKzDj.Yame;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 1D470EB4-53F9E6F60006F732-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:58.458154 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK8ed3.a1d64d2cf645ed8f0255afb7eb2e551d.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKzDj.Yame;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 1D470EB4-53F9E6F60006F732-336A4700'
Max-Forwards: 69'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:58.497116 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK8ed3.a1d64d2cf645ed8f0255afb7eb2e551d.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKzDj.Yame;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.700d'
CSeq: 50 REGISTER'
Call-ID: 1D470EB4-53F9E6F60006F732-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noIlP55vZgF/FyiW4hxtCeXisjIyoPKuRkw4A=", qop="auth"'
Content-Length: 0'
'


U 2014/08/24 15:21:58.497500 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKzDj.Yame;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.700d'
CSeq: 50 REGISTER'
Call-ID: 1D470EB4-53F9E6F60006F732-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noIlP55vZgF/FyiW4hxtCeXisjIyoPKuRkw4A=", qop="auth"'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:21:58.500127 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKu4oByaHU;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 1D470EB4-53F9E6F60006F732-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noIlP55vZgF/FyiW4hxtCeXisjIyoPKuRkw4A=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="5c0c87e5", nc=00000001, response="8a9d3fce482f4e807da7b9763527d86c", algorithm=MD5'
Contact: <sip:127.0.0.1:5080;transport=udp>'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:21:58.500567 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK9ed3.f4150b5b646074e0dbb69d5a66e8405a.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKu4oByaHU;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 1D470EB4-53F9E6F60006F732-336A4700'
Max-Forwards: 69'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noIlP55vZgF/FyiW4hxtCeXisjIyoPKuRkw4A=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="5c0c87e5", nc=00000001, response="8a9d3fce482f4e807da7b9763527d86c", algorithm=MD5'
Content-Length: 0'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
'


U 2014/08/24 15:21:58.527637 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bK9ed3.f4150b5b646074e0dbb69d5a66e8405a.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKu4oByaHU;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.3af1'
CSeq: 51 REGISTER'
Call-ID: 1D470EB4-53F9E6F60006F732-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
'


U 2014/08/24 15:21:58.528097 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKu4oByaHU;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.3af1'
CSeq: 51 REGISTER'
Call-ID: 1D470EB4-53F9E6F60006F732-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:22:08.458496 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKoVz~mavx;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:22:08.469296 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKcd51.c7ac297266acd39bf55c02a2b534965a.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKoVz~mavx;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 50 REGISTER'
Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700'
Max-Forwards: 69'
Expires: 3600'
User-Agent: Sipwise NGCP Application Server 3.X'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:22:08.508165 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKcd51.c7ac297266acd39bf55c02a2b534965a.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKoVz~mavx;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.5b30'
CSeq: 50 REGISTER'
Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noLFP55wAzGtxxRay2h+7wgTYNu/3+KuRsy4A=", qop="auth"'
Content-Length: 0'
'


U 2014/08/24 15:22:08.508630 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 401 Unauthorized'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKoVz~mavx;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.5b30'
CSeq: 50 REGISTER'
Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700'
WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noLFP55wAzGtxxRay2h+7wgTYNu/3+KuRsy4A=", qop="auth"'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'


U 2014/08/24 15:22:08.510736 127.0.0.1:5080 -> 127.0.0.1:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKQD~OaayI;rport'
From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700'
Route: <sip:127.0.0.1:5060;lr>'
Max-Forwards: 70'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noLFP55wAzGtxxRay2h+7wgTYNu/3+KuRsy4A=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="1e9d466d", nc=00000001, response="bdea74007da499b07d7eb94b7df5cdde", algorithm=MD5'
Contact: <sip:127.0.0.1:5080;transport=udp>'
Contact: <sip:178.63.53.154:5060;transport=udp>'
Content-Length: 0'
'


U 2014/08/24 15:22:08.511303 178.63.53.154:5060 -> 72.251.241.166:5060
REGISTER sip:sip.nl.didlogic.net SIP/2.0'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKdd51.94933ea398089bc7312acea7657f7224.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKQD~OaayI;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>'
CSeq: 51 REGISTER'
Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700'
Max-Forwards: 69'
Expires: 3600'
Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noLFP55wAzGtxxRay2h+7wgTYNu/3+KuRsy4A=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="1e9d466d", nc=00000001, response="bdea74007da499b07d7eb94b7df5cdde", algorithm=MD5'
Content-Length: 0'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
'


U 2014/08/24 15:22:08.537818 72.251.241.166:5060 -> 178.63.53.154:5060
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 178.63.53.154;branch=z9hG4bKdd51.94933ea398089bc7312acea7657f7224.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKQD~OaayI;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fee5'
CSeq: 51 REGISTER'
Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
'


U 2014/08/24 15:22:08.538182 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKQD~OaayI;rport=5080'
From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700'
To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fee5'
CSeq: 51 REGISTER'
Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700'
Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
'

-------------- next part --------------
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b335a3700] [run, RegistrationAgent.cpp:190] DEBUG:  Registration 0 does not exist or timeout. Creating registration.
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b335a3700] [create_registration, RegistrationAgent.cpp:131] DEBUG:  calling createRegistration
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:200] DEBUG:  enabling UAC Auth for new registration.
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:208] DEBUG:  arg type is 6
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [add_reg, SIPRegistrarClient.cpp:306] DEBUG:  adding registration '4D864D42-53F9E6BA0006ED5E-335A3700'  (this = 139823532783808)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 50 to list of sent requests.
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKPqU3PamA
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKPqU3PamA;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKPqU3PamA;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340aeca0)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=170134 (repeated=0)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=171709 (repeated=0)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKPqU3PamA;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.140c..CSeq: 50 REGISTER..Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700..WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/nn5lP55roAniF7fJmwfG2t3yTZ4+hHKuQ1lIA=", qop="auth"..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKPqU3PamA
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 401, trans=0x7f2b340aeca0)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340ada60)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340ad1f0)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=170361 (repeated=0)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 401 Unauthorized
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <11F23E85-53F9E6BA0006EE38-336A4700>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <4D864D42-53F9E6BA0006ED5E-335A3700>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.140c>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <50>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/nn5lP55roAniF7fJmwfG2t3yTZ4+hHKuQ1lIA=", qop="auth"..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [11F23E85-53F9E6BA0006EE38-336A4700|4D864D42-53F9E6BA0006ED5E-335A3700] ru SIP reply 401 Unauthorized handled ^^
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '4D864D42-53F9E6BA0006ED5E-335A3700'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533443792' (this = 139823532783808)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 401 Unauthorized): transaction found!
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:165] DEBUG:  SIP reply with code 401 cseq 50 .
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:171] DEBUG:   UACAuth - processing with reply code 401
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:401] DEBUG:  realm='sip.nl.didlogic.net', nonce='U/nn5lP55roAniF7fJmwfG2t3yTZ4+hHKuQ1lIA=', qop='auth'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:447] DEBUG:  calculated response = 107fe88a2ab09de989de170457237e6f
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:468] DEBUG:  Auth req hdr: 'Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn5lP55roAniF7fJmwfG2t3yTZ4+hHKuQ1lIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="64f1d6a4", nc=00000001, response="107fe88a2ab09de989de170457237e6f", algorithm=MD5.'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 51 to list of sent requests.
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:127.0.0.1:5080>>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5080) to int (5080)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKBfUaFaU1
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKBfUaFaU1;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn5lP55roAniF7fJmwfG2t3yTZ4+hHKuQ1lIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="64f1d6a4", nc=00000001, response="107fe88a2ab09de989de170457237e6f", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKBfUaFaU1;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn5lP55roAniF7fJmwfG2t3yTZ4+hHKuQ1lIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="64f1d6a4", nc=00000001, response="107fe88a2ab09de989de170457237e6f", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340b0600)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=170136 (repeated=0)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=171711 (repeated=0)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:234] DEBUG:  authenticated request successfully sent.
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 200 OK..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKBfUaFaU1;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=4D864D42-53F9E6BA0006ED5E-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.2b72..CSeq: 51 REGISTER..Call-ID: 11F23E85-53F9E6BA0006EE38-336A4700..Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKBfUaFaU1
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 200, trans=0x7f2b340b0600)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340af7c0)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340af730)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=170363 (repeated=0)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 200 OK
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <11F23E85-53F9E6BA0006EE38-336A4700>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <4D864D42-53F9E6BA0006ED5E-335A3700>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.2b72>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <51>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [11F23E85-53F9E6BA0006EE38-336A4700|4D864D42-53F9E6BA0006ED5E-335A3700] ru SIP reply 200 OK handled ^^
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '4D864D42-53F9E6BA0006ED5E-335A3700'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533443792' (this = 139823532783808)
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 200 OK): transaction found!
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:287] DEBUG:  positive reply to REGISTER!
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:127.0.0.1:5080>..'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  'Contact:'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      ''
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '127.0.0.1'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5080'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     ''
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  ''
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      'ngcp-lb'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '178.63.53.154'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5060'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     'ngcpct=7369703a3132372e302e302e313a35303830'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:493] DEBUG:   param     'expires'='3600'
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:20:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:345] DEBUG:  no matching Contact - deregistered.
Aug 24 15:20:59 sip ngcp-sems[7535]: [#7f2b336a4700] [checkTimeouts, SIPRegistrarClient.cpp:123] DEBUG:  removing registration
Aug 24 15:20:59 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:729] DEBUG:  callid = 11F23E85-53F9E6BA0006EE38-336A4700
Aug 24 15:20:59 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:730] DEBUG:  local_tag = 4D864D42-53F9E6BA0006ED5E-335A3700
Aug 24 15:20:59 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:731] DEBUG:  uac_trans.size() = 0
Aug 24 15:20:59 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:739] DEBUG:  uas_trans.size() = 0
Aug 24 15:21:03 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340aeca0, eta=170361, t=170361
Aug 24 15:21:03 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110c9c0)
Aug 24 15:21:03 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340b0600, eta=170363, t=170363
Aug 24 15:21:03 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110c8a0)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b335a3700] [run, RegistrationAgent.cpp:190] DEBUG:  Registration 0 does not exist or timeout. Creating registration.
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b335a3700] [create_registration, RegistrationAgent.cpp:131] DEBUG:  calling createRegistration
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:200] DEBUG:  enabling UAC Auth for new registration.
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:208] DEBUG:  arg type is 6
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [add_reg, SIPRegistrarClient.cpp:306] DEBUG:  adding registration '7B1A0959-53F9E6C40006EEE0-335A3700'  (this = 139823532783808)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 50 to list of sent requests.
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKRLKvNab9
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRLKvNab9;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRLKvNab9;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340aef80)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=170634 (repeated=0)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=172209 (repeated=0)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRLKvNab9;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.62cb..CSeq: 50 REGISTER..Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700..WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/nn8FP55sSeO/HhT5qwR5O5XYv2SWpNKuQ6mYA=", qop="auth"..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKRLKvNab9
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 401, trans=0x7f2b340aef80)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340ad430)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340add00)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=170862 (repeated=0)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 401 Unauthorized
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <77B7FA39-53F9E6C40006EF30-336A4700>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <7B1A0959-53F9E6C40006EEE0-335A3700>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.62cb>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <50>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/nn8FP55sSeO/HhT5qwR5O5XYv2SWpNKuQ6mYA=", qop="auth"..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [77B7FA39-53F9E6C40006EF30-336A4700|7B1A0959-53F9E6C40006EEE0-335A3700] ru SIP reply 401 Unauthorized handled ^^
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '7B1A0959-53F9E6C40006EEE0-335A3700'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533444528' (this = 139823532783808)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 401 Unauthorized): transaction found!
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:165] DEBUG:  SIP reply with code 401 cseq 50 .
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:171] DEBUG:   UACAuth - processing with reply code 401
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:401] DEBUG:  realm='sip.nl.didlogic.net', nonce='U/nn8FP55sSeO/HhT5qwR5O5XYv2SWpNKuQ6mYA=', qop='auth'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:447] DEBUG:  calculated response = 1def3161bcbd8883e48b875cc1d97672
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:468] DEBUG:  Auth req hdr: 'Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn8FP55sSeO/HhT5qwR5O5XYv2SWpNKuQ6mYA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="4576ce26", nc=00000001, response="1def3161bcbd8883e48b875cc1d97672", algorithm=MD5.'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 51 to list of sent requests.
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:127.0.0.1:5080>>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5080) to int (5080)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKE8OukaNn
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKE8OukaNn;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn8FP55sSeO/HhT5qwR5O5XYv2SWpNKuQ6mYA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="4576ce26", nc=00000001, response="1def3161bcbd8883e48b875cc1d97672", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKE8OukaNn;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn8FP55sSeO/HhT5qwR5O5XYv2SWpNKuQ6mYA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="4576ce26", nc=00000001, response="1def3161bcbd8883e48b875cc1d97672", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340b0890)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=170637 (repeated=0)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=172212 (repeated=0)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:234] DEBUG:  authenticated request successfully sent.
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 200 OK..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKE8OukaNn;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=7B1A0959-53F9E6C40006EEE0-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.0f7f..CSeq: 51 REGISTER..Call-ID: 77B7FA39-53F9E6C40006EF30-336A4700..Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKE8OukaNn
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 200, trans=0x7f2b340b0890)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340afa50)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340af9c0)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=170863 (repeated=0)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 200 OK
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <77B7FA39-53F9E6C40006EF30-336A4700>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <7B1A0959-53F9E6C40006EEE0-335A3700>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.0f7f>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <51>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [77B7FA39-53F9E6C40006EF30-336A4700|7B1A0959-53F9E6C40006EEE0-335A3700] ru SIP reply 200 OK handled ^^
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '7B1A0959-53F9E6C40006EEE0-335A3700'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533444528' (this = 139823532783808)
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 200 OK): transaction found!
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:287] DEBUG:  positive reply to REGISTER!
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:127.0.0.1:5080>..'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  'Contact:'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      ''
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '127.0.0.1'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5080'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     ''
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  ''
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      'ngcp-lb'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '178.63.53.154'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5060'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     'ngcpct=7369703a3132372e302e302e313a35303830'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:493] DEBUG:   param     'expires'='3600'
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:21:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:345] DEBUG:  no matching Contact - deregistered.
Aug 24 15:21:09 sip ngcp-sems[7535]: [#7f2b336a4700] [checkTimeouts, SIPRegistrarClient.cpp:123] DEBUG:  removing registration
Aug 24 15:21:09 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:729] DEBUG:  callid = 77B7FA39-53F9E6C40006EF30-336A4700
Aug 24 15:21:09 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:730] DEBUG:  local_tag = 7B1A0959-53F9E6C40006EEE0-335A3700
Aug 24 15:21:09 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:731] DEBUG:  uac_trans.size() = 0
Aug 24 15:21:09 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:739] DEBUG:  uas_trans.size() = 0
Aug 24 15:21:13 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340aef80, eta=170862, t=170862
Aug 24 15:21:13 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110c8a0)
Aug 24 15:21:13 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340b0890, eta=170863, t=170863
Aug 24 15:21:13 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x11047f0)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b335a3700] [run, RegistrationAgent.cpp:190] DEBUG:  Registration 0 does not exist or timeout. Creating registration.
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b335a3700] [create_registration, RegistrationAgent.cpp:131] DEBUG:  calling createRegistration
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:200] DEBUG:  enabling UAC Auth for new registration.
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:208] DEBUG:  arg type is 6
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [add_reg, SIPRegistrarClient.cpp:306] DEBUG:  adding registration '5CBECECC-53F9E6CE0006F05E-335A3700'  (this = 139823532783808)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 50 to list of sent requests.
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKaVZfaaw2
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKaVZfaaw2;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKaVZfaaw2;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340af000)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=171134 (repeated=0)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=172709 (repeated=0)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKaVZfaaw2;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.f36d..CSeq: 50 REGISTER..Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700..WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/nn+lP55s7NCpyvab2cwNW4rbgx1SDJKuRGpYA=", qop="auth"..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKaVZfaaw2
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 401, trans=0x7f2b340af000)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340ad510)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340adda0)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=171361 (repeated=0)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 401 Unauthorized
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <1EC02D01-53F9E6CE0006F0A9-336A4700>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <5CBECECC-53F9E6CE0006F05E-335A3700>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.f36d>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <50>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/nn+lP55s7NCpyvab2cwNW4rbgx1SDJKuRGpYA=", qop="auth"..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [1EC02D01-53F9E6CE0006F0A9-336A4700|5CBECECC-53F9E6CE0006F05E-335A3700] ru SIP reply 401 Unauthorized handled ^^
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '5CBECECC-53F9E6CE0006F05E-335A3700'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533444752' (this = 139823532783808)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 401 Unauthorized): transaction found!
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:165] DEBUG:  SIP reply with code 401 cseq 50 .
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:171] DEBUG:   UACAuth - processing with reply code 401
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:401] DEBUG:  realm='sip.nl.didlogic.net', nonce='U/nn+lP55s7NCpyvab2cwNW4rbgx1SDJKuRGpYA=', qop='auth'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:447] DEBUG:  calculated response = 653f353ef8e77154fd1bc762dd7ff2af
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:468] DEBUG:  Auth req hdr: 'Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn+lP55s7NCpyvab2cwNW4rbgx1SDJKuRGpYA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="6924719d", nc=00000001, response="653f353ef8e77154fd1bc762dd7ff2af", algorithm=MD5.'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 51 to list of sent requests.
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:127.0.0.1:5080>>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5080) to int (5080)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKKYtsiaGz
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKKYtsiaGz;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn+lP55s7NCpyvab2cwNW4rbgx1SDJKuRGpYA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="6924719d", nc=00000001, response="653f353ef8e77154fd1bc762dd7ff2af", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKKYtsiaGz;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/nn+lP55s7NCpyvab2cwNW4rbgx1SDJKuRGpYA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="6924719d", nc=00000001, response="653f353ef8e77154fd1bc762dd7ff2af", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340b0940)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=171136 (repeated=0)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=172711 (repeated=0)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:234] DEBUG:  authenticated request successfully sent.
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 200 OK..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKKYtsiaGz;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=5CBECECC-53F9E6CE0006F05E-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.232d..CSeq: 51 REGISTER..Call-ID: 1EC02D01-53F9E6CE0006F0A9-336A4700..Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKKYtsiaGz
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 200, trans=0x7f2b340b0940)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340afb00)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340afa70)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=171363 (repeated=0)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 200 OK
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <1EC02D01-53F9E6CE0006F0A9-336A4700>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <5CBECECC-53F9E6CE0006F05E-335A3700>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.232d>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <51>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [1EC02D01-53F9E6CE0006F0A9-336A4700|5CBECECC-53F9E6CE0006F05E-335A3700] ru SIP reply 200 OK handled ^^
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '5CBECECC-53F9E6CE0006F05E-335A3700'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533444752' (this = 139823532783808)
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 200 OK): transaction found!
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:287] DEBUG:  positive reply to REGISTER!
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:127.0.0.1:5080>..'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  'Contact:'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      ''
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '127.0.0.1'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5080'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     ''
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  ''
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      'ngcp-lb'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '178.63.53.154'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5060'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     'ngcpct=7369703a3132372e302e302e313a35303830'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:493] DEBUG:   param     'expires'='3600'
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:21:18 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:345] DEBUG:  no matching Contact - deregistered.
Aug 24 15:21:19 sip ngcp-sems[7535]: [#7f2b336a4700] [checkTimeouts, SIPRegistrarClient.cpp:123] DEBUG:  removing registration
Aug 24 15:21:19 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:729] DEBUG:  callid = 1EC02D01-53F9E6CE0006F0A9-336A4700
Aug 24 15:21:19 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:730] DEBUG:  local_tag = 5CBECECC-53F9E6CE0006F05E-335A3700
Aug 24 15:21:19 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:731] DEBUG:  uac_trans.size() = 0
Aug 24 15:21:19 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:739] DEBUG:  uas_trans.size() = 0
Aug 24 15:21:23 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340af000, eta=171361, t=171361
Aug 24 15:21:23 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110d110)
Aug 24 15:21:23 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340b0940, eta=171363, t=171363
Aug 24 15:21:23 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110c8c0)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b335a3700] [run, RegistrationAgent.cpp:190] DEBUG:  Registration 0 does not exist or timeout. Creating registration.
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b335a3700] [create_registration, RegistrationAgent.cpp:131] DEBUG:  calling createRegistration
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:200] DEBUG:  enabling UAC Auth for new registration.
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:208] DEBUG:  arg type is 6
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [add_reg, SIPRegistrarClient.cpp:306] DEBUG:  adding registration '48454647-53F9E6D80006F1BD-335A3700'  (this = 139823532783808)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 50 to list of sent requests.
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKwDPZOaCE
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKwDPZOaCE;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKwDPZOaCE;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340af0a0)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=171634 (repeated=0)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=173209 (repeated=0)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKwDPZOaCE;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.98d4..CSeq: 50 REGISTER..Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700..WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noBFP55tjkuncjBQ1LstzIm7bX5h4UKuRNrIA=", qop="auth"..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKwDPZOaCE
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 401, trans=0x7f2b340af0a0)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340ade60)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340ad5f0)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=171861 (repeated=0)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 401 Unauthorized
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <4FB91CB7-53F9E6D80006F24E-336A4700>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <48454647-53F9E6D80006F1BD-335A3700>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.98d4>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <50>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noBFP55tjkuncjBQ1LstzIm7bX5h4UKuRNrIA=", qop="auth"..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [4FB91CB7-53F9E6D80006F24E-336A4700|48454647-53F9E6D80006F1BD-335A3700] ru SIP reply 401 Unauthorized handled ^^
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '48454647-53F9E6D80006F1BD-335A3700'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533444816' (this = 139823532783808)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 401 Unauthorized): transaction found!
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:165] DEBUG:  SIP reply with code 401 cseq 50 .
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:171] DEBUG:   UACAuth - processing with reply code 401
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:401] DEBUG:  realm='sip.nl.didlogic.net', nonce='U/noBFP55tjkuncjBQ1LstzIm7bX5h4UKuRNrIA=', qop='auth'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:447] DEBUG:  calculated response = 6ae930ba0b9b6150dc146587ead4940a
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:468] DEBUG:  Auth req hdr: 'Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noBFP55tjkuncjBQ1LstzIm7bX5h4UKuRNrIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="73bd14fd", nc=00000001, response="6ae930ba0b9b6150dc146587ead4940a", algorithm=MD5.'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 51 to list of sent requests.
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:127.0.0.1:5080>>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5080) to int (5080)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKfaDfgaMU
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKfaDfgaMU;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noBFP55tjkuncjBQ1LstzIm7bX5h4UKuRNrIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="73bd14fd", nc=00000001, response="6ae930ba0b9b6150dc146587ead4940a", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKfaDfgaMU;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noBFP55tjkuncjBQ1LstzIm7bX5h4UKuRNrIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="73bd14fd", nc=00000001, response="6ae930ba0b9b6150dc146587ead4940a", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340b09d0)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=171636 (repeated=0)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=173211 (repeated=0)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:234] DEBUG:  authenticated request successfully sent.
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 200 OK..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKfaDfgaMU;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=48454647-53F9E6D80006F1BD-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.02b4..CSeq: 51 REGISTER..Call-ID: 4FB91CB7-53F9E6D80006F24E-336A4700..Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKfaDfgaMU
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 200, trans=0x7f2b340b09d0)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340afb90)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340afb00)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=171863 (repeated=0)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 200 OK
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <4FB91CB7-53F9E6D80006F24E-336A4700>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <48454647-53F9E6D80006F1BD-335A3700>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.02b4>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <51>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [4FB91CB7-53F9E6D80006F24E-336A4700|48454647-53F9E6D80006F1BD-335A3700] ru SIP reply 200 OK handled ^^
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '48454647-53F9E6D80006F1BD-335A3700'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533444816' (this = 139823532783808)
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 200 OK): transaction found!
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:287] DEBUG:  positive reply to REGISTER!
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:127.0.0.1:5080>..'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  'Contact:'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      ''
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '127.0.0.1'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5080'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     ''
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  ''
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      'ngcp-lb'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '178.63.53.154'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5060'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     'ngcpct=7369703a3132372e302e302e313a35303830'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:493] DEBUG:   param     'expires'='3600'
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:21:28 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:345] DEBUG:  no matching Contact - deregistered.
Aug 24 15:21:29 sip ngcp-sems[7535]: [#7f2b336a4700] [checkTimeouts, SIPRegistrarClient.cpp:123] DEBUG:  removing registration
Aug 24 15:21:29 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:729] DEBUG:  callid = 4FB91CB7-53F9E6D80006F24E-336A4700
Aug 24 15:21:29 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:730] DEBUG:  local_tag = 48454647-53F9E6D80006F1BD-335A3700
Aug 24 15:21:29 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:731] DEBUG:  uac_trans.size() = 0
Aug 24 15:21:29 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:739] DEBUG:  uas_trans.size() = 0
Aug 24 15:21:33 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340af0a0, eta=171861, t=171861
Aug 24 15:21:33 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110c6d0)
Aug 24 15:21:33 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340b09d0, eta=171863, t=171863
Aug 24 15:21:33 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x1104990)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b335a3700] [run, RegistrationAgent.cpp:190] DEBUG:  Registration 0 does not exist or timeout. Creating registration.
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b335a3700] [create_registration, RegistrationAgent.cpp:131] DEBUG:  calling createRegistration
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:200] DEBUG:  enabling UAC Auth for new registration.
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:208] DEBUG:  arg type is 6
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [add_reg, SIPRegistrarClient.cpp:306] DEBUG:  adding registration '787511CD-53F9E6E20006F39C-335A3700'  (this = 139823532783808)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 50 to list of sent requests.
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKn4lvxaOR
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKn4lvxaOR;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 69900D25-53F9E6E20006F41F-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKn4lvxaOR;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 69900D25-53F9E6E20006F41F-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340af130)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=172134 (repeated=0)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=173709 (repeated=0)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKn4lvxaOR;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.effa..CSeq: 50 REGISTER..Call-ID: 69900D25-53F9E6E20006F41F-336A4700..WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noDlP55uLBj5/xUNgN16TYkhU9KO28KuRXtoA=", qop="auth"..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKn4lvxaOR
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 401, trans=0x7f2b340af130)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340adf00)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340ad690)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=172361 (repeated=0)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 401 Unauthorized
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <69900D25-53F9E6E20006F41F-336A4700>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <787511CD-53F9E6E20006F39C-335A3700>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.effa>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <50>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noDlP55uLBj5/xUNgN16TYkhU9KO28KuRXtoA=", qop="auth"..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [69900D25-53F9E6E20006F41F-336A4700|787511CD-53F9E6E20006F39C-335A3700] ru SIP reply 401 Unauthorized handled ^^
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '787511CD-53F9E6E20006F39C-335A3700'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533444976' (this = 139823532783808)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 401 Unauthorized): transaction found!
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:165] DEBUG:  SIP reply with code 401 cseq 50 .
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:171] DEBUG:   UACAuth - processing with reply code 401
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:401] DEBUG:  realm='sip.nl.didlogic.net', nonce='U/noDlP55uLBj5/xUNgN16TYkhU9KO28KuRXtoA=', qop='auth'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:447] DEBUG:  calculated response = e39a0e12e8a9cf26cbe0d8324f41302a
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:468] DEBUG:  Auth req hdr: 'Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noDlP55uLBj5/xUNgN16TYkhU9KO28KuRXtoA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="05fab516", nc=00000001, response="e39a0e12e8a9cf26cbe0d8324f41302a", algorithm=MD5.'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 51 to list of sent requests.
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:127.0.0.1:5080>>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5080) to int (5080)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKGBcD~aYW
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKGBcD~aYW;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 69900D25-53F9E6E20006F41F-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noDlP55uLBj5/xUNgN16TYkhU9KO28KuRXtoA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="05fab516", nc=00000001, response="e39a0e12e8a9cf26cbe0d8324f41302a", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKGBcD~aYW;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 69900D25-53F9E6E20006F41F-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noDlP55uLBj5/xUNgN16TYkhU9KO28KuRXtoA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="05fab516", nc=00000001, response="e39a0e12e8a9cf26cbe0d8324f41302a", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340b0a60)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=172136 (repeated=0)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=173711 (repeated=0)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:234] DEBUG:  authenticated request successfully sent.
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 200 OK..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKGBcD~aYW;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=787511CD-53F9E6E20006F39C-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.c1fc..CSeq: 51 REGISTER..Call-ID: 69900D25-53F9E6E20006F41F-336A4700..Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKGBcD~aYW
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 200, trans=0x7f2b340b0a60)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340afc20)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340afb90)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=172363 (repeated=0)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 200 OK
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <69900D25-53F9E6E20006F41F-336A4700>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <787511CD-53F9E6E20006F39C-335A3700>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.c1fc>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <51>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [69900D25-53F9E6E20006F41F-336A4700|787511CD-53F9E6E20006F39C-335A3700] ru SIP reply 200 OK handled ^^
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '787511CD-53F9E6E20006F39C-335A3700'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533444976' (this = 139823532783808)
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 200 OK): transaction found!
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:287] DEBUG:  positive reply to REGISTER!
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:127.0.0.1:5080>..'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  'Contact:'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      ''
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '127.0.0.1'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5080'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     ''
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  ''
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      'ngcp-lb'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '178.63.53.154'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5060'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     'ngcpct=7369703a3132372e302e302e313a35303830'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:493] DEBUG:   param     'expires'='3600'
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:21:38 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:345] DEBUG:  no matching Contact - deregistered.
Aug 24 15:21:39 sip ngcp-sems[7535]: [#7f2b336a4700] [checkTimeouts, SIPRegistrarClient.cpp:123] DEBUG:  removing registration
Aug 24 15:21:39 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:729] DEBUG:  callid = 69900D25-53F9E6E20006F41F-336A4700
Aug 24 15:21:39 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:730] DEBUG:  local_tag = 787511CD-53F9E6E20006F39C-335A3700
Aug 24 15:21:39 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:731] DEBUG:  uac_trans.size() = 0
Aug 24 15:21:39 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:739] DEBUG:  uas_trans.size() = 0
Aug 24 15:21:43 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340af130, eta=172361, t=172361
Aug 24 15:21:43 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110ce50)
Aug 24 15:21:43 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340b0a60, eta=172363, t=172363
Aug 24 15:21:43 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110c3a0)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b335a3700] [run, RegistrationAgent.cpp:190] DEBUG:  Registration 0 does not exist or timeout. Creating registration.
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b335a3700] [create_registration, RegistrationAgent.cpp:131] DEBUG:  calling createRegistration
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:200] DEBUG:  enabling UAC Auth for new registration.
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:208] DEBUG:  arg type is 6
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [add_reg, SIPRegistrarClient.cpp:306] DEBUG:  adding registration '2D514284-53F9E6EC0006F518-335A3700'  (this = 139823532783808)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 50 to list of sent requests.
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKbaHziaA7
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKbaHziaA7;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKbaHziaA7;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340af1d0)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=172634 (repeated=0)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=174209 (repeated=0)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKbaHziaA7;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.593c..CSeq: 50 REGISTER..Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700..WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noGFP55uzXlBDyjSfe/byaKGFpX8ftKuRdvIA=", qop="auth"..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKbaHziaA7
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 401, trans=0x7f2b340af1d0)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340adf00)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340adfa0)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=172861 (repeated=0)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 401 Unauthorized
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <2453E84D-53F9E6EC0006F57A-336A4700>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <2D514284-53F9E6EC0006F518-335A3700>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.593c>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <50>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noGFP55uzXlBDyjSfe/byaKGFpX8ftKuRdvIA=", qop="auth"..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [2453E84D-53F9E6EC0006F57A-336A4700|2D514284-53F9E6EC0006F518-335A3700] ru SIP reply 401 Unauthorized handled ^^
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '2D514284-53F9E6EC0006F518-335A3700'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533445168' (this = 139823532783808)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 401 Unauthorized): transaction found!
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:165] DEBUG:  SIP reply with code 401 cseq 50 .
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:171] DEBUG:   UACAuth - processing with reply code 401
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:401] DEBUG:  realm='sip.nl.didlogic.net', nonce='U/noGFP55uzXlBDyjSfe/byaKGFpX8ftKuRdvIA=', qop='auth'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:447] DEBUG:  calculated response = 6fedb095f14d0ea80d93de4d77c390f8
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:468] DEBUG:  Auth req hdr: 'Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noGFP55uzXlBDyjSfe/byaKGFpX8ftKuRdvIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="2fe95026", nc=00000001, response="6fedb095f14d0ea80d93de4d77c390f8", algorithm=MD5.'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 51 to list of sent requests.
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:127.0.0.1:5080>>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5080) to int (5080)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKes8MGaO1
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKes8MGaO1;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noGFP55uzXlBDyjSfe/byaKGFpX8ftKuRdvIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="2fe95026", nc=00000001, response="6fedb095f14d0ea80d93de4d77c390f8", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKes8MGaO1;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noGFP55uzXlBDyjSfe/byaKGFpX8ftKuRdvIA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="2fe95026", nc=00000001, response="6fedb095f14d0ea80d93de4d77c390f8", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340b0b30)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=172636 (repeated=0)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=174211 (repeated=0)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:234] DEBUG:  authenticated request successfully sent.
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 200 OK..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKes8MGaO1;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=2D514284-53F9E6EC0006F518-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.22c2..CSeq: 51 REGISTER..Call-ID: 2453E84D-53F9E6EC0006F57A-336A4700..Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKes8MGaO1
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 200, trans=0x7f2b340b0b30)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340afcf0)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340afc60)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=172863 (repeated=0)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 200 OK
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <2453E84D-53F9E6EC0006F57A-336A4700>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <2D514284-53F9E6EC0006F518-335A3700>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.22c2>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <51>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [2453E84D-53F9E6EC0006F57A-336A4700|2D514284-53F9E6EC0006F518-335A3700] ru SIP reply 200 OK handled ^^
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '2D514284-53F9E6EC0006F518-335A3700'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533445168' (this = 139823532783808)
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 200 OK): transaction found!
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:287] DEBUG:  positive reply to REGISTER!
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:127.0.0.1:5080>..'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  'Contact:'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      ''
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '127.0.0.1'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5080'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     ''
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  ''
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      'ngcp-lb'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '178.63.53.154'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5060'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     'ngcpct=7369703a3132372e302e302e313a35303830'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:493] DEBUG:   param     'expires'='3600'
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:21:48 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:345] DEBUG:  no matching Contact - deregistered.
Aug 24 15:21:49 sip ngcp-sems[7535]: [#7f2b336a4700] [checkTimeouts, SIPRegistrarClient.cpp:123] DEBUG:  removing registration
Aug 24 15:21:49 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:729] DEBUG:  callid = 2453E84D-53F9E6EC0006F57A-336A4700
Aug 24 15:21:49 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:730] DEBUG:  local_tag = 2D514284-53F9E6EC0006F518-335A3700
Aug 24 15:21:49 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:731] DEBUG:  uac_trans.size() = 0
Aug 24 15:21:49 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:739] DEBUG:  uas_trans.size() = 0
Aug 24 15:21:53 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340af1d0, eta=172861, t=172861
Aug 24 15:21:53 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110ce50)
Aug 24 15:21:53 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340b0b30, eta=172863, t=172863
Aug 24 15:21:53 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110c3a0)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b335a3700] [run, RegistrationAgent.cpp:190] DEBUG:  Registration 0 does not exist or timeout. Creating registration.
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b335a3700] [create_registration, RegistrationAgent.cpp:131] DEBUG:  calling createRegistration
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:200] DEBUG:  enabling UAC Auth for new registration.
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:208] DEBUG:  arg type is 6
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [add_reg, SIPRegistrarClient.cpp:306] DEBUG:  adding registration '4E10B8B8-53F9E6F60006F697-335A3700'  (this = 139823532783808)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 50 to list of sent requests.
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKzDj.Yame
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKzDj.Yame;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 1D470EB4-53F9E6F60006F732-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKzDj.Yame;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 1D470EB4-53F9E6F60006F732-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340af270)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=173134 (repeated=0)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=174709 (repeated=0)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKzDj.Yame;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.700d..CSeq: 50 REGISTER..Call-ID: 1D470EB4-53F9E6F60006F732-336A4700..WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noIlP55vZgF/FyiW4hxtCeXisjIyoPKuRkw4A=", qop="auth"..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKzDj.Yame
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 401, trans=0x7f2b340af270)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340ae060)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340adf60)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=173361 (repeated=0)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 401 Unauthorized
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <1D470EB4-53F9E6F60006F732-336A4700>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <4E10B8B8-53F9E6F60006F697-335A3700>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.700d>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <50>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noIlP55vZgF/FyiW4hxtCeXisjIyoPKuRkw4A=", qop="auth"..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31a3f700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [1D470EB4-53F9E6F60006F732-336A4700|4E10B8B8-53F9E6F60006F697-335A3700] ru SIP reply 401 Unauthorized handled ^^
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '4E10B8B8-53F9E6F60006F697-335A3700'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533445328' (this = 139823532783808)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 401 Unauthorized): transaction found!
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:165] DEBUG:  SIP reply with code 401 cseq 50 .
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:171] DEBUG:   UACAuth - processing with reply code 401
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:401] DEBUG:  realm='sip.nl.didlogic.net', nonce='U/noIlP55vZgF/FyiW4hxtCeXisjIyoPKuRkw4A=', qop='auth'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:447] DEBUG:  calculated response = 8a9d3fce482f4e807da7b9763527d86c
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:468] DEBUG:  Auth req hdr: 'Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noIlP55vZgF/FyiW4hxtCeXisjIyoPKuRkw4A=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="5c0c87e5", nc=00000001, response="8a9d3fce482f4e807da7b9763527d86c", algorithm=MD5.'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 51 to list of sent requests.
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:127.0.0.1:5080>>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5080) to int (5080)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKu4oByaHU
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKu4oByaHU;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 1D470EB4-53F9E6F60006F732-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noIlP55vZgF/FyiW4hxtCeXisjIyoPKuRkw4A=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="5c0c87e5", nc=00000001, response="8a9d3fce482f4e807da7b9763527d86c", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKu4oByaHU;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 1D470EB4-53F9E6F60006F732-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noIlP55vZgF/FyiW4hxtCeXisjIyoPKuRkw4A=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="5c0c87e5", nc=00000001, response="8a9d3fce482f4e807da7b9763527d86c", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340b0de0)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=173136 (repeated=0)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=174711 (repeated=0)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:234] DEBUG:  authenticated request successfully sent.
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 200 OK..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKu4oByaHU;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=4E10B8B8-53F9E6F60006F697-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.3af1..CSeq: 51 REGISTER..Call-ID: 1D470EB4-53F9E6F60006F732-336A4700..Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKu4oByaHU
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 200, trans=0x7f2b340b0de0)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340affa0)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340aff10)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=173363 (repeated=0)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 200 OK
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <1D470EB4-53F9E6F60006F732-336A4700>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <4E10B8B8-53F9E6F60006F697-335A3700>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.3af1>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <51>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b31d42700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [1D470EB4-53F9E6F60006F732-336A4700|4E10B8B8-53F9E6F60006F697-335A3700] ru SIP reply 200 OK handled ^^
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '4E10B8B8-53F9E6F60006F697-335A3700'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533445328' (this = 139823532783808)
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 200 OK): transaction found!
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:287] DEBUG:  positive reply to REGISTER!
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:127.0.0.1:5080>..'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  'Contact:'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      ''
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '127.0.0.1'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5080'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     ''
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  ''
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      'ngcp-lb'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '178.63.53.154'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5060'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     'ngcpct=7369703a3132372e302e302e313a35303830'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:493] DEBUG:   param     'expires'='3600'
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:21:58 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:345] DEBUG:  no matching Contact - deregistered.
Aug 24 15:21:59 sip ngcp-sems[7535]: [#7f2b336a4700] [checkTimeouts, SIPRegistrarClient.cpp:123] DEBUG:  removing registration
Aug 24 15:21:59 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:729] DEBUG:  callid = 1D470EB4-53F9E6F60006F732-336A4700
Aug 24 15:21:59 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:730] DEBUG:  local_tag = 4E10B8B8-53F9E6F60006F697-335A3700
Aug 24 15:21:59 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:731] DEBUG:  uac_trans.size() = 0
Aug 24 15:21:59 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:739] DEBUG:  uas_trans.size() = 0
Aug 24 15:22:03 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340af270, eta=173361, t=173361
Aug 24 15:22:03 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110d110)
Aug 24 15:22:03 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340b0de0, eta=173363, t=173363
Aug 24 15:22:03 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110c8c0)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b335a3700] [run, RegistrationAgent.cpp:190] DEBUG:  Registration 0 does not exist or timeout. Creating registration.
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b335a3700] [create_registration, RegistrationAgent.cpp:131] DEBUG:  calling createRegistration
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:200] DEBUG:  enabling UAC Auth for new registration.
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onNewRegistration, SIPRegistrarClient.cpp:208] DEBUG:  arg type is 6
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [add_reg, SIPRegistrarClient.cpp:306] DEBUG:  adding registration '6DC60B4A-53F9E7000006F8CF-335A3700'  (this = 139823532783808)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 50 to list of sent requests.
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKoVz~mavx
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKoVz~mavx;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKoVz~mavx;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 50 REGISTER..Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340af590)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=173634 (repeated=0)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=175209 (repeated=0)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKoVz~mavx;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.5b30..CSeq: 50 REGISTER..Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700..WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noLFP55wAzGtxxRay2h+7wgTYNu/3+KuRsy4A=", qop="auth"..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKoVz~mavx
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 401, trans=0x7f2b340af590)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340ad4e0)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340aefc0)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=173862 (repeated=0)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 401 Unauthorized
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <03D5CD86-53F9E7000006F9F7-336A4700>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <6DC60B4A-53F9E7000006F8CF-335A3700>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.5b30>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <50>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/noLFP55wAzGtxxRay2h+7wgTYNu/3+KuRsy4A=", qop="auth"..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [03D5CD86-53F9E7000006F9F7-336A4700|6DC60B4A-53F9E7000006F8CF-335A3700] ru SIP reply 401 Unauthorized handled ^^
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '6DC60B4A-53F9E7000006F8CF-335A3700'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533451424' (this = 139823532783808)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 401 Unauthorized): transaction found!
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:165] DEBUG:  SIP reply with code 401 cseq 50 .
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:171] DEBUG:   UACAuth - processing with reply code 401
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:401] DEBUG:  realm='sip.nl.didlogic.net', nonce='U/noLFP55wAzGtxxRay2h+7wgTYNu/3+KuRsy4A=', qop='auth'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:447] DEBUG:  calculated response = bdea74007da499b07d7eb94b7df5cdde
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:468] DEBUG:  Auth req hdr: 'Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noLFP55wAzGtxxRay2h+7wgTYNu/3+KuRsy4A=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="1e9d466d", nc=00000001, response="bdea74007da499b07d7eb94b7df5cdde", algorithm=MD5.'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 51 to list of sent requests.
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:127.0.0.1:5080>>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5080) to int (5080)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.63.53.154:5060>>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKQD~OaayI
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKQD~OaayI;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noLFP55wAzGtxxRay2h+7wgTYNu/3+KuRsy4A=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="1e9d466d", nc=00000001, response="bdea74007da499b07d7eb94b7df5cdde", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0.......>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKQD~OaayI;rport..From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700..To: <sip:84757 at sip.nl.didlogic.net>..CSeq: 51 REGISTER..Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="84757", realm="sip.nl.didlogic.net", nonce="U/noLFP55wAzGtxxRay2h+7wgTYNu/3+KuRsy4A=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="1e9d466d", nc=00000001, response="bdea74007da499b07d7eb94b7df5cdde", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.63.53.154:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x7f2b340b0e30)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=173637 (repeated=0)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=175212 (repeated=0)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:234] DEBUG:  authenticated request successfully sent.
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 200 OK..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKQD~OaayI;rport=5080..From: <sip:84757 at sip.nl.didlogic.net>;tag=6DC60B4A-53F9E7000006F8CF-335A3700..To: <sip:84757 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fee5..CSeq: 51 REGISTER..Call-ID: 03D5CD86-53F9E7000006F9F7-336A4700..Contact: <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4....--++--
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKQD~OaayI
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 200, trans=0x7f2b340b0e30)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x7f2b340affe0)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x7f2b340b0070)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=173863 (repeated=0)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 200 OK
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <03D5CD86-53F9E7000006F9F7-336A4700>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <6DC60B4A-53F9E7000006F8CF-335A3700>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.fee5>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <51>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [03D5CD86-53F9E7000006F9F7-336A4700|6DC60B4A-53F9E7000006F8CF-335A3700] ru SIP reply 200 OK handled ^^
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '6DC60B4A-53F9E7000006F8CF-335A3700'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '139823533451424' (this = 139823532783808)
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 200 OK): transaction found!
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:287] DEBUG:  positive reply to REGISTER!
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:127.0.0.1:5080>..'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  'Contact:'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      ''
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '127.0.0.1'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5080'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     ''
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:ngcp-lb at 178.63.53.154:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  ''
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      'ngcp-lb'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '178.63.53.154'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5060'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     'ngcpct=7369703a3132372e302e302e313a35303830'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:493] DEBUG:   param     'expires'='3600'
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 15:22:08 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:345] DEBUG:  no matching Contact - deregistered.
Aug 24 15:22:09 sip ngcp-sems[7535]: [#7f2b336a4700] [checkTimeouts, SIPRegistrarClient.cpp:123] DEBUG:  removing registration
Aug 24 15:22:09 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:729] DEBUG:  callid = 03D5CD86-53F9E7000006F9F7-336A4700
Aug 24 15:22:09 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:730] DEBUG:  local_tag = 6DC60B4A-53F9E7000006F8CF-335A3700
Aug 24 15:22:09 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:731] DEBUG:  uac_trans.size() = 0
Aug 24 15:22:09 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmBasicSipDialog.cpp:739] DEBUG:  uas_trans.size() = 0
Aug 24 15:22:13 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x7f2b340af590, eta=173862, t=173862

From jbonilla at sipwise.com  Sun Aug 24 13:17:36 2014
From: jbonilla at sipwise.com (Jon Bonilla (Manwe))
Date: Sun, 24 Aug 2014 19:17:36 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53F9EC2B.2090406@hakwerk.com>
References: <53F9AAE5.2090904@hakwerk.com> <53F9D9E4.40601@sipwise.com>
 <53F9EC2B.2090406@hakwerk.com>
Message-ID: <20140824191736.08d81fc1@quenya>

El Sun, 24 Aug 2014 15:44:11 +0200
Arjan Hakkesteegt <arjan at hakwerk.com> escribi?:

> I attached the output from "ngrep-sip didlogic" for a minute or so, 
> showing the 10 sec interval. I also included the sems.log for that same 
> period.
> 
> I did a grep on expire in all logfiles in /var/log/ngcp/ but there never 
> is an expires: 0 in the logs, only 3600. Any other idea how to find such 
> an unREGISTER?
> 
> 

There was a bug regarding sems not matching contact last week. It was already
fixed in master but maybe it hasn't been released yet.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140824/a421011f/attachment-0001.asc>

From arjan at hakwerk.com  Sun Aug 24 13:27:59 2014
From: arjan at hakwerk.com (Arjan Hakkesteegt)
Date: Sun, 24 Aug 2014 19:27:59 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53F9EC2B.2090406@hakwerk.com>
References: <53F9AAE5.2090904@hakwerk.com> <53F9D9E4.40601@sipwise.com>
 <53F9EC2B.2090406@hakwerk.com>
Message-ID: <53FA209F.4060908@hakwerk.com>

I have been playing around some more, and if I force the Contact header 
of the peer reply in my kamailio.cfg.customtt.tt2 (near the end in 
onreply_route():
     remove_hf("Contact");
     append_hf("Contact: <sip:127.0.0.1:5080>;expires=200\r\n");
), then it works (at least for this particular scenario, and it is 
ignored when handling the 401 unauthorized):

U 2014/08/24 16:21:10.488831 72.251.241.166:5060 -> 178.X.Y.Z:5060
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 
178.X.Y.Z;branch=z9hG4bK09ac.08655b889dff04f59a713f0f644d643d.0;rport=5060'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK2jcbeaSi;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=478F2D6E-53F9F40C000A5CB8-335A3700'
To: 
<sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.434f'
CSeq: 55 REGISTER'
Call-ID: 32D4C33B-53F9F40C000A5D59-336A4700'
Contact: 
<sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600'
Content-Length: 0'
'


U 2014/08/24 16:21:10.489967 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK2jcbeaSi;rport=5080'
From: 
<sip:12345 at sip.nl.didlogic.net>;tag=478F2D6E-53F9F40C000A5CB8-335A3700'
To: 
<sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.434f'
CSeq: 55 REGISTER'
Call-ID: 32D4C33B-53F9F40C000A5D59-336A4700'
Content-Length: 0'
P-NGCP-Src-Ip: 72.251.241.166'
P-NGCP-Src-Port: 5060'
P-NGCP-Src-Proto: udp'
P-NGCP-Src-Af: 4'
Contact: <sip:127.0.0.1:5080>;expires=200'
'

That is, then I see the SEMS registering the reply and counting down 
from 200sec (see attached SEMS log).
At 50% of the expires value it will reregister, as per the following 
method I guess:

bool AmSIPRegistration::timeToReregister(time_t now_sec) {
     return (((unsigned long)reg_begin+ reg_expires/2) < (unsigned 
long)now_sec);
}


I'm still trying to get the hang of all the logic in the kamailio.cfg 
routing and I have no idea of all the SIP scenarios involved, but in 
general I would expect that for incoming messages to the loadbalancer 
that have ngcpct set, kamailio should unmask the contact. Or is that too 
simplistic?


Regards,
Arjan


> Arjan Hakkesteegt <mailto:arjan at hakwerk.com>
> Sunday, August 24, 2014 15:44
> I attached the output from "ngrep-sip didlogic" for a minute or so, 
> showing the 10 sec interval. I also included the sems.log for that 
> same period.
>
> I did a grep on expire in all logfiles in /var/log/ngcp/ but there 
> never is an expires: 0 in the logs, only 3600. Any other idea how to 
> find such an unREGISTER?
>
> Arjan
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> Daniel Grotti <mailto:dgrotti at sipwise.com>
> Sunday, August 24, 2014 14:26
> Hi,
> sorry in the trace below I just see the registration process at 09:39:43.
> Where do you see the second REGISTER after 10sec ? It should 
> Re-REGISTER again after 3600 sec.
>
> Also I don't see the unREGISTER message (with Expires: 0).
> Can you provide such messages ?
>
> Daniel
>
>
>
>
>
>
>
> On 08/24/2014 11:05 AM, Arjan Hakkesteegt wrote:
>
> Arjan Hakkesteegt <mailto:arjan at hakwerk.com>
> Sunday, August 24, 2014 11:05
> Hi all,
>
> I have a fresh install of mr3.4.1 (actually I messed up upgrading from 
> 3.3.1 on a mysql error and didn't have a proper backup; my bad. 
> Completey wiped the VM and started from scratch).
> SEMS is successfully registering with my SIP trunk provider, I can 
> call to and be called from the PSTN.
> However, looking at the sems logs ("debug: 'yes'" in config.yml, 
> attached), it is re-registering every 10 seconds because of a "no 
> matching Contact - deregistered" error.
>
> Below is the output of ngrep-sip for one attempt. I'm no expert but it 
> looks like the unmasking of the contact fails in kamailio-lb.
> 178.X.Y.Z = public IP address
> 12345 = didlogic user id
>
> I'd appreciate any help.
>
> Thanks,
> Arjan
>
>
>
> U 2014/08/24 09:39:43.210372 127.0.0.1:5080 -> 127.0.0.1:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Route: <sip:127.0.0.1:5060;lr>'
> Max-Forwards: 70'
> Expires: 3600'
> User-Agent: Sipwise NGCP Application Server 3.X'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.211469 178.X.Y.Z:5060 -> 72.251.241.166:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Max-Forwards: 69'
> Expires: 3600'
> User-Agent: Sipwise NGCP Application Server 3.X'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.258182 72.251.241.166:5060 -> 178.X.Y.Z:5060
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKc603.4d33604a362202e4562c26f0f8afb615.0;rport=5060' 
>
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6' 
>
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> WWW-Authenticate: Digest realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.258552 127.0.0.1:5060 -> 127.0.0.1:5080
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIG5LNa8x;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fae6' 
>
> CSeq: 50 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> WWW-Authenticate: Digest realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", qop="auth"'
> Content-Length: 0'
> P-NGCP-Src-Ip: 72.251.241.166'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> '
>
>
> U 2014/08/24 09:39:43.260249 127.0.0.1:5080 -> 127.0.0.1:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Route: <sip:127.0.0.1:5060;lr>'
> Max-Forwards: 70'
> Expires: 3600'
> Authorization: Digest username="12345", realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", 
> uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7", 
> nc=00000001, response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
> Contact: <sip:127.0.0.1:5080;transport=udp>'
> Contact: <sip:178.X.Y.Z:5060;transport=udp>'
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.260751 178.X.Y.Z:5060 -> 72.251.241.166:5060
> REGISTER sip:sip.nl.didlogic.net SIP/2.0'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: <sip:12345 at sip.nl.didlogic.net>'
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Max-Forwards: 69'
> Expires: 3600'
> Authorization: Digest username="12345", realm="sip.nl.didlogic.net", 
> nonce="U/mX61P5lr9U1NSl+99whZC51Z20733QKpDIeoA=", 
> uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="570de1e7", 
> nc=00000001, response="2b54500d9b70647866d0190affd850a0", algorithm=MD5'
> Content-Length: 0'
> Contact: 
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
> '
>
>
> U 2014/08/24 09:39:43.288129 72.251.241.166:5060 -> 178.X.Y.Z:5060
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP 
> 178.X.Y.Z;branch=z9hG4bKd603.3582e31aa520aa31282983c13533f2b7.0;rport=5060' 
>
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd' 
>
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Contact: 
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600' 
>
> Content-Length: 0'
> '
>
>
> U 2014/08/24 09:39:43.288567 127.0.0.1:5060 -> 127.0.0.1:5080
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKRaVVYaD1;rport=5080'
> From: 
> <sip:12345 at sip.nl.didlogic.net>;tag=227C9105-53F996BF00032EEE-6060F700'
> To: 
> <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.95fd' 
>
> CSeq: 51 REGISTER'
> Call-ID: 015670DF-53F996BF00033117-60710700'
> Contact: 
> <sip:ngcp-lb at 178.X.Y.Z:5060;ngcpct=7369703a3132372e302e302e313a35303830>;expires=3600' 
>
> Content-Length: 0'
> P-NGCP-Src-Ip: 72.251.241.166'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> '
>
> _______________________________________________
> 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/20140824/6b96274b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1321 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140824/6b96274b/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1214 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140824/6b96274b/attachment-0003.jpg>
-------------- next part --------------
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:287] DEBUG:  positive reply to REGISTER!
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:127.0.0.1:5080>..'
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  'Contact:'
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      ''
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '127.0.0.1'
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5080'
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     ''
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:127.0.0.1:5080>'
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  ''
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      ''
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '127.0.0.1'
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5080'
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     ''
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:493] DEBUG:   param     'expires'='200'
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:314] DEBUG:  contact found
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:321] DEBUG:  got an expires of 200
Aug 24 16:22:51 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:326] DEBUG:  posting SIPRegistrationEvent to 'reg_agent'
Aug 24 16:22:56 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x1110e10, eta=356010, t=356010
Aug 24 16:22:56 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x7f2b340b8d20)
Aug 24 16:22:56 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x1111fa0, eta=356012, t=356012
Aug 24 16:22:56 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110ed30)
Aug 24 16:22:58 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 193s for registration.
Aug 24 16:23:08 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 183s for registration.
Aug 24 16:23:18 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 173s for registration.
Aug 24 16:23:28 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 163s for registration.
Aug 24 16:23:38 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 153s for registration.
Aug 24 16:23:48 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 143s for registration.
Aug 24 16:23:58 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 133s for registration.
Aug 24 16:24:08 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 123s for registration.
Aug 24 16:24:18 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 113s for registration.
Aug 24 16:24:28 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 103s for registration.
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:401] DEBUG:  realm='sip.nl.didlogic.net', nonce='U/n2Z1P59TukBiMOs8y3EnmnaXMr2gXlKvJxwoA=', qop='auth'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:447] DEBUG:  calculated response = 91c7f87b81f92da2a04481c356e7abad
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:468] DEBUG:  Auth req hdr: 'Authorization: Digest username="12345", realm="sip.nl.didlogic.net", nonce="U/n2Z1P59TukBiMOs8y3EnmnaXMr2gXlKvJxwoA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="6413544c", nc=00000001, response="91c7f87b81f92da2a04481c356e7abad", algorithm=MD5.'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 58 to list of sent requests.
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.X.Y.Z:5060>>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKvtPSpazn
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKvtPSpazn;rport..From: <sip:12345 at sip.nl.didlogic.net>;tag=478F2D6E-53F9F40C000A5CB8-335A3700..To: <sip:12345 at sip.nl.didlogic.net>..CSeq: 58 REGISTER..Call-ID: 32D4C33B-53F9F40C000A5D59-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="12345", realm="sip.nl.didlogic.net", nonce="U/n2Z1P59TukBiMOs8y3EnmnaXMr2gXlKvJxwoA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="6413544c", nc=00000001, response="91c7f87b81f92da2a04481c356e7abad", algorithm=MD5..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.X.Y.Z:5060;transport=udp>..Content-Length: 0.......>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKvtPSpazn;rport..From: <sip:12345 at sip.nl.didlogic.net>;tag=478F2D6E-53F9F40C000A5CB8-335A3700..To: <sip:12345 at sip.nl.didlogic.net>..CSeq: 58 REGISTER..Call-ID: 32D4C33B-53F9F40C000A5D59-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="12345", realm="sip.nl.didlogic.net", nonce="U/n2Z1P59TukBiMOs8y3EnmnaXMr2gXlKvJxwoA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="6413544c", nc=00000001, response="91c7f87b81f92da2a04481c356e7abad", algorithm=MD5..User-Agent: Sipwise NGCP Application Server 3.X..Contact: <sip:178.X.Y.Z:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x1110dd0)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=360839 (repeated=0)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=362414 (repeated=0)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKvtPSpazn;rport=5080..From: <sip:12345 at sip.nl.didlogic.net>;tag=478F2D6E-53F9F40C000A5CB8-335A3700..To: <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.76fb..CSeq: 58 REGISTER..Call-ID: 32D4C33B-53F9F40C000A5D59-336A4700..WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/n2zFP59aDbAQoblFDHHtAO1gmzfMTGKvLKGoA=", qop="auth"..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..Contact: <sip:127.0.0.1:5080>;expires=200....--++--
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKvtPSpazn
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 401, trans=0x1110dd0)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x110ea70)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x1110540)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=361066 (repeated=0)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 401 Unauthorized
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <32D4C33B-53F9F40C000A5D59-336A4700>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <478F2D6E-53F9F40C000A5CB8-335A3700>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.76fb>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <<sip:127.0.0.1:5080>;expires=200>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <sip:127.0.0.1:5080>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <58>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <WWW-Authenticate: Digest realm="sip.nl.didlogic.net", nonce="U/n2zFP59aDbAQoblFDHHtAO1gmzfMTGKvLKGoA=", qop="auth"..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31b40700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [32D4C33B-53F9F40C000A5D59-336A4700|478F2D6E-53F9F40C000A5CB8-335A3700] ru SIP reply 401 Unauthorized handled ^^
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '478F2D6E-53F9F40C000A5CB8-335A3700'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '17878400' (this = 139823532783808)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 401 Unauthorized): transaction found!
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:165] DEBUG:  SIP reply with code 401 cseq 58 .
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:171] DEBUG:   UACAuth - processing with reply code 401
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:401] DEBUG:  realm='sip.nl.didlogic.net', nonce='U/n2zFP59aDbAQoblFDHHtAO1gmzfMTGKvLKGoA=', qop='auth'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:447] DEBUG:  calculated response = e3368a1d26ff55d154c269486175428a
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [do_auth, UACAuth.cpp:468] DEBUG:  Auth req hdr: 'Authorization: Digest username="12345", realm="sip.nl.didlogic.net", nonce="U/n2zFP59aDbAQoblFDHHtAO1gmzfMTGKvLKGoA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="040e06f4", nc=00000001, response="e3368a1d26ff55d154c269486175428a", algorithm=MD5.'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [onSendRequest, UACAuth.cpp:271] DEBUG:  adding 59 to list of sent requests.
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:921] DEBUG:  no transport specified, setting default one (udp)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [set_next_hop, trans_layer.cpp:928] DEBUG:  next_hop:next_port is <127.0.0.1:5060/udp>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [resolve_targets, resolver.cpp:1080] DEBUG:  sip_destination: 127.0.0.1:5060/udp
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1005] DEBUG:  checking whether '127.0.0.1' is IP address...
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [set_destination_ip, resolver.cpp:1063] DEBUG:  set destination to 127.0.0.1:5060
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:794] DEBUG:  target list:
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [debug, resolver.cpp:801] DEBUG:  #011127.0.0.1:5060/udp to target list
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1264] DEBUG:  send_request to R-URI <sip:sip.nl.didlogic.net>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:127.0.0.1:5080>>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5080) to int (5080)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [patch_contact_transport, trans_layer.cpp:160] DEBUG:  contact: <<sip:178.X.Y.Z:5060>>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port (5060) to int (5060)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_sip_uri, parse_uri.cpp:338] DEBUG:  Converted URI port () to int (5060)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKWQMR7aaK
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1300] DEBUG:  Sending to 127.0.0.1:5060 <REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKWQMR7aaK;rport..From: <sip:12345 at sip.nl.didlogic.net>;tag=478F2D6E-53F9F40C000A5CB8-335A3700..To: <sip:12345 at sip.nl.didlogic.net>..CSeq: 59 REGISTER..Call-ID: 32D4C33B-53F9F40C000A5D59-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="12345", realm="sip.nl.didlogic.net", nonce="U/n2zFP59aDbAQoblFDHHtAO1gmzfMTGKvLKGoA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="040e06f4", nc=00000001, response="e3368a1d26ff55d154c269486175428a", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.X.Y.Z:5060;transport=udp>..Content-Length: 0.......>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [send, udp_trsp.cpp:259] DEBUG: send  msg to 127.0.0.1:5060.--++--.REGISTER sip:sip.nl.didlogic.net SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKWQMR7aaK;rport..From: <sip:12345 at sip.nl.didlogic.net>;tag=478F2D6E-53F9F40C000A5CB8-335A3700..To: <sip:12345 at sip.nl.didlogic.net>..CSeq: 59 REGISTER..Call-ID: 32D4C33B-53F9F40C000A5D59-336A4700..Route: <sip:127.0.0.1:5060;lr>..Max-Forwards: 70..Expires: 3600..Authorization: Digest username="12345", realm="sip.nl.didlogic.net", nonce="U/n2zFP59aDbAQoblFDHHtAO1gmzfMTGKvLKGoA=", uri="sip:sip.nl.didlogic.net", qop=auth, cnonce="040e06f4", nc=00000001, response="e3368a1d26ff55d154c269486175428a", algorithm=MD5..Contact: <sip:127.0.0.1:5080;transport=udp>..Contact: <sip:178.X.Y.Z:5060;transport=udp>..Content-Length: 0....--++--
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1327] DEBUG:  update_uac_request tt->_t =(nil)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2040] DEBUG:  update_uac_request(t=0x11125d0)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [update_uac_request, trans_layer.cpp:2076] DEBUG:  transport = 'udp'; is_reliable = 0
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type E at time=360841 (repeated=0)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type F at time=362416 (repeated=0)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [send_request, trans_layer.cpp:1349] DEBUG:  logger = (nil)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, UACAuth.cpp:234] DEBUG:  authenticated request successfully sent.
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 127.0.0.1:5060 vv.--++--.SIP/2.0 200 OK..Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKWQMR7aaK;rport=5080..From: <sip:12345 at sip.nl.didlogic.net>;tag=478F2D6E-53F9F40C000A5CB8-335A3700..To: <sip:12345 at sip.nl.didlogic.net>;tag=b27e1a1d33761e85846fc98f5f3a7e58.0852..CSeq: 59 REGISTER..Call-ID: 32D4C33B-53F9F40C000A5D59-336A4700..Content-Length: 0..P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..Contact: <sip:127.0.0.1:5080>;expires=200....--++--
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [parse_via_params, parse_via.cpp:521] DEBUG:  parsed branch: z9hG4bKWQMR7aaK
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [parse_via_params, parse_via.cpp:544] DEBUG:  has_rport: 1
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [process_rcvd_msg, trans_layer.cpp:1708] DEBUG:  Reply matched an existing transaction
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [update_uac_reply, trans_layer.cpp:1766] DEBUG:  update_uac_reply(reply code = 200, trans=0x11125d0)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type E (this=0x110d8b0)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type F (this=0x11117a0)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [reset_timer, sip_trans.cpp:246] DEBUG:  New timer of type K at time=361068 (repeated=0)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:813] DEBUG:  Received reply: 200 OK
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:814] DEBUG:  reply.callid = <32D4C33B-53F9F40C000A5D59-336A4700>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:815] DEBUG:  reply.from_tag = <478F2D6E-53F9F40C000A5CB8-335A3700>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:816] DEBUG:  reply.to_tag = <b27e1a1d33761e85846fc98f5f3a7e58.0852>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:817] DEBUG:  reply.contact = <<sip:127.0.0.1:5080>;expires=200>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:818] DEBUG:  reply.to_uri = <sip:127.0.0.1:5080>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:819] DEBUG:  cseq = <59>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:820] DEBUG:  reply.route = <>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:821] DEBUG:  hdrs = <P-NGCP-Src-Ip: 72.251.241.166..P-NGCP-Src-Port: 5060..P-NGCP-Src-Proto: udp..P-NGCP-Src-Af: 4..>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:822] DEBUG:  body-ct = <>
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b31c41700] [handle_sip_reply, SipCtrlInterface.cpp:828] DEBUG:  ^^ M [32D4C33B-53F9F40C000A5D59-336A4700|478F2D6E-53F9F40C000A5CB8-335A3700] ru SIP reply 200 OK handled ^^
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:254] DEBUG:  get registration '478F2D6E-53F9F40C000A5CB8-335A3700'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [get_reg, SIPRegistrarClient.cpp:262] DEBUG:  get registration : res = '17878400' (this = 139823532783808)
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [onRxReply, AmBasicSipDialog.cpp:445] DEBUG:  onRxReply(rep = 200 OK): transaction found!
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:287] DEBUG:  positive reply to REGISTER!
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:127.0.0.1:5080>..'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  'Contact:'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      ''
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '127.0.0.1'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5080'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     ''
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:479] DEBUG:  --- Uri Info ---
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:480] DEBUG:   uri           '<sip:127.0.0.1:5080>'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:481] DEBUG:   display_name  ''
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:482] DEBUG:   uri_user      ''
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:483] DEBUG:   uri_host      '127.0.0.1'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:484] DEBUG:   uri_port      '5080'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:485] DEBUG:   uri_hdr       ''
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:486] DEBUG:   uri_param     ''
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:493] DEBUG:   param     'expires'='200'
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [dump, AmUriParser.cpp:495] DEBUG:  --------------------
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:314] DEBUG:  contact found
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:321] DEBUG:  got an expires of 200
Aug 24 16:24:32 sip ngcp-sems[7535]: [#7f2b336a4700] [onSipReply, AmSipRegistration.cpp:326] DEBUG:  posting SIPRegistrationEvent to 'reg_agent'
Aug 24 16:24:37 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x1110dd0, eta=361066, t=361066
Aug 24 16:24:37 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110d8f0)
Aug 24 16:24:37 sip ngcp-sems[7535]: [#7f2b31e43700] [fire, sip_trans.cpp:205] DEBUG:  Transaction timer expired: type=K, trans=0x11125d0, eta=361068, t=361068
Aug 24 16:24:37 sip ngcp-sems[7535]: [#7f2b31e43700] [reset_timer, sip_trans.cpp:188] DEBUG:  Clearing old timer of type K (this=0x110ff90)
Aug 24 16:24:38 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 194s for registration.
Aug 24 16:24:48 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 184s for registration.
Aug 24 16:24:58 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 174s for registration.
Aug 24 16:25:08 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 164s for registration.
Aug 24 16:25:18 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 154s for registration.
Aug 24 16:25:28 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 144s for registration.
Aug 24 16:25:38 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 134s for registration.
Aug 24 16:25:48 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 124s for registration.
Aug 24 16:25:58 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 114s for registration.
Aug 24 16:26:08 sip ngcp-sems[7535]: [#7f2b335a3700] [check_registration, RegistrationAgent.cpp:168] DEBUG:  Got state RegisterActive with expires 104s for registration.



From apogrebennyk at sipwise.com  Mon Aug 25 04:54:42 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Mon, 25 Aug 2014 10:54:42 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53FA209F.4060908@hakwerk.com>
References: <53F9AAE5.2090904@hakwerk.com> <53F9D9E4.40601@sipwise.com>
 <53F9EC2B.2090406@hakwerk.com> <53FA209F.4060908@hakwerk.com>
Message-ID: <53FAF9D2.3070702@sipwise.com>

Hi,

On 08/24/2014 07:27 PM, Arjan Hakkesteegt wrote:
> 
> I'm still trying to get the hang of all the logic in the kamailio.cfg
> routing and I have no idea of all the SIP scenarios involved, but in
> general I would expect that for incoming messages to the loadbalancer
> that have ngcpct set, kamailio should unmask the contact. Or is that too
> simplistic?

That's right, for incoming _requests_ with RURI: ngcpct@ kamailio should
unmask the contact URI from RURI. There is no such manipulation required
for the 200 OK response from the UA however.

The problem you are having really looks like the sems bug that Jon is
talking about. The fix however is only in our development trunk and not
in the mr3.4.1 release. I am going to backport it right now and will
reply again when we are good to test.

Andrew


From alutay at sipwise.com  Mon Aug 25 06:04:51 2014
From: alutay at sipwise.com (Alex Lutay)
Date: Mon, 25 Aug 2014 12:04:51 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53F9AAE5.2090904@hakwerk.com>
References: <53F9AAE5.2090904@hakwerk.com>
Message-ID: <53FB0A43.9080209@sipwise.com>

Dear Arjan!

I would like to inform you that ngcp-upgrade automatically
performs backup of all configs and DB snapshot to:
 > /var/backup/ngcp-${UPGRADE_VERSION}/
where UPGRADE_VERSION=mr3.4.1 in your case.

So, next time you can restore your data in case if something went wrong.

On 24/08/14 11:05, Arjan Hakkesteegt wrote:
> ... actually I messed up upgrading from 3.3.1 on a mysql error and didn't have a proper backup; my bad.  ...

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From apogrebennyk at sipwise.com  Mon Aug 25 07:40:19 2014
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Mon, 25 Aug 2014 13:40:19 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53FAF9D2.3070702@sipwise.com>
References: <53F9AAE5.2090904@hakwerk.com> <53F9D9E4.40601@sipwise.com>
 <53F9EC2B.2090406@hakwerk.com> <53FA209F.4060908@hakwerk.com>
 <53FAF9D2.3070702@sipwise.com>
Message-ID: <53FB20A3.2000508@sipwise.com>

Arjan, we are going to create the new release mr3.4.2 with that fix.
While it may take a day or two to do so, please try this package:
https://www.dropbox.com/s/foou1ujlnofvb53/ngcp-sems_1.6.0~20140819~0b6d12-1%2B0~mr3.4.2.0%2B0~20140825092947.264%2Bwheezy~1.gbp4477f1_amd64.deb?dl=0
Install with dpkg -i and it should resolve your problem with upstream
registration.

On 08/25/2014 10:54 AM, Andrew Pogrebennyk wrote:
> On 08/24/2014 07:27 PM, Arjan Hakkesteegt wrote:
>> > 
>> > I'm still trying to get the hang of all the logic in the kamailio.cfg
>> > routing and I have no idea of all the SIP scenarios involved, but in
>> > general I would expect that for incoming messages to the loadbalancer
>> > that have ngcpct set, kamailio should unmask the contact. Or is that too
>> > simplistic?
> That's right, for incoming _requests_ with RURI: ngcpct@ kamailio should
> unmask the contact URI from RURI. There is no such manipulation required
> for the 200 OK response from the UA however.
> 
> The problem you are having really looks like the sems bug that Jon is
> talking about. The fix however is only in our development trunk and not
> in the mr3.4.1 release. I am going to backport it right now and will
> reply again when we are good to test.
> 
> Andrew



From arjan at hakwerk.com  Mon Aug 25 15:45:00 2014
From: arjan at hakwerk.com (Arjan Hakkesteegt)
Date: Mon, 25 Aug 2014 21:45:00 +0200
Subject: [Spce-user] mr3.4.1 sems: "no matching Contact - deregistered"
 / kamailio-lb contact (un)masking
In-Reply-To: <53FB20A3.2000508@sipwise.com>
References: <53F9AAE5.2090904@hakwerk.com> <53F9D9E4.40601@sipwise.com>
 <53F9EC2B.2090406@hakwerk.com> <53FA209F.4060908@hakwerk.com>
 <53FAF9D2.3070702@sipwise.com> <53FB20A3.2000508@sipwise.com>
Message-ID: <53FB923C.7020701@hakwerk.com>

I can confirm that this new package solved the problem for me. Thanks 
for the excellent support!!
Also thank you Alex for the tip on the location of the backup for 
ngcp-upgrade :)

Regards,
Arjan


Andrew Pogrebennyk wrote:
> While it may take a day or two to do so, please try this package:
> https://www.dropbox.com/s/foou1ujlnofvb53/ngcp-sems_1.6.0~20140819~0b6d12-1%2B0~mr3.4.2.0%2B0~20140825092947.264%2Bwheezy~1.gbp4477f1_amd64.deb?dl=0
> Install with dpkg -i and it should resolve your problem with upstream
> registration.


From matthew at tenacit.net  Wed Aug 27 10:43:40 2014
From: matthew at tenacit.net (Matthew Ogden)
Date: Wed, 27 Aug 2014 16:43:40 +0200
Subject: [Spce-user] voip loopback test
Message-ID: <12f5e97bc390af65cbe042959eceacf0@mail.gmail.com>

Hi



Does spce have a number I can dial built-in that is a loopback test?



Regards





*Matthew Ogden*

Management

TenacIT







*Strategic IT Consulting *?* Advanced Networking *? *Virtualisation*

*Custom Development *? *Hosting *? *Syspro Support  *? *MS Licensing*

National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
matthew at tenacit.net

CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
http://www.tenacit.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4809 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment-0004.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 1031 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment-0005.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 1424 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment-0006.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 1287 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment-0007.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 3930 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 4536 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140827/387d486c/attachment-0003.png>

From tabi.tabe at gmail.com  Wed Aug 27 10:58:20 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Wed, 27 Aug 2014 16:58:20 +0200
Subject: [Spce-user] SPCE 3.2.1
Message-ID: <CAOibrm5-Z_bVq+=PeNkZGaY1bS_QsDDiKuNYhoSErnarBpQ-NA@mail.gmail.com>

Hi,

We have a strange issue with SPCE 3.2.1. It has stopped responding to SIP
request from other peers and from endpoints. Any ideas what could be wrong
and how to resolve it?

Much appreciated.


-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140827/e709f0bd/attachment-0001.html>

From dgrotti at sipwise.com  Wed Aug 27 11:33:00 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Wed, 27 Aug 2014 17:33:00 +0200
Subject: [Spce-user] SPCE 3.2.1
Message-ID: <20140827153329.B99A9150209F@zimbra.sipwise.com>

Hi,
Did you check if those IP have been banned?
Is lb still listening on the shared IP?

Is the platform not responding at all or just to some ips?

Daniel

On 27 Aug 2014 16:58, Tabi Tabe Tabi <tabi.tabe at gmail.com> wrote:
>
> Hi,
>
> We have a strange issue with SPCE 3.2.1. It has stopped responding to SIP request from other peers and from endpoints. Any ideas what could be wrong and how to resolve it?
>
> Much appreciated.
>
>
> -- 
> ...Tabi
>

From tabi.tabe at gmail.com  Wed Aug 27 11:43:02 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Wed, 27 Aug 2014 17:43:02 +0200
Subject: [Spce-user] SPCE 3.2.1
In-Reply-To: <20140827153329.B99A9150209F@zimbra.sipwise.com>
References: <20140827153329.B99A9150209F@zimbra.sipwise.com>
Message-ID: <CAOibrm40hDOUYnRmcrBveb6FUaDEvfjHjGJt8xG0tsPs5Xk3yA@mail.gmail.com>

Hi Daniel,

Checked. No IP address is banned.

How do I check ls lb is it is listening on share IP?

It is not responding to all IP addresses. However I can access the web
portal


Regards,

Tabi


On Wed, Aug 27, 2014 at 5:33 PM, Daniel Grotti <dgrotti at sipwise.com> wrote:

> Hi,
> Did you check if those IP have been banned?
> Is lb still listening on the shared IP?
>
> Is the platform not responding at all or just to some ips?
>
> Daniel
>
> On 27 Aug 2014 16:58, Tabi Tabe Tabi <tabi.tabe at gmail.com> wrote:
> >
> > Hi,
> >
> > We have a strange issue with SPCE 3.2.1. It has stopped responding to
> SIP request from other peers and from endpoints. Any ideas what could be
> wrong and how to resolve it?
> >
> > Much appreciated.
> >
> >
> > --
> > ...Tabi
> >
>



-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140827/e660cd26/attachment-0001.html>

From tabi.tabe at gmail.com  Wed Aug 27 11:53:18 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Wed, 27 Aug 2014 17:53:18 +0200
Subject: [Spce-user] SPCE 3.2.1
In-Reply-To: <CAOibrm40hDOUYnRmcrBveb6FUaDEvfjHjGJt8xG0tsPs5Xk3yA@mail.gmail.com>
References: <20140827153329.B99A9150209F@zimbra.sipwise.com>
 <CAOibrm40hDOUYnRmcrBveb6FUaDEvfjHjGJt8xG0tsPs5Xk3yA@mail.gmail.com>
Message-ID: <CAOibrm4Gu837p+u=qbgFsODtBmdbAhx-O68qZAcLR4Gn1BJ+7w@mail.gmail.com>

Hi Daniel,

I can see see traffic in kamailio-lb.log

Should I share that log with you?

Regards,

Tabi


On Wed, Aug 27, 2014 at 5:43 PM, Tabi Tabe Tabi <tabi.tabe at gmail.com> wrote:

> Hi Daniel,
>
> Checked. No IP address is banned.
>
> How do I check ls lb is it is listening on share IP?
>
> It is not responding to all IP addresses. However I can access the web
> portal
>
>
> Regards,
>
> Tabi
>
>
> On Wed, Aug 27, 2014 at 5:33 PM, Daniel Grotti <dgrotti at sipwise.com>
> wrote:
>
>> Hi,
>> Did you check if those IP have been banned?
>> Is lb still listening on the shared IP?
>>
>> Is the platform not responding at all or just to some ips?
>>
>> Daniel
>>
>> On 27 Aug 2014 16:58, Tabi Tabe Tabi <tabi.tabe at gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > We have a strange issue with SPCE 3.2.1. It has stopped responding to
>> SIP request from other peers and from endpoints. Any ideas what could be
>> wrong and how to resolve it?
>> >
>> > Much appreciated.
>> >
>> >
>> > --
>> > ...Tabi
>> >
>>
>
>
>
> --
> ...Tabi
>
>


-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140827/a14c494f/attachment-0001.html>

From vseva at sipwise.com  Wed Aug 27 12:44:51 2014
From: vseva at sipwise.com (Victor Seva)
Date: Wed, 27 Aug 2014 18:44:51 +0200
Subject: [Spce-user] SPCE 3.2.1
Message-ID: <20140827164455.3E5C3150209F@zimbra.sipwise.com>

An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140827/d1adb9ef/attachment-0001.html>

From dgrotti at sipwise.com  Wed Aug 27 12:59:49 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Wed, 27 Aug 2014 18:59:49 +0200
Subject: [Spce-user] voip loopback test
Message-ID: <20140827170018.42CEE150209E@zimbra.sipwise.com>

Hi,
We don't have a specific number.
It depends what you want to achieve, you can call the voicebox number for example or you can call another subscriber with a CF set to a mobile phone.
Again it depends what you mean with loopback test.

Daniel

On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
>
> Hi
>
> ?
>
> Does spce have a number I can dial built-in that is a loopback test?
>
> ?
>
> Regards
>
> ?
>
> ?
>
> Matthew Ogden
>
> Management
>
> TenacIT
>
> ?
>
> ?
>
> ?
>
> Strategic IT Consulting ? Advanced Networking ? Virtualisation
>
> Custom Development ? Hosting ? Syspro Support? ? MS Licensing
>
> National Tel: 041 10 10?100 | Cell: 084 205 4445 | Email: matthew at tenacit.net?
>
> CT Tel: 021?201 0333 | Skype Name: matthew.ogden | Web: http://www.tenacit.net
>
> ?
>
> ?????????
>
> ?

From jward01 at gmail.com  Wed Aug 27 15:20:03 2014
From: jward01 at gmail.com (Jeremy Ward)
Date: Wed, 27 Aug 2014 15:20:03 -0400
Subject: [Spce-user] voip loopback test
In-Reply-To: <20140827170018.42CEE150209E@zimbra.sipwise.com>
References: <20140827170018.42CEE150209E@zimbra.sipwise.com>
Message-ID: <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>

Not to stick my nose in something that it doesn't belong, but I think he is
referring to what asterisk calls an "echo test".

Its usually accessed via a star code (*31, if my memory serves me
correctly).

Hope this helps.

Jeremy D. Ward, CWNE
(954) 661-4965
On Aug 27, 2014 1:01 PM, "Daniel Grotti" <dgrotti at sipwise.com> wrote:

> Hi,
> We don't have a specific number.
> It depends what you want to achieve, you can call the voicebox number for
> example or you can call another subscriber with a CF set to a mobile phone.
> Again it depends what you mean with loopback test.
>
> Daniel
>
> On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
> >
> > Hi
> >
> >
> >
> > Does spce have a number I can dial built-in that is a loopback test?
> >
> >
> >
> > Regards
> >
> >
> >
> >
> >
> > Matthew Ogden
> >
> > Management
> >
> > TenacIT
> >
> >
> >
> >
> >
> >
> >
> > Strategic IT Consulting ? Advanced Networking ? Virtualisation
> >
> > Custom Development ? Hosting ? Syspro Support  ? MS Licensing
> >
> > National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
> matthew at tenacit.net
> >
> > CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
> http://www.tenacit.net
> >
> >
> >
> >
> >
> >
> _______________________________________________
> 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/20140827/a32c5662/attachment-0001.html>

From matthew at tenacit.net  Wed Aug 27 17:24:12 2014
From: matthew at tenacit.net (Matthew Ogden)
Date: Wed, 27 Aug 2014 23:24:12 +0200
Subject: [Spce-user] voip loopback test
In-Reply-To: <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>
References: <20140827170018.42CEE150209E@zimbra.sipwise.com>
 <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>
Message-ID: <8fe5440a16db354e530e18b3f58879e1@mail.gmail.com>

Thanks Jeremy, that?s exactly what I mean!



Echo test.



*From:* Jeremy Ward [mailto:jward01 at gmail.com]
*Sent:* 27 August 2014 09:20 PM
*To:* Daniel Grotti
*Cc:* spce-user at lists.sipwise.com; Matthew Ogden
*Subject:* Re: [Spce-user] voip loopback test



Not to stick my nose in something that it doesn't belong, but I think he is
referring to what asterisk calls an "echo test".

Its usually accessed via a star code (*31, if my memory serves me
correctly).

Hope this helps.

Jeremy D. Ward, CWNE
(954) 661-4965

On Aug 27, 2014 1:01 PM, "Daniel Grotti" <dgrotti at sipwise.com> wrote:

Hi,
We don't have a specific number.
It depends what you want to achieve, you can call the voicebox number for
example or you can call another subscriber with a CF set to a mobile phone.
Again it depends what you mean with loopback test.

Daniel

On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
>
> Hi
>
>
>
> Does spce have a number I can dial built-in that is a loopback test?
>
>
>
> Regards
>
>
>
>
>
> Matthew Ogden
>
> Management
>
> TenacIT
>
>
>
>
>
>
>
> Strategic IT Consulting ? Advanced Networking ? Virtualisation
>
> Custom Development ? Hosting ? Syspro Support  ? MS Licensing
>
> National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
matthew at tenacit.net
>
> CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
http://www.tenacit.net
>
>
>
>
>
>
_______________________________________________
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/20140827/e141453a/attachment-0001.html>

From george.mason at xoomtalk.com  Wed Aug 27 17:26:20 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Wed, 27 Aug 2014 22:26:20 +0100
Subject: [Spce-user] Problems getting calls rated v2.8
Message-ID: <53FE4CFC.5000307@xoomtalk.com>

Hi

Please forgive the question but am learning the ropes on SPCE and
struggling somewhat with billing.

I have created a billing fee which I am attempting to apply to a SIP
peering, such that call costs are included in the CDR table. I have
created a contract which references the fees and applied this to the
peering concerned. However when I place a call for which there should be
a cost, no cost is recorded in the CDR table, and the rated_at field is
NULL. This last detail is different if I use the default fee of zero,
rated_at then includes a date and time, which implies the fault is with
my fee config, but cannot see where.

I have attempted to match destination prefixes in the fees as follows
(presume a call to +441273123456 via peering with IP 2.2.2.2)

^44
^+44
^+44.
^+44.+
^+44.+$
^\+44.+\@.+$

None of these have the desired effect. What am I doing wrong/how can I
troubleshoot this process?

Thanks

George


From george.mason at xoomtalk.com  Wed Aug 27 18:10:27 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Wed, 27 Aug 2014 23:10:27 +0100
Subject: [Spce-user] Problems getting calls rated v2.8
In-Reply-To: <53FE4CFC.5000307@xoomtalk.com>
References: <53FE4CFC.5000307@xoomtalk.com>
Message-ID: <53FE5753.6070803@xoomtalk.com>



On 27/08/14 22:26, George Mason wrote:
> I have attempted to match destination prefixes in the fees as follows
> (presume a call to +441273123456 via peering with IP 2.2.2.2)
>
> ^44
> ^+44
> ^+44.
> ^+44.+
> ^+44.+$
> ^\+44.+\@.+$
>
> None of these have the desired effect. What am I doing wrong/how can I
> troubleshoot this process?

I should add that our carrier in this case requires international
numbers with the + prefix, hence these being in the billing fees. Calls
complete but are not rated.


From george.mason at xoomtalk.com  Wed Aug 27 18:50:03 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Wed, 27 Aug 2014 23:50:03 +0100
Subject: [Spce-user] Problems getting calls rated v2.8
In-Reply-To: <53FE5753.6070803@xoomtalk.com>
References: <53FE4CFC.5000307@xoomtalk.com> <53FE5753.6070803@xoomtalk.com>
Message-ID: <53FE609B.70301@xoomtalk.com>

 On 27/08/14 23:10, George Mason wrote:
> On 27/08/14 22:26, George Mason wrote:
>> > I have attempted to match destination prefixes in the fees as follows
>> > (presume a call to +441273123456 via peering with IP 2.2.2.2)
>> >
>> > ^44
>> > ^+44
>> > ^+44.
>> > ^+44.+
>> > ^+44.+$
>> > ^\+44.+\@.+$
>> >
>> > None of these have the desired effect. What am I doing wrong/how can I
>> > troubleshoot this process?
> I should add that our carrier in this case requires international
> numbers with the + prefix, hence these being in the billing fees. Calls
> complete but are not rated.

Further work on this reveals the following in rate-o-mat.log:

Aug 27 18:45:49 sip1 rate-o-mat[19269]: Error rating CDR batch: No
provider info for provider id 2 found

But cannot seem to find which "provider 2" is and why it has no info!


From barry at flanagan.ie  Thu Aug 28 04:48:28 2014
From: barry at flanagan.ie (Barry Flanagan)
Date: Thu, 28 Aug 2014 09:48:28 +0100
Subject: [Spce-user] voip loopback test
In-Reply-To: <8fe5440a16db354e530e18b3f58879e1@mail.gmail.com>
References: <20140827170018.42CEE150209E@zimbra.sipwise.com>
 <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>
 <8fe5440a16db354e530e18b3f58879e1@mail.gmail.com>
Message-ID: <CALJb548k2yjZOtLO6mXw5TG52woQ3ATgF0-wb63vz3xtPnsD3w@mail.gmail.com>

On 27 August 2014 22:24, Matthew Ogden <matthew at tenacit.net> wrote:

> Thanks Jeremy, that?s exactly what I mean!
>
>
>
> Echo test.
>

You could quite easily do this on the Asterisk server included with spce.
Just make a custom extensions.conf like so:

cd /etc/ngcp-config/templates/etc/asterisk/
cp extentions.conf.tt2 extensions.conf.customtt.tt2

Then edit extensions.conf.customtt.tt2 and add something like the following
at the bottom of the file:

### Echo Test Context ####
[echo-test]
exten => s,1,wait(2)
exten => s,n,Playback(demo-echotest)   ; Let them know what's going on
exten => s,n,Answer()
exten => s,n,Echo()                      ; Do the echo test
exten => s,n,Playback(demo-echodone)   ; Let them know it's over
exten => s,n,Hangup()
### End of Echo Test ###

Then, in the existing [sip-in] context, at the top, put in an extension for
the number you want to use for the echo test. For example, if you wanted to
use 500 as the number someone would dial to do the echo test, then you
would do:

[sip-in] <-- NOTE: this line exists already -  do not put it in, just look
for it in the file!
exten => 500,1,Goto(echo-test,s,1)

You then need to run 'ngcpcfg apply' so that Asterisk picks up the new
config.

Then what you need to do in order to get SPCE to actually send this number
- 500 - to the asterisk voicemail server, is to put a rule into your
subscribers rewrite rule set, under "Inbound Rewrite Rules for Callee":

Match Pattern: ^500$
Replace Pattern: 500 at voicebox.local
Description: Echo Test
Direction: Inbound
Field: Callee

So now, any call from the subscriber to 500 will get re-written to
500 at voicebox.local and sent to the Asterisk server where it should get the
echo test.

Hope this helps.

-Barry Flanagan



>
>
> *From:* Jeremy Ward [mailto:jward01 at gmail.com]
> *Sent:* 27 August 2014 09:20 PM
> *To:* Daniel Grotti
> *Cc:* spce-user at lists.sipwise.com; Matthew Ogden
> *Subject:* Re: [Spce-user] voip loopback test
>
>
>
> Not to stick my nose in something that it doesn't belong, but I think he
> is referring to what asterisk calls an "echo test".
>
> Its usually accessed via a star code (*31, if my memory serves me
> correctly).
>
> Hope this helps.
>
> Jeremy D. Ward, CWNE
> (954) 661-4965
>
> On Aug 27, 2014 1:01 PM, "Daniel Grotti" <dgrotti at sipwise.com> wrote:
>
> Hi,
> We don't have a specific number.
> It depends what you want to achieve, you can call the voicebox number for
> example or you can call another subscriber with a CF set to a mobile phone.
> Again it depends what you mean with loopback test.
>
> Daniel
>
> On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
> >
> > Hi
> >
> >
> >
> > Does spce have a number I can dial built-in that is a loopback test?
> >
> >
> >
> > Regards
> >
> >
> >
> >
> >
> > Matthew Ogden
> >
> > Management
> >
> > TenacIT
> >
> >
> >
> >
> >
> >
> >
> > Strategic IT Consulting ? Advanced Networking ? Virtualisation
> >
> > Custom Development ? Hosting ? Syspro Support  ? MS Licensing
> >
> > National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
> matthew at tenacit.net
> >
> > CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
> http://www.tenacit.net
> >
> >
> >
> >
> >
> >
> _______________________________________________
> 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/20140828/6575e9d8/attachment-0001.html>

From matthew at tenacit.net  Thu Aug 28 04:55:55 2014
From: matthew at tenacit.net (Matthew Ogden)
Date: Thu, 28 Aug 2014 10:55:55 +0200
Subject: [Spce-user] voip loopback test
In-Reply-To: <CALJb548k2yjZOtLO6mXw5TG52woQ3ATgF0-wb63vz3xtPnsD3w@mail.gmail.com>
References: <20140827170018.42CEE150209E@zimbra.sipwise.com>
 <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>
 <8fe5440a16db354e530e18b3f58879e1@mail.gmail.com>
 <CALJb548k2yjZOtLO6mXw5TG52woQ3ATgF0-wb63vz3xtPnsD3w@mail.gmail.com>
Message-ID: <bae72fc8a9a5bbc431a5cd64bc5eb5f1@mail.gmail.com>

Neat!



I?ll try this out a bit later



*From:* Barry Flanagan [mailto:barry at flanagan.ie]
*Sent:* 28 August 2014 10:48 AM
*To:* Matthew Ogden
*Cc:* Jeremy Ward; Daniel Grotti; spce-user at lists.sipwise.com
*Subject:* Re: [Spce-user] voip loopback test



On 27 August 2014 22:24, Matthew Ogden <matthew at tenacit.net> wrote:

Thanks Jeremy, that?s exactly what I mean!



Echo test.



You could quite easily do this on the Asterisk server included with spce.
Just make a custom extensions.conf like so:



cd /etc/ngcp-config/templates/etc/asterisk/

cp extentions.conf.tt2 extensions.conf.customtt.tt2



Then edit extensions.conf.customtt.tt2 and add something like the following
at the bottom of the file:



### Echo Test Context ####

[echo-test]

exten => s,1,wait(2)

exten => s,n,Playback(demo-echotest)   ; Let them know what's going on

exten => s,n,Answer()

exten => s,n,Echo()                      ; Do the echo test

exten => s,n,Playback(demo-echodone)   ; Let them know it's over

exten => s,n,Hangup()

### End of Echo Test ###



Then, in the existing [sip-in] context, at the top, put in an extension for
the number you want to use for the echo test. For example, if you wanted to
use 500 as the number someone would dial to do the echo test, then you
would do:



[sip-in] <-- NOTE: this line exists already -  do not put it in, just look
for it in the file!

exten => 500,1,Goto(echo-test,s,1)



You then need to run 'ngcpcfg apply' so that Asterisk picks up the new
config.



Then what you need to do in order to get SPCE to actually send this number
- 500 - to the asterisk voicemail server, is to put a rule into your
subscribers rewrite rule set, under "Inbound Rewrite Rules for Callee":



Match Pattern: ^500$

Replace Pattern: 500 at voicebox.local

Description: Echo Test

Direction: Inbound

Field: Callee



So now, any call from the subscriber to 500 will get re-written to
500 at voicebox.local and sent to the Asterisk server where it should get the
echo test.



Hope this helps.



-Barry Flanagan







*From:* Jeremy Ward [mailto:jward01 at gmail.com]
*Sent:* 27 August 2014 09:20 PM
*To:* Daniel Grotti
*Cc:* spce-user at lists.sipwise.com; Matthew Ogden
*Subject:* Re: [Spce-user] voip loopback test



Not to stick my nose in something that it doesn't belong, but I think he is
referring to what asterisk calls an "echo test".

Its usually accessed via a star code (*31, if my memory serves me
correctly).

Hope this helps.

Jeremy D. Ward, CWNE
(954) 661-4965

On Aug 27, 2014 1:01 PM, "Daniel Grotti" <dgrotti at sipwise.com> wrote:

Hi,
We don't have a specific number.
It depends what you want to achieve, you can call the voicebox number for
example or you can call another subscriber with a CF set to a mobile phone.
Again it depends what you mean with loopback test.

Daniel

On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
>
> Hi
>
>
>
> Does spce have a number I can dial built-in that is a loopback test?
>
>
>
> Regards
>
>
>
>
>
> Matthew Ogden
>
> Management
>
> TenacIT
>
>
>
>
>
>
>
> Strategic IT Consulting ? Advanced Networking ? Virtualisation
>
> Custom Development ? Hosting ? Syspro Support  ? MS Licensing
>
> National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
matthew at tenacit.net
>
> CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
http://www.tenacit.net
>
>
>
>
>
>
_______________________________________________
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/20140828/605c15a9/attachment-0001.html>

From tabi.tabe at gmail.com  Thu Aug 28 08:11:50 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Thu, 28 Aug 2014 14:11:50 +0200
Subject: [Spce-user] SPCE 3.4.1 not showing call history in Web portal
Message-ID: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>

Hi,

I installed SPCE 3.4.1 and got is working fine. However it does not show
call history under call distribution or subscriber menu. Any idea what
could be the cause?

-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140828/1060baec/attachment-0001.html>

From jward01 at gmail.com  Thu Aug 28 09:36:06 2014
From: jward01 at gmail.com (Jeremy Ward)
Date: Thu, 28 Aug 2014 09:36:06 -0400
Subject: [Spce-user] voip loopback test
In-Reply-To: <CALJb548k2yjZOtLO6mXw5TG52woQ3ATgF0-wb63vz3xtPnsD3w@mail.gmail.com>
References: <20140827170018.42CEE150209E@zimbra.sipwise.com>
 <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>
 <8fe5440a16db354e530e18b3f58879e1@mail.gmail.com>
 <CALJb548k2yjZOtLO6mXw5TG52woQ3ATgF0-wb63vz3xtPnsD3w@mail.gmail.com>
Message-ID: <CAFfjrWqriH0WQNgeoN24696wAQ229xm0Wp4khHtrjteWR9L9fg@mail.gmail.com>

Barry,

Would the same logic then apply to setup an ANAC code?

Some of my carrier clients have voice gateways that terminate to multiple
lines at 66-block like in a multitenant commercial building (MDU).

Many voice techs in the US are used to being able to check the telephone
number assigned to a pair by "ANACing" the line - dialing 2006666666.

This causes the switch to announce the associated telephone number with
that pair of wires.

I realize that the asterisk script would be different, but could it be
accomplished in the same manner? I would imagine asterisk would see the CLI
of the callee as its needed for voicemail access, correct?

Thanks,

Jeremy D. Ward, CWNE
(954) 661-4965
On Aug 28, 2014 4:48 AM, "Barry Flanagan" <barry at flanagan.ie> wrote:

> On 27 August 2014 22:24, Matthew Ogden <matthew at tenacit.net> wrote:
>
>> Thanks Jeremy, that?s exactly what I mean!
>>
>>
>>
>> Echo test.
>>
>
> You could quite easily do this on the Asterisk server included with spce.
> Just make a custom extensions.conf like so:
>
> cd /etc/ngcp-config/templates/etc/asterisk/
> cp extentions.conf.tt2 extensions.conf.customtt.tt2
>
> Then edit extensions.conf.customtt.tt2 and add something like the
> following at the bottom of the file:
>
> ### Echo Test Context ####
> [echo-test]
> exten => s,1,wait(2)
> exten => s,n,Playback(demo-echotest)   ; Let them know what's going on
> exten => s,n,Answer()
> exten => s,n,Echo()                      ; Do the echo test
> exten => s,n,Playback(demo-echodone)   ; Let them know it's over
> exten => s,n,Hangup()
> ### End of Echo Test ###
>
> Then, in the existing [sip-in] context, at the top, put in an extension
> for the number you want to use for the echo test. For example, if you
> wanted to use 500 as the number someone would dial to do the echo test,
> then you would do:
>
> [sip-in] <-- NOTE: this line exists already -  do not put it in, just look
> for it in the file!
> exten => 500,1,Goto(echo-test,s,1)
>
> You then need to run 'ngcpcfg apply' so that Asterisk picks up the new
> config.
>
> Then what you need to do in order to get SPCE to actually send this number
> - 500 - to the asterisk voicemail server, is to put a rule into your
> subscribers rewrite rule set, under "Inbound Rewrite Rules for Callee":
>
> Match Pattern: ^500$
> Replace Pattern: 500 at voicebox.local
> Description: Echo Test
> Direction: Inbound
> Field: Callee
>
> So now, any call from the subscriber to 500 will get re-written to
> 500 at voicebox.local and sent to the Asterisk server where it should get
> the echo test.
>
> Hope this helps.
>
> -Barry Flanagan
>
>
>
>>
>>
>> *From:* Jeremy Ward [mailto:jward01 at gmail.com]
>> *Sent:* 27 August 2014 09:20 PM
>> *To:* Daniel Grotti
>> *Cc:* spce-user at lists.sipwise.com; Matthew Ogden
>> *Subject:* Re: [Spce-user] voip loopback test
>>
>>
>>
>> Not to stick my nose in something that it doesn't belong, but I think he
>> is referring to what asterisk calls an "echo test".
>>
>> Its usually accessed via a star code (*31, if my memory serves me
>> correctly).
>>
>> Hope this helps.
>>
>> Jeremy D. Ward, CWNE
>> (954) 661-4965
>>
>> On Aug 27, 2014 1:01 PM, "Daniel Grotti" <dgrotti at sipwise.com> wrote:
>>
>> Hi,
>> We don't have a specific number.
>> It depends what you want to achieve, you can call the voicebox number for
>> example or you can call another subscriber with a CF set to a mobile phone.
>> Again it depends what you mean with loopback test.
>>
>> Daniel
>>
>> On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
>> >
>> > Hi
>> >
>> >
>> >
>> > Does spce have a number I can dial built-in that is a loopback test?
>> >
>> >
>> >
>> > Regards
>> >
>> >
>> >
>> >
>> >
>> > Matthew Ogden
>> >
>> > Management
>> >
>> > TenacIT
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > Strategic IT Consulting ? Advanced Networking ? Virtualisation
>> >
>> > Custom Development ? Hosting ? Syspro Support  ? MS Licensing
>> >
>> > National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
>> matthew at tenacit.net
>> >
>> > CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
>> http://www.tenacit.net
>> >
>> >
>> >
>> >
>> >
>> >
>> _______________________________________________
>> 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/20140828/1001d20e/attachment-0001.html>

From barry at flanagan.ie  Thu Aug 28 09:44:46 2014
From: barry at flanagan.ie (Barry Flanagan)
Date: Thu, 28 Aug 2014 14:44:46 +0100
Subject: [Spce-user] voip loopback test
In-Reply-To: <CAFfjrWqriH0WQNgeoN24696wAQ229xm0Wp4khHtrjteWR9L9fg@mail.gmail.com>
References: <20140827170018.42CEE150209E@zimbra.sipwise.com>
 <CAFfjrWrxW9WmBvJP1mDZFin=mmB+O+cg=ou1jf2+awJEt-6Kbg@mail.gmail.com>
 <8fe5440a16db354e530e18b3f58879e1@mail.gmail.com>
 <CALJb548k2yjZOtLO6mXw5TG52woQ3ATgF0-wb63vz3xtPnsD3w@mail.gmail.com>
 <CAFfjrWqriH0WQNgeoN24696wAQ229xm0Wp4khHtrjteWR9L9fg@mail.gmail.com>
Message-ID: <CALJb549hoBcwF-B1x5WVE9BpVQiePCXPM0DVZpcVS=OOaF8odA@mail.gmail.com>

On 28 August 2014 14:36, Jeremy Ward <jward01 at gmail.com> wrote:

> Barry,
>
> Would the same logic then apply to setup an ANAC code?
>
> Some of my carrier clients have voice gateways that terminate to multiple
> lines at 66-block like in a multitenant commercial building (MDU).
>
> Many voice techs in the US are used to being able to check the telephone
> number assigned to a pair by "ANACing" the line - dialing 2006666666.
>
> This causes the switch to announce the associated telephone number with
> that pair of wires.
>
> I realize that the asterisk script would be different, but could it be
> accomplished in the same manner? I would imagine asterisk would see the CLI
> of the callee as its needed for voicemail access, correct?
>
>
Yes, it should work the same for that. Same technique, just write an
Asterisk dialplan to speak back the numbers from the CALLERID(number).

If you were building lots of Asterisk applications I would suggest running
them on a separate * box than your voicemail but for just echo test and
ANAC I wouldn't worry too much.

Regards,

-Barry



> Thanks,
>
> Jeremy D. Ward, CWNE
> (954) 661-4965
> On Aug 28, 2014 4:48 AM, "Barry Flanagan" <barry at flanagan.ie> wrote:
>
>> On 27 August 2014 22:24, Matthew Ogden <matthew at tenacit.net> wrote:
>>
>>> Thanks Jeremy, that?s exactly what I mean!
>>>
>>>
>>>
>>> Echo test.
>>>
>>
>> You could quite easily do this on the Asterisk server included with spce.
>> Just make a custom extensions.conf like so:
>>
>> cd /etc/ngcp-config/templates/etc/asterisk/
>> cp extentions.conf.tt2 extensions.conf.customtt.tt2
>>
>> Then edit extensions.conf.customtt.tt2 and add something like the
>> following at the bottom of the file:
>>
>> ### Echo Test Context ####
>> [echo-test]
>> exten => s,1,wait(2)
>> exten => s,n,Playback(demo-echotest)   ; Let them know what's going on
>> exten => s,n,Answer()
>> exten => s,n,Echo()                      ; Do the echo test
>> exten => s,n,Playback(demo-echodone)   ; Let them know it's over
>> exten => s,n,Hangup()
>> ### End of Echo Test ###
>>
>> Then, in the existing [sip-in] context, at the top, put in an extension
>> for the number you want to use for the echo test. For example, if you
>> wanted to use 500 as the number someone would dial to do the echo test,
>> then you would do:
>>
>> [sip-in] <-- NOTE: this line exists already -  do not put it in, just
>> look for it in the file!
>> exten => 500,1,Goto(echo-test,s,1)
>>
>> You then need to run 'ngcpcfg apply' so that Asterisk picks up the new
>> config.
>>
>> Then what you need to do in order to get SPCE to actually send this
>> number - 500 - to the asterisk voicemail server, is to put a rule into your
>> subscribers rewrite rule set, under "Inbound Rewrite Rules for Callee":
>>
>> Match Pattern: ^500$
>> Replace Pattern: 500 at voicebox.local
>> Description: Echo Test
>> Direction: Inbound
>> Field: Callee
>>
>> So now, any call from the subscriber to 500 will get re-written to
>> 500 at voicebox.local and sent to the Asterisk server where it should get
>> the echo test.
>>
>> Hope this helps.
>>
>> -Barry Flanagan
>>
>>
>>
>>>
>>>
>>> *From:* Jeremy Ward [mailto:jward01 at gmail.com]
>>> *Sent:* 27 August 2014 09:20 PM
>>> *To:* Daniel Grotti
>>> *Cc:* spce-user at lists.sipwise.com; Matthew Ogden
>>> *Subject:* Re: [Spce-user] voip loopback test
>>>
>>>
>>>
>>> Not to stick my nose in something that it doesn't belong, but I think he
>>> is referring to what asterisk calls an "echo test".
>>>
>>> Its usually accessed via a star code (*31, if my memory serves me
>>> correctly).
>>>
>>> Hope this helps.
>>>
>>> Jeremy D. Ward, CWNE
>>> (954) 661-4965
>>>
>>> On Aug 27, 2014 1:01 PM, "Daniel Grotti" <dgrotti at sipwise.com> wrote:
>>>
>>> Hi,
>>> We don't have a specific number.
>>> It depends what you want to achieve, you can call the voicebox number
>>> for example or you can call another subscriber with a CF set to a mobile
>>> phone.
>>> Again it depends what you mean with loopback test.
>>>
>>> Daniel
>>>
>>> On 27 Aug 2014 16:43, Matthew Ogden <matthew at tenacit.net> wrote:
>>> >
>>> > Hi
>>> >
>>> >
>>> >
>>> > Does spce have a number I can dial built-in that is a loopback test?
>>> >
>>> >
>>> >
>>> > Regards
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Matthew Ogden
>>> >
>>> > Management
>>> >
>>> > TenacIT
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Strategic IT Consulting ? Advanced Networking ? Virtualisation
>>> >
>>> > Custom Development ? Hosting ? Syspro Support  ? MS Licensing
>>> >
>>> > National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
>>> matthew at tenacit.net
>>> >
>>> > CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
>>> http://www.tenacit.net
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> _______________________________________________
>>> 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/20140828/22e860ae/attachment-0001.html>

From mat at solutionskubix.com  Wed Aug 27 15:55:33 2014
From: mat at solutionskubix.com (Marc-Antoine Talbot)
Date: Wed, 27 Aug 2014 19:55:33 +0000
Subject: [Spce-user] SipProvider as switch
Message-ID: <75FB62B18A57A9478C294EF5484725EF01E570E8@SERVER.kubix.local>

Hi,
I would like to use SipProvider CE to connect all my PBXs so that I can have only one trunk at my provider, and share the channels between the PBXs.

I created my provider peering, and I created a subscriber for each one of my PBX.

The problem is that I need to put my phone number in the subscriber username, otherwise the calls can't be route (404) to my PBX.

Second problem, when I call, the Caller ID is my provider username, and I haven't found any way to bypass it, other than making it hidden.


Is there something I did wrong ?

Thank you !



Marc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140827/97c99efa/attachment-0001.html>

From sebas_elprimo at hotmail.com  Thu Aug 28 10:52:32 2014
From: sebas_elprimo at hotmail.com (sebastian rojo)
Date: Thu, 28 Aug 2014 09:52:32 -0500
Subject: [Spce-user]  [kamailio] Usrloc: cache vs database inconsistencies
Message-ID: <CAH7ArYyyWxHHXW8C2cm=EEOa-GFy3dVPON8Vbi9_NVxyPdA=aQ@mail.gmail.com>

I have noticed a consistent difference between the location records in DB.
and those stored in kamailio chache.


root at sbc:~# ngcp-kamctl proxy ul show |grep Contact

         Contact::
sip:2422 at X.16.10.221:54733;rinstance=48d7e73f599c5826;transport=TCP Q=

         Contact:: sip:2422 at x.1.1.180:36404;rinstance=691517d9fa77703f Q=

         Contact:: sip:4202 at x.1.2.79:43802;rinstance=cd4779b1598d1beb Q=

         Contact:: sip:4202 at x.48.236.198:40862;rinstance=487d6d482fd2cb5f Q=

         Contact:: sip:2420 at x.1.0.175:5060;transport=udp Q=

         Contact::
sip:2420 at x.x.11.213:34945;rinstance=aba2923ddadb6b56;transport=TCP Q=

         Contact:: sip:2420 at x.1.1.12:18584;rinstance=7c30d5a446902dd0 Q=

         Contact:: sip:2421 at x.1.0.232:60492;rinstance=62e978f706b850cd Q=

         Contact:: sip:2417 at x.1.0.180:4750;rinstance=1969d005d5cfd371 Q=

         Contact:: sip:2410 at x.1.0.236:17688;rinstance=bacd6921e1c49d12 Q=

         Contact::
sip:2410 at x.16.10.208:55658;rinstance=0768359aed20d852;transport=UDP Q=

         Contact::
sip:3501 at x.157.133.229:33857;rinstance=36c7a54559d5147a;transport=TCP
Q=

         Contact:: sip:3501 at x.1.0.119:9470;rinstance=7bdf7c5e0c70a752 Q=

         Contact:: sip:s at x.1.0.4:5060 Q=

14 records

On DB see this records.

SELECT username, contact, expires - NOW() FROM kamailio.location;

   username contact expires - NOW()  *3501*
*sip:3501 at X.16.10.243:34959;rinstance=7933832f47243e95;transport=UDP*
*-1918864*  *4202*
*sip:4202 at X.14.26.12:35400;rinstance=9dbc8f7e36af6250;transport=TCP*
*-959457*  *2422*
*sip:2422 at X.16.10.221:47987;rinstance=275352713d6a6325;transport=TCP*
*-958275*  dialcast sip:s at X.1.0.4:5060 29  2410 sip:2410 at X.16.10.208
:55658;rinstance=0768359aed20d852;transport=UDP 95  3501
sip:3501 at X.157.133.229:33857;rinstance=36c7a54559d5147a;transport=TCP 213
4202 Sip:4202 at X.1.2.79:43802;rinstance=cd4779b1598d1beb 240  2420
sip:2420 at X.16.11.213:34945;rinstance=aba2923ddadb6b56;transport=TCP 527
2422 sip:2422 at X.16.10.221:54733;rinstance=48d7e73f599c5826;transport=TCP 715
2417 sip:2417 at X.1.0.180:4750;rinstance=1969d005d5cfd371 1799  2420
sip:2420 at X.1.1.12:18584;rinstance=7c30d5a446902dd0 2298  3501
sip:3501 at X.1.0.119:9470;rinstance=7bdf7c5e0c70a752 7920  2421
sip:2421 at X.1.0.232:60492;rinstance=62e978f706b850cd 8019  2422
sip:2422 at X.1.1.180:36404;rinstance=691517d9fa77703f 8293  4202
sip:4202 at X.48.236.198:40862;rinstance=487d6d482fd2cb5f 8514  2410
sip:2410 at X.1.0.236:17688;rinstance=bacd6921e1c49d12 8925  2420
sip:2420 at X.1.0.175:5060;transport=udp 9927

see this records. already expired records that are not in the cache. but
still the DB

SELECT username, contact, expires FROM kamailio.location WHERE expires <= NOW();

   username contact expires  3501 sip:3501 at 172.16.10.243:34959
;rinstance=7933832f47243e95;transport=UDP 2014-08-26 17:36:44  4202
sip:4202 at 179.14.26.12:35400;rinstance=9dbc8f7e36af6250;transport=TCP 2014-08-27
13:30:51  2422 sip:2422 at 172.16.10.221:47987
;rinstance=275352713d6a6325;transport=TCP 2014-08-27 13:42:33
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140828/9630b360/attachment-0001.html>

From dgrotti at sipwise.com  Thu Aug 28 12:13:46 2014
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Thu, 28 Aug 2014 18:13:46 +0200
Subject: [Spce-user] SipProvider as switch
In-Reply-To: <75FB62B18A57A9478C294EF5484725EF01E570E8@SERVER.kubix.local>
References: <75FB62B18A57A9478C294EF5484725EF01E570E8@SERVER.kubix.local>
Message-ID: <53FF553A.1010305@sipwise.com>

Hi,


On 08/27/2014 09:55 PM, Marc-Antoine Talbot wrote:
>
> Hi,
>
> I would like to use SipProvider CE to connect all my PBXs so that I
> can have only one trunk at my provider, and share the channels between
> the PBXs.
>
>
> I created my provider peering, and I created a subscriber for each one
> of my PBX.
>
>  
>
> The problem is that I need to put my phone number in the subscriber
> username, otherwise the calls can?t be route (404) to my PBX.
>


What you would like to achieve here ?
you need to register you PBXs as a subscriber. Subscriber has a E164
number associated, in order to be called.



>  
>
> Second problem, when I call, the Caller ID is my provider username,
> and I haven?t found any way to bypass it, other than making it hidden.
>


In order to keep the PBX caller ID, you should add the "allowed_clis"
list in your subscriber's preferences.
You can put there an "*" in order to match every number

>  
>
>  
>
> Is there something I did wrong ?
>
>  
>
> Thank you !
>
>  
>
>  
>
>  
>
> *Marc*
>


*Regards,
Daniel


*
>
>  
>
>
>
> _______________________________________________
> 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/20140828/f836c563/attachment-0001.html>

From jbonilla at sipwise.com  Thu Aug 28 14:35:25 2014
From: jbonilla at sipwise.com (Jon Bonilla (Manwe))
Date: Thu, 28 Aug 2014 20:35:25 +0200
Subject: [Spce-user] SipProvider as switch
In-Reply-To: <75FB62B18A57A9478C294EF5484725EF01E570E8@SERVER.kubix.local>
References: <75FB62B18A57A9478C294EF5484725EF01E570E8@SERVER.kubix.local>
Message-ID: <20140828203525.7ab7d14c@quenya>

El Wed, 27 Aug 2014 19:55:33 +0000
Marc-Antoine Talbot <mat at solutionskubix.com> escribi?:

> Hi,
> I would like to use SipProvider CE to connect all my PBXs so that I can have
> only one trunk at my provider, and share the channels between the PBXs.
> 
> I created my provider peering, and I created a subscriber for each one of my
> PBX.
> 
> The problem is that I need to put my phone number in the subscriber username,
> otherwise the calls can't be route (404) to my PBX.

Yes thye can. If you enable "e164_to_ruri" option in the subscriber preference
the number will be sent to the pbx instead of the sip username.


> 
> Second problem, when I call, the Caller ID is my provider username, and I
> haven't found any way to bypass it, other than making it hidden.
> 

It depends on your provider. If it validates the callerid you send in the From
header it can rewrite it with the one it provided to you.

Maybe you need to send the callerid in another header or in another format.
That will depend on your peer and you should discuss it with your support.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140828/4eb0b7b7/attachment-0001.asc>

From vseva at sipwise.com  Fri Aug 29 05:18:15 2014
From: vseva at sipwise.com (Victor Seva)
Date: Fri, 29 Aug 2014 11:18:15 +0200
Subject: [Spce-user] [kamailio] Usrloc: cache vs database inconsistencies
In-Reply-To: <CAH7ArYyyWxHHXW8C2cm=EEOa-GFy3dVPON8Vbi9_NVxyPdA=aQ@mail.gmail.com>
References: <CAH7ArYyyWxHHXW8C2cm=EEOa-GFy3dVPON8Vbi9_NVxyPdA=aQ@mail.gmail.com>
Message-ID: <54004557.6070707@sipwise.com>

On 08/28/2014 04:52 PM, sebastian rojo wrote:
> I have noticed a consistent difference between the location records in
> DB. and those stored in kamailio chache.

Knowing the version you are running could be helpful.
Please post the output of "dpkg -l ngcp-kamailio || dpkg -l kamailio"

Cheers,
Victor

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140829/2b81d9e9/attachment-0001.asc>

From cervajs at fpf.slu.cz  Fri Aug 29 07:15:44 2014
From: cervajs at fpf.slu.cz (Marek Cervenka)
Date: Fri, 29 Aug 2014 13:15:44 +0200
Subject: [Spce-user] spce ip aliases
Message-ID: <540060E0.9000409@fpf.slu.cz>

hi,

is it possible use spce with multiple aliased ips?

like
eth0 192.168.100.1
eth0:1 192.168.100.20
eth0:2 192.168.100.30

and register endpoints to i.e. 192.168.100.30 and answer from spce will 
have src ip 192.168.100.30
thanks

-- 
---------------------------------------
Marek Cervenka
=======================================




From agranig at sipwise.com  Fri Aug 29 07:27:58 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Fri, 29 Aug 2014 13:27:58 +0200
Subject: [Spce-user] spce ip aliases
In-Reply-To: <540060E0.9000409@fpf.slu.cz>
References: <540060E0.9000409@fpf.slu.cz>
Message-ID: <540063BE.3040003@sipwise.com>

Hi,

You might want to check
https://www.sipwise.com/doc/mr3.4.1/spce/ar01s05.html#_extra_sip_listening_ports
for that. You can't just add other ports, but should be able to add
different IPs too.

Andreas

On 08/29/2014 01:15 PM, Marek Cervenka wrote:
> hi,
> 
> is it possible use spce with multiple aliased ips?
> 
> like
> eth0 192.168.100.1
> eth0:1 192.168.100.20
> eth0:2 192.168.100.30
> 
> and register endpoints to i.e. 192.168.100.30 and answer from spce will
> have src ip 192.168.100.30
> thanks
> 


From alutay at sipwise.com  Fri Aug 29 09:03:32 2014
From: alutay at sipwise.com (Alex Lutay)
Date: Fri, 29 Aug 2014 15:03:32 +0200
Subject: [Spce-user] SPCE 3.4.1 not showing call history in Web portal
In-Reply-To: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>
References: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>
Message-ID: <54007A24.2000308@sipwise.com>

Dear Tabi!

On 28/08/14 14:11, Tabi Tabe Tabi wrote:
> I installed SPCE 3.4.1 and got is working fine. However it does not show
> call history under call distribution or subscriber menu. Any idea what
> could be the cause?

Can you try this fix:
> https://github.com/sipwise/ngcp-panel/commit/cf93f0bf63dca1b66775feb5c7622af0c4d4cae6
if it helps you we will include it in next build mr3.4.2.
Thank you!

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From arpagon+sipwise at gmail.com  Fri Aug 29 10:43:25 2014
From: arpagon+sipwise at gmail.com (sebastian rojo)
Date: Fri, 29 Aug 2014 09:43:25 -0500
Subject: [Spce-user] [kamailio] Usrloc: cache vs database inconsistencies
In-Reply-To: <54004557.6070707@sipwise.com>
References: <CAH7ArYyyWxHHXW8C2cm=EEOa-GFy3dVPON8Vbi9_NVxyPdA=aQ@mail.gmail.com>
 <54004557.6070707@sipwise.com>
Message-ID: <CAH7ArYyLm1W4g1tCCWHPzUX-YgNxg_CGO=8A=X83zmfNxcpAsw@mail.gmail.com>

Hi,

root at sbc:~# cat /etc/sipwise_ngcp_version
System installed. NGCP version mr3.3.2 on 2014-07-23 11:12:57

root at sbc:~# dpkg -l ngcp-kamailio || dpkg -l kamailio
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                Version        Architecture   Description
+++-===================-==============-==============-===========================================
ii  ngcp-kamailio       4.1.3-1+0~mr3. amd64          very fast and
configurable SIP proxy



On Fri, Aug 29, 2014 at 4:18 AM, Victor Seva <vseva at sipwise.com> wrote:

> On 08/28/2014 04:52 PM, sebastian rojo wrote:
> > I have noticed a consistent difference between the location records in
> > DB. and those stored in kamailio chache.
>
> Knowing the version you are running could be helpful.
> Please post the output of "dpkg -l ngcp-kamailio || dpkg -l kamailio"
>
> Cheers,
> Victor
>
>
> _______________________________________________
> 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/20140829/d426c8d9/attachment-0001.html>

From tabi.tabe at gmail.com  Fri Aug 29 12:15:00 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Fri, 29 Aug 2014 18:15:00 +0200
Subject: [Spce-user] SPCE 3.4.1 not showing call history in Web portal
In-Reply-To: <54007A24.2000308@sipwise.com>
References: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>
 <54007A24.2000308@sipwise.com>
Message-ID: <CAOibrm52FOQ6CNaR0aLbm6TS0=VVemKtnA1hoby+ME66YtR2wA@mail.gmail.com>

Will do. After updating the .tt file, do I need to run any command to
update the system?

Regards,

Tabi


On Fri, Aug 29, 2014 at 3:03 PM, Alex Lutay <alutay at sipwise.com> wrote:

> Dear Tabi!
>
>
> On 28/08/14 14:11, Tabi Tabe Tabi wrote:
>
>> I installed SPCE 3.4.1 and got is working fine. However it does not show
>> call history under call distribution or subscriber menu. Any idea what
>> could be the cause?
>>
>
> Can you try this fix:
>
>> https://github.com/sipwise/ngcp-panel/commit/
>> cf93f0bf63dca1b66775feb5c7622af0c4d4cae6
>>
> if it helps you we will include it in next build mr3.4.2.
> Thank you!
>
> --
> Alexander Lutay
> Head of Quality Assurance
> Sipwise GmbH, Campus 21/Europaring F15
> AT-2345 Brunn am Gebirge
>
> Office: +43(0)13012036
> Email: alutay at sipwise.com
> Website: http://www.sipwise.com
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>



-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140829/b9c92c96/attachment-0001.html>

From george.mason at xoomtalk.com  Fri Aug 29 12:18:57 2014
From: george.mason at xoomtalk.com (George Mason)
Date: Fri, 29 Aug 2014 17:18:57 +0100
Subject: [Spce-user] LCR in SPCE?
Message-ID: <5400A7F1.6060208@xoomtalk.com>

Hi,

I have been looking around SPCE and like what I see. One element that I
cannot see anywhere, which is useful on other systems, is LCR. Namely
the ability to route a call to a given carrier based on the price for
that call.

As far as I can see, rate-o-mat rates the calls after they have
completed, so there is no account taken of what the cheapest route might
have been. This is a shame as it requires more complex routes to get
traffic over the best-costing carrier.

On that subject - is there a way to bulk import callee patterns against
a SIP peering? I am trying to configure a channel to only route the best
priced destinations and this involves lots (over 60K) of patterns. Will
this kill the routing engine? How can I import these, presume they need
to go straight into the DB?

Thanks

George


From tabi.tabe at gmail.com  Fri Aug 29 12:39:31 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Fri, 29 Aug 2014 18:39:31 +0200
Subject: [Spce-user] SPCE 3.4.1 not showing call history in Web portal
In-Reply-To: <CAOibrm52FOQ6CNaR0aLbm6TS0=VVemKtnA1hoby+ME66YtR2wA@mail.gmail.com>
References: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>
 <54007A24.2000308@sipwise.com>
 <CAOibrm52FOQ6CNaR0aLbm6TS0=VVemKtnA1hoby+ME66YtR2wA@mail.gmail.com>
Message-ID: <CAOibrm4w8u7WJF3eogS0Dk8jkp38yEJcbv8Jak-2630h9d4D2Q@mail.gmail.com>

Hi Alex,

An interesting observation. I checked Kamailio.log and found this errors:

Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database
Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database
Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database
Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database
Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database
Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database
Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Lost connection to MySQL
server during query
Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: acc [acc.c:509]:
acc_db_request(): failed to insert into database



Also checked the CDR table in MySQL and found zero record. Can't connect
MySQL. MySQL is running. What parameters should I check? All serv

Regards,

Tabi


On Fri, Aug 29, 2014 at 6:15 PM, Tabi Tabe Tabi <tabi.tabe at gmail.com> wrote:

> Will do. After updating the .tt file, do I need to run any command to
> update the system?
>
> Regards,
>
> Tabi
>
>
> On Fri, Aug 29, 2014 at 3:03 PM, Alex Lutay <alutay at sipwise.com> wrote:
>
>> Dear Tabi!
>>
>>
>> On 28/08/14 14:11, Tabi Tabe Tabi wrote:
>>
>>> I installed SPCE 3.4.1 and got is working fine. However it does not show
>>> call history under call distribution or subscriber menu. Any idea what
>>> could be the cause?
>>>
>>
>> Can you try this fix:
>>
>>> https://github.com/sipwise/ngcp-panel/commit/
>>> cf93f0bf63dca1b66775feb5c7622af0c4d4cae6
>>>
>> if it helps you we will include it in next build mr3.4.2.
>> Thank you!
>>
>> --
>> Alexander Lutay
>> Head of Quality Assurance
>> Sipwise GmbH, Campus 21/Europaring F15
>> AT-2345 Brunn am Gebirge
>>
>> Office: +43(0)13012036
>> Email: alutay at sipwise.com
>> Website: http://www.sipwise.com
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>>
>
>
>
> --
> ...Tabi
>
>


-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140829/00928f4b/attachment-0001.html>

From tabi.tabe at gmail.com  Fri Aug 29 13:04:17 2014
From: tabi.tabe at gmail.com (Tabi Tabe Tabi)
Date: Fri, 29 Aug 2014 19:04:17 +0200
Subject: [Spce-user] SPCE 3.4.1 not showing call history in Web portal
In-Reply-To: <CAOibrm4w8u7WJF3eogS0Dk8jkp38yEJcbv8Jak-2630h9d4D2Q@mail.gmail.com>
References: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>
 <54007A24.2000308@sipwise.com>
 <CAOibrm52FOQ6CNaR0aLbm6TS0=VVemKtnA1hoby+ME66YtR2wA@mail.gmail.com>
 <CAOibrm4w8u7WJF3eogS0Dk8jkp38yEJcbv8Jak-2630h9d4D2Q@mail.gmail.com>
Message-ID: <CAOibrm4SqsbnjoUVRp8sXWiWM8uciBTHrDWCURbUmWKNo3_SDw@mail.gmail.com>

Please ignore the email on the .tt template. Was not awake :-)

Problem still with database connection though. Any ideas?

Regards,

Tabi


On Fri, Aug 29, 2014 at 6:39 PM, Tabi Tabe Tabi <tabi.tabe at gmail.com> wrote:

> Hi Alex,
>
> An interesting observation. I checked Kamailio.log and found this errors:
>
> Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
> Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
> Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
> Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
> Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
> Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
> Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: db_mysql [km_dbase.c:122]:
> db_mysql_submit_query(): driver error on query: Lost connection to MySQL
> server during query
> Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: <core> [db_query.c:235]:
> db_do_insert_cmd(): error while submitting query
> Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: acc [acc.c:509]:
> acc_db_request(): failed to insert into database
>
>
>
> Also checked the CDR table in MySQL and found zero record. Can't connect
> MySQL. MySQL is running. What parameters should I check? All serv
>
> Regards,
>
> Tabi
>
>
> On Fri, Aug 29, 2014 at 6:15 PM, Tabi Tabe Tabi <tabi.tabe at gmail.com>
> wrote:
>
>> Will do. After updating the .tt file, do I need to run any command to
>> update the system?
>>
>> Regards,
>>
>> Tabi
>>
>>
>> On Fri, Aug 29, 2014 at 3:03 PM, Alex Lutay <alutay at sipwise.com> wrote:
>>
>>> Dear Tabi!
>>>
>>>
>>> On 28/08/14 14:11, Tabi Tabe Tabi wrote:
>>>
>>>> I installed SPCE 3.4.1 and got is working fine. However it does not show
>>>> call history under call distribution or subscriber menu. Any idea what
>>>> could be the cause?
>>>>
>>>
>>> Can you try this fix:
>>>
>>>> https://github.com/sipwise/ngcp-panel/commit/
>>>> cf93f0bf63dca1b66775feb5c7622af0c4d4cae6
>>>>
>>> if it helps you we will include it in next build mr3.4.2.
>>> Thank you!
>>>
>>> --
>>> Alexander Lutay
>>> Head of Quality Assurance
>>> Sipwise GmbH, Campus 21/Europaring F15
>>> AT-2345 Brunn am Gebirge
>>>
>>> Office: +43(0)13012036
>>> Email: alutay at sipwise.com
>>> Website: http://www.sipwise.com
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>
>>
>>
>> --
>> ...Tabi
>>
>>
>
>
> --
> ...Tabi
>
>


-- 
...Tabi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140829/6ff27278/attachment-0001.html>

From kmasse at questblue.com  Fri Aug 29 15:52:50 2014
From: kmasse at questblue.com (Kevin Masse)
Date: Fri, 29 Aug 2014 15:52:50 -0400
Subject: [Spce-user] Subscriber Alias Entries in Database
References: <CEEE718799582B47A55D7897DCB264FC3F5E18@bvusaex.bestvoipusa.local><53C652BD.7000707@sipwise.com>
 <CEEE718799582B47A55D7897DCB264FC3F5E65@bvusaex.bestvoipusa.local>
 <CEEE718799582B47A55D7897DCB264FC3F5F7F@bvusaex.bestvoipusa.local>
 <CEEE718799582B47A55D7897DCB264FC3F61AD@bvusaex.bestvoipusa.local>
Message-ID: <CEEE718799582B47A55D7897DCB264FC3F62FD@bvusaex.bestvoipusa.local>

Greetings group:

I was hoping that someone might have had some thought on the two
questions below or perhaps it got buried.

\\ locate the 
************* 2 questions below ****************
\\ below

Thanks
Kevin



-----Original Message-----
From: Kevin Masse 
Sent: Thursday, August 14, 2014 7:33 AM
To: Kevin Masse; 'Andreas Granig'; 'spce-user at lists.sipwise.com'
Subject: RE: [Spce-user] Subscriber Alias Entries in Database

Hello Andraes, have you had a chance to review the two questions stated
below?

Our dev team is seeking to close out this issue we are having.

Thank you
Kevin




-----Original Message-----
From: Kevin Masse
Sent: Wednesday, August 06, 2014 7:55 AM
To: Kevin Masse; 'Andreas Granig'; 'spce-user at lists.sipwise.com'
Subject: RE: [Spce-user] Subscriber Alias Entries in Database

Hello, I was wondering if there was a response to this that I missed.
There are two specific questions we are trying to answer.


Thank you
Kevin



-----Original Message-----
From: Kevin Masse
Sent: Thursday, July 24, 2014 10:02 AM
To: Kevin Masse; Andreas Granig; spce-user at lists.sipwise.com
Subject: RE: [Spce-user] Subscriber Alias Entries in Database

Andraes one additional scenario has come up based on our last thread:
I wanted to post to the group the question from our dev team:

****  Begin Comment ****
It is going to be a long post because I can't explain in a short
message. I'll provide some example to explain what I mean. 

We have SIP named QBATRUNK.  If you open administrator page
(https://DOMAIN:1443/subscriber/detail?subscriber_id=395) you can see
there following info:

Contract ID (405) - This is main ID which we store in (customer site -
not part of Sipwise it is our Database) . All operations like
lock/unlock SIP, add/remove DID using the ID in it request to API.

Subscriber ID (395) - I can call it internal info, it is not used in any
request to Sipwise API but to make direct request to Sipwise DB I have
to use it.

I routed 3384066 DID to the SIP to work with the example. 
According to previous instructions we use two databases to store
aliases. Now I'll show you request to retrieve the DID from Sipwise DB.

First I use billing DB. Let's retrieve Subscriber ID (we do not know it
when call DB directly). I use voip_subscribers table which stores the
info.

mysql> select * from voip_subscribers where contract_id = 405;
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+
| id | contract_id | uuid | username | domain_id | status | 
| primary_number_id | external_id |
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+
| 395 | 405 | 14a58c84-c83e-4673-9d10-361a1a6b990e | QBATRUNK | 1 | 
| active | NULL | NULL |
+-----+-------------+--------------------------------------+----------+-
----------+--------+-------------------+-------------+

OK you can see that I receive id 395. We need it.

 

Let's get DIDs info from voip_numbers, DB - 

mysql> select * from voip_numbers where subscriber_id = 395;
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+
| id | cc | ac | sn | reseller_id | subscriber_id | status | ported | 
| list_timestamp |
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+
| 2119 | 1 | 910 | 3384066 | NULL | 395 | active | 1 | 2014-07-22 
| 18:32:16 |
+------+----+-----+---------+-------------+---------------+--------+----
----+---------------------+

Everything is OK we got it as expected. Lets' get DID info from second
DB (provisioning) I'll do it using DID number

mysql> select * from voip_dbaliases where username like '%3384066%';
+------+-------------+-----------+---------------+
| id | username | domain_id | subscriber_id |
+------+-------------+-----------+---------------+
| 2821 | 19103384066 | 3 | 398 |

As you can see subscriber_id in the table does not corresponds to the
subscriber_id which we retrieve from billing DB. That is the question
for me.

I found that the subscriber_id is stored in voip_dbaliases table but the
ID does not corresponds to the subscriber_id from billing table.




************* 2 questions below ****************





Question 1
I do not understand how subscriber_id in billing DB (table voip_numbers)
related with subscriber_id in provisioning DB (table voip_dbaliases ).

Question 2
Another question. I found that DIDs info is stored in voip_dbaliases
table (provisioning) but I did not told to creae the record by VoIP
specialist.


mysql> select * from voip_dbaliases where username like '%3384066%';
+------+-------------+-----------+---------------+
| id | username | domain_id | subscriber_id |
+------+-------------+-----------+---------------+
| 2821 | 19103384066 | 3 | 398 |
+------+-------------+-----------+---------------+

Hopefully I explained my questions clear. If not please let me know

Thanks,
*** End Comment from DEV ***



In conclusion Andreas do you think there is a proper answer for the
above Question 1 and Question 2?
Thank you
Kevin 





-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Kevin Masse
Sent: Wednesday, July 16, 2014 8:56 AM
To: Andreas Granig; spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Subscriber Alias Entries in Database

Thank you Andreas, I appreciate the detailed response.  Works as
described.
Kevin



-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Andreas Granig
Sent: Wednesday, July 16, 2014 6:24 AM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Subscriber Alias Entries in Database

Hi,

On 07/15/2014 03:05 PM, Kevin Masse wrote:

> **  Current operation:   We use SOAP to add alias numbers to a
subscriber 
> 
> Requested operation:  We would like to write a new alias number for a 
> subscriber directly to the database.

As long as you make sure to write it to both billing.voip_numbers and
provisioning.voip_dbaliases, it should be fine.

Andreas

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/listinfo/spce-user

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/listinfo/spce-user


From agranig at sipwise.com  Fri Aug 29 18:09:45 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Sat, 30 Aug 2014 00:09:45 +0200
Subject: [Spce-user] SPCE 3.4.1 not showing call history in Web portal
In-Reply-To: <CAOibrm4SqsbnjoUVRp8sXWiWM8uciBTHrDWCURbUmWKNo3_SDw@mail.gmail.com>
References: <CAOibrm5h_Pnqe8X+sabQzQbCwA8=2Yw8Ubwbkxdtmnw67ed=9Q@mail.gmail.com>
 <54007A24.2000308@sipwise.com>
 <CAOibrm52FOQ6CNaR0aLbm6TS0=VVemKtnA1hoby+ME66YtR2wA@mail.gmail.com>
 <CAOibrm4w8u7WJF3eogS0Dk8jkp38yEJcbv8Jak-2630h9d4D2Q@mail.gmail.com>
 <CAOibrm4SqsbnjoUVRp8sXWiWM8uciBTHrDWCURbUmWKNo3_SDw@mail.gmail.com>
Message-ID: <5400FA29.4050908@sipwise.com>

Hi,

You need to check if mysqld is running and if you can connect to it via
command line.

Usual suspects for such issues are running out of memory (check dmesg
for OOM messages) and running out of disk space.

Andreas

On 08/29/2014 07:04 PM, Tabi Tabe Tabi wrote:
> Please ignore the email on the .tt template. Was not awake :-)
> 
> Problem still with database connection though. Any ideas?
> 
> Regards,
> 
> Tabi
> 
> 
> On Fri, Aug 29, 2014 at 6:39 PM, Tabi Tabe Tabi <tabi.tabe at gmail.com
> <mailto:tabi.tabe at gmail.com>> wrote:
> 
>     Hi Alex,
> 
>     An interesting observation. I checked Kamailio.log and found this
>     errors:
> 
>     Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:23:56 sipbc-2 proxy[16661]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
>     Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:25:58 sipbc-2 proxy[16665]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
>     Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:25:59 sipbc-2 proxy[16671]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
>     Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:26:02 sipbc-2 proxy[16667]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
>     Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:27:22 sipbc-2 proxy[16661]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
>     Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:27:23 sipbc-2 proxy[16665]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
>     Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: db_mysql
>     [km_dbase.c:122]: db_mysql_submit_query(): driver error on query:
>     Lost connection to MySQL server during query
>     Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: <core>
>     [db_query.c:235]: db_do_insert_cmd(): error while submitting query
>     Aug 29 18:27:24 sipbc-2 proxy[16667]: ERROR: acc [acc.c:509]:
>     acc_db_request(): failed to insert into database
> 
> 
> 
>     Also checked the CDR table in MySQL and found zero record. Can't
>     connect MySQL. MySQL is running. What parameters should I check? All
>     serv
> 
>     Regards,
> 
>     Tabi
> 
> 
>     On Fri, Aug 29, 2014 at 6:15 PM, Tabi Tabe Tabi <tabi.tabe at gmail.com
>     <mailto:tabi.tabe at gmail.com>> wrote:
> 
>         Will do. After updating the .tt file, do I need to run any
>         command to update the system?
> 
>         Regards,
> 
>         Tabi
> 
> 
>         On Fri, Aug 29, 2014 at 3:03 PM, Alex Lutay <alutay at sipwise.com
>         <mailto:alutay at sipwise.com>> wrote:
> 
>             Dear Tabi!
> 
> 
>             On 28/08/14 14:11, Tabi Tabe Tabi wrote:
> 
>                 I installed SPCE 3.4.1 and got is working fine. However
>                 it does not show
>                 call history under call distribution or subscriber menu.
>                 Any idea what
>                 could be the cause?
> 
> 
>             Can you try this fix:
> 
>                 https://github.com/sipwise/__ngcp-panel/commit/__cf93f0bf63dca1b66775feb5c7622a__f0c4d4cae6
>                 <https://github.com/sipwise/ngcp-panel/commit/cf93f0bf63dca1b66775feb5c7622af0c4d4cae6>
> 
>             if it helps you we will include it in next build mr3.4.2.
>             Thank you!
> 
>             -- 
>             Alexander Lutay
>             Head of Quality Assurance
>             Sipwise GmbH, Campus 21/Europaring F15
>             AT-2345 Brunn am Gebirge
> 
>             Office: +43(0)13012036 <tel:%2B43%280%2913012036>
>             Email: alutay at sipwise.com <mailto:alutay at sipwise.com>
>             Website: http://www.sipwise.com
>             _________________________________________________
>             Spce-user mailing list
>             Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>             https://lists.sipwise.com/__listinfo/spce-user
>             <https://lists.sipwise.com/listinfo/spce-user>
> 
> 
> 
> 
>         -- 
>         ...Tabi
> 
> 
> 
> 
>     -- 
>     ...Tabi
> 
> 
> 
> 
> -- 
> ...Tabi
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From agranig at sipwise.com  Fri Aug 29 18:16:52 2014
From: agranig at sipwise.com (Andreas Granig)
Date: Sat, 30 Aug 2014 00:16:52 +0200
Subject: [Spce-user] LCR in SPCE?
In-Reply-To: <5400A7F1.6060208@xoomtalk.com>
References: <5400A7F1.6060208@xoomtalk.com>
Message-ID: <5400FBD4.2020506@sipwise.com>

Hi,

You can bulk-upload a CSV via the panel (since pretty much from the
start) or via REST API (since mr3.4).

You can then enable LCR for peerings by setting "perform_peer_lcr" to
"yes" in config.yml (off by default).

Andreas

On 08/29/2014 06:18 PM, George Mason wrote:
> Hi,
> 
> I have been looking around SPCE and like what I see. One element that I
> cannot see anywhere, which is useful on other systems, is LCR. Namely
> the ability to route a call to a given carrier based on the price for
> that call.
> 
> As far as I can see, rate-o-mat rates the calls after they have
> completed, so there is no account taken of what the cheapest route might
> have been. This is a shame as it requires more complex routes to get
> traffic over the best-costing carrier.
> 
> On that subject - is there a way to bulk import callee patterns against
> a SIP peering? I am trying to configure a channel to only route the best
> priced destinations and this involves lots (over 60K) of patterns. Will
> this kill the routing engine? How can I import these, presume they need
> to go straight into the DB?
> 
> Thanks
> 
> George
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From jbonilla at sipwise.com  Sat Aug 30 03:25:47 2014
From: jbonilla at sipwise.com (Jon Bonilla (Manwe))
Date: Sat, 30 Aug 2014 09:25:47 +0200
Subject: [Spce-user] LCR in SPCE?
In-Reply-To: <5400A7F1.6060208@xoomtalk.com>
References: <5400A7F1.6060208@xoomtalk.com>
Message-ID: <20140830092547.76a3abb4@quenya>

El Fri, 29 Aug 2014 17:18:57 +0100
George Mason <george.mason at xoomtalk.com> escribi?:

> Hi,
> 
> I have been looking around SPCE and like what I see. One element that I
> cannot see anywhere, which is useful on other systems, is LCR. Namely
> the ability to route a call to a given carrier based on the price for
> that call.
> 
> As far as I can see, rate-o-mat rates the calls after they have
> completed, so there is no account taken of what the cheapest route might
> have been. This is a shame as it requires more complex routes to get
> traffic over the best-costing carrier.
> 
> On that subject - is there a way to bulk import callee patterns against
> a SIP peering? I am trying to configure a channel to only route the best
> priced destinations and this involves lots (over 60K) of patterns. Will
> this kill the routing engine? How can I import these, presume they need
> to go straight into the DB?
> 
>

Hi George

You can enable lcr in config.yml, in the proxy section.




 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140830/c4436726/attachment-0001.asc>

From aalejandro at alliedtechnologygrouppr.com  Sun Aug 31 03:05:11 2014
From: aalejandro at alliedtechnologygrouppr.com (Abel Alejandro)
Date: Sun, 31 Aug 2014 03:05:11 -0400
Subject: [Spce-user] invoke-rc.d: policy-rc.d denied execution of stop.
Message-ID: <CAKiNg21vn2UqtTBvjpEW9jxTt41UYL-rcAzUeOS-Va085q=yrg@mail.gmail.com>

Hello,

Upgrading from mr3.3.1 to mr3.4.1 I got a few of those errors and it seems
the upgrade tried to stop a few demons but got stuck when it couldnt stop
mysql.

Just stopped the mysql daemon manually and the upgraded continued fine.

Everything seems to be working after upgrade just wanted to report in case.

Thanks.

-- 
*Abel Alejandro*

787 586 8313 | 787 705 0555
<joquendo at alliedtechnologygrouppr.com>

400 Calle Calaf 477
San Juan, PR 00918
aalejandro at alliedtechnologygrouppr.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140831/8a0bcab3/attachment-0001.html>

From mprokop at sipwise.com  Sun Aug 31 03:29:31 2014
From: mprokop at sipwise.com (Michael Prokop)
Date: Sun, 31 Aug 2014 09:29:31 +0200
Subject: [Spce-user] invoke-rc.d: policy-rc.d denied execution of stop.
In-Reply-To: <CAKiNg21vn2UqtTBvjpEW9jxTt41UYL-rcAzUeOS-Va085q=yrg@mail.gmail.com>
References: <CAKiNg21vn2UqtTBvjpEW9jxTt41UYL-rcAzUeOS-Va085q=yrg@mail.gmail.com>
Message-ID: <2014-08-31T09-27-06@devnull.michael-prokop.at>

* Abel Alejandro [Sun Aug 31, 2014 at 03:05:11AM -0400]:

> Upgrading from mr3.3.1 to mr3.4.1 I got a few of those errors and it seems
> the upgrade tried to stop a few demons but got stuck when it couldnt stop
> mysql.

> Just stopped the mysql daemon manually and the upgraded continued fine.

> Everything seems to be working after upgrade just wanted to report in case.

Did your upgrade actually really interrupt/abort? If so do you have
any error logs available for us?

The 'invoke-rc.d: policy-rc.d denied execution of stop' are only
warnings and no error messages, that setup is by intention and
should be working just fine.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140831/7e263ad6/attachment-0001.asc>

From aalejandro at alliedtechnologygrouppr.com  Sun Aug 31 03:38:37 2014
From: aalejandro at alliedtechnologygrouppr.com (Abel Alejandro)
Date: Sun, 31 Aug 2014 03:38:37 -0400
Subject: [Spce-user] invoke-rc.d: policy-rc.d denied execution of stop.
In-Reply-To: <2014-08-31T09-27-06@devnull.michael-prokop.at>
References: <CAKiNg21vn2UqtTBvjpEW9jxTt41UYL-rcAzUeOS-Va085q=yrg@mail.gmail.com>
 <2014-08-31T09-27-06@devnull.michael-prokop.at>
Message-ID: <CAKiNg23G0-S2V4PCzgK2pSOHD0i+iU0+M3pEkyJRV0=zTNZg2w@mail.gmail.com>

While the upgrade got stuck I ran this:

root at sip:/var/log# tail /tmp/upgrade.log
Unpacking replacement mysql-client-5.5 ...
Preparing to replace mysql-server-core-5.5 5.5.37-0+wheezy1 (using
.../mysql-server-core-5.5_5.5.38-0+wheezy1_amd64.deb) ...
Unpacking replacement mysql-server-core-5.5 ...
Preparing to replace ngcp-installer-ce 0.14.1.3+0~mr3.3.1.3 (using
.../ngcp-installer-ce_0.15.1.2+0~mr3.4.1.2_all.deb) ...
Unpacking replacement ngcp-installer-ce ...
Processing triggers for man-db ...
Setting up mysql-client-5.5 (5.5.38-0+wheezy1) ...
Setting up mysql-server-core-5.5 (5.5.38-0+wheezy1) ...
Setting up mysql-server-5.5 (5.5.38-0+wheezy1) ...
invoke-rc.d: policy-rc.d denied execution of stop.
root at sip:/var/log#

I had two instances of mysqld trying to come up, the last one kept changing
process id, so I just killed the old one

root at sip:/var/log# ps -aux
warning: bad ps syntax, perhaps a bogus '-'?
See http://gitorious.org/procps/procps/blobs/master/Documentation/FAQ
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0  10648   696 ?        Ss   Jul19   1:23 init [2]
root         2  0.0  0.0      0     0 ?        S    Jul19   0:00 [kthreadd]
root         3  0.0  0.0      0     0 ?        S    Jul19   0:19
[ksoftirqd/0]
root         5  0.0  0.0      0     0 ?        S    Jul19   0:26
[kworker/u:0]
root         6  0.0  0.0      0     0 ?        S    Jul19   0:00
[migration/0]
root         7  0.0  0.0      0     0 ?        S    Jul19   0:08
[watchdog/0]
root         8  0.0  0.0      0     0 ?        S    Jul19   0:00
[migration/1]
root         9  0.0  0.0      0     0 ?        S    Jul19   1:11
[kworker/1:0]
root        10  0.0  0.0      0     0 ?        S    Jul19   0:15
[ksoftirqd/1]
root        11  0.0  0.0      0     0 ?        S    Jul19   1:34
[kworker/0:1]
root        12  0.0  0.0      0     0 ?        S    Jul19   0:06
[watchdog/1]
root        13  0.0  0.0      0     0 ?        S    Jul19   0:00
[migration/2]
root        14  0.0  0.0      0     0 ?        S    Jul19   1:22
[kworker/2:0]
root        15  0.0  0.0      0     0 ?        S    Jul19   0:15
[ksoftirqd/2]
root        16  0.0  0.0      0     0 ?        S    Jul19   0:07
[watchdog/2]
root        17  0.0  0.0      0     0 ?        S    Jul19   0:00
[migration/3]
root        19  0.0  0.0      0     0 ?        S    Jul19   0:16
[ksoftirqd/3]
root        20  0.0  0.0      0     0 ?        S    Jul19   0:06
[watchdog/3]
root        21  0.0  0.0      0     0 ?        S    Jul19   0:17
[migration/4]
root        23  0.0  0.0      0     0 ?        S    Jul19   0:20
[ksoftirqd/4]
root        24  0.0  0.0      0     0 ?        S    Jul19   0:06
[watchdog/4]
root        25  0.0  0.0      0     0 ?        S    Jul19   0:17
[migration/5]
root        27  0.0  0.0      0     0 ?        S    Jul19   0:18
[ksoftirqd/5]
root        28  0.0  0.0      0     0 ?        S    Jul19   0:06
[watchdog/5]
root        29  0.0  0.0      0     0 ?        S    Jul19   0:17
[migration/6]
root        31  0.0  0.0      0     0 ?        S    Jul19   0:16
[ksoftirqd/6]
root        32  0.0  0.0      0     0 ?        S    Jul19   0:06
[watchdog/6]
root        33  0.0  0.0      0     0 ?        S    Jul19   0:17
[migration/7]
root        35  0.0  0.0      0     0 ?        S    Jul19   0:15
[ksoftirqd/7]
root        36  0.0  0.0      0     0 ?        S    Jul19   0:06
[watchdog/7]
root        37  0.0  0.0      0     0 ?        S<   Jul19   0:00 [cpuset]
root        38  0.0  0.0      0     0 ?        S<   Jul19   0:00 [khelper]
root        39  0.0  0.0      0     0 ?        S    Jul19   0:00 [kdevtmpfs]
root        40  0.0  0.0      0     0 ?        S<   Jul19   0:00 [netns]
root        41  0.0  0.0      0     0 ?        S    Jul19   0:06
[sync_supers]
root        42  0.0  0.0      0     0 ?        S    Jul19   0:00
[bdi-default]
root        43  0.0  0.0      0     0 ?        S<   Jul19   0:00
[kintegrityd]
root        44  0.0  0.0      0     0 ?        S<   Jul19   0:00 [kblockd]
root        45  0.0  0.0      0     0 ?        S    Jul19   1:25
[kworker/1:1]
root        46  0.0  0.0      0     0 ?        S    Jul19   1:18
[kworker/2:1]
root        47  0.0  0.0      0     0 ?        S    Jul19   2:21
[kworker/3:1]
root        48  0.0  0.0      0     0 ?        S    Jul19   1:21
[kworker/4:1]
root        49  0.0  0.0      0     0 ?        S    Jul19   0:58
[kworker/5:1]
root        51  0.0  0.0      0     0 ?        S    Jul19   0:34
[kworker/7:1]
root        52  0.0  0.0      0     0 ?        S    Jul19   0:02
[khungtaskd]
root        53  0.0  0.0      0     0 ?        S    Jul19   0:00 [kswapd0]
root        54  0.0  0.0      0     0 ?        SN   Jul19   0:00 [ksmd]
root        55  0.0  0.0      0     0 ?        SN   Jul19   0:00
[khugepaged]
root        56  0.0  0.0      0     0 ?        S    Jul19   0:00
[fsnotify_mark]
root        57  0.0  0.0      0     0 ?        S<   Jul19   0:00 [crypto]
root       183  0.0  0.0      0     0 ?        S    Jul19   0:00 [khubd]
root       184  0.0  0.0      0     0 ?        S    Jul19   0:00
[cciss_scan]
root       185  0.0  0.0      0     0 ?        S<   Jul19   0:00 [ata_sff]
root       186  0.0  0.0      0     0 ?        S    Jul19   0:00 [scsi_eh_0]
root       187  0.0  0.0      0     0 ?        S    Jul19   0:00 [scsi_eh_1]
root       189  0.0  0.0      0     0 ?        S    Jul19   0:00 [scsi_eh_2]
root       191  0.0  0.0      0     0 ?        S    Jul19   0:30
[kworker/u:1]
root       200  0.0  0.0      0     0 ?        S    Jul19   1:15
[kworker/7:2]
root       205  0.0  0.0      0     0 ?        S    Jul19   0:29
[kworker/4:2]
root       207  0.0  0.0      0     0 ?        S    Jul19   2:14
[kworker/3:2]
root       229  0.0  0.0      0     0 ?        S    Jul19  11:13
[jbd2/cciss!c0d0]
root       230  0.0  0.0      0     0 ?        S<   Jul19   0:00
[ext4-dio-unwrit]
root       370  0.0  0.0  21380  1376 ?        Ss   Jul19   0:00 udevd
--daemon
root       481  0.0  0.0  21376   908 ?        S    Jul19   0:00 udevd
--daemon
root       483  0.0  0.0  21376   908 ?        S    Jul19   0:00 udevd
--daemon
root       523  0.0  0.0      0     0 ?        S    Jul19   1:49
[kworker/0:2]
root       534  0.0  0.0      0     0 ?        S<   Jul19   0:00 [kpsmoused]
root       537  0.0  0.0      0     0 ?        S<   Jul19   0:00
[edac-poller]
root       544  0.0  0.0      0     0 ?        S<   Jul19   0:00 [ttm_swap]
root      1901  0.0  0.0      0     0 ?        S    Jul19   1:19
[kworker/5:2]
root      1978  0.1  0.0 257932  2168 ?        Sl   Jul19  78:58
/usr/sbin/rsyslogd -c5
root      2165  0.0  0.0   4116   652 ?        Ss   Jul19   0:00
/usr/sbin/acpid
root      2183  0.0  0.0  20412   704 ?        Ss   Jul19   2:30
/usr/sbin/irqbalance
root      2206  0.0  0.0  20408  1084 ?        Ss   Jul19   0:20
/usr/sbin/cron
root      2235  0.0  0.0  14860   152 ?        Ss   Jul19   0:00
/usr/sbin/in.tftpd --listen --user tftp --address 0.0.0.0:69 --secure
/srv/tftp
ntp       2263  0.0  0.0  39072  2392 ?        Ss   Jul19   2:01
/usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 105:107
root      2281  0.0  0.0      0     0 ?        S    Jul19  23:39
[flush-104:0]
root      2344  0.0  0.0  49932  1256 ?        Ss   Jul19   0:54
/usr/sbin/sshd
root      3210  0.0  0.0      0     0 ?        S    Aug30   0:12
[kworker/6:2]
root      3325  0.0  0.0  12364   324 ?        Ss   Jul19   0:00
/usr/sbin/collectdmon -P /var/run/collectdmon.pid -- -C
/etc/collectd/collectd.conf
root      3326  0.7  0.1 533100 28296 ?        SLl  Jul19 451:48 collectd
-C /etc/collectd/collectd.conf -f
101       4415  0.0  0.0  46804  1064 ?        Ss   Jul19   0:00
/usr/sbin/exim4 -bd -q30m
root      4610  0.0  0.0  16256   960 tty1     Ss+  Jul19   0:00
/sbin/getty 38400 tty1
root      4611  0.0  0.0  16256   960 tty2     Ss+  Jul19   0:00
/sbin/getty 38400 tty2
root      4612  0.0  0.0  16256   952 tty3     Ss+  Jul19   0:00
/sbin/getty 38400 tty3
root      4613  0.0  0.0  16256   956 tty4     Ss+  Jul19   0:00
/sbin/getty 38400 tty4
root      4614  0.0  0.0  16256   964 tty5     Ss+  Jul19   0:00
/sbin/getty 38400 tty5
root      4615  0.0  0.0  16256   960 tty6     Ss+  Jul19   0:00
/sbin/getty 38400 tty6
root      4616  0.0  0.0  14576   876 ttyS1    Ss+  Jul19   0:00
/sbin/agetty 9600 ttyS1 vt100
root      8860  0.0  0.0  71292  3688 ?        Ss   02:22   0:00 sshd:
root at pts/2
root      8920  0.0  0.0  20652  3548 pts/2    Ss   02:22   0:00 -bash
root     11355  0.0  0.0  10784  1508 pts/2    S+   02:28   0:00 /bin/bash
/usr/sbin/ngcp-upgrade
root     11388  0.0  0.0  16052   844 pts/2    S+   02:28   0:00 script
-fqc '/usr/sbin/ngcp-upgrade' '--inside-log' /tmp/upgrade.log
root     11389  0.0  0.0  16056   528 pts/2    S+   02:28   0:00 script
-fqc '/usr/sbin/ngcp-upgrade' '--inside-log' /tmp/upgrade.log
root     11390  0.0  0.0  10780  1528 pts/3    Ss+  02:28   0:00 /bin/bash
/usr/sbin/ngcp-upgrade --inside-log
root     11394  0.0  0.0  39460  8832 pts/3    S+   02:28   0:00 python -m
SimpleHTTPServer 4242
root     11408  0.0  0.0  10776  1512 pts/3    S+   02:28   0:00 /bin/bash
/usr/share/ngcp-upgrade-mr3.4.1/upgrade-mr3.3.1-to-mr3.4.1
root     11807  0.0  0.0   4180   712 pts/3    S+   02:28   0:00 /bin/sh
/usr/bin/mysqld_safe
root     12302  0.0  0.0      0     0 ?        S    Aug26   0:30
[kworker/6:0]
mysql    12742  2.1  6.6 9527732 1099144 pts/3 Sl+  02:28   0:13
/usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql
--plugin-dir=/usr/lib/mysql/plugin --user=mysql
--log-error=/var/log/mysql/mysqld.err --pid-f
root     13384  0.0  0.1  58476 25800 pts/3    S+   02:29   0:00 apt-get -y
--force-yes -o DPkg::Options::=--force-confnew dist-upgrade
root     15334  0.0  0.0  12252  3900 pts/0    Ss+  02:31   0:00
/usr/bin/dpkg --force-confnew --status-fd 16 --configure
mysql-client-5.5:amd64 mysql-server-core-5.5:amd64 mysql-server-5.5:amd64
root     15381  0.0  0.0  58488 12852 pts/0    S+   02:31   0:00
/usr/bin/perl -w /usr/share/debconf/frontend
/var/lib/dpkg/info/mysql-server-5.5.postinst configure 5.5.37-0+wheezy1
root     15387  0.0  0.0   9364  1540 pts/0    S+   02:31   0:00 /bin/bash
/var/lib/dpkg/info/mysql-server-5.5.postinst configure 5.5.37-0+wheezy1
root     16673  0.0  0.0  71292  3692 ?        Ss   02:35   0:00 sshd:
root at pts/4
root     16725  0.0  0.0  20636  3544 pts/4    Ss   02:36   0:00 -bash
mysql    17483  4.3  4.0 9386576 661012 pts/0  Sl+  02:38   0:00
/usr/sbin/mysqld --bootstrap --user=mysql --skip-grant-tables
root     17554  0.0  0.0   4096   324 ?        S    02:38   0:00 sleep 10
root     17572  0.0  0.0   4096   324 ?        S    02:38   0:00 sleep 10
root     17588  0.0  0.0  16836  1288 pts/4    R+   02:38   0:00 ps -aux
root     18616  0.0  0.0  39424  5080 ?        Sl   Jul20  31:46 captagent
-d




On Sun, Aug 31, 2014 at 3:29 AM, Michael Prokop <mprokop at sipwise.com> wrote:

> * Abel Alejandro [Sun Aug 31, 2014 at 03:05:11AM -0400]:
>
> > Upgrading from mr3.3.1 to mr3.4.1 I got a few of those errors and it
> seems
> > the upgrade tried to stop a few demons but got stuck when it couldnt stop
> > mysql.
>
> > Just stopped the mysql daemon manually and the upgraded continued fine.
>
> > Everything seems to be working after upgrade just wanted to report in
> case.
>
> Did your upgrade actually really interrupt/abort? If so do you have
> any error logs available for us?
>
> The 'invoke-rc.d: policy-rc.d denied execution of stop' are only
> warnings and no error messages, that setup is by intention and
> should be working just fine.
>
> regards,
> -mika-
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAlQCztsACgkQ2N9T+zficuhBHACfexNoI4e9u2puc+kbmSe4Y3x/
> aO8AnjmXnkmde5TZFqibgULZ1kpiUDlN
> =UbCF
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>


-- 
*Abel Alejandro*

787 586 8313 | 787 705 0555
<joquendo at alliedtechnologygrouppr.com>

400 Calle Calaf 477
San Juan, PR 00918
aalejandro at alliedtechnologygrouppr.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140831/48eccb5f/attachment-0001.html>

From jbonilla at sipwise.com  Sun Aug 31 04:24:26 2014
From: jbonilla at sipwise.com (Jon Bonilla (Manwe))
Date: Sun, 31 Aug 2014 10:24:26 +0200
Subject: [Spce-user] invoke-rc.d: policy-rc.d denied execution of stop.
In-Reply-To: <CAKiNg23G0-S2V4PCzgK2pSOHD0i+iU0+M3pEkyJRV0=zTNZg2w@mail.gmail.com>
References: <CAKiNg21vn2UqtTBvjpEW9jxTt41UYL-rcAzUeOS-Va085q=yrg@mail.gmail.com>
 <2014-08-31T09-27-06@devnull.michael-prokop.at>
 <CAKiNg23G0-S2V4PCzgK2pSOHD0i+iU0+M3pEkyJRV0=zTNZg2w@mail.gmail.com>
Message-ID: <20140831102426.0736cb0a@quenya>

El Sun, 31 Aug 2014 03:38:37 -0400
Abel Alejandro <aalejandro at alliedtechnologygrouppr.com> escribi?:

> While the upgrade got stuck I ran this:
> 
> root at sip:/var/log# tail /tmp/upgrade.log
> Unpacking replacement mysql-client-5.5 ...
> Preparing to replace mysql-server-core-5.5 5.5.37-0+wheezy1 (using
> .../mysql-server-core-5.5_5.5.38-0+wheezy1_amd64.deb) ...
> Unpacking replacement mysql-server-core-5.5 ...
> Preparing to replace ngcp-installer-ce 0.14.1.3+0~mr3.3.1.3 (using
> .../ngcp-installer-ce_0.15.1.2+0~mr3.4.1.2_all.deb) ...
> Unpacking replacement ngcp-installer-ce ...
> Processing triggers for man-db ...
> Setting up mysql-client-5.5 (5.5.38-0+wheezy1) ...
> Setting up mysql-server-core-5.5 (5.5.38-0+wheezy1) ...
> Setting up mysql-server-5.5 (5.5.38-0+wheezy1) ...
> invoke-rc.d: policy-rc.d denied execution of stop.
> root at sip:/var/log#
>

I recently experienced the problem during the upgrade and had to kill mysql
processes to allow the upgrade process to continue.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140831/574746e4/attachment-0001.asc>

From marek.cervenka at fpf.slu.cz  Fri Aug 29 06:56:19 2014
From: marek.cervenka at fpf.slu.cz (=?UTF-8?B?TWFyZWsgxIxlcnZlbmth?=)
Date: Fri, 29 Aug 2014 10:56:19 -0000
Subject: [Spce-user] spce ip aliases
Message-ID: <54005A50.3040206@fpf.slu.cz>

hi,

is it possible use spce with multiple aliased ips?

like
eth0 192.168.100.1
eth0:1 192.168.100.20
eth0:2 192.168.100.30

and register endpoints to i.e. 192.168.100.30 and answer from spce will 
have src ip 192.168.100.30
thanks

-- 
---------------------------------------
Marek Cervenka
=======================================



From noreply at sipwise.com  Fri Aug  1 04:08:06 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 01 Aug 2014 08:08:06 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1406880480.756988.585.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.7+0~mr3.3.2.7 to version 1.3.2.8+0~mr3.3.2.8
* ngcp-panel-tools was updated from version 1.3.2.7+0~mr3.3.2.7 to version 1.3.2.8+0~mr3.3.2.8

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug  1 04:37:58 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 01 Aug 2014 08:37:58 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1406882272.737715.7090.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.8+0~mr3.3.2.8 to version 1.3.2.9+0~mr3.3.2.9
* ngcp-panel-tools was updated from version 1.3.2.8+0~mr3.3.2.8 to version 1.3.2.9+0~mr3.3.2.9

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Sun Aug  3 20:38:55 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 04 Aug 2014 00:38:55 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1407112725.689451.13182.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-db-schema was updated from version 3.3.3.2+0~mr3.3.2.2 to version 3.3.3.3+0~mr3.3.2.3

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Sun Aug  3 20:41:29 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 04 Aug 2014 00:41:29 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1407112882.807813.16593.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-schema was updated from version 3.1.2.1+0~mr3.3.2.1 to version 3.1.2.2+0~mr3.3.2.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug  5 01:18:50 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 05 Aug 2014 05:18:50 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1407215924.972116.6498.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.9+0~mr3.3.2.9 to version 1.3.2.10+0~mr3.3.2.10
* ngcp-panel-tools was updated from version 1.3.2.9+0~mr3.3.2.9 to version 1.3.2.10+0~mr3.3.2.10

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Sat Aug  9 22:55:09 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Sun, 10 Aug 2014 02:55:09 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1407639304.052809.12176.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.10+0~mr3.3.2.10 to version 1.3.2.11+0~mr3.3.2.11
* ngcp-panel-tools was updated from version 1.3.2.10+0~mr3.3.2.10 to version 1.3.2.11+0~mr3.3.2.11

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug 12 10:48:21 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 12 Aug 2014 14:48:21 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1407854896.027288.13608.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.11+0~mr3.3.2.11 to version 1.3.2.12+0~mr3.3.2.12
* ngcp-panel-tools was updated from version 1.3.2.11+0~mr3.3.2.11 to version 1.3.2.12+0~mr3.3.2.12

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Wed Aug 13 18:05:16 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Wed, 13 Aug 2014 22:05:16 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1407967510.346840.19837.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.12+0~mr3.3.2.12 to version 1.3.2.13+0~mr3.3.2.13
* ngcp-panel-tools was updated from version 1.3.2.12+0~mr3.3.2.12 to version 1.3.2.13+0~mr3.3.2.13

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Aug 14 06:58:05 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 14 Aug 2014 10:58:05 -0000
Subject: [Spce-user] FYI: Package update(s) in release 2.8
Message-ID: <1408013880.010662.2242.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 2.8:

* ngcp-db-schema was updated from version 2.8.5 to version 2.8.6
* ngcp-handbook-ce was updated from version 2.8.6 to version 2.8.7
* ngcp-handbook-pro was updated from version 2.8.6 to version 2.8.7
* ngcp-libswrate-dev was updated from version 1.1.6 to version 1.1.7
* ngcp-libswrate0 was updated from version 1.1.6 to version 1.1.7

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Aug 14 07:34:43 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 14 Aug 2014 11:34:43 -0000
Subject: [Spce-user] FYI: Package update(s) in release 2.8
Message-ID: <1408016078.095405.9059.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 2.8:

* ngcp-db-schema was updated from version 2.8.6 to version 2.8.7

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Aug 14 09:32:58 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 14 Aug 2014 13:32:58 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408023172.740440.20421.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.13+0~mr3.3.2.13 to version 1.3.2.14+0~mr3.3.2.14
* ngcp-panel-tools was updated from version 1.3.2.13+0~mr3.3.2.13 to version 1.3.2.14+0~mr3.3.2.14

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Aug 14 12:21:45 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 14 Aug 2014 16:21:45 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408033300.747504.23259.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-db-schema was updated from version 3.3.3.3+0~mr3.3.2.3 to version 3.3.3.4+0~mr3.3.2.4

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Aug 14 13:15:00 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 14 Aug 2014 17:15:00 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408036493.194163.15496.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.14+0~mr3.3.2.14 to version 1.3.2.15+0~mr3.3.2.15
* ngcp-panel-tools was updated from version 1.3.2.14+0~mr3.3.2.14 to version 1.3.2.15+0~mr3.3.2.15

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Aug 14 17:18:49 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 14 Aug 2014 21:18:49 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408051124.097466.15979.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.15+0~mr3.3.2.15 to version 1.3.2.16+0~mr3.3.2.16
* ngcp-panel-tools was updated from version 1.3.2.15+0~mr3.3.2.15 to version 1.3.2.16+0~mr3.3.2.16

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Aug 18 13:57:55 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 18 Aug 2014 17:57:55 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408384669.586131.24700.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.16+0~mr3.3.2.16 to version 1.3.2.17+0~mr3.3.2.17
* ngcp-panel-tools was updated from version 1.3.2.16+0~mr3.3.2.16 to version 1.3.2.17+0~mr3.3.2.17

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug 19 11:58:43 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 19 Aug 2014 15:58:43 -0000
Subject: [Spce-user] FYI: Package update(s) in release 3.0
Message-ID: <1408463920.314711.30200.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 3.0:

* ngcp-libswrate-dev was updated from version 1.1.6 to version 1.1.7
* ngcp-libswrate0 was updated from version 1.1.6 to version 1.1.7

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug 19 12:16:00 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 19 Aug 2014 16:16:00 -0000
Subject: [Spce-user] FYI: Package update(s) in release 3.1
Message-ID: <1408464957.243005.32207.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 3.1:

* ngcp-libswrate-dev was updated from version 1.1.6 to version 1.1.7
* ngcp-libswrate0 was updated from version 1.1.6 to version 1.1.7
* ngcp-panel was updated from version 1.1.16 to version 1.1.17

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug 19 12:58:49 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 19 Aug 2014 16:58:49 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.2.1
Message-ID: <1408467523.789979.3789.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.2.1:

* ngcp-libswrate-dev was updated from version 1.1.6.1+0~mr3.2.1.1 to version 1.1.7.1+0~mr3.2.1.2
* ngcp-libswrate0 was updated from version 1.1.6.1+0~mr3.2.1.1 to version 1.1.7.1+0~mr3.2.1.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Wed Aug 20 05:48:43 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Wed, 20 Aug 2014 09:48:43 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408528117.364976.9228.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-panel was updated from version 1.3.2.17+0~mr3.3.2.17 to version 1.3.2.18+0~mr3.3.2.18
* ngcp-panel-tools was updated from version 1.3.2.17+0~mr3.3.2.17 to version 1.3.2.18+0~mr3.3.2.18

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 06:51:22 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 10:51:22 -0000
Subject: [Spce-user] FYI: Package update(s) in release 2.8
Message-ID: <1408704676.701742.26194.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 2.8:

* ngcp-backup-tools was updated from version 0.1.1 to version 0.1.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 06:56:43 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 10:56:43 -0000
Subject: [Spce-user] FYI: Package update(s) in release 3.0
Message-ID: <1408704998.315949.27128.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 3.0:

* ngcp-backup-tools was updated from version 0.2.0 to version 0.2.1

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 06:58:10 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 10:58:10 -0000
Subject: [Spce-user] FYI: Package update(s) in release 3.1
Message-ID: <1408705085.177531.27383.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release 3.1:

* ngcp-backup-tools was updated from version 0.2.0 to version 0.2.1

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 07:15:53 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 11:15:53 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.2.1
Message-ID: <1408706148.493018.3202.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.2.1:

* ngcp-backup-tools was updated from version 0.2.0.1+0~mr3.2.1.1 to version 0.2.0.2+0~mr3.2.1.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 07:16:43 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 11:16:43 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.2.2
Message-ID: <1408706198.076724.3302.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.2.2:

* ngcp-backup-tools was updated from version 0.2.1.1+0~mr3.2.2.1 to version 0.2.1.2+0~mr3.2.2.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 07:19:43 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 11:19:43 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.1
Message-ID: <1408706378.501945.3644.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.1:

* ngcp-backup-tools was updated from version 0.3.1.2+0~mr3.3.1.2 to version 0.3.1.3+0~mr3.3.1.3

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Fri Aug 22 07:22:41 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Fri, 22 Aug 2014 11:22:41 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.3.2
Message-ID: <1408706556.214057.7583.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.3.2:

* ngcp-backup-tools was updated from version 0.3.2.1+0~mr3.3.2.1 to version 0.3.2.2+0~mr3.3.2.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug 26 06:53:14 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 26 Aug 2014 10:53:14 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.2.1
Message-ID: <1409050387.571493.12561.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.2.1:

* ngcp-backup-tools was updated from version 0.2.0.2+0~mr3.2.1.2 to version 0.2.1.3+0~mr3.2.1.3

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Tue Aug 26 06:54:00 2014
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Tue, 26 Aug 2014 10:54:00 -0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.2.2
Message-ID: <1409050435.587701.12736.nullmailer@deb.sipwise.com>

One or more updates have been released in NGCP release mr3.2.2:

* ngcp-backup-tools was updated from version 0.2.1.2+0~mr3.2.2.2 to version 0.2.2.3+0~mr3.2.2.3

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com