[sr-dev] scscf modifying contact:
jason.penton at gmail.com
Thu Feb 6 06:48:07 CET 2014
Can you be more specific about where in the specs you say contact should
not be modified. If current functionality is wrong I'm happy to change in
This email was sent using my phone. It may be brief, to the point, or
On 6 Feb 2014 00:16, "Daniel Ciprus" <daniel.ciprus at acision.com> wrote:
> Thanks for quick response. Yes, this is 3rd party registration.
> Unfortunately this (according to specs I listed below) shouldn't happen. Is
> there any workaround except messing around with textops and replacing
> things in Contact: ? I will need to add optional parameters from original
> REGISTER to 3rd party REGISTER, that's the goal.
> On 02/05/2014 02:16 PM, Camille Oudot wrote:
> Le Wed, 5 Feb 2014 12:13:17 -0500,
> Daniel Ciprus <daniel.ciprus at acision.com> <daniel.ciprus at acision.com> a écrit :
> For our application to work we'd like to see not modified Contact:
> from Kamailio being sent towards our AS. Unfortunately this is not
> happening now. Below are REGISTER messages from client and message
> which is sent to AS. I wasn't able to find any logic in .cfg file so
> I thought this would be the place where I should post my problem.
> According to 3GPP TS 24.229, RFC 3261, RFC 5626 it seems like this is
> not the behavior which should be happening.
> Hi Daniel,
> This looks like a third party register sent on the ISC interface.
> AFAIK, the behavior you are seeing is normal. The original REGISTER is
> not proxied: a new dialog between S-CSCF and AS is started instead (the
> S-CSCF becomes the UAC). The IMPU of the user that is triggering the
> third party register cans be seen in the To: header field, and the
> original Contact URI info is lost.
> *Daniel Ciprus*
> Integration engineer
> 9954 Mayland Dr
> Suite 3100
> Richmond, VA 23233
> T: +1 804 762 5601
> E: daniel.ciprus at acision.com
> This e-mail and any attachment is for authorised use by the intended
> recipient(s) only. It may contain proprietary material, confidential
> information and/or be subject to legal privilege. It should not be copied,
> disclosed to, retained or used by, any other party. If you are not an
> intended recipient then please promptly delete this e-mail and any
> attachment and all copies and inform the sender. Thank you for
> sr-dev mailing list
> sr-dev at lists.sip-router.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sr-dev