date:20180313

Re: [Project Clearwater] Does Clearwater support to provision wildcarded PSI?

2018-03-13 Thread Anthony Lee

Thanks, Ben.


I wonder what the difference is between using DNS to map the (w)PSI domain
to my application server
and using (w)PSI in HSS profile.


Anthony


On Tue, Mar 13, 2018 at 1:17 PM, Bennett Allen  wrote:

> Hi Anthony,
>
> From the logs you have sent I see that you are using homestead-prov, we
> only support wildcarded entries with a HSS, which would explain the issues
> you are hitting. Here is a link to the docs about a HSS -
> http://clearwater.readthedocs.io/en/stable/External_HSS_Integration.html .
>
> Let us know how it goes,
>
> Ben
>
>
>
>
>
> *From:* Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org]
> *On Behalf Of *Anthony Lee
> *Sent:* 10 March 2018 20:02
> *To:* clearwater@lists.projectclearwater.org
> *Subject:* Re: [Project Clearwater] Does Clearwater support to provision
> wildcarded PSI?
>
>
>
> Now I added P-Profile-Key header into the request, the header value is my
> wildcard PSI uri( sip:.+@list-service.example.com ).
>
>
>
> Homestead  log:
>
> 10-03-2018 19:39:50.073 UTC [7f22987f8700] Debug http_handlers.cpp:619:
> Determining request type from '{"reqtype": "call", "server_name": "
> sip:scscf.192.168.1.10:5054;transport=TCP", "wildcard_identity": "
> sip:.+@list-service.example.com"}'
>
>
>
> 10-03-2018 19:39:50.074 UTC [7f22c4fb1700] Debug memcached_cache.cpp:27:
> Pausing stopwatch due to Memcached GET fetch result for
> impu\\sip:.+@list-service.example.com
>
> 10-03-2018 19:39:50.075 UTC [7f22c4fb1700] Debug memcached_cache.cpp:33:
> Resuming stopwatch due to Memcached GET fetch result for impu\\
> sip:.+@list-service.example.com
>
>
>
> 10-03-2018 19:39:50.075 UTC [7f22c4fb1700] Debug memcachedstore.cpp:414:
> Key not found
>
>
>
> 10-03-2018 19:39:50.075 UTC [7f229affd700] Debug hsprov_store.cpp:78:
> Issuing get for key sip:7gbcen27b7lqvh3noa3nt8nftc7gbc
> en27b7lqvh3noa3nt8n...@list-service.example.com
>
>
>
> 10-03-2018 19:39:50.078 UTC [7f229affd700] Debug cassandra_store.cpp:536:
> Cassandra request failed: rc=2, Row sip:7gbcen27b7lqvh3noa3nt8nftc7gbc
> en27b7lqvh3noa3nt8n...@list-service.example.com not present in
> column_family impu
>
>
>
>
>
> Looks like Homestead uses P-Profile-Key's value to search in cache but
> uses R-URI to search in database.
>
>
>
> Is it expected behavior?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Sat, Mar 10, 2018 at 10:48 AM, Anthony Lee 
> wrote:
>
> Sorry, forgot to mention that  Sprout's log  shows that 404 not found for
> that wildcard PSI return from Homestead. .
>
>
>
> On Sat, Mar 10, 2018 at 10:44 AM, Anthony Lee 
> wrote:
>
> My wildcard PSI is  sip:.+@list-service.example.com
>
>
>
>
>
> I found some information in Homestead_current.txt:
>
>
>
> Debug http_handlers.cpp:695: Did not receive valid JSON with a
> 'wildcard_identity' element
>
>
>
> Does it mean scscf need to add "wildcard_identity" into the JSON request?
>
> Is there any configuration need to be done in Sprout?
>
>
>
>
>
>
>
> On Fri, Mar 9, 2018 at 10:54 PM, Anthony Lee 
> wrote:
>
> I need to provision wildcarded PSI, does clearwater support to do that?
>
> If yes, could you provide an example?
>
>
>
> Thanks
>
>
>
> Anthony
>
>
>
>
>
>
>
> ___
> Clearwater mailing list
> Clearwater@lists.projectclearwater.org
> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.
> projectclearwater.org
>
>
___
Clearwater mailing list
Clearwater@lists.projectclearwater.org
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Re: [Project Clearwater] Failed to register to client (Zoiper5 and XLite)

2018-03-13 Thread Bennett Allen

