Hi Andrew, If I was to go down that route, do you have any suggestions on the nature of the change required to do this? (i.e. what source would I need to modify, etc)? Well..i don't know what sources especifically you need to change/use..but to begin you can give a look at: SdpCandidate::setPort , SdpConnection and others :) best, Paulo On Fri, Jun 19, 2009 at 9:22 AM, Andrew Lavigne <alavi...@nortel.com> wrote:
> Hi, Paulo > > When you say "on the fly", I'm going to assume you mean "at the start of > each call" (and not during a call). > > Anyway, I do indeed need to specify the RTP port at the start of each call > (because for each call, I want to direct the RTP stream to a port that I > already know about). > > Now, as we talked about already, using the RTP start address might suffice > -- we'll see. However, regarding your statement that contains your > comment about 'needing to provide such functionality': If I was to go down > that route, do you have any suggestions on the nature of the change required > to do this? (i.e. what source would I need to modify, etc)? > > ...Andrew > > ------------------------------ > *From:* Paulo Vicentini [mailto:vicentini.pa...@gmail.com] > *Sent:* Thursday, June 18, 2009 3:18 PM > *To:* Lavigne, Andrew (CAR:PC00) > *Cc:* sipxtapi-dev@list.sipfoundry.org > *Subject:* Re: [sipxtapi-dev] Support for specifying port to use for RTP > stream? > > Hi, > you might specify the udp port to use during initialization time with that > function. > Such port would be used on SDP. > > Do you need to change/set RTP port on the fly per call basis? > If so, I think you need to provide such functionality > regards > Paulo > > On Thu, Jun 18, 2009 at 2:47 PM, Andrew Lavigne <alavi...@nortel.com>wrote: > >> Hi, Paulo >> >> Yes, I've noticed that field. But that just specifies the start of the >> range from which sipxtapi will start automatically allocating ports, no? >> >> I suppose I could specify a new rtp start port each time I create a new >> call. Is that what you are implying? >> >> ...Andrew >> >> ------------------------------ >> *From:* Paulo Vicentini [mailto:vicentini.pa...@gmail.com] >> *Sent:* Thursday, June 18, 2009 1:45 PM >> *To:* Lavigne, Andrew (CAR:PC00) >> *Cc:* sipxtapi-dev@list.sipfoundry.org >> *Subject:* Re: [sipxtapi-dev] Support for specifying port to use for RTP >> stream? >> >> Hi, >> what about: >> SIPXTAPI_API SIPX_RESULT sipxInitialize(SIPX_INST* phInst, >> const int udpPort = DEFAULT_UDP_PORT, >> const int tcpPort = DEFAULT_TCP_PORT, >> const int tlsPort = DEFAULT_TLS_PORT, >> const int rtpPortStart = DEFAULT_RTP_START_PORT, >> const int maxConnections = DEFAULT_CONNECTIONS, >> const char* szIdentity = DEFAULT_IDENTITY, >> const char* szBindToAddr = DEFAULT_BIND_ADDRESS, >> bool bUseSequentialPorts = false, >> const char* szTLSCertificateNickname = NULL, >> const char* szTLSCertificatePassword = NULL, >> const char* szDbLocation = NULL, >> bool bEnableLocalAudio = true) ; >> you might set rtpPortStart >> Regards >> Paulo >> >> >> On Thu, Jun 18, 2009 at 9:56 AM, Andrew Lavigne <alavi...@nortel.com>wrote: >> >>> Hi, All >>> >>> I'm using sipxtapi to initiate SIP calls. I need to be able to connect >>> the RTP packet stream associated with this SIP call (my side of the call, >>> the client side) to a port of my choosing. At SIP call setup time, I >>> already know what port I need to use. Therefore, I need to somehow tell >>> sipxtapi that it should use this particular port as part of the SDP data it >>> sends during the media negotiation phase of setting up a call. I don't want >>> sipxtapi to pick a port for me. I've looked and haven't yet located any >>> part of the API that would permit me to do this. >>> >>> I've also looked through the archives of this mailing list and did come >>> across one posting a couple of years ago (which outlines a problem similar >>> to mine). A reply to that posting hinted that support for this did not >>> exist. Can anyone comment on whether there is support for this sort of >>> thing now, and if not, perhaps a bit more detail on the "will require >>> changes in underlying libs" that is mentioned? >>> >>> Many thanks in advance, >>> …Andrew >>> alavi...@nortel.com >>> >>> ----- quoted message ----- >>> >>> Re: [sipxtapi-dev] Down and dirty RTP-SIP >>> >>> Alexander Chemeris >>> Sun, 22 Jul 2007 11:57:17 -0700 >>> >>> Hello, >>> >>> On 7/22/07, Brett Dawson <[EMAIL PROTECTED]> wrote: >>> > I've got an RTP stream from an external device that I can send wherever >>> I >>> > need to. What is the easiest way to get that RTP stream to a connected >>> SIP >>> > call using the SipxTapi? >>> >>> There is no API in sipXtapi to do this. It is implementable, but will >>> require >>> changes in underlying libs (sipXtackLib and so). >>> >>> Do you need your client to be RTP proxy or you may just mention >>> this stream in SDP? >>> >>> ----- end quoted message ----- >>> >>> >>> _______________________________________________ >>> sipxtapi-dev mailing list >>> sipxtapi-dev@list.sipfoundry.org >>> List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/ >>> >> >> >
_______________________________________________ sipxtapi-dev mailing list sipxtapi-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
