Search results for query: *

Restarting the IP Office service on the SE resolved this. Thank you!

Thank you Derfloh It's connected and green in the Solution - Here is the license Form - If it was firewall, what would I have the customer look for in their firewall?

As you could see from the one snip that the time was off on the Mexico IP500, but that has been resolved now. Time is poling good. License errors remain. Thank you,

I tried running the initial configuration and also regenerated a new PLDS license and neither of these resolved the issue

SE - IP500 Expansion in Mexico - IP500 Expansion in US -

No. I do see a System ID has changed: You must acquire a license based on the new System ID days remaining 24, but this was 20 days ago and it's in black not red. The other IP500 expansion had license errors on 11/14 but those have cleared and it shows a valid SE license that expires -...

Should I run the initial configuration again?

Using PLDS licensing not WebLM.

Installing SE R11.1.3.1 with 2 IP500 expansions. No calls were made on the expansion shipped to Mexico, yet I still get the message that the grace period has expired. The expansion is not getting the SE license or SIP trunks licenses from the server. How do I get it out of this Grace period...

Looks like I needed to disable Direct Media

I have a SE R11.1.3.1 with H.323 QSIG trunk to CM. We are trying to take an inbound call from CM with them inserting a 9 and routing it out the SIP trunks on the IP Office. All other calling is working fine and we are receiving the 9 + the number from CM on the H.323 trunk but getting Cause...

These are group mailboxes for supervisors to check if employees are calling in sick. I think I'll suggest the User Portal for them to make it easy to check and save messages.

I have a customer IP Office SE 11.1.3.1 that wants to manually set a mailbox password that is permanent and his users are not prompted to change when logging into their mailboxes. I think I know the answer to this questions, but have to ask just to make sure. Can this be done as an...

Figured it out. Per the Application notes for AT&T SIP with BE the RTP ports need to be changed. I changed it back to default and dial tone work now and the SIP trunks are also working. The AT&T engineer told me that they access any RTP port from 6000 - 65000.

Is this a know workaround for this issue? Something you've done before to get this working?

I tried disabling Media Security and the extension level as to not impact the SIP trunks and this didn't help, still no dial tone on J139s and 9600s.

Installing analog ports today, but they will be on an IP500 SE expansion I added Local Tones on the H.323 Extensions, but this didn't help. I'm wondering if I should tweak the security System > VoIP > VoIP Security. I set this up per the Application Notes for A&T SIP trunks with BE.

Menniss, mine is set the same as they are using AT&T SIP trunks and this is now the Application Notes say to configure keepalives.

The 9600s are H.323 but also have no dial tone

J139s display SIP Feature in SSA Telephone Type: Avaya J139 (SIP Feature) User-agent SIP header: Avaya J139 IP Phone 4.0.10.3.2 c81feaa2ee45 Part number is - 700513916 for the new J139s, some of them are reused from the CM