Hi Schahzad,

Thanks for raising this.

The call is being rejected as the request URI in your INVITE is 
“sip:[email protected]<mailto:sip%[email protected]>”. The 
domain of this URI is your IBCF node, but the domain in the request URI should 
always be the subscriber’s domain. Previously, Bono (or the IBCF) changed the 
domain of the request URI to the home domain if it was routing upstream, but 
this was removed in the ‘CounterStrike’ release.

In the latest release ‘Doom’ (please see the attached release notes) this 
function is enhanced, so that the domain is rewritten again, but only when the 
request is coming from a SIP trunk and the domain in the request URI matches 
the local address of the IBCF. Can you upgrade to this release and retest?

Ellie

From: [email protected] 
[mailto:[email protected]] On Behalf Of Schahzad 
Zafar
Sent: 14 April 2014 14:07
To: Matt Williams
Cc: [email protected]
Subject: Re: [Clearwater] Sip truking

Hi Matt,

Here is an interesting Case,

Previously i was having issue from inside to outside call problem , but i just 
upgraded the clearwater IMS via command apt-get upgrade and after that, my 
outgoing calls are fine but my incoming calls started to had issue.



i am calling from 03219001131 which is my GSM mobile number to my Sip client


03219001131 GSM trunk ---> Asterisk ---> IBCF--->sprout -bono --> sip number 
0305073908X
Asterisk = 192.168.31.24

192.168.31.24 is added in trusted Peer list in user_setting file at ibcf

ibcf=192.168.9.94
sprout=192.168.9.97

on IBCF i see

14-04-2014 12:3ener6:27.647 Debug stateful_proxy.cpp:685: Request received on 
non-trusted port 5060
14-04-2014 12:36:27.647 Debug stateful_proxy.cpp:875: Perform access proxy 
routing for INVITE request
14-04-2014 12:36:27.647 Debug stateful_proxy.cpp:990: Message received on 
non-trusted port 5060
14-04-2014 12:36:27.647 Debug flowtable.cpp:137: Find flow for transport 
udp0x8dc840 (1), remote address 192.168.9.97:5054<http://192.168.9.97:5054>
14-04-2014 12:36:27.647 Warning stateful_proxy.cpp:1181: Rejecting request from 
untrusted source

Details sequence logs are below,  What i dont understand, the request is 
generated by IBCF to Sprout why its saying understated source,



this is my config file at ibcf

# Deployment definitions
home_domain=ef.net<http://ef.net>
sprout_hostname=sprout.ef.net<http://sprout.ef.net>
chronos_hostname=localhost:7253
hs_hostname=192.168.9.99:8888<http://192.168.9.99:8888>
hs_provisioning_hostname=192.168.9.99:8889<http://192.168.9.99:8889>
xdms_hostname=192.168.9.98:7888<http://192.168.9.98:7888>

# Local IP configuration
local_ip=192.168.9.94
public_ip=192.168.9.94
public_hostname=ibcf

this is my config file at sprout




Record-Route: <sip:192.168.9.94:5058;transport=TCP;lr>
Record-Route: <sip:ibcf:5060;transport=UDP;lr>
Via: SIP/2.0/UDP 
192.168.9.97:5054;rport;branch=z9hG4bKPjXkQkx3b7bDUC.OnDJcyAiyX2UZ9e2ouz
Via: SIP/2.0/TCP 
192.168.9.94:46178;rport=46178;received=192.168.9.94;branch=z9hG4bKPjPqt3n8p2Bq3-uxa2cvKDEmehI1JbICRt
Via: SIP/2.0/UDP 
192.168.31.24:5060;rport=5060;received=192.168.31.24;branch=z9hG4bK4184bb1d
Max-Forwards: 68
From: "03219001131" 
<sip:[email protected]<mailto:sip%[email protected]>>;tag=as2c65e1aa
To: <sip:[email protected]<mailto:sip%[email protected]>>
Contact: 
<sip:[email protected]:5060<http://sip:[email protected]:5060>>
Call-ID: 
[email protected]:5060<http://[email protected]:5060>
CSeq: 102 INVITE
User-Agent: Asterisk PBX 1.8.14.0
Date: Mon, 14 Apr 2014 12:36:27 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, 
PUBLISH
Supported: replaces, timer
Session-Expires: 600
Content-Type: application/sdp
Content-Length:   239

