New system is : sipXconfig (4.2.1-018971.dhubler 2010-08-21T04:59:23 build37)
I thought for a moment that it might be because it's not been updated after building but it's the same as my prod servers. On Fri, 7 Jan 2011 10:13:43 -0500, Tony Graziano wrote: > what is your build number? > > On Fri, Jan 7, 2011 at 9:58 AM, [email protected] <[email protected]> wrote: >>> Alarm Text: SipXproxy could not allocate the Media Relay Session >>> required for a call likely resulting in speech >>> path issues. Suggested Resolution: Not enough RTP ports are allocated >>> to the Media Relay. Increase the >>> RTP port range allocated to the Media Relay using sipXconfig >>> (under System->Servers->(click on server)->NAT->Show Advanced Settings). >>> >> Brand new system, barely configures yet, sitting idle mostly, only one >> test account created along with superadmin, no gateway, no phones >> configured, it's basically a shell waiting to be completed. I did some >> quick registration tests and can register, had created a second User and >> was able to call ext to ext. >> >> All config tests pass, statistics compared to a working server are very >> similar, nothing out of the ordinary. >> >> Since it's not in use yet, what would cause it to send me such errors, >> about 50 of them around 2am last night. >> Searching google isn't leading to anything much which explains why this >> would happen. >> >> Mike >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
