Cannot configure h323 gateway

[techguy]

Hi,

I have one brand new 2911 router with following IOS. I have changed ios too. Initially there was M4, I have tried M1 and now M but to no vain.

"flash:c2900-universalk9-mz.SPA.151-4.M.bin"

cr2911#sh voice iec description 1.1.186.5.7.5

    IEC Version: 1

    Entity: 1 (Gateway)

    Category: 186 (Signaling socket failure)

    Subsystem: 5 (H323)

    Error: 7 (Socket error)

    Diagnostic Code: 5

[paolo bevilacqua]

In other words, what happens ?

[techguy]

In other words, Calls are not working on both direction ( inbound & outbound ). Giving busy tone.

[Ayodeji Okanlawon]

What is the status of the gateway in cucm? Do you see it as unknow and ip address or unknown unknown. Send your config

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

[Ayodeji Okanlawon]

Have you configured the interface to bind h323 signalling to? Can you share your config.

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

[techguy]

voice service voip

allow-connections h323 to h323

allow-connections h323 to sip

allow-connections sip to h323

allow-connections sip to sip

h323

sip

  bind control source-interface Loopback105

  bind media source-interface Loopback105

  registrar server

!

!

voice class codec 1

codec preference 1 g711ulaw

codec preference 2 g711alaw

codec preference 3 g729r8

!

!

!

!

voice class h323 1

  h225 timeout tcp establish 3

!

!

!

voice-card 0

dspfarm

dsp services dspfarm

!

!

application

global

  service alternate DEFAULT

!

!

!

!

!

!

interface Loopback105

ip address 10.1.211.193 255.255.255.192

h323-gateway voip interface

h323-gateway voip bind srcaddr 10.1.211.193

!

voice-port 0/0/0

trunk-group FXO

timing hookflash-out 50

connection plar 2222

caller-id enable

!

dial-peer voice 10 pots

trunkgroup FXO

tone ringback alert-no-PI

description International

destination-pattern 900.T

fax rate disable

prefix 00

!

dial-peer voice 7000 voip

preference 1

destination-pattern 1234

voice-class codec 1

voice-class h323 1

session target ipv4:10.50.2.3

dtmf-relay h245-alphanumeric

req-qos guaranteed-delay audio

acc-qos guaranteed-delay audio

fax-relay ecm disable

fax rate 14400

fax nsf 000000

fax protocol pass-through g711ulaw

no vad

!

!

!

dial-peer voice 7002 voip

huntstop

preference 2

destination-pattern 1234

voice-class codec 1

voice-class h323 1

session target ipv4:10.50.2.4

dtmf-relay h245-alphanumeric

req-qos guaranteed-delay audio

acc-qos guaranteed-delay audio

fax-relay ecm disable

fax rate 14400

fax nsf 000000

fax protocol pass-through g711ulaw

no vad

!

[Ayodeji Okanlawon]

You are binding sip and h323 to the same interface..I think this is why you are getting socket signalling error

sip

bind control source-interface Loopback105

bind media source-interface Loopback105

!

interface Loopback105

ip address 10.1.211.193 255.255.255.192

h323-gateway voip interface

h323-gateway voip bind srcaddr 10.1.211.193

If you want to use h323 then remove the sip binding...

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

[techguy]

but SIP binding is only for IP phone in srst mode. Since i didnt have any sip tunk and sip dialpeer in order to make trunk between CUCM and Gateway.

I am using same config in other gateways too.

[Ayodeji Okanlawon]

I suggest you remove it first and see if it works. It is not good to bind different protocol to the same interface. You are telling the gateway to source both h323 and sip signalling from the same interface...

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

[techguy]

Let me change the configuration as you have suggested then i would let you know the result. Thanks

[paolo bevilacqua]

I suggest you remove it first and see if it works. It is not good to bind different protocol to the same interface. You are telling the gateway to source both h323 and sip signalling from the same interface...

That is perfectly fine, nothing prevents a router/gateway to behave like that.

[paolo bevilacqua]

Check that addresse matches between GW  and CMm and ping with the relecant addresses.

Also for simplicity you can use a physical interface instead of loopback.

[daniel.carlton]

Did you ever resolve this? We are getting the same thing.