Astha,

Because I was cc'ed in your email asking the question about UDP support I 
mistakenly responded to you directly instead of the mailing list.  You can find 
my answer below which I'm posting on the mailing list to help anyone facing 
similar issues.

Andrew

-----Original Message-----
From: Andrew Edmonds 
Sent: Friday, May 19, 2017 9:56 AM
To: 'Astha Sharma' <astha.sha...@aricent.com>
Subject: RE: Clearwater Digest, Vol 49, Issue 8

Hi Astha,

Thank you for your question.

I can see from your shared config that the parameters in the angle brackets 
have not been filled in correctly, in scscf_uri "<sprout_hostname>" should be 
replaced by the hostname of the AIO node (which you should be able to find in 
/etc/hostname) likewise in scscf_node "<local_ip>" should be replaced with the 
IP address of your AIO node (which can be found by running the command 
ifconfig).

Once you have done this can you please reboot the node and try making the call 
again. Note that the call may not work, looking through you logs I can see:

12-05-2017 23:40:46.123 UTC Debug bono.cpp:2776: Adding a Route header to 
sip:scscf.cw-aio:5052;transport=TCP

which suggests that Bono is sending a message to Sprout over TCP. This may 
still be the case after you've changed the config. However we should be able to 
get more helpful diagnostics once you have the correct config in place.

Thanks,

Andrew

-----Original Message-----
From: Astha Sharma [mailto:astha.sha...@aricent.com] 
Sent: Monday, May 15, 2017 7:41 AM
To: clearwater@lists.projectclearwater.org
Cc: Andrew Edmonds <andrew.edmo...@metaswitch.com>
Subject: RE: Clearwater Digest, Vol 49, Issue 8

Hi Andrew,
Still UDP call is not working for AIO image.
Although I have executed following steps:
In /etc/clearwater/shared_config set or update the fields:

a.       
scscf_uri=sip:scscf.<sprout_hostname>;transport=udp<sip:scscf.%3csprout_hostname%3e;transport=udp>

b.      disable_tcp_switch=Y
In /etc/clearwater/local_config set or update the field on each of your Sprout 
nodes:

a.       
scscf_node_uri=sip:<local_ip>:5054;transport=udp<sip:%3clocal_ip%3e:5054;transport=udp>

sudo 
/usr/share/clearwater/clearwater-config-manager/scripts/upload_shared_config
Configuration file change: shared_config was modified by user root. Lines 
added: "disable_tcp_switch=Y", 
"scscf_uri="sip:scscf.<sprout_hostname>;transport=udp"".


