| Summary: | ASTERISK-06223: h.323 native bridge | ||
| Reporter: | Sergey Basmanov (sb) | Labels: | |
| Date Opened: | 2006-01-31 08:52:03.000-0600 | Date Closed: | 2011-06-07 14:02:48 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) chan_h323.diff ( 1) h323.diff | |
| Description: | I made some changes to current channels/h323 code to make native bridge working. There was some issue with incorrect sessionId in h323_native_bridge. At least for now, it redirects Rx channel to remote host. But I have no idea how to redirect Tx channel started at FastStart. To tell remote to send rtp to other host, I close logical channel, setting ip and port with SetExternalAddress() in MyH323_ExternalRTPChannel constructor and when remote requests openLogicalChannel it gets correct ip and port. The question is: how to tell remote that we sending from another ip ? ****** ADDITIONAL INFORMATION ****** h323 native bridge would be very useful in setup: SIP UA -> asterisk -> H323 peer May be somebody who more familiar with openh323 can point me to documentation on how to implement this ? | ||
| Comments: | By: Sergey Basmanov (sb) 2006-01-31 09:16:41.000-0600 With this patch only Rx channel being redirected. By: Matthew Fredrickson (mattf) 2006-01-31 17:17:37.000-0600 For specific developmental questions such as this, it is usually better to consult the author (check the header of the file) before posting a potentially buggy patch. By: Sergey Basmanov (sb) 2006-02-01 03:05:07.000-0600 Well, this is not working patch. Just a start of implementation of h323 native bridge. I thought that may be other people will have some ideas about this. By: Matthew Fredrickson (mattf) 2006-02-02 09:19:02.000-0600 Probably a better place for this would be on the -dev mailing list. We're trying to move developmental discussionary issues off the bug tracker so that they get more exposure. When you have a completed (and working) implementation, repost it and we'll see about getting it in. | ||