MWI issue with Aura Messaging with SIP integration

[m50258]

Hi,

In our lab, we have SIP phones registering to a Session Manager and CM configured as a feature server. We also have Aura Messaging with SIP integration to the Session Manager (all at the most current software release). The solution works properly except for the MWI. Using the SIP trace viewer on Session Manager, we can see that Aura Messaging has sent the notify message to trun on the indicator, but Session Manager does not forward the message to the phone. It replies instead with "SIP/2.0 481 call or transaction does not exist". I have not found any application notes describing our configuration and I am wondering if one exists? I am also wondering if anyone else tried this scenario before? Thanks.

[ahmed1]

Hi,

I understand that you have SIP phones registering to Session Manager and also have CM working as a Feature Server.
Firstly, I think your SIP phone is not subscribing to the "Message-Summary" event package with Session Manager.

There are 5 event packages that the SIP phones (with CM features - OPTIM ext) gets subscribed to, while they are logging / Registering to Session Manager:

They are:

1. Reg (Registration)
2. Dialog
3. ccs-profile (for ppm functionality)
4. Message-Summary
5. CM features

If the SIP phones doesnt subscribe to the above event packages then any NOTIFY messages from other SIP entities would result in 481 Transaction does not exit error response code, as this is abvious.

I would firstly ask you to check if the Avaya SIP phone is set to "Avaya Environment = Auto". This will make the Avaya SIP phones to also subscribe to all events including MWI events.

Secondly, completely read the traceSM logs of the SIP phones getting registered to find clues of what is happening while registrations. Do you see and esclamation Mark (! in a triangle) on your SIP phone display. If so then the SIP phone is not registering and subscribing to all events.
In case you are not able to resolve the issue, please raise a ticket with Avaya Support and we shall assist you by looging into the logs.

Thanks,

Regards,

Sabir.

[jstasiek]

In the traceSM logs, are you seeing a "487 Proxy Authentication Error?" Also, are you able to perform an outcall, to the phone, using the "Diagnostics Application", from one of your Application Servers?

[mbacak]

Hi, please is some one whole document learning more about these procedures?
1. Reg (Registration)
2. Dialog
3. ccs-profile (for ppm functionality)
4. Message-Summary
5. CM features

I can see this messages during turn on sequences app (subscribe - notify), but I need to more undestand exactly understanding of points 1 to 5. I have got problem with error 484 address incomplete during sequence app (to CM) and why is first invite with same "from" and "to" field in traceSM? This error isnt critical for connection - it isnt interrupt connection, but error is note there.

Originally Posted by ahmed1

Hi,

I understand that you have SIP phones registering to Session Manager and also have CM working as a Feature Server.
Firstly, I think your SIP phone is not subscribing to the "Message-Summary" event package with Session Manager.

There are 5 event packages that the SIP phones (with CM features - OPTIM ext) gets subscribed to, while they are logging / Registering to Session Manager:

They are:

1. Reg (Registration)
2. Dialog
3. ccs-profile (for ppm functionality)
4. Message-Summary
5. CM features

If the SIP phones doesnt subscribe to the above event packages then any NOTIFY messages from other SIP entities would result in 481 Transaction does not exit error response code, as this is abvious.

I would firstly ask you to check if the Avaya SIP phone is set to "Avaya Environment = Auto". This will make the Avaya SIP phones to also subscribe to all events including MWI events.

Secondly, completely read the traceSM logs of the SIP phones getting registered to find clues of what is happening while registrations. Do you see and esclamation Mark (! in a triangle) on your SIP phone display. If so then the SIP phone is not registering and subscribing to all events.
In case you are not able to resolve the issue, please raise a ticket with Avaya Support and we shall assist you by looging into the logs.

Thanks,

Regards,

Sabir.

[rmcdou]

I found this, maybe is relevant.

MWI issue with Aura Messaging with SIP integration
June 5, 2011 07:24 AM (in response to Marc Juillet)
On signalling form IMS should be enabled for Feature server.
ALso, check your public-unknown numbering form, this should have correct entry for your extensions.
Choice of public / private unkown numbering will depend on your trunk group form settings.

[chal3o]

Are you able to perform an outcall, to the phone, using the "Diagnostics Application", from one of your Application Servers?







-------------------
GuL

[chal3o]

Are you able to perform an outcall, to the phone, using the "Diagnostics Application", from one of your Application Servers?


______________________
learnspanishonline.me www.learnspanishonline.me
leather jackets leather jackets
motorcycle leather jackets motorcycle leather jackets
646-365 questions 646-365 questions