Trixbox 2.8.0.2 setup with OCS

Hi guys, great to hear you're rolling up your sleeves and having a crack.

Ok - for my purpose, in that blog post, I wanted to pass calls from OCSTrixboxOutside world.

And to date, she's been working like a treat.

So my route rules that I created basically say "anything coming FROM OCS...send to OUTSIDE world" and visa versa.

From reading above, am I correct in assuming you want devices hanging off your Trixbox that you want OCS + potentially outside world to call.
e.g. phones, faxes etc???

If that's IS the case, then you'll need to play around with the route rules (from my perspective). I'm sure a Trixbox expert will fall back on the 95% of the other product features I didn't use.

Couple of things while you're testing all of this - when you hear "busy/can't connect..." etc. that's the phone's way of saying 'error' (it would be nice if it could say "IP address not found"...")

It is *essential* that while you're running your tests e.g. OCS->Trixbox etc. You need to SSH/Telnet onto the Trixbox and run a 'asterisk -r' session (I speak about this in my blog)

This gives you a view into what is going on when you make that call (something more than 'busy/error' signals) - so from this view we can work out:
- what is the actual number sent to Asterisk from OCS with an translations e.g. a dialled ext. number of 5050 might be sent to Trixbox as '+1 425 8808 5050'. What ever it actually *is* it's a good idea to know it - this also applies for calls coming in from external to Trixbox.

- if you suspect the error is on the OCS side, then have a look at this http://blogs.breezetraining.com.au/mickb/2009/09/27/WhatDoesOCSSe...

Let me know how you get on guys - I'm happy to help out where I can

Cheers,

Mick.