But still in logs :
12-05-2017 23:40:46.117 UTC Debug baseresolver.cpp:425: Attempt to parse 
scscf.cw-aio as IP address
12-05-2017 23:40:46.117 UTC Debug sipresolver.cpp:128: Port is specified
12-05-2017 23:40:46.117 UTC Debug sipresolver.cpp:296: Perform A/AAAA record 
lookup only, name = scscf.cw-aio
12-05-2017 23:40:46.117 UTC Verbose dnscachedresolver.cpp:486: Check cache for 
scscf.cw-aio type 1
12-05-2017 23:40:46.117 UTC Debug dnscachedresolver.cpp:588: Pulling 1 records 
from cache for scscf.cw-aio A
12-05-2017 23:40:46.117 UTC Debug baseresolver.cpp:366: Found 1 A/AAAA records, 
creating iterator
12-05-2017 23:40:46.117 UTC Debug baseresolver.cpp:819: 11.0.1.223:5052 
transport 6 has state: BLACK
12-05-2017 23:40:46.117 UTC Debug baseresolver.cpp:819: 11.0.1.223:5052 
transport 6 has state: BLACK
12-05-2017 23:40:46.117 UTC Debug baseresolver.cpp:1032: Added an unhealthy 
server, now have 1 of 1
12-05-2017 23:40:46.117 UTC Debug sip_connection_pool.cpp:178: Successfully 
resolved scscf.cw-aio to IPv4 address
12-05-2017 23:40:46.117 UTC Verbose pjsip: tcpc0x7f4d6007 tcp->base.local_name: 
11.0.1.223
12-05-2017 23:40:46.117 UTC Verbose pjsip: tcpc0x7f4d6007 TCP client transport 
created
12-05-2017 23:40:46.117 UTC Verbose pjsip: tcpc0x7f4d6007 TCP transport 
11.0.1.223:5058 is connecting to 11.0.1.223:5052...
12-05-2017 23:40:46.117 UTC Debug sip_connection_pool.cpp:248: Created 
transport tcpc0x7f4d60075798 in slot 49 (11.0.1.223:5058 to 11.0.1.223:5052)
12-05-2017 23:40:46.121 UTC Error pjsip: tcpc0x7f4d6004 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.121 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d600488b8 in slot 0 has failed
12-05-2017 23:40:46.121 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.121 UTC Error pjsip: tcpc0x7f4d6003 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.121 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d600392a8 in slot 1 has failed
12-05-2017 23:40:46.121 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.121 UTC Error pjsip: tcpc0x7f4d6002 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.121 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d6002fd58 in slot 2 has failed
12-05-2017 23:40:46.121 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.121 UTC Error pjsip: tcpc0x7f4d6006 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.121 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d600604b8 in slot 8 has failed
12-05-2017 23:40:46.121 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.121 UTC Error pjsip: tcpc0x7f4d6004 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.121 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d60045648 in slot 9 has failed
12-05-2017 23:40:46.121 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.121 UTC Error pjsip: tcpc0x7f4d6004 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.121 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d60042628 in slot 10 has failed
12-05-2017 23:40:46.121 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.121 UTC Error pjsip: tcpc0x7f4d6002 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.121 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d600280e8 in slot 13 has failed
12-05-2017 23:40:46.121 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.121 UTC Error pjsip: tcpc0x7f4d6005 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.121 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d6005db78 in slot 17 has failed
12-05-2017 23:40:46.121 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.121 UTC Verbose pjsip: tcpc0x7f4d6004 TCP transport 
destroyed with reason 120111: Connection refused
12-05-2017 23:40:46.121 UTC Verbose pjsip: tcpc0x7f4d6005 TCP transport 
destroyed with reason 120111: Connection refused
12-05-2017 23:40:46.121 UTC Verbose pjsip: tcpc0x7f4d6004 TCP transport 
destroyed with reason 120111: Connection refused
12-05-2017 23:40:46.121 UTC Verbose pjsip: tcpc0x7f4d6002 TCP transport 
destroyed with reason 120111: Connection refused
12-05-2017 23:40:46.121 UTC Verbose pjsip: tcpc0x7f4d6003 TCP transport 
destroyed with reason 120111: Connection refused
12-05-2017 23:40:46.121 UTC Verbose pjsip: tcpc0x7f4d6004 TCP transport 
destroyed with reason 120111: Connection refused
12-05-2017 23:40:46.122 UTC Verbose pjsip: tcpc0x7f4d6002 TCP transport 
destroyed with reason 120111: Connection refused
12-05-2017 23:40:46.122 UTC Verbose pjsip: tcpc0x7f4d6006 TCP transport 
destroyed with reason 120111: Connection refused
12-05-2017 23:40:46.122 UTC Error pjsip: tcpc0x7f4d6002 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.122 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d60020de8 in slot 18 has failed
12-05-2017 23:40:46.122 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.122 UTC Error pjsip: tcpc0x7f4d6006 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.122 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d600634d8 in slot 19 has failed
12-05-2017 23:40:46.122 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.122 UTC Verbose pjsip: tcpc0x7f4d6002 TCP transport 
destroyed with reason 120111: Connection refused
12-05-2017 23:40:46.122 UTC Verbose pjsip: tcpc0x7f4d6006 TCP transport 
destroyed with reason 120111: Connection refused
12-05-2017 23:40:46.122 UTC Error pjsip: tcpc0x7f4d6005 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.122 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d60056d38 in slot 21 has failed
12-05-2017 23:40:46.122 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.122 UTC Error pjsip: tcpc0x7f4d6006 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.122 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d6006caa8 in slot 22 has failed
12-05-2017 23:40:46.122 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.122 UTC Error pjsip: tcpc0x7f4d6001 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.122 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d6001c5b8 in slot 26 has failed
12-05-2017 23:40:46.122 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.122 UTC Error pjsip: tcpc0x7f4d6001 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.122 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d6001ddc8 in slot 27 has failed
12-05-2017 23:40:46.122 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.122 UTC Error pjsip: tcpc0x7f4d6001 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.122 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d60014748 in slot 28 has failed
12-05-2017 23:40:46.122 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.122 UTC Error pjsip: tcpc0x7f4d6001 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.122 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d60015f58 in slot 29 has failed
12-05-2017 23:40:46.122 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.122 UTC Error pjsip: tcpc0x7f4d6005 TCP connect() error: 
Connection refused [code=120111]
12-05-2017 23:40:46.122 UTC Debug sip_connection_pool.cpp:360: Transport 
tcpc0x7f4d60059628 in slot 31 has failed
12-05-2017 23:40:46.122 UTC Debug baseresolver.cpp:400: Add 11.0.1.223:5052 
transport 6 to blacklist for 30 seconds, graylist for 0 seconds
12-05-2017 23:40:46.122 UTC Debug pjsip: sip_endpoint.c Processing incoming 
message: Request msg REGISTER/cseq=7 (rdata0x7f4d5c000cb0)
12-05-2017 23:40:46.122 UTC Verbose common_sip_processing.cpp:120: RX 506 bytes 
Request msg REGISTER/cseq=7 (rdata0x7f4d5c000cb0) from TCP 10.203.217.15:57576:
--start msg--

