Hi David, Could you try setting:
mmtel=5056 bgcf=5057 in /etc/clearwater/shared_config as well, and then running 'service sprout stop' to restart it and pick the change up? Because Linphone isn't going through Bono, it looks like the upstream_hostname setting isn't being used, so we're not getting the "scscf.sprout.witlab6" Route header we need to identify the S-CSCF. The config above should move the other applications (BGCF and MMTel AS) to other ports, so that we can say "this has come in on port 5054, it must be for the S-CSCF" and process the request correctly. Hope that helps, Rob -----Original Message----- From: David Salvador [mailto:[email protected]] Sent: 21 April 2016 11:12 To: Robert Day (projectclearwater.org) <[email protected]> Subject: Re: [Project Clearwater] CW-AIO IPv6 INVITE getting 403 Response Hi Rob, I've tried your advice: scscf_uri=sip:scscf.sprout.witlab6:5054 upstream_hostname=scscf.sprout.witlab6 upstream_port=5054 and add scscf.sprout.witlab6 to DNS (and disable ims.mnc874.mcc405.3gppnetwork.org from DNS) and got the 503. In summary: - if i have DNS zone ims.mnc874.mcc405.3gppnetwork.org i got 403 to Invites - If i Disable it i got 503. I've attached Sprout logs, as well as DNS configurations. Thanks again for all the support Best Regards, David Salvador On 20/04/2016, Robert Day (projectclearwater.org) <[email protected]> wrote: > Hi David, > > Can you try setting the following values? > > scscf_uri=sip:scscf.sprout.witlab6:5054 > upstream_hostname=scscf.sprout.witlab6 > upstream_port=5054 > > (You'll also need to set "scscf.sprout.witlab6" up in DNS or > /etc/hosts to point to the same IP address as "sprout.witlab6") > > I think currently Bono is just setting a Route header of > "sip:sprout.witlab6:5054" - without the "scscf." prefix, that might > not be specific enough to get the message processed correctly. I think > we've fixed this issue in the Charizard release (which we released > today), but the change above should get things working on an earlier release. > > Best, > Rob > > -----Original Message----- > From: David Salvador [mailto:[email protected]] > Sent: 20 April 2016 11:29 > To: Robert Day (projectclearwater.org) <[email protected]> > Subject: Re: [Project Clearwater] CW-AIO IPv6 INVITE getting 403 > Response > > Hi Robert, > > below is the /etc/clearwater/shared_config (home domain and > additional_home are different because we need to support both > domains): > > # Deployment definitions > home_domain=ims.mnc874.mcc405.3gppnetwork.org > additional_home_domains=ims.mnc864.mcc405.3gppnetwork.org > sprout_hostname=sprout.witlab6 > hs_hostname=homestead.witlab6:8888 > hs_provisioning_hostname=homestead.witlab6:8889 > ralf_hostname= > xdms_hostname=homer.witlab6:7888 > > scscf_uri=sip:sprout.witlab6:5054 > reg_max_expires=1800 > > # Email server configuration > smtp_smarthost=sprout.witlba6 > smtp_username=admin > smtp_password=wit$rjil > [email protected] > > #icscf=5052 > #upstream_hostname=icscf.sprout.witlab6 > #upstream_port=5052 > > # Keys > signup_key=secret > turn_workaround=secret > ellis_api_key=secret > ellis_cookie_key=secret > > #scscf_uri=sip:sprout.witlab6:5054;transport=TCP > > > Any Idea? > > Best Regards, > David Salvador > > On 19/04/2016, Robert Day (projectclearwater.org) > <[email protected]> wrote: >> Hi David, >> >> It looks like the Request-URI is "ims.mnc874.mcc405.3gppnetwork.org" >> but the Sprout hostname is "sprout.witlab6" - I'm wondering if the >> domains haven't been configured correctly, such that Sprout doesn't >> recognise "ims.mnc874.mcc405.3gppnetwork.org" as local. Could you >> post your /etc/clearwater/shared_config file? I think you'd need >> either `home_domain=ims.mnc874.mcc405.3gppnetwork.org` or >> `additional_home_domains=ims.mnc874.mcc405.3gppnetwork.org` set in >> there for this call to work. >> >> Best, >> Rob >> >> >> -----Original Message----- >> From: David Salvador [mailto:[email protected]] >> Sent: 19 April 2016 11:14 >> To: Robert Day (projectclearwater.org) <[email protected]> >> Subject: Re: [Project Clearwater] CW-AIO IPv6 INVITE getting 403 >> Response >> >> HI Robert, >> >> Thanks again for the help. >> >> I've tested Linphone on a CW IPv4 Environment that we have, and it >> works ok. >> >> I'll paste below Sprout logs, any help would be great. Thanks >> >> >> 19-04-2016 10:06:19.162 UTC Verbose sproutletproxy.cpp:1980: Routing >> Request msg INVITE/cseq=20 (tdta0x7ff1c8352fc0) (1318 bytes) to >> downstream sproutlet >> mmtel: >> --start msg-- >> >> INVITE sip:[email protected] SIP/2.0 >> Via: SIP/2.0/UDP >> [2520::b5f9:64af:2c31:d92e]:5065;rport=5065;received=2520::b5f9:64af: >> 2 >> c31:d92e;branch=z9hG4bK.T8BGMpm~8 >> From: >> <sip:[email protected]>;tag=8CwryLy0G >> To: <sip:[email protected]> >> CSeq: 20 INVITE >> Call-ID: qI2N1PvOWf >> Max-Forwards: 70 >> Route: <sip:sprout.witlab6:5054;lr;orig> >> Supported: outbound >> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, >> SUBSCRIBE, INFO, UPDATE >> Contact: >> <sip:+916505550705@[2520::b5f9:64af:2c31:d92e]:5065>;+sip.instance="<urn:uuid:686adf0e-c7f5-4d65-b862-d843b7921c1e>" >> User-Agent: Linphone/3.9.1 (belle-sip/1.4.2) >> Content-Type: application/sdp >> Content-Length: 555 >> >> v=0 >> o=+916505550705 2230 699 IN IP6 2520::b5f9:64af:2c31:d92e s=Talk c=IN >> IP6 2520::b5f9:64af:2c31:d92e >> t=0 0 >> a=rtcp-xr:rcvr-rtt=all:10000 stat-summary=loss,dup,jitt,TTL >> voip-metrics m=audio 7078 RTP/AVP 96 97 98 99 0 8 101 100 102 >> a=rtpmap:96 opus/48000/2 >> a=fmtp:96 useinbandfec=1 >> a=rtpmap:97 SILK/16000 >> a=rtpmap:98 speex/16000 >> a=fmtp:98 vbr=on >> a=rtpmap:99 speex/8000 >> a=fmtp:99 vbr=on >> a=rtpmap:101 telephone-event/48000 >> a=rtpmap:100 telephone-event/16000 >> a=rtpmap:102 telephone-event/8000 >> m=video 9078 RTP/AVP 96 >> a=rtpmap:96 VP8/90000 >> >> --end msg-- >> 19-04-2016 10:06:19.162 UTC Debug pjutils.cpp:691: Cloned >> tdta0x7ff1c8352fc0 to tdta0x7ff1c8309ed0 >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:1136: Remove top >> Route header Route: <sip:sprout.witlab6:5054;lr;orig> >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:1653: Adding >> message >> 0x7ff1c830a4e0 => txdata 0x7ff1c8309f78 mapping >> 19-04-2016 10:06:19.162 UTC Verbose sproutletproxy.cpp:1505: >> mmtel-0x7ff1c828fad0 pass initial request Request msg INVITE/cseq=20 >> (tdta0x7ff1c8309ed0) to Sproutlet >> 19-04-2016 10:06:19.162 UTC Debug sproutletappserver.cpp:71: Store >> onward route-set for request >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:1271: Sproutlet >> send_request 0x7ff1c830a4e0 >> 19-04-2016 10:06:19.162 UTC Verbose sproutletproxy.cpp:1307: >> mmtel-0x7ff1c828fad0 sending Request msg INVITE/cseq=20 >> (tdta0x7ff1c8309ed0) on fork 0 >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:1668: Processing >> actions from sproutlet - 0 responses, 1 requests, 0 timers >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:1708: Processing >> request 0x7ff1c8309f78, fork = 0 >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:1832: >> mmtel-0x7ff1c828fad0 transmitting request on fork 0 >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:1846: >> mmtel-0x7ff1c828fad0 store reference to non-ACK request Request msg >> INVITE/cseq=20 (tdta0x7ff1c8309ed0) on fork 0 >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:1660: Removing >> message >> 0x7ff1c830a4e0 => txdata 0x7ff1c8309f78 mapping >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:120: Find target >> Sproutlet for request >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:154: Found next >> routable URI: sip:[email protected] >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:270: Found user >> - >> +916505550539 >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:290: Possible >> service name - ims >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:296: Hostname - >> mnc874.mcc405.3gppnetwork.org >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:270: Found user >> - >> +916505550539 >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:290: Possible >> service name - ims >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:296: Hostname - >> mnc874.mcc405.3gppnetwork.org >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:270: Found user >> - >> +916505550539 >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:290: Possible >> service name - ims >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:296: Hostname - >> mnc874.mcc405.3gppnetwork.org >> 19-04-2016 10:06:19.162 UTC Debug sproutletproxy.cpp:795: No local >> sproutlet matches request >> 19-04-2016 10:06:19.162 UTC Debug pjsip: tsx0x7ff1c830b Transaction >> created for Request msg INVITE/cseq=20 (tdta0x7ff1c8309ed0) >> 19-04-2016 10:06:19.162 UTC Debug basicproxy.cpp:1618: Added trail >> identifier 91 to UAC transaction >> 19-04-2016 10:06:19.162 UTC Debug pjutils.cpp:490: Next hop node is >> encoded in Request-URI >> 19-04-2016 10:06:19.162 UTC Debug sipresolver.cpp:86: >> SIPResolver::resolve for name ims.mnc874.mcc405.3gppnetwork.org, port >> 0, transport -1, family 10 >> 19-04-2016 10:06:19.162 UTC Debug baseresolver.cpp:513: Attempt to >> parse ims.mnc874.mcc405.3gppnetwork.org as IP address >> 19-04-2016 10:06:19.162 UTC Debug sipresolver.cpp:145: Do NAPTR >> look-up for ims.mnc874.mcc405.3gppnetwork.org >> 19-04-2016 10:06:19.162 UTC Debug ttlcache.h:171: Found the entry in >> the cache >> 19-04-2016 10:06:19.162 UTC Debug sipresolver.cpp:194: NAPTR lookup >> failed, so do SRV lookups for UDP and TCP >> 19-04-2016 10:06:19.162 UTC Verbose dnscachedresolver.cpp:240: Check >> cache for _sip._udp.ims.mnc874.mcc405.3gppnetwork.org type 33 >> 19-04-2016 10:06:19.162 UTC Debug dnscachedresolver.cpp:255: Expired >> entry found in cache >> 19-04-2016 10:06:19.162 UTC Debug dnscachedresolver.cpp:282: Create >> and execute DNS query transaction >> 19-04-2016 10:06:19.162 UTC Verbose dnscachedresolver.cpp:240: Check >> cache for _sip._tcp.ims.mnc874.mcc405.3gppnetwork.org type 33 >> 19-04-2016 10:06:19.162 UTC Debug dnscachedresolver.cpp:255: Expired >> entry found in cache >> 19-04-2016 10:06:19.162 UTC Debug dnscachedresolver.cpp:282: Create >> and execute DNS query transaction >> 19-04-2016 10:06:19.162 UTC Debug dnscachedresolver.cpp:294: Wait for >> query responses >> 19-04-2016 10:06:19.725 UTC Debug dnscachedresolver.cpp:435: Received >> DNS response for _sip._udp.ims.mnc874.mcc405.3gppnetwork.org type SRV >> 19-04-2016 10:06:19.725 UTC Error dnscachedresolver.cpp:567: Failed >> to retrieve record for _sip._udp.ims.mnc874.mcc405.3gppnetwork.org: >> Timeout while contacting DNS servers >> 19-04-2016 10:06:19.725 UTC Debug dnscachedresolver.cpp:650: Adding >> _sip._udp.ims.mnc874.mcc405.3gppnetwork.org to cache expiry list with >> deletion time of 1461060709 >> 19-04-2016 10:06:19.725 UTC Debug dnscachedresolver.cpp:435: Received >> DNS response for _sip._tcp.ims.mnc874.mcc405.3gppnetwork.org type SRV >> 19-04-2016 10:06:19.725 UTC Error dnscachedresolver.cpp:567: Failed >> to retrieve record for _sip._tcp.ims.mnc874.mcc405.3gppnetwork.org: >> Timeout while contacting DNS servers >> 19-04-2016 10:06:19.725 UTC Debug dnscachedresolver.cpp:650: Adding >> _sip._tcp.ims.mnc874.mcc405.3gppnetwork.org to cache expiry list with >> deletion time of 1461060709 >> 19-04-2016 10:06:19.725 UTC Debug dnscachedresolver.cpp:298: Received >> all query responses >> 19-04-2016 10:06:19.725 UTC Debug dnscachedresolver.cpp:326: Pulling >> 0 records from cache for _sip._udp.ims.mnc874.mcc405.3gppnetwork.org >> SRV >> 19-04-2016 10:06:19.725 UTC Debug dnscachedresolver.cpp:326: Pulling >> 0 records from cache for _sip._tcp.ims.mnc874.mcc405.3gppnetwork.org >> SRV >> 19-04-2016 10:06:19.725 UTC Debug sipresolver.cpp:210: UDP SRV record >> _sip._udp.ims.mnc874.mcc405.3gppnetwork.org returned 0 records >> 19-04-2016 10:06:19.725 UTC Debug sipresolver.cpp:213: TCP SRV record >> _sip._tcp.ims.mnc874.mcc405.3gppnetwork.org returned 0 records >> 19-04-2016 10:06:19.725 UTC Debug sipresolver.cpp:233: UDP and TCP >> SRV queries unsuccessful, default to UDP >> 19-04-2016 10:06:19.725 UTC Debug sipresolver.cpp:296: Perform A/AAAA >> record lookup only, name = ims.mnc874.mcc405.3gppnetwork.org >> 19-04-2016 10:06:19.725 UTC Verbose dnscachedresolver.cpp:240: Check >> cache for ims.mnc874.mcc405.3gppnetwork.org type 28 >> 19-04-2016 10:06:19.725 UTC Debug dnscachedresolver.cpp:255: Expired >> entry found in cache >> 19-04-2016 10:06:19.725 UTC Debug dnscachedresolver.cpp:282: Create >> and execute DNS query transaction >> 19-04-2016 10:06:19.725 UTC Debug dnscachedresolver.cpp:294: Wait for >> query responses >> 19-04-2016 10:06:20.663 UTC Debug dnscachedresolver.cpp:435: Received >> DNS response for ims.mnc874.mcc405.3gppnetwork.org type AAAA >> 19-04-2016 10:06:20.663 UTC Error dnscachedresolver.cpp:567: Failed >> to retrieve record for ims.mnc874.mcc405.3gppnetwork.org: Timeout >> while contacting DNS servers >> 19-04-2016 10:06:20.663 UTC Debug dnscachedresolver.cpp:650: Adding >> ims.mnc874.mcc405.3gppnetwork.org to cache expiry list with deletion >> time of >> 1461060710 >> 19-04-2016 10:06:20.663 UTC Debug dnscachedresolver.cpp:298: Received >> all query responses >> 19-04-2016 10:06:20.663 UTC Debug dnscachedresolver.cpp:326: Pulling >> 0 records from cache for ims.mnc874.mcc405.3gppnetwork.org AAAA >> 19-04-2016 10:06:20.663 UTC Debug baseresolver.cpp:361: Found 0 >> A/AAAA records, randomizing >> 19-04-2016 10:06:20.663 UTC Debug baseresolver.cpp:420: Adding 0 >> servers from blacklist >> 19-04-2016 10:06:20.663 UTC Info pjutils.cpp:938: Resolved >> destination URI sip:[email protected] >> to 0 servers >> 19-04-2016 10:06:20.663 UTC Debug pjutils.cpp:490: Next hop node is >> encoded in Request-URI >> 19-04-2016 10:06:20.663 UTC Debug basicproxy.cpp:1641: Next hop >> ims.mnc874.mcc405.3gppnetwork.org is not a stateless proxy >> 19-04-2016 10:06:20.663 UTC Debug basicproxy.cpp:1655: Sending >> request for sip:[email protected] >> 19-04-2016 10:06:20.663 UTC Debug basicproxy.cpp:1710: Failed to send >> request (70006 Not found (PJ_ENOTFOUND)) >> 19-04-2016 10:06:20.663 UTC Debug basicproxy.cpp:1408: Dissociate UAC >> transaction 0x7ff1c8057a10 for target 0 >> 19-04-2016 10:06:20.663 UTC Verbose sproutletproxy.cpp:637: Notifying >> upstream sproutlet mmtel of client failure: TRANSPORT_ERROR >> 19-04-2016 10:06:20.663 UTC Verbose sproutletproxy.cpp:1599: >> mmtel-0x7ff1c828fad0 received error TRANSPORT_ERROR on fork 0, state >> = Calling >> 19-04-2016 10:06:20.663 UTC Debug sproutletproxy.cpp:1653: Adding >> message >> 0x7ff1c830ccb0 => txdata 0x7ff1c830c748 mapping >> 19-04-2016 10:06:20.663 UTC Verbose sproutletproxy.cpp:1334: >> mmtel-0x7ff1c828fad0 sending Response msg 503/INVITE/cseq=20 >> (tdta0x7ff1c830c6a0) >> 19-04-2016 10:06:20.663 UTC Debug sproutletproxy.cpp:1668: Processing >> actions from sproutlet - 1 responses, 0 requests, 0 timers >> 19-04-2016 10:06:20.663 UTC Debug sproutletproxy.cpp:1754: >> Aggregating response with status code 503 >> 19-04-2016 10:06:20.663 UTC Debug sproutletproxy.cpp:1804: >> 3xx/4xx/5xx/6xx response >> 19-04-2016 10:06:20.663 UTC Debug sproutletproxy.cpp:1808: Best >> 3xx/4xx/5xx/6xx response so far >> 19-04-2016 10:06:20.663 UTC Debug sproutletproxy.cpp:1695: All UAC >> responded >> 19-04-2016 10:06:20.663 UTC Debug sproutletproxy.cpp:1660: Removing >> message >> 0x7ff1c830ccb0 => txdata 0x7ff1c830c748 mapping >> 19-04-2016 10:06:20.663 UTC Debug pjsip: tsx0x7ff1c8355 Sending >> Response msg >> 503/INVITE/cseq=20 (tdta0x7ff1c830c6a0) in state Proceeding >> 19-04-2016 10:06:20.663 UTC Debug pjsip: tdta0x7ff1c830 Destroying >> txdata Response msg 100/INVITE/cseq=20 (tdta0x7ff1c8306f70) >> 19-04-2016 10:06:20.663 UTC Verbose common_sip_processing.cpp:136: TX >> 371 bytes Response msg 503/INVITE/cseq=20 (tdta0x7ff1c830c6a0) to UDP >> 2520::b5f9:64af:2c31:d92e:5065: >> --start msg-- >> >> SIP/2.0 503 Service Unavailable >> Via: SIP/2.0/UDP >> [2520::b5f9:64af:2c31:d92e]:5065;rport=5065;received=2520::b5f9:64af: >> 2 >> c31:d92e;branch=z9hG4bK.T8BGMpm~8 >> Call-ID: qI2N1PvOWf >> From: >> <sip:[email protected]>;tag=8CwryLy0G >> To: >> <sip:[email protected]>;tag=z9hG4bK.T8B >> G >> Mpm~8 >> CSeq: 20 INVITE >> Content-Length: 0 >> >> >> --end msg-- >> 19-04-2016 10:06:20.664 UTC Debug pjsip: tsx0x7ff1c8355 State changed >> from Proceeding to Completed, event=TX_MSG >> 19-04-2016 10:06:20.664 UTC Debug basicproxy.cpp:213: >> tsx0x7ff1c8355028 - tu_on_tsx_state UAS, TSX_STATE TX_MSG >> state=Completed >> 19-04-2016 10:06:20.664 UTC Verbose sproutletproxy.cpp:1746: >> mmtel-0x7ff1c828fad0 suiciding >> 19-04-2016 10:06:20.664 UTC Debug sproutletproxy.cpp:1081: Destroying >> SproutletWrapper 0x7ff1c8180290 >> 19-04-2016 10:06:20.664 UTC Debug sproutletproxy.cpp:1090: Free >> original request Request msg INVITE/cseq=20 (tdta0x7ff1c8352fc0) >> (tdta0x7ff1c8352fc0) >> 19-04-2016 10:06:20.664 UTC Debug thread_dispatcher.cpp:193: Worker >> thread completed processing message 0x7ff1ec0dc9c8 >> 19-04-2016 10:06:20.664 UTC Debug thread_dispatcher.cpp:199: Request >> latency = 1502546us >> 19-04-2016 10:06:20.681 UTC Debug pjsip: sip_endpoint.c Processing >> incoming >> message: Request msg ACK/cseq=20 (rdata0x21d45e8) >> 19-04-2016 10:06:20.681 UTC Verbose common_sip_processing.cpp:120: RX >> 527 bytes Request msg ACK/cseq=20 (rdata0x21d45e8) from UDP >> 2520::b5f9:64af:2c31:d92e:5065: >> --start msg-- >> >> ACK sip:[email protected] SIP/2.0 >> Via: SIP/2.0/UDP >> [2520::b5f9:64af:2c31:d92e]:5065;branch=z9hG4bK.T8BGMpm~8;rport >> Call-ID: qI2N1PvOWf >> From: >> <sip:[email protected]>;tag=8CwryLy0G >> To: >> <sip:[email protected]>;tag=z9hG4bK.T8B >> G >> Mpm~8 >> Contact: >> <sip:+916505550705@[2520::b5f9:64af:2c31:d92e]:5065>;+sip.instance="<urn:uuid:686adf0e-c7f5-4d65-b862-d843b7921c1e>" >> Route: <sip:sprout.witlab6:5054;orig;lr> >> Max-Forwards: 70 >> CSeq: 20 ACK >> >> >> On 18/04/2016, Robert Day (projectclearwater.org) >> <[email protected]> wrote: >>> Hi David, >>> >>> Yes, that sounds like a client issue - I'd expect all requests to go >>> through the P-CSCF. I don't use Linphone, so I can't say whether >>> that's normal, but Blink and X-Lite work quite well for me when I >>> test with softphones - if you use one of those, you should have >>> better luck. >>> >>> If you continue to see 503 errors, feel free to send the Sprout logs >>> and I'll see if I can spot anything odd. >>> >>> Best, >>> Rob >>> >>> >>> -----Original Message----- >>> From: David Salvador [mailto:[email protected]] >>> Sent: 18 April 2016 16:10 >>> To: Robert Day (projectclearwater.org) <[email protected]> >>> Subject: Re: [Project Clearwater] CW-AIO IPv6 INVITE getting 403 >>> Response >>> >>> Hi Robert, >>> >>> Thanks for the response to both emails. >>> >>> The cassandra issue we found later that it was a missing symlik. the >>> cassandra.yaml was locate in /usr/share/... (can't remember the full >>> path), but was not located in /etc/cassandra/ >>> >>> Also, we've tried a new approach, that is to install CW manual >>> installation (several VMs). >>> In this approach we also found the cassandra.yaml issue, but that >>> was easily fixed with the above solution. >>> >>> Now we are facing a different issue, instead of 403, we are getting >>> 503 to Call Invite. We are using Linphone, and we still don't know >>> if it is a client issue, because it has a odd behaviour: >>> 1- Register goes through Bono >>> 2- Invite goes directly to Sprout. (I know that on 200 OK to >>> Register it's given a Service-Route, but still, client should always >>> forward SIP Requests through P-CSCF right?) >>> >>> Again, Thanks for the help. >>> >>> Best Regards, >>> David Salvador >>> >>> >>> >>> On 18/04/2016, Robert Day (projectclearwater.org) >>> <[email protected]> wrote: >>>> Hi David, >>>> >>>> Thanks for raising this! I've reopened >>>> https://github.com/Metaswitch/sprout/issues/1029 to cover the >>>> hostname problem, but your config change sounds good. >>>> >>>> On the Bono issue, it's difficult to debug the issue without full >>>> logs >>>> - for example, you have the log saying "Find flow for transport >>>> tcpsxxx (130), remote address [2520::d33:7c78:8ae1:a3c3]:49541", >>>> but I can't see whether it successfully finds that flow, or whether >>>> such a flow has ever been created. >>>> Could you get the full Bono log off the machine somehow (perhaps >>>> with a USB >>>> stick?) and send it? >>>> >>>> By the way, it sounds like you have got subscribers registering on >>>> the >>>> IPv6 node now - does this mean you've resolved the Cassandra issue >>>> from your previous email? >>>> >>>> Best, >>>> Rob >>>> >>>> >>>> -----Original Message----- >>>> From: Clearwater >>>> [mailto:[email protected]] On Behalf >>>> Of David Salvador >>>> Sent: 14 April 2016 16:59 >>>> To: [email protected] >>>> Subject: [Project Clearwater] CW-AIO IPv6 INVITE getting 403 >>>> Response >>>> >>>> Hi All, >>>> >>>> I'm trying to get the last version of OVF AIO working at IPv6, but >>>> i've faced a few issues: >>>> >>>> Sprout was unable to start the Registrar using the default configs, >>>> the workaround was to change the sprout_hostname at >>>> /etc/clearwater/shared_config to "cw-aio" and then add the >>>> "scscf.cw-aio" to /etc/hosts (to the ipv6 of the VM) >>>> >>>> At this point, clients are able to register but when i try to send >>>> an INVITE (also tried with MESSAGE) I get a 403 response. >>>> >>>> I've increased Bono log level and i can see the following (I'll >>>> copy only the relevant data because i don't have internet on the >>>> machine were I'm running tests): >>>> >>>> ... uri_classifier.cpp:197 Classified URI as 4 ... bono.cpp:279: >>>> Proxy RX request ... pjutils.cpp:674: Cloned Request msg >>>> INVITE/cseq=20 (...) to ... >>>> ... bono.cpp:803: Request received on non-trusted port 5060 ... >>>> bono.cpp:1043: Perform access proxy routing for INVITE request ... >>>> uri_classifier.cpp:197 Classified URI as 5 ... pjutils.cpp:509: >>>> Found Route header, URI = sip:scscf.cw-aio;transport=TCP;lr;orig >>>> ... bono.cpp:1180: Message Received on non-trusted port 5060 ... >>>> flowtable.cpp:136: Find flow for transport tcpsxxx (130), remote >>>> address >>>> [2520::d33:7c78:8ae1:a3c3]:49541 ... bono.cpp:1370: Rejecting >>>> request from untrusted source ... bono.cpp:757: Reject INVITE >>>> request with >>>> 403 status code >>>> >>>> Anyone has any ideas what is wrong ? >>>> >>>> Best Regards, >>>> David >>>> >>>> _______________________________________________ >>>> Clearwater mailing list >>>> [email protected] >>>> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists. >>>> p >>>> rojectclearwater.org >>>> >>> >> > _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
