×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

codec negotiation process (dial-peer)

Answered Question
Jul 30th, 2014
User Badges:

Good day everyone,

 

I am trying to see the process of codec negotiation.

My situation is: 2CME connected by a link. From one side, under dial-peer (voip) towards the another side I added a few commands:

!

dial-peer voice 3000 voip
 destination-pattern 5553...
 session target ipv4:10.1.250.102
 voice-class codec 10
 no vad
!
voice class codec 10
 codec preference 1 g723r53
 codec preference 2 ilbc
 codec preference 3 g729br8

!

From ip-phone (SCCP) I called to another skinny ip-phone(5553001).  I want to see the situation when one side is offering: g723, ilbc, g729 and another side agree on g729, for example. How can I see the process codec negotiation? 

I guess it should be seen by: "debug h245 asn1", am I right?  Could you show it to me in my output (plz check the attached file).

Thank you in advance.

--

DMitry

Attachment: 
Correct Answer by Ayodeji Okanlawon about 3 years 2 weeks ago

(+ 5) to Brian for the excellent ideas as usual..

The logs doesnt show the h245 terminal capabilites negotiations. (TCS) It is possible that this has been over written in the buffer. This is where you will see the codec negotiation taken place..

Please increase the size of your buffer as follows and then do the test again...

logging buffered 10000000 debug

 

You can also see the codec negotiation on ccme by using another debug..

debug ephone detail

I suggest you try this after you are done with the h245 debug..as this can generate a lot of output. This is quite useful in seeing every interaction from when you dial the digits to how the call progresses..
 

Correct Answer by Brian Meade about 3 years 2 weeks ago

You'll see it in the H245 TerminalCapabilitySet message.  I don't see that in your debug so it may have overran the monitor session.  Try capturing the debug again with this:

no logging monitor

no logging console

logging buffered 5000000

logging buffered debug

service sequence-numbers

 

then do:

clear log

debug h245 asn1

 

After call is complete, do:

un all

show log

 

That should show you all the H245 messaging for the call now hopefully.  If not, the sequence numbers will at least show you if you have any gaps where the missing messages may be.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (3 ratings)
Loading.
Correct Answer
Brian Meade Wed, 07/30/2014 - 12:38
User Badges:
  • Silver, 250 points or more

You'll see it in the H245 TerminalCapabilitySet message.  I don't see that in your debug so it may have overran the monitor session.  Try capturing the debug again with this:

no logging monitor

no logging console

logging buffered 5000000

logging buffered debug

service sequence-numbers

 

then do:

clear log

debug h245 asn1

 

After call is complete, do:

un all

show log

 

That should show you all the H245 messaging for the call now hopefully.  If not, the sequence numbers will at least show you if you have any gaps where the missing messages may be.

kozorezdi Thu, 07/31/2014 - 01:03
User Badges:

Dear Brian,

I appreciate your help.  I have followed by your recommendations.  Please check the new attached file. THANK YOU!

 

no logging monitor
no logging console
logging buffered 5000000
logging buffered debug
service sequence-numbers

clear log
debug h245 asn1


Cisco IOS Software, 2800 Software (C2800NM-IPVOICE_IVS-M), Version 15.1(2)T1, RELEASE SOFTWARE (fc1)

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
                 Call from HQ(5552002) to BR(5553001):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
HQ-1:
voice class codec 10
 codec preference 1 g711ulaw
 codec preference 2 ilbc
!
dial-peer voice 3000 voip
 destination-pattern 5553...
 session target ipv4:10.1.250.102
 voice-class codec 10
 no vad
!
HQ-1#
HQ-1#sh voice call status
CallID     CID  ccVdb      Port        Slot/DSP:Ch  Called #   Codec    MLPP Dial-peers
0x114      1492 0x497BF1F0 50/0/2.0                 5553001    g711ulaw 20002/3000
1 active call found

HQ-1#sh call active voice compact
 <callID>  A/O FAX T<sec> Codec       type        Peer Address       IP R<ip>:<udp>
