Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
4969
Views
9
Helpful
6
Replies

SIP to SIP proble through ASA VPN

Helmi Muzammil
Level 1
Level 1

‎06-04-2012 09:49 PM - edited ‎03-16-2019 11:29 AM

Hi All,

I have a problem with my cisco mobile 8.0  for iphone via vpn when i call to avaya. the avaya phone is ringing but i can't hear voice from, likewise Avaya phone. I use 5502 ASA with Version 7.2(3) and call manager version is 8.0.3.20000-2.

the topology is :

internet - ASA VPN & firewall - Switch Edge - Server Farm - Call Manager and Avaya.

when my cisco mobile for iphone connect wireless (not throgh ASA), i can call avaya and hear voice from it. when my cisco mobile connect vpn, call to cisco phone (SCCP) is no problem. vpn client use IPSEC protocol. the traffic from outside - inside an inside - outside already any any. i think it's sip to sip problem through VPN.

what i need to check more ?

Need your Advice from you all.

Many Thanks

Labels:
0 Helpful
6 Replies 6

Gordon Ross
Level 9
Level 9

‎06-05-2012 01:42 AM

I'd take a punt at SIP Inspection on the ASA. It's not perfect, so try disabling it temporarilly.

GTG

Please rate all helpful posts.

Helmi Muzammil
Level 1
Level 1
In response to Gordon Ross

‎06-05-2012 09:32 PM

Hi Gordon Ross,

Thank you for your reply. i've tried to disable sip inspection on ASA, but no change . suddenly CIPC via VPN not hear any voice from Avaya when called it.

0 Helpful

Gordon Ross
Level 9
Level 9
In response to Helmi Muzammil

‎06-05-2012 10:44 PM

OK. It looks like you've got a routing or access-list issue in the ASA for the media/RTP between your phone and the Avaya. If it was a routing issue on the Avaya, you'd at least get one-way audio.

One possible way to prove this, is to enable MTP for either the phone or Avaya SIP trunk. This should force media to flow through CUCM (which you can already talk to)

I had similar problems on an ASA myself. You can sometimes tie yourself in knots tracking these problems down. I trust you're not NATing this VPN connect too...

GTG

Please rate all helpful posts.

Helmi Muzammil
Level 1
Level 1
In response to Gordon Ross

‎06-05-2012 11:55 PM

Hi Gordon Ross,

That's a very kind of you to reply my post.

i've checked routing and access list on ASA, i think no problem. also I have tried to add some MTP resouce on phone an Avaya trunk, but no change too.

do i have to NATing Avaya and Call Manager, gordon?

may i ask you about this log? i got it when i traced on ASA.

6|May 31 2012|14:30:35|607001|10.12.3.205||Pre-allocate SIP NOTIFY TCP secondary channel for outside:10.12.60.33/50340 to inside:10.12.3.205 from 200 message

6|May 31 2012|14:30:34|607001|10.12.3.205||Pre-allocate SIP Via TCP secondary channel for outside:10.12.60.33/50340 to inside:10.12.3.205 from ACK message

6|May 31 2012|14:30:24|607001|10.12.3.205||Pre-allocate SIP Via TCP secondary channel for outside:10.12.60.33/50340 to inside:10.12.3.205 from ACK message

6|May 31 2012|14:30:20|607001|10.12.3.205||Pre-allocate SIP NOTIFY TCP secondary channel for outside:10.12.60.33/50340 to inside:10.12.3.205 from NOTIFY message

6|May 31 2012|14:30:20|607001|10.12.60.33||Pre-allocate SIP NOTIFY TCP secondary channel for inside:10.12.3.205/5060 to outside:10.12.60.33 from NOTIFY message

6|May 31 2012|14:30:16|607001|10.12.3.205||Pre-allocate SIP NOTIFY TCP secondary channel for outside:10.12.60.33/50340 to inside:10.12.3.205 from NOTIFY message

6|May 31 2012|14:30:16|607001|10.12.60.33||Pre-allocate SIP NOTIFY TCP secondary channel for inside:10.12.3.205/5060 to outside:10.12.60.33 from NOTIFY message

6|May 31 2012|14:30:01|607001|10.12.3.205||Pre-allocate SIP NOTIFY TCP secondary channel for outside:10.12.60.33/50340 to inside:10.12.3.205 from NOTIFY message

