Aleksey Beregov wrote: > We have discovered that there is a hard coded limit of 10 on the number of > simultaneous calls in SIPXTAPI. > How was this number determined and why is it hard coded? > > pInst->pCallManager = new CallManager(FALSE, > pInst->pLineManager, > TRUE, // early media in 180 ringing > pInst->pCodecFactory, > rtpPortStart, // rtp start > rtpPortEnd, // rtp end > localAddress.data(), > localAddress.data(), > pInst->pSipUserAgent, > 0, // sipSessionReinviteTimer > NULL, // mgcpStackTask > NULL, // defaultCallExtension > Connection::RING, // availableBehavior > NULL, // unconditionalForwardUrl > -1, // forwardOnNoAnswerSeconds > NULL, // forwardOnNoAnswerUrl > Connection::BUSY, // busyBehavior > NULL, // sipForwardOnBusyUrl > NULL, // speedNums > CallManager::SIP_CALL, // > phonesetOutgoingCallProtocol > 4, // numDialPlanDigits > CallManager::NEAR_END_HOLD, // holdType > 5000, // offeringDelay > "", > CP_MAXIMUM_RINGING_EXPIRE_SECONDS, > QOS_LAYER3_LOW_DELAY_IP_TOS, > 10, > sipXmediaFactoryFactory(NULL)); >
I have just made 16 simultaneous calls using my client, so its not really 10. When trying to make 17th simultaneous call, it gets blocked somewhere. If you look into call manager, you will see it just means that if there are more than 10 calls, it will send a BUSY_HERE SIP (486) message back to the sender on inbound call. I'm planning to revamp the whole sipxtapi, introduce new parameters like this. Jaroslav Libak _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