Hi Pushpendra,
Firstly I have CC’d this onto the clearwater mailing list and please send all 
replies via this as otherwise your emails may not be seen by my colleagues or 
me!
In answer to your questions I don’t think what the ns value is matters so what 
you’ve got should be fine, and the second value using your bind IP looks good. 
It also doesn’t look like the DNS server/queries is the problem in your 
situation, as homestead is trying to contact the vellum node and failing there.
If you have a look at the logs on the vellum node for Cassandra, Astaire and 
Rogers, these are at /var/log/Cassandra/, /var/log/Astaire and /var/log/rogers. 
This should give a clue as to what is happening, as based on the monit.log they 
don’t look like they’re working properly.
Let us know how it goes,
Ben


From: Pushpendra [mailto:pushpendra16mn...@gmail.com]
Sent: 09 March 2018 11:06
To: Bennett Allen 
Subject: Failed to register to client (Zoiper5 and XLite)

Hi Ben,
I am able to login and create private identity on ellis, but when I am trying 
to register these identity on client app (zoiper5 an XLite), its not 
registered. Its in an endless loop. I am using  as domain while 
registering to client. Please find the log detail below:
Please let me what is wrong and how can I fix, thanks in advance ☺

[vellum]ubuntu@vellum:/var/log$ tail -40 monit.log
[IST Mar  7 23:54:05] error: 'cassandra_process' process is not running
[IST Mar  7 23:54:05] info : 'cassandra_process' trying to restart
[IST Mar  7 23:54:05] info : 'cassandra_process' restart: /bin/bash
[IST Mar  7 23:54:06] info : 'cassandra_process' process is running with 
pid 31746
[IST Mar  7 23:54:06] error: 'cassandra_uptime' 
'/usr/share/clearwater/infrastructure/monit_uptime/check-cassandra-uptime' 
failed with exit status (1) -- no output
[IST Mar  7 23:54:06] error: 'astaire_uptime' 
'/usr/share/clearwater/infrastructure/monit_uptime/check-astaire-uptime' failed 
with exit status (1) -- no output
[IST Mar  7 23:54:16] error: 'rogers_process' process is not running
[IST Mar  7 23:54:16] info : 'rogers_process' trying to restart
[IST Mar  7 23:54:16] info : 'rogers_process' restart: /bin/bash
[IST Mar  7 23:54:16] info : 'rogers_process' process is running with pid 
31827
[IST Mar  7 23:54:16] error: 'clearwater_cluster_manager_process' process 
is not running
[IST Mar  7 23:54:16] info : 'clearwater_cluster_manager_process' trying to 
restart
[IST Mar  7 23:54:16] info : 'clearwater_cluster_manager_process' restart: 
/bin/bash
[IST Mar  7 23:54:17] error: 'cassandra_process' process is not running
[IST Mar  7 23:54:17] info : 'cassandra_process' trying to restart
[IST Mar  7 23:54:17] info : 'cassandra_process' restart: /bin/bash
[IST Mar  7 23:54:17] info : 'cassandra_process' process is running with 
pid 32022
[IST Mar  7 23:54:17] error: 'cassandra_uptime' 
'/usr/share/clearwater/infrastructure/monit_uptime/check-cassandra-uptime' 
failed with exit status (1) -- no output
[IST Mar  7 23:54:17] error: 'astaire_uptime' 
'/usr/share/clearwater/infrastructure/monit_uptime/check-astaire-uptime' failed 
with exit status (1) -- no output
[IST Mar  7 23:54:27] error: 'rogers_uptime' 
'/usr/share/clearwater/infrastructure/monit_uptime/check-rogers-uptime' failed 
with exit status (1) -- no output
[IST Mar  7 23:54:27] info : 'clearwater_cluster_manager_process' process 
is running with pid 31936
[IST Mar  7 23:54:27] error: 'cassandra_process' process is not running
[IST Mar  7 23:54:27] info : 'cassandra_process' trying to restart
[IST Mar  7 23:54:27] info : 'cassandra_process' restart: /bin/bash
[IST Mar  7 23:54:28] info : 'cassandra_process' process is running with 
pid 32610
[IST Mar  7 23:54:28] error: 'cassandra_uptime' 
'/usr/share/clearwater/infrastructure/monit_uptime/check-cassandra-uptime' 
failed with exit status (1) -- no output
[IST Mar  7 23:54:28] error: 'astaire_uptime' 
'/usr/share/clearwater/infrastructure/monit_uptime/check-astaire-uptime' failed 
with exit status (1) -- no output
[IST Mar  7 23:54:38] error: 'rogers_uptime' 
'/usr/share/clearwater/infrastructure/monit_uptime/check-rogers-uptime' failed 
with exit status (1) -- no output
[IST Mar  7 23:54:38] error: 'cassandra_uptime' 
'/usr/share/clearwater/infrastructure/monit_uptime/check-cassandra-uptime' 
failed with exit status (1) -- no output
[IST Mar  7 23:54:39] info : 'astaire_uptime' status succeeded [status=0] 
-- zmq_msg_recv: Resource temporarily unavailable
[IST Mar  7 23:54:46] info : Awakened by the SIGHUP signal
Reinitializing Monit - Control file '/etc/monit/monitrc'
[IST Mar  7 23:54:47] info : 'node-vellum' Monit reloaded
[IST Mar  7 23:54:47] error: Cannot create socket to [localhost]:2812 -- 
Connection refused
[IST Mar  7 23:54:57] info : Awakened by the SIGHUP signal
Reinitializing Monit - Control file