Total call-legs: 2
       276 ANS     T147   g711ulaw    TELE        P5552002
       277 ORG     T147   g711ulaw    VOIP        P5553001     10.1.250.102:18978

HQ-1#
HQ-1#sh dial-peer voice summary
dial-peer hunt 0
             AD                                    PRE PASS                OUT
TAG    TYPE  MIN  OPER PREFIX    DEST-PATTERN      FER THRU SESS-TARGET    STAT PORT    KEEPALIVE
20001  pots  up   up             5552001$           0                           50/0/1
20002  pots  up   up             5552002$           0                           50/0/2
7      pots  up   up             0[2-9]......       0                      up   0/2/0:15
10     pots  up   up             00[2-9]......      0                      up   0/2/0:15
9011   pots  up   up   00        000T               0                      up   0/2/0:15
112    pots  up   up   112       112                0                      up   0/2/0:15
1120   pots  up   up   112       0112               0                      up   0/2/0:15
1      pots  up   up                                0                      down
3000   voip  up   up             5553...            0  syst ipv4:10.1.250.102
HQ-1#


BR-1:
voice class codec 10
 codec preference 1 ilbc
 codec preference 2 g711alaw
 codec preference 3 g711ulaw
!
dial-peer voice 2000 voip
 destination-pattern 5552...
 session target ipv4:10.1.250.101
 voice-class codec 10
!

BR-1#sh voice call status
CallID     CID  ccVdb      Port        Slot/DSP:Ch  Called #   Codec    MLPP Dial-peers
0xA4       1492 0x48A16948 50/0/1.0                *5553001    g711ulaw 2000/20001
1 active call found

BR-1#sh call active voice compact
 <callID>  A/O FAX T<sec> Codec       type        Peer Address       IP R<ip>:<udp>
Total call-legs: 2
       163 ANS     T235   g711ulaw    VOIP        P5552002     10.1.250.101:16384
       164 ORG     T235   g711ulaw    TELE        P5553001

BR-1#sh dial-peer voice summary
dial-peer hunt 0
             AD                                    PRE PASS                OUT
TAG    TYPE  MIN  OPER PREFIX    DEST-PATTERN      FER THRU SESS-TARGET    STAT PORT    KEEPALIVE
20001  pots  up   up             5553001$           0                           50/0/1
7      pots  up   up             9[2-9]......       0                      up   0/2/0:23
10     pots  up   up             91[2-9]..[2-9]..-  0                      up   0/2/0:23
                                 ....
9011   pots  up   up   011       9011T              0                      up   0/2/0:23
911    pots  up   up             911                0                      up   0/2/0:23
9911   pots  up   up   911       9911               0                      up   0/2/0:23
1      pots  up   up                                0                      down
2000   voip  up   up             5552...            0  syst ipv4:10.1.250.101
BR-1#
dial-peer voice 2000 voip
 destination-pattern 5552...
 session target ipv4:10.1.250.101
 voice-class codec 10
!

 

Sorry, I don't see the situation by the debug...

--

Dmitry

Attachment: 
Correct Answer
Ayodeji Okanlawon Thu, 07/31/2014 - 01:43
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

(+ 5) to Brian for the excellent ideas as usual..

The logs doesnt show the h245 terminal capabilites negotiations. (TCS) It is possible that this has been over written in the buffer. This is where you will see the codec negotiation taken place..

Please increase the size of your buffer as follows and then do the test again...

logging buffered 10000000 debug

 

You can also see the codec negotiation on ccme by using another debug..

debug ephone detail

I suggest you try this after you are done with the h245 debug..as this can generate a lot of output. This is quite useful in seeing every interaction from when you dial the digits to how the call progresses..
 

kozorezdi Thu, 07/31/2014 - 04:38
User Badges:

Dear Brian and Ayodeji,

THANK YOU VERY MUCH!!!

Now I can see it ;)  I have missed the main idea of Brian, but after additional explanation from Ayodeji - everything clear right now!  THANKS!!!

--

Have a nice day,

Dmitry

Actions

This Discussion