[Serusers] Cisco3600 to SER

[Greger V. Teigre]

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 at 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 at 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 at 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 at SER-ip;user=phone;phone-context=local
>>> SIP/2.0..Via: SIP/2.0/UDP  cisco-ip:5060..From: "6113640"
>>> <sip:6113640 at cisco-ip>..To:
>>> <sip:6119203 at 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 at cisco-ip>..To:
>>> <sip:6119203 at SER-ip;user=phone;phone-context=local>...........................
>>> # U cisco-ip:55299 -> SER-ip:5080
>>>  CANCEL sip:6119203 at SER-ip;user=phone;phone-context=local
>>> SIP/2.0..Via: SIP/2.0/UDP  222.50.103.247:5060..From:
>>> "6113640"<sip:6113640 at cisco-ip>..To:
>>> <sip:6119203 at 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 at cisco3600>
>>> To:
>>> <sip:6119203 at SER-ip;user=phone;phone-context=local>;tag=bc78c497f1336138e83d95d77d963f1b-f81d
>>> Call-ID: 22B8BA3E-E32911D9-82A1EC22-7AD29AB0 at 222.50.103.247
>>> CSeq
>>>
>>> _______________________________________________
>>> Serusers mailing list
>>> serusers at lists.iptel.org
>>> http://lists.iptel.org/mailman/listinfo/serusers