Search results for query: *

sbc with remote worker CES sbc allows cell phone to register as a station on cm and dial out with CLID of company ces allows techs to make a call, which actually gets PBX to call their cell, then calls other party, all while showing company CLID these are the easiest options as techs dont need...

as a start i would change all the signalling from CM / SM and AAM to TCP. Their is a requirement for a new TLS license now - so unless you have that, TCP would be the best. For all devices, the same protocol should be used end to end, so either all TCP or all TLS thanks

demanding; What you need is Avaya Client Applications. As per the installation guide blurb, this is a brief synopsis of what it is: Lync Integration is intended for a network environment where the Microsoft Lync Server is deployed. Lync Integration is a client side add-in to the Microsoft...

dclake - are you avaya appliances on System Platform or VMWare ? If you are on System Platfrom - you will need to set the WebLM host via CDOM - you enter it as https://<IP_ADDRESS>>:52233/WebLM/LicenseServer The URL will be the licensing address of System Manager For VMWare, this is dne via...

the cm profile for the station should be a regular SIP96X1 station type. This will allow you to also login another SIP station, or even a H.323 (which will still point to CM, not SM)

do you have an operator console? if so, would room cutoff allow you to block all outbound, but still allow incoming calls ?

ok so you posted details of CM dial plan. you need to check the SMGR dial plan too. this is the one that will pass MWI notify messages from SM to CM - without a 2XXX pattern in SMGR, you will experience this issue. as posted above, login to SMGR and review the setup of 1XXX and copy that for...

i assume you will be putting in Session Manager? if so, setting up a trunk between each CM to SM will allow you to do staged migration of the CM system. What you will need to do is initially keep all of your trunks on the old CM. then when a site is migrated to the new CM, if there is a...

Newglide; does your AAM connect to Session Manager or CM. As its HA, i would suspect its via Session Manager. As such, i recommend you need to create a dial plan in System Manager for 2XXX towards the CM entity. A review of the 1XXX pattern may give you an idea of how it needs to be setup...

Hi; From reading this post, i am guessing the purpose is to have the SBC and AMM setup a chain of trust based upon a common Certificate Authority. The SMGR is a Certificate Authority, so can sign a CSR generated on the SBC. For the chain of trust to be completed, you will need to generate a...

the avaya support site has a good tool to view the compatibility between the Avaya product suite: https://support.avaya.com/CompatibilityMatrix/Index.aspx have a look at the applications you require - its quite easy to use.

ok - bit of confusion... the mention of trunks was to try and show how different the two offerings of one-x mobile are. the SIP version will only use a trunk if the user makes a call outside of the PBX. If they simply call another user, or voicemail, then no trunks, but still all data for...

Yes, the SIP client will register do the Session Manager via two routes: 1 - if you are off the enterprise WIFI, then the client will register through the SBC to SM. This connection could be achieved via the data leg of the cellular phone, or via any WIFI network the cellular device is...

it would only need to be the CM application that has the certificate loaded. what issue are you seeing with TLS ? Have you reverted to TCP to isolate security?

Dave- check the support.avaya.com site avaya does support VMWare for most applications, and they have requirements documents that cover the sizing of each VM for each application. As a note - the two dell servers you list are very slim in terms of memory and processor etc, so highly unlikely...

kyle555 is correct: If your station is H.323 - then you must enter the credentials to login to the presence elements If your station is SIP - this happens automatically thanks

your title is a little misleading - direct sip indicates NO SM, but you appear to have SM. on the cm side - a 488 indicates potentially a codec issue. make sure the codecs being advertised in the SDP are available in the ip-codec-set in CM. it would be better to do your tracing on the SM via...

Wallot; 488 messages are errors relating to either party not liking part of the SDP (Session Description Protocol). You are correct in that the SDP will contain information relating to Codec negotiation. I find it odd that a list trace on the TAC shows no data for these calls. How about a list...

you will need to liaise with Avaya or an Avaya Business Partner to arrange the software.

if your issue is that a SIP phone cannot dial a H.323 phone, then the issue is in System Manager > Routing > Dial Patterns You may be missing a dial pattern that matches stations on CM. add a pattern, and point it to the entity for CM and see how this works.