cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
355
Views
0
Helpful
0
Replies

voice is not audible to the person who is listening

Karthik_R
Level 1
Level 1

Hi,

I have collected tcp-dump logs on SIP server. The outside customer voice is clearly audible to the person who initiated the call but his voice is not audible to the person who is listening

I have attached the tcp-dump logs in here. anyone please provide an solution for this.

09:04:10.959946 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: INVITE sip:029876543210@172.19.62.67:5060 SIP/2.0
09:04:10.979349 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 100 Trying
09:04:11.120096 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 183 Session Progress
09:04:17.702455 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: CANCEL sip:029876543210@172.19.62.67:5060 SIP/2.0
09:04:17.721686 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 200 OK
09:04:17.721843 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 487 Request Terminated
09:04:17.722845 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: ACK sip:029876543210@172.19.62.67:5060 SIP/2.0
09:04:23.257685 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: INVITE sip:mum-ums-01@10.254.5.10:5060 SIP/2.0
09:04:23.259297 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: SIP/2.0 200 OK
09:04:23.281706 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: ACK sip:mum-ums-01@10.254.5.10:5060 SIP/2.0
09:04:29.851720 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: REGISTER sip:172.19.62.67:5060 SIP/2.0
09:04:29.851831 IP MUM-UMS-01.sip > NTSCOREEXPR.sip: SIP: REGISTER sip:172.19.62.68:5060 SIP/2.0
09:04:29.871088 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 200 OK
09:04:29.871202 IP NTSCOREEXPR.sip > MUM-UMS-01.sip: SIP: SIP/2.0 200 OK
09:04:29.908227 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: INVITE sip:029876543210@172.19.62.67:5060 SIP/2.0
09:04:29.927588 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 100 Trying
09:04:30.030017 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 183 Session Progress
09:04:31.648608 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: INVITE sip:jpr-ums-01@172.19.62.67:5060;transport=UDP SIP/2.0
09:04:31.667962 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 100 Trying
09:04:31.711469 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 200 OK
09:04:31.712607 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: ACK sip:jpr-ums-01@172.19.62.67:5060;transport=UDP SIP/2.0
09:04:38.530693 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: INVITE sip:mum-ums-01@10.254.5.10:5060 SIP/2.0
09:04:38.532337 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: SIP/2.0 200 OK
09:04:38.561168 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: ACK sip:mum-ums-01@10.254.5.10:5060 SIP/2.0
09:04:42.330860 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 200 OK
09:04:42.332138 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: ACK sip:029876543210@172.19.62.67:5060;transport=UDP SIP/2.0
09:04:54.936024 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: INVITE sip:mum-ums-02@172.19.62.67:5060;transport=UDP SIP/2.0
09:04:54.955450 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 100 Trying
09:04:54.976987 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 200 OK
09:04:54.978041 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: ACK sip:mum-ums-02@172.19.62.67:5060;transport=UDP SIP/2.0
09:04:59.346567 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: INVITE sip:mum-ums-02@172.19.62.67:5060;transport=UDP SIP/2.0
09:04:59.365891 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 100 Trying
09:04:59.387016 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: SIP/2.0 200 OK
09:04:59.388413 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: ACK sip:mum-ums-02@172.19.62.67:5060;transport=UDP SIP/2.0
09:05:16.396471 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: INVITE sip:mum-ums-01@10.254.5.10:5060 SIP/2.0
09:05:16.398011 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: SIP/2.0 200 OK
09:05:16.420326 IP NTSCOREEXP.sip > MUM-UMS-01.sip: SIP: ACK sip:mum-ums-01@10.254.5.10:5060 SIP/2.0
09:05:17.222403 IP MUM-UMS-01.sip > NTSCOREEXP.sip: SIP: BYE sip:029876543210@172.19.62.67:5060;transport=UDP SIP/2.0

 

0 Replies 0