<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
I have a 0.9.6 SER proxy running and one particular UA that is creating some problems with a RECORD-ROUTE header I am not handling correctly. Here is how I have my record_route configured (XXXs are replaced by my actual proxy IP):<br><br>if (!(uri=~^"sip:XXX.XXX.XXX.XXX"))<br> {<br> record_route_preset("XXX.XXX.XXX.XXX:5060;nat=yes");<br> };<br><br>When inbound traffic arrives for this particular UA, the INVITE is passed along. when the 200 OK comes back, there is a Record-Route header that looks like this (YYYs are replaced with the UA's public IP):<br><br>RECORD-ROUTE: <sip:YYY.YYY.YYY.YYY:5060;lr;transport=udp><br><br>Instead of adding a new Record-Route header with my IP before this one, the message is simply proxied back to the call origination. The ACK is then sent DIRECTLY to the UA, bipassing my proxy...as well as the BYE/200 OK that terminates the call....thus rendering my stateful proxy as stateless.<br><br>Can I remove the RECORD-ROUTE that my terminating UA is attaching? If not, why am I not adding my own Record-Route header like normal?<br><br>What am I missing?<br><br>Thanks,<br>Steve<br><br /><hr />Windows Live™ Groups: Create an online spot for your favorite groups to meet. <a href='http://windowslive.com/online/groups?ocid=TXT_TAGLM_WL_groups_032009' target='_new'>Check it out.</a></body>
</html>