Auto Attendent does not work

• Question

• 

  

  0

  Sign in to vote

  We're testing with OCS in combination with Exchange UM. The strange is that mailbox access will work but the Auto Attendent doesn't work.

   

  Here's a trace which we made via the communicator:

   

  A SIP request made by Communicator failed in an unexpected manner (status code 80ef01e0). More information is contained in the following technical data:
   
   RequestUri:   sip:+31302475000@ocs.local;user=phone
  From:         sip:GPeppard@ocs.local;tag=966054911b
  To:           sip:+31302475000@ocs.local;user=phone;tag=391C08B8DB0D4A78BEE5EA74E68169BA
  Call-ID:      ca5ebd7e94a646108d89e675d938ef45
  Content-type: application/sdp;call-type=audiovideo

  v=0
  o=- 0 0 IN IP4 192.168.9.154
  s=session
  c=IN IP4 192.168.9.154
  b=CT:99980
  t=0 0
  m=audio 31104 RTP/AVP 114 111 112 115 116 4 8 0 97 101
  k=base64:ghiPNMPJYBT+PBwyZpJDZbIpstqHo/swmQhlZ1Hicgko12AW9q5WcXcR1DB3
  a=candidate:iM98s3JjjcYc5MMw4BUfM6/BzHHzxpVI5mIaTYUBZbg 1 eFubSCjqDpndqzLy3UtmyQ UDP 0.840 192.168.9.154 31104
  a=candidate:iM98s3JjjcYc5MMw4BUfM6/BzHHzxpVI5mIaTYUBZbg 2 eFubSCjqDpndqzLy3UtmyQ UDP 0.840 192.168.9.154 64768
  a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:my60Jd+tWT0+z3GE1rbOVTKh5vyUl1Mw0w0P+lHJ|2^31|1:1
  a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:gLnTOfOP1yXjtOGR3/73ecouVvnKeuimvjF1Htnp|2^31|1:1
  a=maxptime:200
  a=rtcp:64768
  a=rtpmap:114 x-msrta/16000
  a=fmtp:114 bitrate=29000
  a=rtpmap:111 SIREN/16000
  a=fmtp:111 bitrate=16000
  a=rtpmap:112 G7221/16000
  a=fmtp:112 bitrate=24000
  a=rtpmap:115 x-msrta/8000
  a=fmtp:115 bitrate=11800
  a=rtpmap:116 AAL2-G726-32/8000
  a=rtpmap:4 G723/8000
  a=rtpmap:8 PCMA/8000
  a=rtpmap:0 PCMU/8000
  a=rtpmap:97 RED/8000
  a=rtpmap:101 telephone-event/8000
  a=fmtp:101 0-16
  a=encryptionptional

  
  Response Data:

  183  Session Progress

  
  181  Progress Report
  ms-diagnostics:  13007;reason="Request was proxied to an application.";source="ocsstd.ocs.local";targetApp="exumCS.ocs.local:autoattendent";appName="InboundRouting"

  
  101  Diagnostics
  ms-diagnostics:  15009;reason="Routing to UM for Auto-Attendant";source="ocsstd.ocs.local";dialplan="OCS.ocs.local";umserver="ad01.ocs.local";aaname="autoattendent";appName="ExumRouting"

  
  480  Temporarily Unavailable
  ms-diagnostics:  13001;reason="The routing rules did not result in a suitable final response";source="ocsstd.ocs.local";received="403";appName="InboundRouting"

   
   Resolution:
   If this error continues to occur, please contact your network administrator. The network administrator can use a tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit in order to interpret any error codes listed above.

  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

   

  Anybody has seen this issue before ?

   

  Regards,

   

  Johan

  Wednesday, June 18, 2008 3:27 PM