"So, it was not a typo......this time :o)" (as we all know TT (travelling Tony) had a few in the past days, I especially liked the "block everything access" http://forum.sipfoundry.org/index.php?t=msg&th=16656&goto=63334&S=58bc77940ab3597c4c454ca47645680d#msg_63334 )
I hope the new hard disk is a 3 TB disk. And it always happens on a friday! From: Philippe Laurent <[email protected]> To: Discussion list for users of sipXecs software <[email protected]> Date: 16-09-2011 15:15 Subject: Re: [sipx-users] CallCentric Limitations Sent by: [email protected] For those curious: "So it was not a typo????this time ?o?" Yeah, couldn't figure out the rest. Maybe braille typo? On Fri, Sep 16, 2011 at 8:53 AM, <[email protected]> wrote: Tony Graziano <[email protected]> wrote on 16-09-2011 14:28:08: > sorry traveling does that > On Sep 16, 2011 8:25 AM, "Michael Picher" <[email protected]> wrote: > > Thanks, the "Nehos from au andbe" that threw me. I can't understand why, > > it's perfectly clear. > > > > > > > > From: [email protected] > > [mailto:[email protected]] On Behalf Of Tony Graziano > > Sent: Friday, September 16, 2011 8:20 AM > > To: Discussion list for users of sipXecs software > > Subject: Re: [sipx-users] CallCentric Limitations > > > > > > > > Nehos is an isp and trunk provider"down under". > > > > callcentric has a unique us offering to au. all im suggesting is that there > > are alternatives. > > > > all you really needed to do was turn upside down to look at it because > > you're at the other end of the world from them. > > > > On Sep 16, 2011 8:17 AM, "Michael Picher" <[email protected]> wrote: > >> Could I get that last message in braille please? > >> > >> On Fri, Sep 16, 2011 at 8:08 AM, Tony Graziano > > <[email protected] > >>> wrote: > >> > >>> callcentric is not rfc3261 compliant. if you search the archives of the > >>> user list you'll see a lot of discussion to that end. > >>> > >>> I think the only thing they normally bring to the table are low rates > >>> australia. at the same time you could just get a truck with Nehos from au > >>> andbe done with that. > >>> On Sep 16, 2011 8:05 AM, "Tim Byng" <[email protected]> wrote: > >>> > I have found that transfers (blind or assisted) and conference calls do > >>> not > >>> > work either. Is this to be expected with CallCentric? If so, then I > > guess > >>> > they're not an option. > >>> > > >>> > All of this works as expected with voip.ms. > >>> > > >>> > Has anyone been able to get this to work with CallCentric? > >>> > > >>> > Regards, > >>> > Tim > >>> > > >>> > On Thu, Sep 15, 2011 at 3:11 PM, Tim Byng <[email protected]> wrote: > >>> > > >>> >> I was contemplating not putting CallCentric in the subject of this > >>> email, > >>> >> as I know they're generally not recommended with sipXecs and some of > > you > >>> may > >>> >> not even read this. However, I'm running out of options. I won't get > >>> into it > >>> >> here, but my choices are very limited, so if I can get CallCentric to > >>> work > >>> >> with sipXecs, I'm happy. > >>> >> > >>> >> So far I have the basics working. Both inbound and outbound calls seem > >>> to > >>> >> be working as expected (minus the inbound caller id name, but I've > > only > >>> >> tested one number so far). However, I just ran into a problem where an > >>> >> external line will not ring when I set a call forwarding rule for a > >>> user. > >>> >> Here are the scenarios: > >>> >> > >>> >> - OK: Landline -> voip.ms DID -> sipXecs -> internal extension -> > >>> >> voip.ms -> external number > >>> >> - OK: Landline -> callcentric DID -> sipXecs -> internal extension -> > >>> >> voip.ms -> external number > >>> >> - Not OK: Landline -> voip.ms DID -> sipXecs -> internal extension -> > >>> >> callcentric -> external number > >>> >> - Not OK: Landline -> callcentric DID -> sipXecs -> internal extension > >>> >> -> callcentric -> external number > >>> >> > >>> >> In all cases, the internal extension rings. However, when callcentric > > is > >>> >> used to forward the number, the external number does not ring. > >>> >> > >>> >> Is this a known issue with CallCentric? If someone was able to get > > this > >>> to > >>> >> work, what steps did you take? > >>> >> > >>> >> Are there any other limitations with CallCentric that I should know > >>> about? > >>> >> > >>> >> Regards, > >>> >> Tim > >>> >> > >>> > >>> _______________________________________________ > >>> sipx-users mailing list > >>> [email protected] > >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > >>> > >> > >> > >> > >> -- > >> Michael Picher > >> eZuce > >> Director of Technical Services > >> O.978-296-1005 X2015 > >> M.207-956-0262 > >> @mpicher <http://twitter.com/mpicher> > >> www.ezuce.com > > _______________________________________________ > 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/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
<<image/gif>>
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
