Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

H323 calls cut off after 15 secs

Status
Not open for further replies.

rubycoo

Programmer
Jul 27, 2009
34
0
0
GB
We have 3 R3.0 (fully patched) BCM50s with H323 trunks connected to an Option 81. Calls from all of these sites to other sites (R1 & R2) cut off after approx 15s. Older systems do not have the same problems. Could be the BCMs or the Option 81. Any ideas?
 
Multiple Possibilities... network possible (errors on spans)... config of systems (codec-payload)... What information do you receive from the system/s when the call disconnects?

Bryan J Miles
Systems Engineer
Service Communications, Inc.
 
Hi Bryan - apologies for the following long reply:
We do not think it is a network issue, as BCM50’s on other sites (Rls1 and Rls2) work fine, also there is a huge number of option 11’s and a few other option 81’s that are coping fine, it is just 1 option 81 and any BCM50 Rls3 that has the problem, the codec and other info can been seen in a snippet of the UIP Log below. The only weird thing is that the BCM is set to negotiate G.729, but it ends up negotiating G.711, as a result we have tried changing codecs, but as the other maintainer (option81) did not have access to the ITG card on the option81, we were not able to investigate payload sizes at the far end, the BCM is using default payload sizes as is all the BCM’s regardless of software level.

Trunk 2 14:56:08 < CC < CRef Origin: CRef 234 SETUP
Bearer capability - Speech - G.711 A-law
Information Transfer Capability: speech
Coding Standard: CCITT standardized coding
Information Transfer Rate: 64 Kbits/s
Transfer Mode: circuit mode
User Information L1 Protocol ID: Recommendation G.711 A-law
Layer and Protocol Identification: User Information L1 Protocol
13 00 81 90 00 00 A3 00 00 00 00 00 00 00
Channel identification - B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 0
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: CCITT standard as in Recommendation Q.931
Channel Number: :
0F 00 E9 00 83 00 01 00 81 00
NA Display - Kidd1833509
03 00 B1 00 0B 00 4B 69 64 64 31 38 33 33 35 30 39
Calling party number - Private/Subscriber - 418309
Numbering Plan Identification: Unknown/Reserved Value
Type of Number: Unknown/Reserved Value
Screening indicator: User provided, not screened
Presentation indicator: Presentation allowed
Number Digits: - 418309
07 00 42 80 06 00 04 01 08 03 0A 09
Called party number - Private/Subscriber - 466498
Numbering Plan Identification: Unknown/Reserved Value
Type of Number: Unknown/Reserved Value
Number Digits: - 466498
03 00 C2 00 06 00 04 06 06 04 09 08
Trunk 2 14:56:09 > CC > CRef Origin: CRef 96 ALERTING
Channel identification - B-
Information Channel Selection: B1 channel
D-Channel Indicator: channel identified is not the D-channel
Preferred/Exclusive: exclusive - only the indicated channel is acceptable
Interface Type: primary rate interface
Interface Identifier Present: interface explicily identified
Interface Identifier: 160
Channel Type/Map Element Type: B-channel units
Number/Map: channel indicated by number
Coding Standard: CCITT standard as in Recommendation Q.931
Channel Number: :
0F 00 E9 A0 83 00 01 00 21
Trunk 2 14:56:09 > CC > CRef Origin: CRef 96 NOTIFY
Notification indicator
Notification Description: Unknown/Reserved Value
01 00 F1
NA Display - BT ENGINEER
03 00 B2 00 0B 00 42 54 20 45 4E 47 49 4E 45 45 52
Trunk 2 14:56:11 > CC > CRef Origin: CRef 96 CONNECT
Trunk 2 14:56:22 < CC < CRef Origin: CRef 234 DISCONNECT
Cause - Normal
Location: User
Coding Standard: CCITT standardized coding as described below
Cause Class: Normal Event
Cause: Normal clearing
05 00 80 00 10 00
 
check the payload size on the pbx as the pbx default is different to the bcm.
 
Payload size is the same on the R3 as the R1 & R2s, so not applicable
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top