H.323 trunk not disconnecting

[clindberg]

I have 2 IP offices connected via H.323 trunks. Short codes on system A allow me to make calls out of system B.

The first call works fine. But at the end of the call, system B does not close the channel. Seemingly not getting signalled that the call was hung up.

This causes call 2 to get rejected. "UNOBTAINABLE Disc" appears on the screen. Call 2 being rejected actually causes the channel to finally get hung up on system B, allowing the next call to be completed.

So in a nutshell, every other call is rejected. I'm hoping there is just an H.323 setting to tweak. Any ideas? Thanks in advance

 

[Bas1234]

Re-check all IP routes, in the IPO and in you VPN routers.

Does a ping answer from site a to b and viceversa?

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[IPOfficeIreland]

what versions are you running.

In <v5 you can try enable/disable Fast Start on the IP line. from v5 on it defaults to scn settings, so worth your while upgrading.

 

[clindberg]

Both are running R5

 

[ngagne]

Sorry for the thread necromancy, but we're having this exact same problem and were very interested to find out how you resolved it.

 

[intrigrant]

What kind of trunk do you break out on?
Please don't tell it are analog trunks....

 

[ngagne]

Forgive me, but I'm not a phone guy. The two IP Office systems are connected via an IPSEC VPN between two Cisco ASA5505s, and talk to each other over h323. The phones connected to the respective IP Office systems are not VoIP phones; I'm assuming they are plain old digital phones.

Again, sorry for the lack of info/understanding on my part...I'm just a lowly network guy trying to track down this problem for a client

 

[intrigrant]

So it is station to station calling when it happens?
Does it happen the other way around also, calling from B to A?

 

[ngagne]

1.) Yes, when a user in location A tries to dial an extension at location B, every other time he gets the Unobtainable message.

2.) No.

 

[tlpeter]

Can you provide the type of ipo's and software versions ?


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

 

[ngagne]

From the info I have, one is an IPO 500 and one is a 400. Both are running 5.0.8.

 

[intrigrant]

What if user 1 on A calls a user on siteB, second user on site A calls a user on B and then a third user on site A calls a user on site B?
Does the third caller get the same result as the second caller?
I have seen thus before on a IP Office, then the gatekeeper on LAN1 or LAN2 was disabled and there was only one ip port available. The site were the call is initiat

 

[TheSmash]

Hi guys,

Going to hijack here and say I'm having a similar problem. Recently upgraded customer from V4 to V5 and periodically SCN calls get chopped with Unobtainable Disc. Never happened before on V4.

Trace shows;


Disconncet message

700749296mS H323Evt: Shared tcp socket for line 10 disconnected
700749296mS H323Evt: H323Pipe:isconnectIndication cap 1
700749297mS H323Evt: H323Pipe:isconnectIndication cap 2
700749297mS H323Evt: H323 stack for line 10 is disconnected
700750058mS H323Evt: RTP(50r): 192.168.136.103/49158 192.168.36.103/49156 CODEC=Alaw64K(4) PKTSZ=160 RFC2833=off AGE=1034 SENT=38 (avg size=160) RECV=50 (avg size=160)


Connect Message

700764309mS H323Evt: V5 on the other side of line 10 tcp f4fbac44 shared_tcp f4f11c58 tcp f4fbac44 shared_msg_sent 0 new_caps 3 ver_major 5
700764309mS H323Evt: H323 stack for line 10 is connected
700764310mS H323Evt: H323Pipe::ConnectIndication cap 1
700764310mS H323Evt: H323Pipe::ConnectIndication cap 2
700764310mS H323Evt: Shared TCP became operational for line 10
700764317mS H323Evt: Handshake facility sent for line 10, but socket changed

Setting up a wireshark trace tomorrow to see what may be causing this.

Any thoughts appreciated.

My name is Mike but everyone calls me The Smash...