Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

OPS on Off-PBX

Status
Not open for further replies.

sekitori

Technical User
Jun 27, 2006
253
NL
We have a number of Ascom i62 wifi sets that have OPS on their off-pbx mapping, where other extensions have EC500 to their cellphone.
This was installed by a third party but they cannot explain what it does and why it's necessary, just that is has to be there...

Needless to say that this was their last installation on our site......[banghead]

Can any of you explain this ?

Kind regards,
Sekitori
 
It seems to be similar to how SIP phones integrate with Session Manager. Basically, the Ascoms register to Session Manager. The SM integrates with CM over a trunk.

So, to explain off-pbx-station mapping - when a phone with EC500 enabled is called, CM sees that in off-pbx-station mapping and routes the call to that number external to CM, and would do so through AAR or ARS - the type of routing you use to get to trunks. In the case of EC500, it would be to your normal ARS route patterns, out the same trunks you use for normal outbound calling.

For the Ascoms, they would go to AAR. If you "list aar analysis" you'd probably see the extension ranges for those phones point to a route. That route points to a trunk. The other end of that trunk is Session Manager. The SM receives the call for that extension, and it then routes it to the phone.

That all being said, it could be a Session Manager, or perhaps an Ascom SIP gateway the phones register to. In any event, SIP devices do not connect directly to CM, and what you're describing sounds pretty close to the reference configuration for implementing them.

 
Okay, thanks Kyle555.

I'll check out the config guide.

The Ascom's are registered as 9600SIP sets, and have on the stationconfig page 6 a field that says SIP Trunk, which is also set to the trunknumber that routes to the Ascom Unite server.
Apparently the Ascoms need two routes to the same trunk ?
There's nothing special in the AAR/ARS for these sets, though....

The Ascoms we have at the moment are 'protectors' that have an alarm-button and use Ekahau for location determination.

I'm planning to use 'talkers' as VoWifi sets, if I get them to work [tongue]
These won't register to the Unite server...

Sekitori
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top