Well, there is documentation.
/Fredrik
Original message
From: Johan Vikman
Date:
To: Fredrik Thulin
Cc: yxa-devel@lists.su.se
Subject: Re: [Yxa-devel] Changing transport to TLS/TCP
Hi again,
How can I proxy the request to the PSAP? What do I need to return in the
Hi again,
How can I proxy the request to the PSAP? What do I need to return in the
request function?
/Johan
Ok, well - that's just not how SIP works. The response is sent using the
same transport as the request arrived on.
The UAS can send back a redirect to get the UAC to re-submit it's
re
> "JV" == Johan Vikman writes:
JV> That was my guess to, but the product owner wants the transport to change
in the 300 response.
You will need to use two 300 replies.
If LRF detects that the final leg will be a sips: uri and the incoming
invite is not onver TLS, it needs to send a 300 poi
On Mon, 2013-09-02 at 13:47 +0200, Johan Vikman wrote:
...
> >
> > So, really, I don't think the requirement is for the 300 response in
> > step 3 to be sent using TLS/TCP (SIP does not support upgrading from
> > TCP/UDP for the response, IIRC). I think the requirement is that the
> > E-CSCF uses
Hi Fredrik,
See my response below.
Thanks for your help!
BR,
Johan
On Sep 2, 2013, at 1:02 PM, Fredrik Thulin wrote:
> On Mon, 2013-09-02 at 12:26 +0200, Johan Vikman wrote:
>> Hi Fredrik,
>>
>> Of course, below I describe one way this could happen, the yxa stack is used
>> in the LRF node.
On Mon, 2013-09-02 at 12:26 +0200, Johan Vikman wrote:
> Hi Fredrik,
>
> Of course, below I describe one way this could happen, the yxa stack is used
> in the LRF node.
>
> UE E-CSCF
> LRF
Hi Fredrik,
Of course, below I describe one way this could happen, the yxa stack is used in
the LRF node.
UE E-CSCF
LRF PSAP
1 |--SIP INVITE TCP-->|
On Mon, 2013-09-02 at 11:20 +0200, Johan Vikman wrote:
> Hi,
>
> I am using the yxa stack to provide Geolocations over SIP.
>
> I now have gotten a requirement that says that if the Geolocation ultimately
> will be sent to a contact using sips, I need to respond to the request using
> TLS/TCP,