Re: [Project Clearwater] Does Clearwater support to provision wildcarded PSI?

2018-03-13 Thread Bennett Allen

Hi Anthony,
From the logs you have sent I see that you are using homestead-prov, we only 
support wildcarded entries with a HSS, which would explain the issues you are 
hitting. Here is a link to the docs about a HSS - 
http://clearwater.readthedocs.io/en/stable/External_HSS_Integration.html .
Let us know how it goes,
Ben

From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On 
Behalf Of Anthony Lee
Sent: 10 March 2018 20:02
To: clearwater@lists.projectclearwater.org
Subject: Re: [Project Clearwater] Does Clearwater support to provision 
wildcarded PSI?

Now I added P-Profile-Key header into the request, the header value is my 
wildcard PSI uri( 
sip:.+@list-service.example.com ).

Homestead  log:
10-03-2018 19:39:50.073 UTC [7f22987f8700] Debug http_handlers.cpp:619: 
Determining request type from '{"reqtype": "call", "server_name": 
"sip:scscf.192.168.1.10:5054;transport=TCP", "wildcard_identity": 
"sip:.+@list-service.example.com"}'

10-03-2018 19:39:50.074 UTC [7f22c4fb1700] Debug memcached_cache.cpp:27: 
Pausing stopwatch due to Memcached GET fetch result for 
impu\\sip:.+@list-service.example.com
10-03-2018 19:39:50.075 UTC [7f22c4fb1700] Debug memcached_cache.cpp:33: 
Resuming stopwatch due to Memcached GET fetch result for 
impu\\sip:.+@list-service.example.com

10-03-2018 19:39:50.075 UTC [7f22c4fb1700] Debug memcachedstore.cpp:414: Key 
not found

10-03-2018 19:39:50.075 UTC [7f229affd700] Debug hsprov_store.cpp:78: Issuing 
get for key 
sip:7gbcen27b7lqvh3noa3nt8nftc7gbcen27b7lqvh3noa3nt8n...@list-service.example.com

10-03-2018 19:39:50.078 UTC [7f229affd700] Debug cassandra_store.cpp:536: 
Cassandra request failed: rc=2, Row 
sip:7gbcen27b7lqvh3noa3nt8nftc7gbcen27b7lqvh3noa3nt8n...@list-service.example.com
 not present in column_family impu

Looks like Homestead uses P-Profile-Key's value to search in cache but uses 
R-URI to search in database.

Is it expected behavior?

On Sat, Mar 10, 2018 at 10:48 AM, Anthony Lee 
> wrote:
Sorry, forgot to mention that  Sprout's log  shows that 404 not found for that 
wildcard PSI return from Homestead. .

On Sat, Mar 10, 2018 at 10:44 AM, Anthony Lee 
> wrote:
My wildcard PSI is  
sip:.+@list-service.example.com

I found some information in Homestead_current.txt:

Debug http_handlers.cpp:695: Did not receive valid JSON with a 
'wildcard_identity' element

Does it mean scscf need to add "wildcard_identity" into the JSON request?
Is there any configuration need to be done in Sprout?

On Fri, Mar 9, 2018 at 10:54 PM, Anthony Lee 
> wrote:
I need to provision wildcarded PSI, does clearwater support to do that?
If yes, could you provide an example?

Thanks

Anthony

___
Clearwater mailing list
Clearwater@lists.projectclearwater.org
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Re: [Project Clearwater] SIP registeration cw-aio virtualbox

2018-03-13 Thread jaber daneshamooz

Hi. tanx for your help. I could overcome the problem by changing the
advanced setting of client application(zoiper)




-- 
* Jaber Daneshamooz  *
___
Clearwater mailing list
Clearwater@lists.projectclearwater.org
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Re: [Project Clearwater] Does Clearwater support to provision wildcarded PSI?

Re: [Project Clearwater] Failed to register to client (Zoiper5 and XLite)

Re: [Project Clearwater] Does Clearwater support to provision wildcarded PSI?

Re: [Project Clearwater] SIP registeration cw-aio virtualbox

4 matches

Site Navigation

Mail list logo

Footer information