Hi,

I have a question about the Request URI in Subscribe messages.

We are trying to get working subscribe and notify to get presence service
after the introduction of SBC/P-CSCF.



To have it working we needed to enabled elaboration by SBC of the SIP
Request URI.

The request URI arrives to Sprout in the following form:

[email protected]

and not:

[email protected]



The producer of the SBC said that this behaviour is completely normal since
the SBC is replacing the URI with the value in the retrieved service route
header (i.e. sprout since S-CSCF).



Sprout does the passages S-I-S CSCF but interrogating the HSS the answer is
not found (because the number domain is not the same).



I am getting confused about this, in my opinion the logical elaboration
should be to put the domain in the R-URI and not sprout but apparently they
disagree.

Maybe an interrogation to the ENUM (returning for our range of numbers
@ims.prod.lan) should be performed?



I thank you in advance for any help you may provide,



Best regards,


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

Reply via email to