REGISTER sip:example.com;transport=TCP SIP/2.0
Via: SIP/2.0/TCP 10.203.217.15:62748;branch=z9hG4bK-524287-1---8f5dd1cf04a7f934
Max-Forwards: 70
Contact: 
<sip:6505550840@10.203.217.15:62748;rinstance=98099d7be5970add;transport=tcp>
To: <sip:6505550...@example.com;transport=TCP>
From: <sip:6505550...@example.com;transport=TCP>;tag=4a468a51
Call-ID: Nhmaxt514y1wyddenzzPWQ..
CSeq: 7 REGISTER
Expires: 3600
User-Agent: Z 3.15.40006 rv2.8.20
Allow-Events: presence, kpml, talk
Content-Length: 0


Please sugest how to proceed further.


I am also adding bono logs as an attachment.


Regards,
Astha
-----Original Message-----
From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On 
Behalf Of clearwater-requ...@lists.projectclearwater.org
Sent: Friday, May 12, 2017 2:34 PM
To: clearwater@lists.projectclearwater.org
Subject: Clearwater Digest, Vol 49, Issue 8

Send Clearwater mailing list submissions to 
clearwater@lists.projectclearwater.org

To subscribe or unsubscribe via the World Wide Web, visit 
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

or, via email, send a message with subject or body 'help' to 
clearwater-requ...@lists.projectclearwater.org

You can reach the person managing the list at 
clearwater-ow...@lists.projectclearwater.org

When replying, please edit your Subject line so it is more specific than "Re: 
Contents of Clearwater digest..."


Today's Topics:

   1. registration not working over UDP for AIO (Astha Sharma)
   2. Re: 403 forbidden on registering sip over UDP (Andrew Edmonds)


----------------------------------------------------------------------

Message: 1
Date: Fri, 12 May 2017 07:16:33 +0000
From: Astha Sharma <astha.sha...@aricent.com>
To: "clearwater@lists.projectclearwater.org"
<clearwater@lists.projectclearwater.org>
Subject: [Project Clearwater] registration not working over UDP for AIO
Message-ID:
<bmxpr01mb06798bf08b5361875b28ecc596...@bmxpr01mb0679.indprd01.prod.outlook.com>

Content-Type: text/plain; charset="us-ascii"

Hi,
While making call over UDP, Registration itself failing for AIO.
Please suggest detailed steps how to configure UDP so that sipp client or xlite 
or Zoiper will be able to register with CW IMS for AIO.


Regards,
Astha
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for 
the use of the individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for any purpose 
other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended 
recipient, you are notified that you are strictly prohibited from using, 
copying, altering, or disclosing the contents of this message. Aricent accepts 
no responsibility for loss or damage arising from the use of the information 
transmitted by this email including damage from virus."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.projectclearwater.org/pipermail/clearwater_lists.projectclearwater.org/attachments/20170512/3db20ec7/attachment-0001.html>

------------------------------

Message: 2
Date: Fri, 12 May 2017 09:03:00 +0000
From: Andrew Edmonds <andrew.edmo...@metaswitch.com>
To: Astha Sharma <astha.sha...@aricent.com>, 
"clearwater@lists.projectclearwater.org"
<clearwater@lists.projectclearwater.org>
Subject: Re: [Project Clearwater] 403 forbidden on registering sip over UDP
Message-ID:
<blupr02mb4377b4ab06098eafc6b698be5...@blupr02mb437.namprd02.prod.outlook.com>