v=0
o=root 1988013493 1988013493 IN IP4 192.168.31.24
s=Asterisk PBX 1.8.14.0
c=IN IP4 192.168.31.24
t=0 0
m=audio 11814 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

--end msg--
14-04-2014 12:36:27.646 Debug stack.cpp:410: Queuing cloned received message 
0x7fe34c021088 for worker threads
14-04-2014 12:36:27.646 Debug stack.cpp:188: Worker thread dequeue message 
0x7fe34c021088
14-04-2014 12:36:27.646 Debug pjsip: sip_endpoint.c Distributing rdata to 
modules: Request msg INVITE/cseq=102 (rdata0x7fe34c021088)
14-04-2014 12:36:27.647 Debug stateful_proxy.cpp:241: Proxy RX request
14-04-2014 12:36:27.647 Debug stateful_proxy.cpp:685: Request received on 
non-trusted port 5060
14-04-2014 12:36:27.647 Debug stateful_proxy.cpp:875: Perform access proxy 
routing for INVITE request
14-04-2014 12:36:27.647 Debug stateful_proxy.cpp:990: Message received on 
non-trusted port 5060
14-04-2014 12:36:27.647 Debug flowtable.cpp:137: Find flow for transport 
udp0x8dc840 (1), remote address 192.168.9.97:5054<http://192.168.9.97:5054>
14-04-2014 12:36:27.647 Warning stateful_proxy.cpp:1181: Rejecting request from 
untrusted source
14-04-2014 12:36:27.647 Debug pjsip:       endpoint Response msg 
403/INVITE/cseq=102 (tdta0x7fe344010760) created
14-04-2014 12:36:27.647 Verbose stack.cpp:241: TX 768 bytes Response msg 
403/INVITE/cseq=102 (tdta0x7fe344010760) to UDP 
192.168.9.97:5054<http://192.168.9.97:5054>:
--start msg--

SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 
192.168.9.97:5054;rport=5054;received=192.168.9.97;branch=z9hG4bKPjXkQkx3b7bDUC.OnDJcyAiyX2UZ9e2ouz
Via: SIP/2.0/TCP 
192.168.9.94:46178;rport=46178;received=192.168.9.94;branch=z9hG4bKPjPqt3n8p2Bq3-uxa2cvKDEmehI1JbICRt
Via: SIP/2.0/UDP 
192.168.31.24:5060;rport=5060;received=192.168.31.24;branch=z9hG4bK4184bb1d
Record-Route: <sip:sprout.ef.net:5054;transport=TCP;lr>
Record-Route: <sip:192.168.9.94:5058;transport=TCP;lr>
Record-Route: <sip:ibcf:5060;transport=UDP;lr>
Call-ID: 
[email protected]:5060<http://[email protected]:5060>
From: "03219001131" 
<sip:[email protected]<mailto:sip%[email protected]>>;tag=as2c65e1aa
To: 
<sip:[email protected]<mailto:sip%[email protected]>>;tag=z9hG4bKPjXkQkx3b7bDUC.OnDJcyAiyX2UZ9e2ouz
CSeq: 102 INVITE
Content-Length:  0

These are sprout logs



SIP/2.0 100 Trying
Via: SIP/2.0/TCP 
192.168.9.94:40071;rport=40071;received=192.168.9.94;branch=z9hG4bKPjH9srWNA1cAEfGfVeWzDnJLX9jvpbBRwA
Via: SIP/2.0/UDP 
192.168.31.26:5060;rport=5060;received=192.168.31.26;branch=z9hG4bK2e4ef902
Record-Route: <sip:192.168.9.94:5058;transport=TCP;lr>
Record-Route: <sip:ibcf:5060;transport=UDP;lr>
Call-ID: 
[email protected]:5060<http://[email protected]:5060>
From: "03219001131" 
<sip:[email protected]<mailto:sip%[email protected]>>;tag=as3ed0d0b6
To: <sip:[email protected]<mailto:sip%[email protected]>>
CSeq: 102 INVITE
Content-Length:  0