6|May 31 2012|14:30:01|607001|10.12.60.33||Pre-allocate SIP NOTIFY TCP secondary channel for inside:10.12.3.205/5060 to outside:10.12.60.33 from NOTIFY message

6|May 31 2012|14:29:52|607001|10.12.3.205||Pre-allocate SIP NOTIFY TCP secondary channel for outside:10.12.60.33/50340 to inside:10.12.3.205 from NOTIFY message

6|May 31 2012|14:29:52|607001|10.12.60.33||Pre-allocate SIP NOTIFY TCP secondary channel for inside:10.12.3.205/5060 to outside:10.12.60.33 from NOTIFY message

6|May 31 2012|14:29:51|607001|10.12.60.33||Pre-allocate SIP SUBSCRIBE TCP secondary channel for inside:10.12.3.205/5060 to outside:10.12.60.33 from 200 message

6|May 31 2012|14:29:17|302016|10.12.60.33|10.12.3.205|Teardown UDP connection 258775487 for outside:10.12.60.33/53604 to inside:10.12.3.205/69 duration 0:00:00 bytes 61 (rizqi.anwar)

6|May 31 2012|14:29:17|302016|10.12.60.33|10.12.3.205|Teardown UDP connection 258775488 for outside:10.12.60.33/53604 to inside:10.12.3.205/46547 duration 0:00:00 bytes 19

Thanks for your help

0 Helpful

Helmi Muzammil
Level 1
Level 1
In response to Helmi Muzammil

‎06-06-2012 02:54 AM

Hi Gordon,

I want to update my problem, i tried register x-lite SIP softphone on call manager via VPN on my laptop. after that i tested call to avaya, finally no problem found.

Thanks

0 Helpful

alexdelangel
Level 1
Level 1
In response to Helmi Muzammil

‎12-24-2014 06:48 AM

Hello friends,

Please, allow me to resurect this old post. I am getting similar logs in the ASA, would you help me to figure out what it means?

Regards and Merry Christmas!

6|Dec 24 2014 06:35:25|607001: Pre-allocate SIP REFER TCP secondary channel for OUTSIDE:172.17.100.12/5060 to INSIDE:172.17.5.97 from 200 message
6|Dec 24 2014 06:35:25|607001: Pre-allocate SIP REFER TCP secondary channel for OUTSIDE:172.17.100.12/5060 to INSIDE:172.17.5.84 from 200 message
6|Dec 24 2014 06:35:25|607001: Pre-allocate SIP REFER TCP secondary channel for OUTSIDE:172.17.100.11/5060 to INSIDE:172.17.5.86 from 200 message
6|Dec 24 2014 06:35:25|607001: Pre-allocate SIP REFER TCP secondary channel for OUTSIDE:172.17.100.12/5060 to INSIDE:172.17.5.85 from 200 message
6|Dec 24 2014 06:35:25|607001: Pre-allocate SIP REFER TCP secondary channel for OUTSIDE:172.17.100.12/5060 to INSIDE:172.17.5.109 from 200 message
6|Dec 24 2014 06:35:25|607001: Pre-allocate SIP REFER TCP secondary channel for OUTSIDE:172.17.100.12/5060 to INSIDE:172.17.5.84 from 200 message
6|Dec 24 2014 06:35:25|607001: Pre-allocate SIP REFER TCP secondary channel for OUTSIDE:172.17.100.12/5060 to INSIDE:172.17.5.108 from 200 message
6|Dec 24 2014 06:35:25|607001: Pre-allocate SIP REFER TCP secondary channel for OUTSIDE:172.17.100.12/5060 to INSIDE:172.17.5.119 from 200 message
6|Dec 24 2014 06:35:25|607001: Pre-allocate SIP REFER TCP secondary channel for OUTSIDE:172.17.100.12/5060 to INSIDE:172.17.5.85 from 200 message
6|Dec 24 2014 06:35:25|607001: Pre-allocate SIP REFER TCP secondary channel for OUTSIDE:172.17.100.12/5060 to INSIDE:172.17.5.109 from 200 message
6|Dec 24 2014 06:35:25|607001: Pre-allocate SIP REFER TCP secondary channel for OUTSIDE:172.17.100.12/5060 to INSIDE:172.17.5.108 from 200 message
6|Dec 24 2014 06:35:25|607001: Pre-allocate SIP REFER TCP secondary channel for OUTSIDE:172.17.100.12/5060 to INSIDE:172.17.5.119 from 200 message

0 Helpful
Customers Also Viewed These Support Documents