On Sun, 2008-09-14 at 09:31 -0500, voice wrote: > Can i get a second opinion about this Howto?
The procedure is correct as stated. However - it is incorrect to refer to the current builds as 'beta'. They are far to unstable to characterize as 'beta'. We are still very much in development; the current nightly builds are exactly that - nightly builds. Their purpose is to facilitate testing and make sure that we have not broken the build itself, and should not be considered for us in any production situation. > ----- Original Message ----- > From: "Tony Graziano" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Cc: <sipx-dev@list.sipfoundry.org> > Sent: Sunday, September 14, 2008 7:56 AM > Subject: Re: [sipX-dev] p-asserted Identy support is not as expected. > > > Install 3.10.2 stable from the ISO, then change the yum repo to the dev > version and yum update it to the dev version. > > >>> "voice" <[EMAIL PROTECTED]> 09/14/08 07:09 AM >>> > We are presently testing Grandsteams IP PBX GXE-5028. These device's > firmware > have a switch that turns off registration username and password info. > Otherwise nothing else to mess with. We have tested with a wide range of > Grandstream phones locally and remote. > > I guess it may be time again to down load your latest beta. Is there a > straight forward 3.11.6 install Howto for Centos5 available? > > ----- Original Message ----- > From: "Scott Lawrence" <[EMAIL PROTECTED]> > To: "voice" <[EMAIL PROTECTED]> > Cc: <sipx-dev@list.sipfoundry.org> > Sent: Saturday, September 13, 2008 10:33 AM > Subject: Re: [sipX-dev] p-asserted Identy support is not as expected. > > > > > > On Sat, 2008-09-13 at 08:31 -0500, voice wrote: > > > I don't know if this will offer any insight. > > > > > > We are using CommPartners and Broadvox both CLEC and ITSP's (SIP Trunk > > > provider).. > > > > > > They use two (2) ip addr's one for orgination and one for termination > > > > > > They expect the From to be in this form > > > > > > [EMAIL PROTECTED] only (IPaddr of the sipXbridge/sipX box) > > > > > > and will not accept [EMAIL PROTECTED] or any other contrivance. > > > > Our present mechanism can handle that just fine. > > > > > They will not provide any details to anyone (for security reason) how > > > they handle sip packetts after it hits their ITSP gateway, period. So > > > don't expect Nortel to help you with AT&T or anyother SIP Trunk > > > provider. > > > > We needn't concern ourselves with what happens inside their network; all > > we need is a solid specification of what has to happen at the PBX/ITSP > > interface. > > > > > > > > > > > > > _______________________________________________ > sipx-dev mailing list > sipx-dev@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > > > > _______________________________________________ > sipx-dev mailing list > sipx-dev@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev _______________________________________________ sipx-dev mailing list sipx-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
