Smy,
One thing to keep in mind when dealing with Cisco 3600 routers (and others with ALG functionality) is that if you are using mediaproxy or rtpproxy and accidentially call use_media_session() or force_rtp_session() more than once when dealing with NATed clients, that SER will corrupt the c= field in the SDP payload and the Cisco 3600 will refuse to pass that message -- we can call this a "feature" :-)
Regards, Paul
On 6/24/05, Greger V. Teigre greger@teigre.com wrote:
Looks like the cisco box never receives the trying... U SER-ip:5080 -> cisco-ip:5060
If Cisco listens to port 5080 and not 5060, it's obvious... However, the box announces 5060 in: Via: SIP/2.0/UDP cisco-ip:5060
So, you need to change the cisco's announced port. Should be some parameter somewhere... g-)
smy@addm.com wrote:
Hi all,
I'm currently working with a cisco3600 with SER 0.9.2. Thanks to Onsp.org http://Onsp.org, I can land calls from SER to Cisco 3600
without any
problems. Yet I'm experiencing some problems with Cisco3600 passing calls onto SER.
My setup is as follow:
Cisco 3600 ==> SER+Mediaproxy ===> IP Phone
When a call come in via DID method through the Cisco3600, SER received the all SIP messages (I got it via ngrep), yet the call couldn't pass onto the IP Phone.
Currently, all devices (including cisco) have been configured to use port 5080 instead of port 5060 due to port restrictions on the network, and that I have specified the ip in the trusted table under mysql. Yet I don't know why the call still can not get through. The following are the logs I received from ngrep and cisco..... Any help is welcome and is GREATLY APPRCIATED!!
------------------- ngrep from SER server
U cisco-ip:55299 -> SER-ip:5080 INVITE sip:6119203@SER-ip;user=phone;phone-context=local SIP/2.0..Via: SIP/2.0/UDP cisco-ip:5060..From: "6113640" sip:6113640@cisco-ip..To: sip:6119203@SER-ip;user=phone;phone-context=local.............. # U SER-ip:5080 -> cisco-ip:5060 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 222.50.103.247:5060 http://222.50.103.247:5060..From: "6113640" <
sip:6113640@cisco-ip>..To:
<sip:6119203@SER-ip
;user=phone;phone-context=local>...........................
# U cisco-ip:55299 -> SER-ip:5080 CANCEL sip:6119203@SER-ip;user=phone;phone-context=local SIP/2.0..Via: SIP/2.0/UDP 222.50.103.247:5060http://222.50.103.247:5060
..From:
"6113640"sip:6113640@cisco-ip..To: sip:6119203@SER-ip;user=phone;phone-context=local.................
---------------- mysql trusted table +----------------+-------+--------------+
src_ip | proto | from_pattern |
+----------------+-------+--------------+
cisco-ip | any | ^sip:.*$ |
+----------------+-------+--------------+
----------------- log from cisco3600 Jun 23 14:23:53: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: SER-ip:5080 Jun 23 14:23:57: Received: SIP/2.0 408 Request Timeout Via: SIP/2.0/UDP cisco-ip:5060 From: "6113640" sip:6113640@cisco3600 To: <sip:6119203@SER-ip
;user=phone;phone-context=local>;tag=bc78c497f1336138e83d95d77d963f1b-f81d
Call-ID: 22B8BA3E-E32911D9-82A1EC22-7AD29AB0@222.50.103.247 CSeq
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers