Solved

SIP connected but no audio

Posted on 2010-08-18
3
4,515 Views
Last Modified: 2012-05-10
Here is our network design.

                          internet -- ASA -- SIP Phones
The symptom is i can receive incoming calls but can't make outbound calls. Also, when I receive incoming calls, either parties can't hear anything. I remember that I deleted "inspect sip" under global-policy and put it back.
Somehow the SIP Phones stop working. I attached asa configuration, debug sip, and asa log.

I really need your help and thank you all in advance.

<Configuration>

global (outside) 1 interface
nat (outside) 1 10.100.10.0 255.255.255.0   --> SIP phones IP Address range: 10.100.10.208/28


object-group protocol DM_INLINE_PROTOCOL_1
 protocol-object udp
 protocol-object tcp

access-list outside_access_in_1 extended permit object-group DM_INLINE_PROTOCOL_1 any any eq sip

policy-map type inspect dns preset_dns_map
 parameters
  message-length maximum 512
policy-map global_policy
 class inspection_default
  inspect dns preset_dns_map
  inspect ftp
  inspect h323 h225
  inspect h323 ras
  inspect rsh
  inspect rtsp
  inspect esmtp
  inspect sqlnet
  inspect skinny
  inspect xdmcp
  inspect sip
  inspect netbios
  inspect tftp
  inspect icmp
!
service-policy global_policy global

<xlate result>               --> x.y.z.66 is the asa outside interface IP which SIP phones are translated to
asa# sh xlate | i 10.100.10.214
PAT Global x.y.z.66(1753) Local 10.100.10.214(5060)
PAT Global x.y.z.66(1737) Local 10.100.10.214(5080)
Ndoors5505# sh xlate | i 10.100.10.213
PAT Global x.y.z.66(1725) Local 10.100.10.213(5060)
Ndoors5505# sh xlate | i 10.100.10.212
PAT Global x.y.z.66(1733) Local 10.100.10.212(5060)


<debug sip information >

Ndoors5505# SIP::REGISTER received from inside:10.100.10.210/5060 to outside:203.254.210.225/5060
SIP::regex engine has reached end of packet
SIP::Found CSeq 16626 REGISTER
SIP::Found valid SIP URI: sip:07070176843@sniproxy.samsung070.com:5060
SIP::Found From addr "sip:07070176843@sniproxy.samsung070.com:5060" (44)
SIP::Found From addr tag "058763beea00f9d" (15)
SIP::Found valid SIP URI: sip:07070176843@sniproxy.samsung070.com:5060
SIP::Found To addr "sip:07070176843@sniproxy.samsung070.com:5060" (44)
SIP::Found Via branch "z9hG4bK5cd505386" (16)
SIP::Found Via addr "SIP/2.0/UDP 10.100.10.210:5060;branch=z9hG4bK5cd505386" (54)
SIP::Found Max-Forwards 70
SIP::Found Call-ID ab91e5a37c11a46129cc937b2debda7e@10.100.10.210 (46)
SIP::Found valid SIP URI: sip:07070176843@10.100.10.210:5060
SIP::Found Contact sip:07070176843@10.100.10.210:5060
SIP::Found Content-length 0
        Found port 5060
Via Port 5060
SIP::Cannot translate portmapped addr 10.100.10.210 without a port
        Found port 5060
SIP::Found Expires, 3600 seconds
SIP::Found User-Agent
Created SIP session for inside:10.100.10.210/5060 to outside:203.254.210.225/5060, 6 total
        From: sip:07070176843@sniproxy.samsung070.com:5060 (44);tag=058763beea00f9d (15)
        To: sip:07070176843@sniproxy.samsung070.com:5060 (44)
        Call-ID: ab91e5a37c11a46129cc937b2debda7e@10.100.10.210 (46)
Created SIP Transaction for inside:10.100.10.210/5060 to outside:203.254.210.225/5060
        Call-ID: ab91e5a37c11a46129cc937b2debda7e@10.100.10.210 (46)
        CSeq: 16626 REGISTER
        Branch: z9hG4bK5cd505386
SIP::Updating xlate timeout for 10.100.10.210/5060 to 1:00:00
SIP:: Forward 834 bytes, total 834
SIP::200 received from outside:203.254.210.225/5060 to inside:10.100.10.210/5060
        Found port 1747
Via Port 1747
        Found port 5060
SIP::Found Expires, 270 seconds
        Found port 1747
SIP::Found Expires, 270 seconds
SIP::regex engine has reached end of packet
SIP::Found CSeq 16626 REGISTER
SIP::Found valid SIP URI: sip:07070176843@sniproxy.samsung070.com:5060
SIP::Found From addr "sip:07070176843@sniproxy.samsung070.com:5060" (44)
SIP::Found From addr tag "058763beea00f9d" (15)
SIP::Found valid SIP URI: sip:07070176843@sniproxy.samsung070.com:5060
SIP::Found To addr "sip:07070176843@sniproxy.samsung070.com:5060" (44)
SIP::Found To addr tag "aprq15gr571-hnv96r3000g4f" (25)
SIP::Found Via branch "z9hG4bK5cd505386" (16)
SIP::Found Via addr "SIP/2.0/UDP 10.100.10.210:5060;branch=z9hG4bK5cd505386" (54)
SIP::Found Call-ID ab91e5a37c11a46129cc937b2debda7e@10.100.10.210 (46)
SIP::Found valid SIP URI: sip:07070176843@10.100.10.210:5060
SIP::Found Contact sip:07070176843@10.100.10.210:5060
SIP::Updating xlate timeout for 10.100.10.210/5060 to 0:04:30
SIP:: Freeing signaling conn outside:203.254.210.225/0 to inside:12.49.180.66/1747
SIP:: Forward 460 bytes, total 460
SIP::REGISTER received from inside:10.100.10.211/5060 to outside:203.254.211.248/5060
SIP::regex engine has reached end of packet
SIP::Found CSeq 119 REGISTER
SIP::Found valid SIP URI: sip:07070176842@proxy.samsung070.com
SIP::Found From addr "sip:07070176842@proxy.samsung070.com" (36)
SIP::Found From addr tag "94c56dd8-a640ad3-13c4-1dff-5592973-1dff" (39)
SIP::Found valid SIP URI: sip:07070176842@proxy.samsung070.com
SIP::Found To addr "sip:07070176842@proxy.samsung070.com" (36)
SIP::Found Via branch "z9hG4bK-1dff-752ecc-546cef49" (28)
SIP::Found Via addr "SIP/2.0/UDP 10.100.10.211:5060;branch=z9hG4bK-1dff-752ecc-546cef49" (66)
SIP::Found Max-Forwards 70
SIP::Found Call-ID 94c523c0-a640ad3-13c4-5-65f6fb5c-5 (34)
SIP::Found Expires, 3600 seconds
SIP::Found valid SIP URI: sip:07070176842@10.100.10.211
SIP::Found Contact sip:07070176842@10.100.10.211
SIP::Found Content-length 0
        Found port 5060
Via Port 5060
SIP::Found User-Agent
Created SIP session for inside:10.100.10.211/5060 to outside:203.254.211.248/5060, 7 total
        From: sip:07070176842@proxy.samsung070.com (36);tag=94c56dd8-a640ad3-13c4-1dff-5592973-1dff (39)
        To: sip:07070176842@proxy.samsung070.com (36)
        Call-ID: 94c523c0-a640ad3-13c4-5-65f6fb5c-5 (34)
Created SIP Transaction for inside:10.100.10.211/5060 to outside:203.254.211.248/5060
        Call-ID: 94c523c0-a640ad3-13c4-5-65f6fb5c-5 (34)
        CSeq: 119 REGISTER
        Branch: z9hG4bK-1dff-752ecc-546cef49
SIP::Updating xlate timeout for 10.100.10.211/5060 to 1:00:00
SIP:: Forward 750 bytes, total 750
SIP::REGISTER received from inside:10.100.10.211/5060 to outside:203.254.211.248/5060
SIP::regex engine has reached end of packet
SIP::Found CSeq 119 REGISTER
SIP::Found valid SIP URI: sip:07070176842@proxy.samsung070.com
SIP::Found From addr "sip:07070176842@proxy.samsung070.com" (36)
SIP::Found From addr tag "94c56dd8-a640ad3-13c4-1dff-5592973-1dff" (39)
SIP::Found valid SIP URI: sip:07070176842@proxy.samsung070.com
SIP::Found To addr "sip:07070176842@proxy.samsung070.com" (36)
SIP::Found Via branch "z9hG4bK-1dff-752ecc-546cef49" (28)
SIP::Found Via addr "SIP/2.0/UDP 10.100.10.211:5060;branch=z9hG4bK-1dff-752ecc-546cef49" (66)
SIP::Found Max-Forwards 70
SIP::Found Call-ID 94c523c0-a640ad3-13c4-5-65f6fb5c-5 (34)
SIP::Found Expires, 3600 seconds
SIP::Found valid SIP URI: sip:07070176842@10.100.10.211
SIP::Found Contact sip:07070176842@10.100.10.211
SIP::Found Content-length 0
        Found port 5060
Via Port 5060
SIP::Found User-Agent
SIP::State Machine: New Request '119 REGISTER' received on existing transaction, Deleting existing transaction
Deleted SIP Transaction
        Call-ID: 94c523c0-a640ad3-13c4-5-65f6fb5c-5 (34)
        CSeq: 119 REGISTER
        Branch: z9hG4bK-1dff-752ecc-546cef49
Created SIP Transaction for inside:10.100.10.211/5060 to outside:203.254.211.248/5060
        Call-ID: 94c523c0-a640ad3-13c4-5-65f6fb5c-5 (34)
        CSeq: 119 REGISTER
        Branch: z9hG4bK-1dff-752ecc-546cef49
SIP::Updating xlate timeout for 10.100.10.211/5060 to 1:00:00
SIP:: Forward 750 bytes, total 750
SIP::200 received from outside:203.254.211.248/5060 to inside:10.100.10.211/5060
        Found port 1732
Via Port 1732
        Found port 1732
SIP::Found Expires, 180 seconds
SIP::regex engine has reached end of packet
SIP::Found CSeq 119 REGISTER
SIP::Found valid SIP URI: sip:07070176842@proxy.samsung070.com
SIP::Found From addr "sip:07070176842@proxy.samsung070.com" (36)
SIP::Found From addr tag "94c56dd8-a640ad3-13c4-1dff-5592973-1dff" (39)
SIP::Found valid SIP URI: sip:07070176842@proxy.samsung070.com
SIP::Found To addr "sip:07070176842@proxy.samsung070.com" (36)
SIP::Found To addr tag "aprq2lgrlv0-0te3nu00000e7" (25)
SIP::Found Via branch "z9hG4bK-1dff-752ecc-546cef49" (28)
SIP::Found Via addr "SIP/2.0/UDP 10.100.10.211:5060;branch=z9hG4bK-1dff-752ecc-546cef49" (66)
SIP::Found Call-ID 94c523c0-a640ad3-13c4-5-65f6fb5c-5 (34)
SIP::Found valid SIP URI: sip:07070176842@10.100.10.211:5060
SIP::Found Contact sip:07070176842@10.100.10.211:5060
SIP::Updating xlate timeout for x.y.z.66/1732 to 0:03:00
SIP:: Freeing signaling conn outside:203.254.211.248/0 to inside:x.y.z.66/1732
SIP:: Forward 405 bytes, total 405
SIP::200 received from outside:203.254.211.248/5060 to inside:10.100.10.211/5060
        Found port 1732
Via Port 1732
        Found port 1732
SIP::Found Expires, 180 seconds
SIP::regex engine has reached end of packet
SIP::Found CSeq 119 REGISTER
SIP::Found valid SIP URI: sip:07070176842@proxy.samsung070.com
SIP::Found From addr "sip:07070176842@proxy.samsung070.com" (36)
SIP::Found From addr tag "94c56dd8-a640ad3-13c4-1dff-5592973-1dff" (39)
SIP::Found valid SIP URI: sip:07070176842@proxy.samsung070.com
SIP::Found To addr "sip:07070176842@proxy.samsung070.com" (36)
SIP::Found To addr tag "aprq2lgrlv0-0te3nu00000e7" (25)
SIP::Found Via branch "z9hG4bK-1dff-752ecc-546cef49" (28)
SIP::Found Via addr "SIP/2.0/UDP 10.100.10.211:5060;branch=z9hG4bK-1dff-752ecc-546cef49" (66)
SIP::Found Call-ID 94c523c0-a640ad3-13c4-5-65f6fb5c-5 (34)
SIP::Found valid SIP URI: sip:07070176842@10.100.10.211:5060
SIP::Found Contact sip:07070176842@10.100.10.211:5060
SIP::Updating xlate timeout for x.y.z.66/1732 to 0:03:00
SIP:: Forward 405 bytes, total 405
term monSIP::REGISTER received from inside:10.100.10.209/5060 to outside:203.254.210.241/5060
SIP::regex engine has reached end of packet
SIP::Found CSeq 7644 REGISTER
SIP::Found valid SIP URI: sip:07070176840@proxy.samsung070.com
SIP::Found From addr "sip:07070176840@proxy.samsung070.com" (36)
SIP::Found From addr tag "94c57908-a640ad1-13c4-1363b6-3dcd5991-1363b6" (44)
SIP::Found valid SIP URI: sip:07070176840@proxy.samsung070.com
SIP::Found To addr "sip:07070176840@proxy.samsung070.com" (36)
SIP::Found Via branch "z9hG4bK-1363b6-4bbd7f58-3aa5b746" (32)
SIP::Found Via addr "SIP/2.0/UDP 10.100.10.209:5060;branch=z9hG4bK-1363b6-4bbd7f58-3aa5b746" (70)
SIP::Found Max-Forwards 70
SIP::Found Call-ID 94c52ef0-a640ad1-13c4-6-abcbdc-6 (32)
SIP::Found Expires, 3600 seconds
SIP::Found valid SIP URI: sip:07070176840@10.100.10.209
SIP::Found Contact sip:07070176840@10.100.10.209
SIP::Found Content-length 0
        Found port 5060
Via Port 5060
SIP::Found User-Agent
Created SIP session for inside:10.100.10.209/5060 to outside:203.254.210.241/5060, 8 total
        From: sip:07070176840@proxy.samsung070.com (36);tag=94c57908-a640ad1-13c4-1363b6-3dcd5991-1363b6 (44)
        To: sip:07070176840@proxy.samsung070.com (36)
        Call-ID: 94c52ef0-a640ad1-13c4-6-abcbdc-6 (32)
Created SIP Transaction for inside:10.100.10.209/5060 to outside:203.254.210.241/5060
        Call-ID: 94c52ef0-a640ad1-13c4-6-abcbdc-6 (32)
        CSeq: 7644 REGISTER
        Branch: z9hG4bK-1363b6-4bbd7f58-3aa5b746
SIP::Updating xlate timeout for 10.100.10.209/5060 to 1:00:00
SIP:: Forward 758 bytes, total 758

Ndoors5505# SIP::200 received from outside:203.254.210.241/5060 to inside:10.100.10.209/5060
        Found port 1745
Via Port 1745
        Found port 1745
SIP::Found Expires, 180 seconds
SIP::regex engine has reached end of packet
SIP::Found CSeq 7644 REGISTER
SIP::Found valid SIP URI: sip:07070176840@proxy.samsung070.com
SIP::Found From addr "sip:07070176840@proxy.samsung070.com" (36)
SIP::Found From addr tag "94c57908-a640ad1-13c4-1363b6-3dcd5991-1363b6" (44)
SIP::Found valid SIP URI: sip:07070176840@proxy.samsung070.com
SIP::Found To addr "sip:07070176840@proxy.samsung070.com" (36)
SIP::Found To addr tag "aprq1tgrl81-c29tcn30087od" (25)
SIP::Found Via branch "z9hG4bK-1363b6-4bbd7f58-3aa5b746" (32)
SIP::Found Via addr "SIP/2.0/UDP 10.100.10.209:5060;branch=z9hG4bK-1363b6-4bbd7f58-3aa5b746" (70)
SIP::Found Call-ID 94c52ef0-a640ad1-13c4-6-abcbdc-6 (32)
SIP::Found valid SIP URI: sip:07070176840@10.100.10.209:5060
SIP::Found Contact sip:07070176840@10.100.10.209:5060
SIP::Updating xlate timeout for x.y.z.66/1745 to 0:03:00
SIP:: Freeing signaling conn outside:203.254.210.241/0 to inside:x.y.z.66/1745
SIP:: Forward 413 bytes, total 413


