microsoft exchange issues

[Plantman2000]

hi all
got a very weird problem with a recent vendor install.

we have a cs1k 5.5 network with 3 SMGs and a 1 core site, with each site having their own primary rate trks.
we have recently installed MS exchange on a 2007 server using sip trunking to the server, very occasionally we get the msg from the server "are you still there?" maybe this occurs once every 200 calls, no particular pattern or type of call, no events logged to the server,
all switches are running latest deplists etc and ms latest updates.
we r running 30 mg les ccts between sites and have no other issues with voice.
anyone had this before? we are stuck!

 

[sl1input]

I have had this.

What codec is your CS1k using alaw or mu law ?

By default the MS Ex will use Mu law, so if you Cs1k is Alaw then you may see issues, due to codec negotiation.

We changed the MS Ex box to use Alaw in the registry and this fixed.

----------

Whilst researching my issue i came across someone else with similar issue. Their fix was changing CS1k endpoint in NRS from static SIP to Dynamic.

This was not the fix for me as mine was all ready Dynamic.

 

[Plantman2000]

Thanks. Do you have the key handy?

 

[Plantman2000]

Found this....similar?

http://kevvo2000.blogspot.com/2009/11/ms-exchange-2007-and-nortel-cs1k-um.html

 

[sl1input]

Yes this is the same key.

 

[sl1input]

Did this fix?

 

[Plantman2000]

Well, after a bit of testing... NO it does not appear to have fixed the issue

I had users coming to me with about 4 instances of this yesterday.

 

[Plantman2000]

Is our current order of Codecs..

RTAudio16KHz
RTAudio8KHz
G.723.1(6.3)
G.711A
G.711u

 

[Plantman2000]

More development:

I can replicate the 'Are you still there?' message everytime with the following scenario:

Call in to my IP phone from say mobile and try to transfer the call to the Automated Attendant.

When prompted to say/spell the persons name I get the 'Are you still there?' message everytime.

The only way to successfully transfer the call is hitting # and dialling the end users extension.

Seems like a line or channel issue?

 

[sl1input]

Our issue was also with transfers into/out of auto attendant.

Did you restart the Exchange box - or the service after making the registry change?

Have you the latest CS and SS deplist installed?

Is your CS1k SIP endpoint registered using Dynamic registration?

 

[Plantman2000]

Yup, service restarted and also tried a box restart...

Latest deplists should be on....

CS1k SIP endpoint is RAS H.323 / Dynamic SIP / NCS

Cheers.

 

[Plantman2000]

We have also had this 'Are you still there' message when someone has tried to log in to their voiemail in order to change their greeting.

It gives the message when she was entering her PIN number...

 

[sl1input]

What codec are you using on SIP trunks?

Should be G711 20ms.

Also make sure you have latest patches on CS and SS and MS Ex (roll up packs).

There are a hand full of patches on the 5.5 SS that relate to Exchange UM that sound similar.

Ensure the latest deplists are installed the addition Ex UM SS patches. Then if still no joy, raise a Nortel TAC.

 

[sl1input]

Some more before you call Nortel,

If you can recreate the fault then observe the Sig Server CLI via telnet or serial to see the output when this occurs.

May be some indications from the CLI, i saw sipnpmxxxxxx etc errors relating.

Also check the MS exchange event logs for any suspects events.

Next i would run wireshark or similar on the MS Exchange box, then recreate the issue and look at trace.

I saw one occurrence of "unsupported media type" in my wireshark traces.

 

[Plantman2000]

No errors on the MS voice access server.

We have run wireshark....but what do we need to look for?

Noticed no 'unsupported media type' messages....

We got "488 Not Acceptable Here" but we got this on both a working trace...and a trace that had failed.

We also get "unrecognised sip header (UMWS-MESSAGE-ID"

I will attempt to observe the Sig Server CLI via telnet.

Thanks

 

[Plantman2000]

Just FYI we are still getting this message.