When people start to build a new Microsoft PBX system such as Exchange + Lync, they always like to know how to quickly switch to new PBX, to get rid of their existing legacy PBX or old VOIP PBX during the migration and implement. SIP/2.0 481 Call leg/transaction does not exist SUBSCRIPTION-STATE: terminated reason=noresources REFERRED-BY: ms-identity=”MIIBPQYJKoZIhvcNAQcCoIIBLjCCASoCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHATGCAQkwggEFAgEBMGMwTDESMBAGCgmSJomT8ixkARkWAnVzMRwwGgYKCZImiZPyLGQBGRYMdGltZXN0ZWxlY29tMRgwFgYDVQQDEw90aW1lc3RlbGVjb20udXMCE3wAAAAkUVwbVSi7OiMAAAAAACQwCQYFKw4DAhoFADANBgkqhkiG9w0BAQEFAASBgA9yGTtnAmdjXH5nPx1GA4019h9xmnp2F0n9rEphRC01EtnQqQe7iqFsiFrCHoaVSDjxB+19HpURIi09JrAGF2N20ogAfL6qbcdLd4jhq5kF84g9NEeO1adw/cLesaT+1h8Hyb9DeaLSQus+o0YAKZYDfBXNJCWtFDPwh2RtzCgv:Sun, 22:16:20 GMT” ms-identity-info=”sip::5066 transport=Tls” ms-identity-alg=rsa-sha1 VIA: SIP/2.0/TLS .124:43749 branch=z9hG4bKc9903f12ĬONTACT: automata text audio video image After searching online, I just changed ‘REFER Support’ to something else instead of ‘Enable sending REFER to the gateway’. In fact, tracing back to last few SIP messages, I knew Exchange found correct SIP URI extension and tried to send it to Lync “ REFER-TO: “.Īt beginning, I thought the problem was caused by Exchange REFER feature and I never thought about Lync at all.
Open C:\windows\tracing\S4.txt, for my case, the major part is at bottom part and I saw Lync 2013 rejected extension call by rerunning “ SIP/2.0 481 Call leg/transaction does not exist“. \OCSTracer.exe format /LogFilePath:C:\windows\tracing\S4.etl /OutPutFile:C:\windows\tracing\S4.txt \OCSTracer.exe stop /* run it and bext after test call is done \OCSTracer.exe start /Component:S4 /*run it before the test call to Exchange Auto Attendant’ When Exchange 2013 AA is not able to connect to a extension, the common trace tool in Exchange server is Ocstracer.exe under “C:\Program Files\Microsoft UCMA 4.0\Runtime\Tracing”Ĭd “C:\Program Files\Microsoft UCMA 4.0\Runtime\Tracing”
Exchange cannot connect to extension (no matter Lync client or phone) after caller enters extension or person’s name.Īs long as we have deployed UM and AA by having donesuccessfully following, the most cost common problem is ‘REFER Support’ option. Both of them are equipped with Microsoft text-to-speech which listens to caller and asks for users caller looks for, reads email or person’s name to a user who like to call UM and listen missed call or email.Īs I searched from online, many people experienced connection problem of either UM or AA to extension or from extension.įor example, Lync client 2013 is not able to connect to UM by holding 1. After the message plays, callers are forwarded to the receptionist or operator, or they can return to the main menu.Įxchange 2013 has 2 different kind of applications working with Lync 2013 together, Unified Messaging (UM) and Auto Attendant (AA). Some auto attendant systems use message-only information menus and voice menus so an organization can provide business hours, directions to the premises, information about job opportunities, and answers to other frequently asked questions. In many auto attendant systems, a receptionist or operator can be reached by pressing or saying zero. In telephony or Unified Messaging environments, an automated attendant or auto attendant menu system transfers callers to the extension of a user or department without the intervention of a receptionist or an operator.
0 kommentar(er)
