Samuel,<br>
<br>
Probably the easiest way to prevent the extra call to use_media_proxy() is to do something like this<br>
<br>
if (!isflagset(22)) {<br>
setflag(22);<br>
use_media_proxy();<br>
}<br><br>
Regrads,<br>
Paul<br>
<br><div><span class="gmail_quote">On 6/26/05, <b class="gmail_sendername"><a href="mailto:smy@addm.com">smy@addm.com</a></b> <<a href="mailto:smy@addm.com">smy@addm.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thank-you all for the tips.... I was out of town for a meeting, that's why I<br>couldn't reply any sooner. I will give it a shot and let you all know how it<br>goes. Paul, as for the corrupt c= field, what can I do or go around
<br>it?!? Again, my setup is based on the <a href="http://ONSIP.org">ONSIP.org</a> document which calls<br>use_media_session(). If this is the case, what can I do or what should I pay<br>attention to??<br><br>Thank-you all for your input.... If this works, I think I'm gonna start up a
<br>HOW-TO document for Cisco 3600 and SER, and hope that all your contributions<br>would be helpful for both me and everyone else dealing with Cisco 3600<br>and SER.<br><br>Cheers!<br><br>Best Regards,<br>Samuel Yeung<br>
<br><br><br><br>Quoting Java Rockx <<a href="mailto:javarockx@gmail.com">javarockx@gmail.com</a>>:<br><br>> Smy,<br>><br>> One thing to keep in mind when dealing with Cisco 3600 routers (and others<br>> with ALG functionality) is that if you are using mediaproxy or rtpproxy and
<br>> accidentially call use_media_session() or force_rtp_session() more than once<br>> when dealing with NATed clients, that SER will corrupt the c= field in the<br>> SDP payload and the Cisco 3600 will refuse to pass that message -- we can
<br>> call this a "feature" :-)<br>><br>> Regards,<br>> Paul<br>><br>> On 6/24/05, Greger V. Teigre <<a href="mailto:greger@teigre.com">greger@teigre.com</a>> wrote:<br>>><br>>> Looks like the cisco box never receives the trying...
<br>>> U SER-ip:5080 -> cisco-ip:5060<br>>><br>>> If Cisco listens to port 5080 and not 5060, it's obvious... However, the<br>>> box announces 5060 in:<br>>> Via: SIP/2.0/UDP cisco-ip:5060
<br>>><br>>> So, you need to change the cisco's announced port. Should be some<br>>> parameter<br>>> somewhere...<br>>> g-)<br>>><br>>> <a href="mailto:smy@addm.com">smy@addm.com</a>
wrote:<br>>> > Hi all,<br>>> ><br>>> > I'm currently working with a cisco3600 with SER 0.9.2. Thanks to<br>>> > <a href="http://Onsp.org">Onsp.org</a> <<a href="http://Onsp.org">http://Onsp.org
</a>>, I can land calls from SER to Cisco 3600<br>>> without any<br>>> > problems. Yet I'm experiencing some problems with Cisco3600 passing<br>>> > calls onto SER.<br>>> ><br>>> > My setup is as follow:
<br>>> ><br>>> > Cisco 3600 ==> SER+Mediaproxy ===> IP Phone<br>>> ><br>>> > When a call come in via DID method through the Cisco3600, SER<br>>> > received the all SIP messages (I got it via ngrep), yet the call
<br>>> > couldn't pass onto the IP Phone.<br>>> ><br>>> > Currently, all devices (including cisco) have been configured to use<br>>> > port 5080 instead of port 5060 due to port restrictions on the
<br>>> > network, and that I have specified the ip in the trusted table under<br>>> > mysql. Yet I don't know why the call still can not get through. The<br>>> > following are the logs I received from ngrep and cisco..... Any help
<br>>> > is welcome and is GREATLY APPRCIATED!!<br>>> ><br>>> > ------------------- ngrep from SER server<br>>> ><br>>> > U cisco-ip:55299 -> SER-ip:5080<br>>> > INVITE
sip:6119203@SER-ip;user=phone;phone-context=local<br>>> > SIP/2.0..Via: SIP/2.0/UDP cisco-ip:5060..From: "6113640"<br>>> > <sip:6113640@cisco-ip>..To:<br>>> > <sip:6119203@SER-ip
;user=phone;phone-context=local>.............. #<br>>> > U SER-ip:5080 -> cisco-ip:5060<br>>> > SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP<br>>> > <a href="http://222.50.103.247:5060">
222.50.103.247:5060</a> <<a href="http://222.50.103.247:5060">http://222.50.103.247:5060</a>>..From: "6113640" <<br>>> sip:6113640@cisco-ip>..To:<br>>> > <sip:6119203@SER-ip<br>>> ;user=phone;phone-context=local>...........................
<br>>> > #<br>>> > U cisco-ip:55299 -> SER-ip:5080<br>>> > CANCEL sip:6119203@SER-ip;user=phone;phone-context=local<br>>> > SIP/2.0..Via: SIP/2.0/UDP <a href="http://222.50.103.247:5060">
222.50.103.247:5060</a><<a href="http://222.50.103.247:5060">http://222.50.103.247:5060</a>><br>>> ..From:<br>>> > "6113640"<sip:6113640@cisco-ip>..To:<br>>> > <sip:6119203@SER-ip
;user=phone;phone-context=local>.................<br>>> ><br>>> > ---------------- mysql trusted table<br>>> > +----------------+-------+--------------+<br>>> >> src_ip | proto | from_pattern |
<br>>> > +----------------+-------+--------------+<br>>> >> cisco-ip | any | ^sip:.*$ |<br>>> > +----------------+-------+--------------+<br>>> ><br>>> > ----------------- log from cisco3600
<br>>> > Jun 23 14:23:53: HandleUdpSocketReads :Msg enqueued for SPI with<br>>> > IPaddr: SER-ip:5080<br>>> > Jun 23 14:23:57: Received:<br>>> > SIP/2.0 408 Request Timeout<br>>> > Via: SIP/2.0/UDP cisco-ip:5060
<br>>> > From: "6113640" <sip:6113640@cisco3600><br>>> > To:<br>>> > <sip:6119203@SER-ip<br>>> ;user=phone;phone-context=local>;tag=bc78c497f1336138e83d95d77d963f1b-f81d
<br>>> > Call-ID: <a href="mailto:22B8BA3E-E32911D9-82A1EC22-7AD29AB0@222.50.103.247">22B8BA3E-E32911D9-82A1EC22-7AD29AB0@222.50.103.247</a><br>>> > CSeq<br>>> ><br>>> > _______________________________________________
<br>>> > Serusers mailing list<br>>> > <a href="mailto:serusers@lists.iptel.org">serusers@lists.iptel.org</a><br>>> > <a href="http://mail.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers
</a><br>>><br>>> _______________________________________________<br>>> Serusers mailing list<br>>> <a href="mailto:Serusers@iptel.org">serusers@lists.iptel.org</a><br>>> <a href="http://mail.iptel.org/mailman/listinfo/serusers">
http://lists.iptel.org/mailman/listinfo/serusers</a><br>>><br>><br><br><br></blockquote></div><br>