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

CME - Vanguard

Alan Couto
Level 1
Level 1

Hello friends,

I am making tests between CME and Vanguard using the codec G723. When I make calls from Vanguard to CUCME works perfectly (see the attached show's). But when I try to make a call to an analog phone that is attached at Vanguard FXS the phone rings but when I try to answer to the call, the call drop and I receive a loud and fast busy tone.

It seems that CME does not activate the transcode for any reason that I don't know.

See the show run attached,  need help...

Many Thanks.

11 Accepted Solutions

Accepted Solutions

Ayodeji Okanlawon
VIP Alumni
VIP Alumni

Hi Alan,

The problem is not with CME. When calls coming to CME, cme invokes a xcoder and the call succeeds. When call is going to Vanguard, vanguard needs to invoke the cme. I doubt if vanguard can do that so I suggest you configure calls going to Vanguard from cme to use the same codec. Either g711 or G723.

When a call comes in from Vanguard it comes in as G723 and the phone is on G711 so cme invookes a xcoder. The same should happen in reverse but its vanguard that need to invoke xcoder...

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

View solution in original post

Alan,

Is a little bit tricky. The only way this can work is to set the call up such that call going to vanguard will use g723. Since cisco IP phones cant use G723, then we have to find a way to xcode the call on CME to G723 before it goes to vanguard.

On CME you can try this...

dial-peer voice xxxx voip

incoming called number yyyyy

codec G723

Where xxxxx= any dial-peer number range eg 2000

and yyyy= the vanguard called number

So this way when ip phone originate call on g711, the outboung leg is set to G723, then cme should invove xcoder and when that is done then the call wil go to vanguard using g723...

Can you send a sh run of your gateway..or if you can try what I suggested..test and then send me a debug voip ccapi inout

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

View solution in original post

No,

It is not similar. You are using voice-class codec, which means that call from IP Phones on CME will always use G711.

You need to change it like I suggested..

dial-peer voice 28 voip

destination-pattern 4027....

session target ipv4:192.168.0.2 ( if this is your Vanguard router)

codec G723

This way all calls going to vanguard will use G723 and cme will be forced to xcode before the call goes to vanguard.

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

View solution in original post

Can you quickly send 

debug voip ccapi inout

Please leave the config as it is now with codec g723 on the dial-peer to vanguard

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

View solution in original post

Alan,

I looked at the trace and yes g723 was sent to vanguard, vanguard also responded with g723. But the call disconnected with normal cause..

Can you send a

debug ephone state

Lets see whats happening on the ip phone side..

NB: i will be a way for a while so i will respond when im back

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

View solution in original post

Alan,

So yes The debug confirms that the xcoding is not happening and the disconnect reason also confirms is a codc mismactch problem...We just need to figure out why..I will think about it..

011807: *Jun 12 17:13:47.746: dn_tone_control DN=2 chan 1 tonetype=0:DtSilence onoff=0 pid=263

011808: *Jun 12 17:13:47.746: ephone-2[4]:OpenReceive DN 2 chan 1 codec 4:G711Ulaw64k  duration 20 ms bytes 160

011809: *Jun 12 17:13:47.750: DN: 2, CHAN: 1, voice_hcmask: 0x890000F

011810: *Jun 12 17:13:47.754: dn_tone_control DN=2 chan 1 tonetype=37:DtReorderTone onoff=1 pid=263

011811: *Jun 12 17:13:47.754: ephone-2[1/4][AN43E1B195B0001]:DN 2 disc reason 65 bear cap not impl state ALERTING

+++We see the gateway sending OLC to the router.+++

011256: *Jun 12 16:50:39.582: H245 FS OLC OUTGOING PDU ::=

value OpenLogicalChannel ::=
    {
      forwardLogicalChannelNumber 1
      forwardLogicalChannelParameters
      {
        dataType audioData : g7231 :

The vanguard resposnd with OLC

H225.0 INCOMING PDU ::=
centralizedVideo FALSE
              distributedVideo FALSE
            }
                    {
          capabilityTableEntryNumber 1
          capability receiveAndTransmitAudioCapability : g7231        capability receiveAudioCapability : g7231 :

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

View solution in original post

Lets do this, send me the ff for the successful incoming call..

debug voip ccapi inout

debug ephone state

sh voip rtp connection

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

View solution in original post

Thanks..you removed

debug h225 asn1 and h245 asn1..

Can you please send those

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

View solution in original post

I have looked at it and I see that on the call that worked. Call from Vanguard to CME, Vandguard sends its media IP in the h245 negotiation. But for the call that is failing Vanguard is not doing so.

++++++++Here...Succesful call++++++++

H245 FS OLC INCOMING PDU ::=

value OpenLogicalChannel ::=
    {
      forwardLogicalChannelNumber 1
      forwardLogicalChannelParameters
      {
        dataType audioData : g7231 :
        {
          maxAl-sduAudioFrames 2
          silenceSuppression FALSE
        }
        multiplexParameters h2250LogicalChannelParameters :
        {
          sessionID 1
          mediaControlChannel unicastAddress : iPAddress :
          {
            network 'C0A80002'H  (192.168.0.2) Vanguard IP where RTP should be send and RTP port 16521
            tsapIdentifier 16521
       

++++++++On the failed call+++++

225.0 INCOMING PDU ::=
centralizedVideo FALSE
              distributedVideo FALSE
            }
          }
        }
        mcCapability
        {
          centralizedConferenceMC FALSE
          decentralizedConferenceMC FALSE
        }
        rtcpVideoControlCapability FALSE
        mediaPacketizationCapability
        {
          h261aVideoPacketization FALSE
        }
      }
      capabilityTable
      {

        {
          capabilityTableEntryNumber 1
          capability receiveAndTransmitAudioCapability : g7231        capability receiveAudioCapability : g7231 :
          {
            maxAl-sduAudioFrames 1
            silenceSuppression TRUE
          }
        },
        {
          capabilityTableEntryNumber 16
          capability receiveAudioCapability : nonStandard :
          {
            nonStandardIdentifier h221NonStandard :
            {
              t35CountryCode 181
              t35Extension 0
              manufacturerCode 18
            }
            data '47373233316172'H
          }

Unless your trace was incomplete then something is not quite right with the way vanguard is sending its OLC for calls to it.

I like you to do this test..

Please do a test call again and send me only

debug h225 asn1

debug h245asn1

run them at the same time

2. Can you confugre vanguard to use g711u just for test? If so please do and change the codec on dial-peer to vanguard to use g711u. Then test and let me know

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

View solution in original post

Ok. Let  me know when you change the codec. You can use G729 too. IP Phones support G729. If vanguard does not support G711u..

The log you sent me is for a succesful call from vanduard to cme. I want a failed call from cme to vanguard

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

View solution in original post

Alan.

I am glad to have helped. But you have not rated any of my posts! Feel free to rate posts that helped

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

View solution in original post

24 Replies 24

Ayodeji Okanlawon
VIP Alumni
VIP Alumni

Hi Alan,

The problem is not with CME. When calls coming to CME, cme invokes a xcoder and the call succeeds. When call is going to Vanguard, vanguard needs to invoke the cme. I doubt if vanguard can do that so I suggest you configure calls going to Vanguard from cme to use the same codec. Either g711 or G723.

When a call comes in from Vanguard it comes in as G723 and the phone is on G711 so cme invookes a xcoder. The same should happen in reverse but its vanguard that need to invoke xcoder...

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

aokanlawon

Many thanks for replaying. Actually I must use G723 at Vanguard side because of some particularities of the project. If Vanguard can not make xcode (I really think that does not) do you have any ideia for that case? May we can use a ISR as a cube/gatekeeper dedicated to make transcoding...

Thanks in advance!!

Alan.

Alan,

Is a little bit tricky. The only way this can work is to set the call up such that call going to vanguard will use g723. Since cisco IP phones cant use G723, then we have to find a way to xcode the call on CME to G723 before it goes to vanguard.

On CME you can try this...

dial-peer voice xxxx voip

incoming called number yyyyy

codec G723

Where xxxxx= any dial-peer number range eg 2000

and yyyy= the vanguard called number

So this way when ip phone originate call on g711, the outboung leg is set to G723, then cme should invove xcoder and when that is done then the call wil go to vanguard using g723...

Can you send a sh run of your gateway..or if you can try what I suggested..test and then send me a debug voip ccapi inout

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

Hello,

It seems that my configuration is similar what you the one you are asking me to test.. See below:

dial-peer voice 10 voip

incoming called-number .

voice-class codec 1

dtmf-relay rtp-nte

!

dial-peer voice 28 voip

destination-pattern 4027....

session target ipv4:192.168.0.2

incoming called-number .

voice-class codec 1

My show run is already attached at the case (CME_11_06.txt.zip)

Also.. See the debug plus show commands too.. attached now (cme to vanguard and vanguard to cme)

Thanks again!!

No,

It is not similar. You are using voice-class codec, which means that call from IP Phones on CME will always use G711.

You need to change it like I suggested..

dial-peer voice 28 voip

destination-pattern 4027....

session target ipv4:192.168.0.2 ( if this is your Vanguard router)

codec G723

This way all calls going to vanguard will use G723 and cme will be forced to xcode before the call goes to vanguard.

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

CME_ISRG2(config)#do sh run | begin dial-peer

dial-peer voice 1 pots

service stcapp

port 0/0/0

!

dial-peer voice 2 pots

service stcapp

port 0/0/1

!

dial-peer voice 100 voip

destination-pattern 0T

session target sip-server

!

dial-peer voice 3 pots

service stcapp

port 0/0/2

!

dial-peer voice 4 pots

service stcapp

port 0/0/3

!

dial-peer voice 10 voip

incoming called-number .

voice-class codec 1

dtmf-relay rtp-nte

!

dial-peer voice 28 voip

destination-pattern 4027....

session target ipv4:192.168.0.2

codec g723r63

!

!

gateway

timer receive-rtp 1200

CME_ISRG2(config)#dial-peer

CME_ISRG2(config)#dial-peer voice 28

CME_ISRG2(config-dial-peer)#codec g723r53

CME_ISRG2(config-dial-peer)#

The call continue to drop (with both codec r53 and r63) , no xcoding.

Thanks...

Can you quickly send 

debug voip ccapi inout

Please leave the config as it is now with codec g723 on the dial-peer to vanguard

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

I've also tried on this way:

dial-peer voice 28 voip

destination-pattern 4027....

session target ipv4:192.168.0.2

voice-class codec 2

!

voice class codec 2

codec preference 1 g723r63

codec preference 2 g723ar63

codec preference 3 g723r53

codec preference 4 g723ar53

!

aokanlawon

See attached... thanks...

Alan,

I looked at the trace and yes g723 was sent to vanguard, vanguard also responded with g723. But the call disconnected with normal cause..

Can you send a

debug ephone state

Lets see whats happening on the ip phone side..

NB: i will be a way for a while so i will respond when im back

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

aokanlawon

See attached  the debug ephone state,

many thanks,

Alan.

Alan,

So yes The debug confirms that the xcoding is not happening and the disconnect reason also confirms is a codc mismactch problem...We just need to figure out why..I will think about it..

011807: *Jun 12 17:13:47.746: dn_tone_control DN=2 chan 1 tonetype=0:DtSilence onoff=0 pid=263

011808: *Jun 12 17:13:47.746: ephone-2[4]:OpenReceive DN 2 chan 1 codec 4:G711Ulaw64k  duration 20 ms bytes 160

011809: *Jun 12 17:13:47.750: DN: 2, CHAN: 1, voice_hcmask: 0x890000F

011810: *Jun 12 17:13:47.754: dn_tone_control DN=2 chan 1 tonetype=37:DtReorderTone onoff=1 pid=263

011811: *Jun 12 17:13:47.754: ephone-2[1/4][AN43E1B195B0001]:DN 2 disc reason 65 bear cap not impl state ALERTING

+++We see the gateway sending OLC to the router.+++

011256: *Jun 12 16:50:39.582: H245 FS OLC OUTGOING PDU ::=

value OpenLogicalChannel ::=
    {
      forwardLogicalChannelNumber 1
      forwardLogicalChannelParameters
      {
        dataType audioData : g7231 :

The vanguard resposnd with OLC

H225.0 INCOMING PDU ::=
centralizedVideo FALSE
              distributedVideo FALSE
            }
                    {
          capabilityTableEntryNumber 1
          capability receiveAndTransmitAudioCapability : g7231        capability receiveAudioCapability : g7231 :

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts

aokanlawon,

thanks for the return.. If you need anything else tell me, I am really without idea :/

again many thanks for the help...

Alan.

Lets do this, send me the ff for the successful incoming call..

debug voip ccapi inout

debug ephone state

sh voip rtp connection

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

Please rate all useful posts