--end msg--
14-04-2014 13:01:14.587 Debug pjsip: tsx0x7f4734229 State changed from Trying 
to Proceeding, event=TX_MSG
14-04-2014 13:01:14.588 Debug stateful_proxy.cpp:345: tsx0x7f4734229918 - 
tu_on_tsx_state UAS, TSX_STATE TX_MSG state=Proceeding
14-04-2014 13:01:14.588 Debug pjutils.cpp:565: Added Record-Route header, URI = 
sip:sprout.ef.net:5054;transport=TCP;lr
14-04-2014 13:01:14.588 Debug stateful_proxy.cpp:2212: Single Record-Route for 
the BGCF case
14-04-2014 13:01:14.588 Info stateful_proxy.cpp:1492: Route request to domain 
192.168.9.94
14-04-2014 13:01:14.588 Debug bgcfservice.cpp:132: Getting route for URI domain 
192.168.9.94 via BGCF lookup
14-04-2014 13:01:14.588 Debug stateful_proxy.cpp:3037: Allocating transaction 
and data for target 0
14-04-2014 13:01:14.588 Debug pjsip: tsx0x7f4734232 Transaction created for 
Request msg INVITE/cseq=102 (tdta0x7f4734230ef0)
14-04-2014 13:01:14.588 Debug stateful_proxy.cpp:3057: Adding trail identifier 
228 to UAC transaction
14-04-2014 13:01:14.588 Debug stateful_proxy.cpp:3076: Updating request URI and 
route for target 0
14-04-2014 13:01:14.588 Debug stateful_proxy.cpp:3508: Resolve next hop 
destination
14-04-2014 13:01:14.588 Debug pjutils.cpp:489: Next hop node is encoded in 
Request-URI
14-04-2014 13:01:14.588 Debug sipresolver.cpp:84: SIPResolver::resolve for name 
192.168.9.94, port 0, transport -1, family 2
14-04-2014 13:01:14.589 Debug baseresolver.cpp:474: Attempt to parse 
192.168.9.94 as IP address
14-04-2014 13:01:14.589 Debug sipresolver.cpp:101: Target is an IP address - 
default port/transport if required
14-04-2014 13:01:14.589 Info pjutils.cpp:772: Resolved destination URI 
sip:[email protected]<mailto:sip%[email protected]> to 1 servers
14-04-2014 13:01:14.589 Debug pjsip: tsx0x7f4734232 Sending Request msg 
INVITE/cseq=102 (tdta0x7f4734230ef0) in state Null
14-04-2014 13:01:14.589 Debug pjsip:       endpoint Request msg INVITE/cseq=102 
(tdta0x7f4734230ef0): skipping target resolution because address is already set
14-04-2014 13:01:14.589 Verbose stack.cpp:241: TX 1260 bytes Request msg 
INVITE/cseq=102 (tdta0x7f4734230ef0) to UDP 
192.168.9.94:5060<http://192.168.9.94:5060>:
--start msg--

INVITE sip:[email protected]<mailto:sip%[email protected]> 
SIP/2.0
Record-Route: <sip:sprout.ef.net:5054;transport=TCP;lr>
Record-Route: <sip:192.168.9.94:5058;transport=TCP;lr>
Record-Route: <sip:ibcf:5060;transport=UDP;lr>
Via: SIP/2.0/UDP 
192.168.9.97:5054;rport;branch=z9hG4bKPjH4kJ5NIiCwBQCu5HcTIMaFejBvN0cDBn
Via: SIP/2.0/TCP 
192.168.9.94:40071;rport=40071;received=192.168.9.94;branch=z9hG4bKPjH9srWNA1cAEfGfVeWzDnJLX9jvpbBRwA
Via: SIP/2.0/UDP 
192.168.31.26:5060;rport=5060;received=192.168.31.26;branch=z9hG4bK2e4ef902
Max-Forwards: 68
From: "03219001131" 
<sip:[email protected]<mailto:sip%[email protected]>>;tag=as3ed0d0b6
To: <sip:[email protected]<mailto:sip%[email protected]>>
Contact: 
<sip:[email protected]:5060<http://sip:[email protected]:5060>>
Call-ID: 
[email protected]:5060<http://[email protected]:5060>
CSeq: 102 INVITE
User-Agent: Asterisk PBX 1.8.14.0
Date: Mon, 14 Apr 2014 13:01:14 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, 
PUBLISH
Supported: replaces, timer
Session-Expires: 600
Content-Type: application/sdp
Content-Length:   239

v=0
o=root 2059010150 2059010150 IN IP4 192.168.31.26
s=Asterisk PBX 1.8.14.0
c=IN IP4 192.168.31.26
t=0 0
m=audio 11116 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

