Thomas,

Thanks for these logs.

I think they show
- sprout receiving an INVITE from '0985 to '0793
- sprout applying originating processing based on '0985's IFCs and sending to 
the AS
- the AS returning the INVITE without the ODI token, but also without the orig 
parameter, so sprout switches to terminating processing (skipping any further 
ASes that might have been in the IFCs)
- sprout applying terminating processing based on '0793's IFCs and sending to 
the AS
- the AS again returning the INVITE without the ODI token.
We don't actually see a cycle in the logs, but you're right that we would cycle 
immediately after this as sprout would again apply terminating processing.

The key point here is that even though the AS is acting as a B2BUA, I think it 
still needs to copy the Route header from the INVITE it receives to the INVITE 
it sends back to the S-CSCF.

Is it possible to make your AS behave in this way? 

The only other way I'm aware of avoiding this cycle is for the IFCs to be 
configured to match on some criteria that the AS sets up on the terminating 
side, and not re-route to the AS on that basis.  I think using ODI tokens is 
the better solution, and I can't see a way that sprout on its own can resolve 
this cycle.

Please let me know how you get on.

Thanks,

Matt 

________________________________________
From: Thomas Titty [[email protected]]
Sent: 22 November 2013 19:16
To: Matt Williams
Cc: [email protected]
Subject: RE: SIP OPTIONS not forwarded at Bono

I see the ODI added to the route header by sprout.

In this case, the AS is acting as a B2BUA and has independent originating and 
terminating legs and hence do not carry the route header in the INVITE sent 
back to sprout.
So I made the AS send the INVITE to the trusted sprout port 5054.
But then, I guess sprout does the iFC match for the INVITE and send it back to 
AS and an INVITE loop follows.

I have given the sprout logs below.

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

Reply via email to