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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Transport Mismatch, h323 problem

Status
Not open for further replies.

donavasq

Vendor
Mar 6, 2007
72
DO
Hi Everyone,

I'm trying to connect using h323 a BCM50 Rls. 3.0 and an ipLDK 60. The call signaling is good, however, there is no speech between both system.

The BCM rises a 53010 Alarm stating that there is a Transport Mismatch. I can conclude that there is a layer 4 issue but have no clue where exactly is the problem.

I believe that it is the same scenario between BCM and other h323 gateway, so I don't believe it's "Rocket Science".

C'mon!! I know there's one of you who have done this before

Thanks
 

Never worked on ipLDK 60 before but one thing you could check is if you have the same payload size on your IP trunks on both systems, they have to match.
 
This is the message that I can capture from the wireshark:

192.168.0.236 192.168.0.246 192.168.0.33
| | |
| | |
setup OLC (g711U g711U) | |
(35609)----------------------->|(1720) |
| | |
| | RTP(g711U) |
| (2106)|---------------------->|(51014)
|callProcd OLC(g711U) | |
|<----------------------| |
| | |
|alerting OLC(g711U) | |
|<----------------------| |
| | |
|connect OLC(g711U) | |
|<----------------------| |
| | |
|facility TCS (723 g729 | |
|g711A g711U g729A) | |
|<----------------------| |
| | |
|facility MSD | |
|<----------------------| |
| | |
|facility TCS (g711U)MSD| |
|---------------------->| |
| | |
|facility TCSAck | |
|---------------------->| |
| | |
|facility TCSAck MSDAck | |
|<----------------------| |
| | |
|facility MSDAck | |
|---------------------->| |
| | |
|facility TCS | |
|---------------------->| |
| | |
|releaseComplete CLC ESC| |
|---------------------->| |
| | |
|facility TCS | |
|releaseComplete CLC ESC| |
|---------------------->| |

There is no possibility of changing the payload size (as far as I know) in the ipLDK. I will appreciate your response
 
Ok. This is how it is:

192.168.0.236---> BCM
192.168.0.246---> ipLDK
192.168.0.33---> BCM ip phone
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top