--end msg--
14-04-2014 13:01:14.589 Debug pjsip: tsx0x7f4734232 State changed from Null to 
Calling, event=TX_MSG
14-04-2014 13:01:14.589 Debug stateful_proxy.cpp:345: tsx0x7f4734232f58 - 
tu_on_tsx_state UAC, TSX_STATE TX_MSG state=Calling
14-04-2014 13:01:14.589 Debug stateful_proxy.cpp:3646: tsx0x7f4734232f58 - 
uac_data = 0x7f4734227160, uas_data = 0x7f4734238060
14-04-2014 13:01:14.589 Debug stack.cpp:190: Worker thread completed processing 
message 0x7f47382ab908
14-04-2014 13:01:14.589 Debug stack.cpp:196: Request latency = 3883us
14-04-2014 13:01:14.606 Debug pjsip: sip_endpoint.c Processing incoming 
message: Response msg 403/INVITE/cseq=102 (rdata0xc56188)
14-04-2014 13:01:14.607 Verbose stack.cpp:225: RX 768 bytes Response msg 
403/INVITE/cseq=102 (rdata0xc56188) from UDP 
192.168.9.94:5060<http://192.168.9.94:5060>:

--start msg--

SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 
192.168.9.97:5054;rport=5054;received=192.168.9.97;branch=z9hG4bKPjH4kJ5NIiCwBQCu5HcTIMaFejBvN0cDBn
Via: SIP/2.0/TCP 
192.168.9.94:40071;rport=40071;received=192.168.9.94;branch=z9hG4bKPjH9srWNA1cAEfGfVeWzDnJLX9jvpbBRwA
Via: SIP/2.0/UDP 
192.168.31.26:5060;rport=5060;received=192.168.31.26;branch=z9hG4bK2e4ef902
Record-Route: <sip:sprout.ef.net:5054;transport=TCP;lr>
Record-Route: <sip:192.168.9.94:5058;transport=TCP;lr>
Record-Route: <sip:ibcf:5060;transport=UDP;lr>
Call-ID: 
[email protected]:5060<http://[email protected]:5060>
From: "03219001131" 
<sip:[email protected]<mailto:sip%[email protected]>>;tag=as3ed0d0b6
To: 
<sip:[email protected]<mailto:sip%[email protected]>>;tag=z9hG4bKPjH4kJ5NIiCwBQCu5HcTIMaFejBvN0cDBn
CSeq: 102 INVITE
Content-Length:  0


Thanks


On Mon, Apr 7, 2014 at 1:24 PM, Matt Williams 
<[email protected]<mailto:[email protected]>> wrote:
Schahzad,

Thanks for those logs.

I think the issue is that the IBCF node is not recognizing itself in the Route 
header (which reads "<sip:ibcf:5058;transport=TCP;lr>") and so it's doing what 
a proxy should, and forwarding on to "ibcf" - this turns out to be itself).

The solution is to tell the IBCF node that "ibcf" is (one of) its names.  The 
easiest way to do this is to set it in the public_hostname field in 
/etc/clearwater/config, i.e. "public_hostname=ibcf" - just on the IBCF node.  
Please can you try that, and let me know how you get on?

Incidentally, your top-level Clearwater domain should normally resolve to bono. 
 This allows clients to connect to the service (via bono) without needing any 
manual proxy configuration.  See 
https://github.com/Metaswitch/clearwater-docs/wiki/Clearwater-DNS-Usage for 
more information.   (Note that this shouldn't be causing any problems with your 
deployment - it might just make things simpler.)

Thanks,

Matt

From: Schahzad Zafar [mailto:[email protected]<mailto:[email protected]>]
Sent: 07 April 2014 08:34
To: Matt Williams; 
[email protected]<mailto:[email protected]>
Subject: Fwd: [Clearwater] Sip truking



Hi Matt,

Thanks for respose,
currently when i dial out from my local cleint connected to bono following is 
happening

my local number is 6505550045<tel:6505550045>
my outgoing number is 03219001131 ( on asterisk via sip trunk with ibcf)
my sip trunk ip is 192.168.31.34

ibcf -----192.168.31.34 trunk ----> asterisk
when i dial from sip client

03219001131 IBCF runs logs lot of logs like loop and sip client generate 
request timeout

when i dial [email protected]<mailto:[email protected]>

my remote sip client start ringing.

at sprout my eneum.json is