<ASA Log File>

6|Aug 18 2010|03:36:26|607001|203.254.211.248||Pre-allocate SIP NOTIFY UDP secondary channel for inside:10.100.10.211/5060 to outside:203.254.211.248 from 200 message
6|Aug 18 2010|03:36:26|302016|203.254.211.248|10.100.10.211|Teardown UDP connection 15004 for outside:203.254.211.248/0 to inside:10.100.10.211/5060 duration 0:00:00 bytes 0
6|Aug 18 2010|03:36:25|607001|203.254.211.248||Pre-allocate SIP Via UDP secondary channel for inside:10.100.10.211/5060 to outside:203.254.211.248 from REGISTER message
6|Aug 18 2010|03:36:21|302016|211.115.194.21|10.100.10.211|Teardown UDP connection 14198 for outside:211.115.194.21/123 to inside:10.100.10.211/1042 duration 0:10:01 bytes 96
6|Aug 18 2010|03:36:16|302016|210.98.16.100|10.100.10.211|Teardown UDP connection 14192 for outside:210.98.16.100/123 to inside:10.100.10.211/1041 duration 0:10:01 bytes 48
6|Aug 18 2010|03:36:15|302016|203.241.135.135|10.100.10.211|Teardown UDP connection 14187 for outside:203.241.135.135/53 to inside:10.100.10.211/1040 duration 0:10:01 bytes 31
6|Aug 18 2010|03:34:27|302016|203.254.211.248|10.100.10.211|Teardown UDP connection 14765 for outside:203.254.211.248/0 to inside:10.100.10.211/5060 duration 0:03:01 bytes 0
6|Aug 18 2010|03:33:56|607001|203.254.211.248||Pre-allocate SIP NOTIFY UDP secondary channel for inside:10.100.10.211/5060 to outside:203.254.211.248 from 200 message
6|Aug 18 2010|03:33:56|607001|203.254.211.248||Pre-allocate SIP NOTIFY UDP secondary channel for inside:10.100.10.211/5060 to outside:203.254.211.248 from 200 message
6|Aug 18 2010|03:33:56|302016|203.254.211.248|10.100.10.211|Teardown UDP connection 14888 for outside:203.254.211.248/0 to inside:10.100.10.211/5060 duration 0:00:00 bytes 0

KJ
0
Comment
Question by:ndoorsinteractive
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 1

Expert Comment

by:mere-mortal
ID: 33473167
Where in you configuration are you allowing the RTP traffic which carries the SIP Audio?  Port 5060 is only used for call setup and teardown.
0
 
LVL 15

Expert Comment

by:Perarduaadastra
ID: 33473318
Is this a new installation, or a new problem on an existing installation? Also, what phones are you using?

Mere-mortal is on the ball; there seem to be no references to media or audio in the SIP debug log, and no RTP traffic = silence, even though the call is established.

I take it that the SIP debug log is from the phone itself?
0
 

Accepted Solution

by:
ndoorsinteractive earned 0 total points
ID: 33481344
Thanks to all.
Somehow the phones start working again....didn't do any....guess it was provider's issue...

Again, Thank you for your responses.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Network traffic routing plays key role in your network, if you have single site with heavy browsing or multiple sites, replicating important application data from your Primary Default Gateway ,you have to route your other network traffic from your p…
Article by: user_n
How Sip Phone (User Agent) works and communicates with sip servers 1.  There is a sip server and a sip registrar.  The sip server and sip registrar can be one server or two different servers. The sip registrar is the server on which it is record…
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…
In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…
Suggested Courses

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question