Search results for query: *

I was able to find the answer. It turns out that having the MM SIP trunk to Avaya CM was a bad idea since it was not forwarding all of the SIP messages from MM to Cisco. I created a SIP trunk from MM to Avaya Session Manager and routed the calls to both Cisco and Avaya CM through it. That got...

I can enter "change node-names" on the PBX and my only options after that are IP or AUDIX. I cannot add anything as an MM type, however I doubt that would be the crux of the problem with getting the MWI across to an H.323 phone registered to the PBX.

I have verified that my setup is configured the same way as the document that you sent the link for with one exception. On page 11 the node name for the MM server is shown as having a type of MM instead of IP or AUDIX. That is not an option on my system. It is either IP or AUDIX.

That was my mistake. There is a default port group configured but it is only set to be used for PC Clients, Telephone User Interface, Call Me and FAX. It is not set to be used for MWI, but there is no option for that either. I cannot delete the port group and calls cannot reach the MM from CM if...

The only port group is used for PC Clients, Telephone User Interface, Call Me and FAX. None of the ports are being used for MWI.

There are 48 ports setup for MWI in the MM for the IP SIP Telephony Interface. Thank you for taking the time to help me with this.

I also performed a trace on the trunk group built between the PBX and MM. There was no activity on the trunk when MM sent the MWI and the trace timed out.

I understand what you are looking for now. I do get an error similar to what you are asking: ERROR NT significant event with ID '3221227238' was reported with strings 'Set\nXXXXXXX\nUnknown error\n' The following statement reads: MWI request to 'Set' the lamp has been called for extension...

The vmsc is the IP address of the processor on Avaya CM. Advanced logging is turned on for the system as well. Here is the error I receive: 146816921 FINE 00E60 mwiserver [Undefined] CMWIServiceWrapper OnChange.MAS1-AES-LAB Operation failed due to transient error, request will be retried...

The only trunking for MWI is between the CM and MM. I do not have the licensing on MM to support a multi-PBX environment.

When I run a trace on the SIP trunk between CM and MM there is nothing. When I run a trace on the hunt group extension I also get nothing. Is there something else that needs a trace run on it?

Hello, I am trying to configure my MM 5.2 system to work with my Cisco CUCM system. The MM has a SIP trunk configured to CM 6. CM has a SIP trunk to CUCM Session Manager. Session Manager has a SIP trunk to CUCM. Call flow is Avaya phone thru SM to CUCM/VM pilot back to Avaya CM thru SM and...