| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index |
For the P-* headers, you can use ExtensionHeader. There is a small example of use in the class doc for SipMessage, and some test cases that use it in resip/stack/test (although most of these uses are not good real-world examples). For the Path header, something is very strange. Path headers are kinda like Record-Route; they are typically inserted by proxies, and always should point to the proxy that inserted it. The port in that Path header does not even match the port you're using for the REGISTER, so it seems doubly fishy to me. But, if this is just for testing/experimentation, an example can be found in repro/ResponseContext.cxx (look for "h_Paths"). For more info on this (in particular, what UAs need to do to support the Path header, and what proxies/registrars are supposed to do with it), go look at http://tools.ietf.org/html/rfc3327 .
Best regards,
Byron Campen
On 2/5/14 2:38 AM, Siva Kumar wrote:
Hi all,
I am getting 400 Bad request for register request sent to Server.
I found that I need to add following header fields while sending Register Message:
P-Access-Network-Info: 3GPP-UTRAN
P-Visited-Network-ID: vz.mavenir.lab
Please let me how to add these fields in the Register request.
Regards,Siva Kumar
_______________________________________________ resiprocate-users mailing list resiprocate-users@xxxxxxxxxxxxxxx List Archive: http://list.resiprocate.org/archive/resiprocate-users/