Hi all,
I'm currently working with a cisco3600 with SER 0.9.2. Thanks to 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..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: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
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, 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..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: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
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
Thank-you all for the tips.... I was out of town for a meeting, that's why I couldn't reply any sooner. I will give it a shot and let you all know how it goes. Paul, as for the corrupt c= field, what can I do or go around it?!? Again, my setup is based on the ONSIP.org document which calls use_media_session(). If this is the case, what can I do or what should I pay attention to??
Thank-you all for your input.... If this works, I think I'm gonna start up a HOW-TO document for Cisco 3600 and SER, and hope that all your contributions would be helpful for both me and everyone else dealing with Cisco 3600 and SER.
Cheers!
Best Regards, Samuel Yeung
Quoting Java Rockx javarockx@gmail.com:
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
Samuel,
Probably the easiest way to prevent the extra call to use_media_proxy() is to do something like this
if (!isflagset(22)) { setflag(22); use_media_proxy(); }
Regrads, Paul
On 6/26/05, smy@addm.com smy@addm.com wrote:
Thank-you all for the tips.... I was out of town for a meeting, that's why I couldn't reply any sooner. I will give it a shot and let you all know how it goes. Paul, as for the corrupt c= field, what can I do or go around it?!? Again, my setup is based on the ONSIP.org http://ONSIP.orgdocument which calls use_media_session(). If this is the case, what can I do or what should I pay attention to??
Thank-you all for your input.... If this works, I think I'm gonna start up a HOW-TO document for Cisco 3600 and SER, and hope that all your contributions would be helpful for both me and everyone else dealing with Cisco 3600 and SER.
Cheers!
Best Regards, Samuel Yeung
Quoting Java Rockx javarockx@gmail.com:
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 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 <
http://222.50.103.247:5060%3E..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
Hi all,
Thanks Greger, for pointing out the issue with the announcement port running on port 5060. I've tried to figure this out with my engineers, but we can't find the config location of this announcement port thingy in the Cisco, let alone configuring it.
As mentioned previously, the Cisco 3600 has changed it's default SIP port to 5080, but according to the ngrep report, it sends a reply (announcement) port on 5060, therefore when SER replies back to Cisco 3600, it tries to send it back via 5060 thus Cisco can not receive message.
We're STUCK here!! If there're anyone out there with experience / solution in solving this problem with the cisco, your help is needed & GREATLY appreciated!!!
PS: I just need to get Cisco to work with SER!! Any suggestions in an easier method to get this working are welcome!!
Best Regards, Samuel Yeung
Quoting "Greger V. Teigre" greger@teigre.com:
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, 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..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: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
Use something like this for all messages destined for the Cisco and right before t_relay: if(src_ip=="your_cisco_ip"){ rewritehostport("your_cisco_ip:5080"); }
g-)
smy@addm.com wrote:
Hi all,
Thanks Greger, for pointing out the issue with the announcement port running on port 5060. I've tried to figure this out with my engineers, but we can't find the config location of this announcement port thingy in the Cisco, let alone configuring it.
As mentioned previously, the Cisco 3600 has changed it's default SIP port to 5080, but according to the ngrep report, it sends a reply (announcement) port on 5060, therefore when SER replies back to Cisco 3600, it tries to send it back via 5060 thus Cisco can not receive message. We're STUCK here!! If there're anyone out there with experience / solution in solving this problem with the cisco, your help is needed & GREATLY appreciated!!!
PS: I just need to get Cisco to work with SER!! Any suggestions in an easier method to get this working are welcome!!
Best Regards, Samuel Yeung
Quoting "Greger V. Teigre" greger@teigre.com:
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, 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..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: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
Greger,
Thanks for the tip. Since I'm using Mediaproxy in my SER, there is no t_relay command in the config file. (Again, my config is based on www.onsip.org doc)
So what I've done is placing your command at the top (1st commend) in the opening of route{}. It improved the situation, since SER kept on resending INVITEs back to the Cisco via 5080 according to ngrep, yet the trying message is still sending back to the Cisco via port 5060. I can't seem to locate (since I'm still getting familiar with SER) the section where it sends the trying message in the configure file. Perhaps you can give me some pointers in where I should be placing the rewritehostport line inorder for the trying message to be sent on port 5080 back to the cisco. Thanks!!
The following is the Ngrep I got after the addition of the rewritehostport...
U cisco-ip:54215 -> 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 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:5080 INVITE sip:6119203@cisco-ip:5080;user=phone;phone-context=local SIP/2.0..Record-Route: sip:6119203@SER-ip:5080;nat=yes;lr=on..Via: SIP/2.0/UDP SER-ip:5080;branch=z9hG4bKea02.173ff176.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..............
Quoting "Greger V. Teigre" greger@teigre.com:
Use something like this for all messages destined for the Cisco and right before t_relay: if(src_ip=="your_cisco_ip"){ rewritehostport("your_cisco_ip:5080"); }
g-)
smy@addm.com wrote:
Hi all,
Thanks Greger, for pointing out the issue with the announcement port running on port 5060. I've tried to figure this out with my engineers, but we can't find the config location of this announcement port thingy in the Cisco, let alone configuring it.
As mentioned previously, the Cisco 3600 has changed it's default SIP port to 5080, but according to the ngrep report, it sends a reply (announcement) port on 5060, therefore when SER replies back to Cisco 3600, it tries to send it back via 5060 thus Cisco can not receive message. We're STUCK here!! If there're anyone out there with experience / solution in solving this problem with the cisco, your help is needed & GREATLY appreciated!!!
PS: I just need to get Cisco to work with SER!! Any suggestions in an easier method to get this working are welcome!!
Best Regards, Samuel Yeung
Quoting "Greger V. Teigre" greger@teigre.com:
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, 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..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: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
smy@addm.com wrote:
Thanks for the tip. Since I'm using Mediaproxy in my SER, there is no t_relay command in the config file. (Again, my config is based on www.onsip.org doc)
? I'm sorry that I'm not capable of remembering stuff across threads, I tend to mix up. However, not using t_relay because you use mediaproxy doesn't make any sense to me. It's in route[1]?!
So what I've done is placing your command at the top (1st commend) in the opening of route{}.
Yes, same effect... Just executed more often ;-)
It improved the situation, since SER kept on resending INVITEs back to the Cisco via 5080 according to ngrep, yet the trying message is still sending back to the Cisco via port 5060.
Yes, that's true. The trying is auto-generated by ser. A quick-fix would be to add: sl_send_reply("100","trying..."); for all Cisco invites. You would still get the 5060 auto-generated one, but at least the box will get its trying... g-)
I can't seem to locate (since I'm still getting familiar with SER) the section where it sends the trying message in the configure file. Perhaps you can give me some pointers in where I should be placing the rewritehostport line inorder for the trying message to be sent on port 5080 back to the cisco. Thanks!!
The following is the Ngrep I got after the addition of the rewritehostport... U cisco-ip:54215 -> 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 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:5080 INVITE sip:6119203@cisco-ip:5080;user=phone;phone-context=local SIP/2.0..Record-Route: sip:6119203@SER-ip:5080;nat=yes;lr=on..Via: SIP/2.0/UDP SER-ip:5080;branch=z9hG4bKea02.173ff176.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..............
Quoting "Greger V. Teigre" greger@teigre.com:
Use something like this for all messages destined for the Cisco and right before t_relay: if(src_ip=="your_cisco_ip"){ rewritehostport("your_cisco_ip:5080"); }
g-)
smy@addm.com wrote:
Hi all,
Thanks Greger, for pointing out the issue with the announcement port running on port 5060. I've tried to figure this out with my engineers, but we can't find the config location of this announcement port thingy in the Cisco, let alone configuring it.
As mentioned previously, the Cisco 3600 has changed it's default SIP port to 5080, but according to the ngrep report, it sends a reply (announcement) port on 5060, therefore when SER replies back to Cisco 3600, it tries to send it back via 5060 thus Cisco can not receive message. We're STUCK here!! If there're anyone out there with experience / solution in solving this problem with the cisco, your help is needed & GREATLY appreciated!!!
PS: I just need to get Cisco to work with SER!! Any suggestions in an easier method to get this working are welcome!!
Best Regards, Samuel Yeung
Quoting "Greger V. Teigre" greger@teigre.com:
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, 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..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: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
-
Greger V. Teigre -
Java Rockx -
smy＠addm.com