{
    "number_blocks" : [
                         {
                                "name" : "Clearwater external number 
03219001131",
                                "prefix" : "03219001131",
                                "regex" : 
"!(^.*$)!sip:\\[email protected]<mailto:[email protected]>!"
                        },


                        { "name" : "Clearwater internal numbers",
                          "prefix" : "650555",
                          "regex" : 
"!(^.*$)!sip:\\[email protected]<mailto:[email protected]>!"

                },

        {
            "name" : "Clearwater external number 0300",
            "prefix" : "0300",
            "regex" : "!(^.*$)!sip:\\[email protected]<mailto:[email protected]>!"
        },
        {
            "name" : "Clearwater external number 0321",
            "prefix" : "0321",
            "regex" : "!(^.*$)!sip:\\[email protected]<mailto:[email protected]>!"
        }

    ]
}


My bgcf.json at sprout is


{
    "routes" : [
                 { "name" : "outside net",
                   "domain" : "192.168.31.34",
                   "route"  : ["ibcf:5058"]
                 }
    ]
}




My IP Scheme

192.168.9.96 BONO
192.168.9.97 SPROUTE
192.168.9.94 IBCF
SIP trunk
192.168.31.34

my clearwater domain is ef.net<http://ef.net> ( not sure to which node 
ef.net<http://ef.net> should resolve so currently its pointing to sproute)



Please find attached IBCF call logs(tried to keep it a single call)

###############################################################################################
Best Regards
Schahzad

On Sat, Apr 5, 2014 at 3:58 AM, Matt Williams 
<[email protected]<mailto:[email protected]>> wrote:

No problem - thanks for signing up!

Matt
On 4 Apr 2014 23:07, Shahzad Zafar 
<[email protected]<mailto:[email protected]>> wrote:
Hi Matt
I have already sign up my qery main just send some minutes earlier i got 
confirmation mail from list admin sorry for that

Sent from my iPad

> On 05-Apr-2014, at 2:58 am, Matt Williams 
> <[email protected]<mailto:[email protected]>> wrote:
>
> Shazad,
>
> Please can you sign up to the mailing list at 
> http://lists.projectclearwater.org/listinfo/clearwater?  Then you're 
> guaranteed to see any responses people send, and you'll also be able to see 
> if anyone asks any other questions that are relevant to what you're doing.
>
> (I'll reply to your questions on the mailing list itself.)
>
> Thanks!
>
> Matt
>
> -----Original Message-----
> From: 
> [email protected]<mailto:[email protected]>
>  [mailto:[email protected]] On Behalf Of Shahzad 
> Zafar
> Sent: 04 April 2014 22:25
> To: 
> [email protected]<mailto:[email protected]>
> Subject: [Clearwater] Sip truking
>
> Hi every one
> I am trying to setup sip trunk to external network.
>
> I have set up bgcf.json and enum ( via fix enum.json file)is doing fine. I 
> can dial from my external network to my bone clients, call land on ibcf and 
> reaches fine to bone sip clients.
>
> But when itry to call from my sip client to external clients i saw different 
> errors
>
> My understanding is call flow is below
>
> Sip client --> bono --> sproute ( enum lookup only required here)-->ibcf 
> where trunk is confiugred and other end shows trunk is active and reachable 
> When sproute send call to ibcf , ibcf show error that call received from 
> sproute on port 5060 which is not a trust port and forbidden message is 
> generated.
>
> During playing i changed bgcf.json at sproute to have ibcf as ibcf:5058. 
> Assuming it ll be trust port then ibcf started to throw huge logs like some 
> loop is happening.
>
> During list search i found --trusted-port switch to bono at ibcf node i tried 
> to add port 5060 to trust port but ibcf dont start then.
>
> My config is simple
> I have 6550555* series at local net and 0234* numbers are at remote net via 
> sip trunk.
>
> Cann you please let me know config files of enum.json bgcf.json and what to 
> configure in ibcf.
>
> My user_setting at ibcf has one line of trusted peer = sip truk ip Best 
> regards
>
> Shahzad
> _______________________________________________
> Clearwater mailing list
> [email protected]<mailto:[email protected]>
> http://lists.projectclearwater.org/listinfo/clearwater



--
Best Regards
Schahzad Z. Choudhry
0092 - 321 -9001131<tel:321%20-9001131>

Never argue with an idiot, they will just drag you down to their level and beat 
you with experience.








--
Best Regards
Schahzad Z. Choudhry
0092 - 321 -9001131

Never argue with an idiot, they will just drag you down to their level and beat 
you with experience.

_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater

Reply via email to