Content-Type: text/plain; charset="us-ascii"

Hi Astha,

You are welcome for the response. In future could you please reply to the 
mailing list instead of replying to me directly, that way we might be able to 
help some people out in the future if they have a similar issue.

If the command cw-upload_shared_config is not working for you I think you must 
be using an old version of Project Clearwater that was released before we added 
shortened names for our deployment management scripts.

We have updated our documentation now but I believe one of the following 
commands should work on the older versions:


*         sudo 
/usr/share/clearwater/clearwater-config-manager/scripts/upload_shared_config

*         sudo /usr/bin/cw-upload_shared_config

If neither of the following work could you please let me know what version of 
Project Clearwater you are using by running the command "clearwater-version"

Thanks,

Andrew

From: Astha Sharma [mailto:astha.sha...@aricent.com]
Sent: Friday, May 12, 2017 9:50 AM
To: Andrew Edmonds <andrew.edmo...@metaswitch.com>
Subject: Re: 403 forbidden on registering sip over UDP


Hi Andrew,

Thanks for quick response.

I have followed following steps:
In /etc/clearwater/shared_config set or update the fields:

a.       
scscf_uri=sip:scscf.<sprout_hostname>;transport=udp<sip:scscf.%3csprout_hostname%3e;transport=udp>

b.      disable_tcp_switch=Y
In /etc/clearwater/local_config set or update the field on each of your Sprout 
nodes:

a.       
scscf_node_uri=sip:<local_ip>:5054;transport=udp<sip:%3clocal_ip%3e:5054;transport=udp>

and after that as per your suggestion, I tried to run the command "sudo 
cw-upload_shared_config"
But it is failing:
[cw-aio]root@cw-aio:/etc/clearwater# cw-upload_shared_config
cw-upload_shared_config: command not found


Regards,
Astha
________________________________
From: Andrew Edmonds 
<andrew.edmo...@metaswitch.com<mailto:andrew.edmo...@metaswitch.com>>
Sent: 12 May 2017 13:55:11
To: Astha Sharma
Subject: RE: 403 forbidden on registering sip over UDP

Hi Astha,

Thank you for your question about UDP support.

Project Clearwater does support using SIP-over-UDP. For details on how to 
configure your deployment to use UDP please follow the instructions 
here<http://clearwater.readthedocs.io/en/stable/Configuring_an_Application_Server.html#sip-over-udp-configuration>.

Once you have made these changes run the command "sudo cw-upload_shared_config" 
and try registering again. Let me know if this resolves your issue.

Thanks,

Andrew

From: Clearwater [mailto:mailman-boun...@host.metaswitch.com] On Behalf Of 
Astha Sharma
Sent: Monday, May 8, 2017 12:32 PM
To: 
clearwater-ow...@lists.projectclearwater.org<mailto:clearwater-ow...@lists.projectclearwater.org>
Subject: 403 forbidden on registering sip over UDP

Hi,
I am facing issue while registering xlite over UDP. I am working over all in 
one image of clear water ims.
All the nodes are running normally.
Receiving 403 forbidden from clearwater ims.

Please suggest how to make changes for udp in config files in all in one image 
clearwater ims.

Also please find herein pcap files of ims where I am sending register message 
having udp tramsport and getting 403 forbidden.


Regards,
Astha
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for 
the use of the individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for any purpose 
other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended 
recipient, you are notified that you are strictly prohibited from using, 
copying, altering, or disclosing the contents of this message. Aricent accepts 
no responsibility for loss or damage arising from the use of the information 
transmitted by this email including damage from virus."
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for 
the use of the individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for any purpose 
other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended 
recipient, you are notified that you are strictly prohibited from using, 
copying, altering, or disclosing the contents of this message. Aricent accepts 
no responsibility for loss or damage arising from the use of the information 
transmitted by this email including damage from virus."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.projectclearwater.org/pipermail/clearwater_lists.projectclearwater.org/attachments/20170512/ae1b53f4/attachment.html>

------------------------------

Subject: Digest Footer

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


------------------------------

End of Clearwater Digest, Vol 49, Issue 8
*****************************************
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for 
the use of the individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for any purpose 
other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended 
recipient, you are notified that you are strictly prohibited from using, 
copying, altering, or disclosing the contents of this message. Aricent accepts 
no responsibility for loss or damage arising from the use of the information 
transmitted by this email including damage from virus."

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

Reply via email to