none
Cannot call Exchange voicemail from Lync client RRS feed

  • Question

  • Dear all,

    new day, new never-seen-before issues. At a deployment I see errors, if users click on the call voicemail button. Such calls always fail. If locating UM SA contact object, and calling it, or calling the SA number via PSTN, system lets user to enter into the OVA. I suspect the issue is with the built-in integration of Lync and ExUM, which bypasses UM authentication PIN code requirement.

    Event log:

    Log Name: Lync Server
    Source: LS UserPin Service
    Date: 09/06/2011 19:46:21
    Event ID: 47055
    Task Category: (1044)
    Level: Warning
    Keywords: Classic
    User: N/A
    Computer: SV-CYLYNCINT.cy.DOMAIN.com
    Description:
    GetAndPublish web service failed due to an internal error

    Request Details - Entity: [user1@DOMAIN.com], Device Id: [{A7C394D3-99CB-5D24-A361-4865A9D4421B}], Authenticated User: [sip:user1@DOMAIN.com].
    Cause: This is an unexpected failure
    Resolution:
    Re-start the web server. If you see this error continuously, examine the server traces and contact product support.
    Event Xml:
    ">http://schemas.microsoft.com/win/2004/08/events/event">
    47055
    3
    1044
    0x80000000000000
    1084112
    Lync Server
    SV-CYLYNCINT.cy.DOMAIN.com
    user1@DOMAIN.com
    {A7C394D3-99CB-5D24-A361-4865A9D4421B}
    sip:user1@DOMAIN.com



    Calling via the dedicated voicemail button in Lync client:

    SIPSTACK trace on Front end:

    TL_INFO(TF_PROTOCOL) [1]1E3C.0F84::06/09/2011-13:12:56.022.00004c11 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 3424051562
    Instance-Id: 000001B7
    Direction: incoming
    Peer: 10.3.60.73:26692
    Message-Type: request
    Start-Line: INVITE sip:user1@DOMAIN.com;opaque=app:voicemail SIP/2.0
    From: ;tag=5b80826305;epid=04e6604476
    To:
    CSeq: 1 INVITE
    Call-ID: 9f6c871fe70d4b7f8bc51c05e434b126
    Via: SIP/2.0/TLS 10.3.60.73:26692
    Max-Forwards: 70
    Contact:
    User-Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)
    Supported: ms-dialog-route-set-update
    Ms-Conversation-ID: Acwmpmozddc9/D/tTKedV11hOMyAcQAAIjGQ
    Supported: timer
    Supported: histinfo
    Supported: ms-safe-transfer
    Supported: ms-sender
    Supported: ms-early-media
    Supported: 100rel
    ms-keep-alive: UAC;hop-hop=yes
    Allow: INVITE, BYE, ACK, CANCEL, INFO, UPDATE, REFER, NOTIFY, BENOTIFY, OPTIONS
    ms-subnet: 10.3.60.0
    Accept-Language: en-US
    ms-endpoint-location-data: NetworkScope;ms-media-location-type=Intranet
    Ms-Exchange-Command: skip-pin
    P-Preferred-Identity: ,
    Supported: replaces
    Supported: ms-conf-invite
    Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="F2212B2E", targetname="sip/SV-CYLYNCINT.cy.DOMAIN.com", crand="2cc0a18f", cnum="29", response="040400ffffffffff00000000000000003460f9cd7a985e23610cbb35"
    Content-Type: multipart/alternative;boundary="----=_NextPart_000_08F1_01CC26C0.1854AAC0"
    Content-Length: 2946
    Message-Body: ------=_NextPart_000_08F1_01CC26C0.1854AAC0
    Content-Type: application/sdp
    Content-Transfer-Encoding: 7bit
    Content-ID: <6db47ab8804c4366b3671caa07611c7a@DOMAIN.com>
    Content-Disposition: session; handling=optional; ms-proxy-2007fallback
    v=0
    o=- 0 0 IN IP4 10.3.60.73
    s=session
    c=IN IP4 10.3.60.73
    b=CT:99980
    t=0 0
    m=audio 32116 RTP/SAVP 114 9 112 111 0 8 116 115 4 97 13 118 101
    a=candidate:tRHGYkLroVBXfVVv7ytGfWpP6kG82mefT2gWsg59G/Y 1 j7vvUmYQ7rsDg/BaNGgLxg UDP 0.830 10.3.60.73 32116
    a=candidate:tRHGYkLroVBXfVVv7ytGfWpP6kG82mefT2gWsg59G/Y 2 j7vvUmYQ7rsDg/BaNGgLxg UDP 0.830 10.3.60.73 32117
    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:4wEw0ExU9Np0rwYgIpHEW5qdBYq/dcQ3/VKhgxlf|2^31|1:1
    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:SWwZ1Nln5ZKZQZV0UAJCVfCp3+DQWRwejessbqRI|2^31|1:1
    a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:pjkVXu4uZdSsP0y08IDaYjFxOc8UVqPC8wC0OAcd|2^31
    a=maxptime:200
    a=rtpmap:114 x-msrta/16000
    a=fmtp:114 bitrate=29000
    a=rtpmap:9 G722/8000
    a=rtpmap:112 G7221/16000
    a=fmtp:112 bitrate=24000
    a=rtpmap:111 SIREN/16000
    a=fmtp:111 bitrate=16000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:116 AAL2-G726-32/8000
    a=rtpmap:115 x-msrta/8000
    a=fmtp:115 bitrate=11800
    a=rtpmap:4 G723/8000
    a=rtpmap:97 RED/8000
    a=rtpmap:13 CN/8000
    a=rtpmap:118 CN/16000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=encryption:required
    ------=_NextPart_000_08F1_01CC26C0.1854AAC0
    Content-Type: application/sdp
    Content-Transfer-Encoding: 7bit
    Content-ID:
    Content-Disposition: session; handling=optional
    v=0
    o=- 0 0 IN IP4 10.3.60.73
    s=session
    c=IN IP4 10.3.60.73
    b=CT:99980
    t=0 0
    m=audio 23668 RTP/SAVP 114 9 112 111 0 8 116 115 4 97 13 118 101
    a=ice-ufrag:GNNX
    a=ice-pwd:kbxc1At73gTTaeQOz7d6qNOY
    a=candidate:1 1 UDP 2130706431 10.3.60.73 23668 typ host
    a=candidate:1 2 UDP 2130705918 10.3.60.73 23669 typ host
    a=candidate:2 1 TCP-ACT 1684798975 10.3.60.73 23668 typ srflx raddr 10.3.60.73 rport 23668
    a=candidate:2 2 TCP-ACT 1684798462 10.3.60.73 23668 typ srflx raddr 10.3.60.73 rport 23668
    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:4wEw0ExU9Np0rwYgIpHEW5qdBYq/dcQ3/VKhgxlf|2^31|1:1
    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:SWwZ1Nln5ZKZQZV0UAJCVfCp3+DQWRwejessbqRI|2^31|1:1
    a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:pjkVXu4uZdSsP0y08IDaYjFxOc8UVqPC8wC0OAcd|2^31
    a=maxptime:200
    a=rtpmap:114 x-msrta/16000
    a=fmtp:114 bitrate=29000
    a=rtpmap:9 G722/8000
    a=rtpmap:112 G7221/16000
    a=fmtp:112 bitrate=24000
    a=rtpmap:111 SIREN/16000
    a=fmtp:111 bitrate=16000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:116 AAL2-G726-32/8000
    a=rtpmap:115 x-msrta/8000
    a=fmtp:115 bitrate=11800
    a=rtpmap:4 G723/8000
    a=rtpmap:97 RED/8000
    a=rtpmap:13 CN/8000
    a=rtpmap:118 CN/16000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=encryption:required
    ------=_NextPart_000_08F1_01CC26C0.1854AAC0--
    $$end_record

    TL_INFO(TF_DIAG) [1]1E3C.0F84::06/09/2011-13:12:56.053.000058b9 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
    LogType: diagnostic
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 100 Trying
    SIP-Call-ID: 9f6c871fe70d4b7f8bc51c05e434b126
    SIP-CSeq: 1 INVITE
    Peer: 10.3.60.73:26692
    Data: destination="user1@DOMAIN.com"
    $$end_record


    TL_INFO(TF_PROTOCOL) [1]1E3C.0F84::06/09/2011-13:12:56.053.000058c7 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 3424051562
    Instance-Id: 000001B8
    Direction: outgoing;source="local"
    Peer: 10.3.60.73:26692
    Message-Type: response
    Start-Line: SIP/2.0 100 Trying
    From: "USER1";tag=5b80826305;epid=04e6604476
    To:
    CSeq: 1 INVITE
    Call-ID: 9f6c871fe70d4b7f8bc51c05e434b126
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="F2212B2E", srand="D8C23AA7", snum="33", rspauth="040401ffffffffff0000000000000000b9b305607a7e46a09baff2bb", targetname="sip/SV-CYLYNCINT.cy.DOMAIN.com", realm="SIP Communications Service", version=4
    Via: SIP/2.0/TLS 10.3.60.73:26692;ms-received-port=26692;ms-received-cid=1D00
    Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FInterClusterRouting
    Content-Length: 0
    Message-Body: –
    $$end_record

    TL_ERROR(TF_DIAG) [1]1E3C.0F84::06/09/2011-13:12:56.067.00005d86 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(143))$$begin_record
    LogType: diagnostic
    Severity: error
    Text: Could not update Referred-By header
    Result-Code: 0x80070032
    SIP-Start-Line: INVITE sip:user1@DOMAIN.com;opaque=app:voicemail SIP/2.0
    SIP-Call-ID: 9f6c871fe70d4b7f8bc51c05e434b126
    SIP-CSeq: 1 INVITE
    $$end_record

    TL_INFO(TF_DIAG) [1]1E3C.0F84::06/09/2011-13:12:56.069.0000610f (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
    LogType: diagnostic
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 183 Session Progress
    SIP-Call-ID: 9f6c871fe70d4b7f8bc51c05e434b126
    SIP-CSeq: 1 INVITE
    Peer: 10.3.60.73:26692
    Data: destination="user1@DOMAIN.com"
    $$end_record

    TL_INFO(TF_PROTOCOL) [1]1E3C.0F84::06/09/2011-13:12:56.069.0000611d (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 3424051562
    Instance-Id: 000001BA
    Direction: outgoing;source="local"
    Peer: 10.3.60.73:26692
    Message-Type: response
    Start-Line: SIP/2.0 183 Session Progress
    From: "USER1";tag=5b80826305;epid=04e6604476
    To:
    CSeq: 1 INVITE
    Call-ID: 9f6c871fe70d4b7f8bc51c05e434b126
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="F2212B2E", srand="7DDA7D40", snum="34", rspauth="040401ffffffffff0000000000000000ae46dd5b911b63e89a426a60", targetname="sip/SV-CYLYNCINT.cy.DOMAIN.com", realm="SIP Communications Service", version=4
    Content-Length: 0
    Via: SIP/2.0/TLS 10.3.60.73:26692;ms-received-port=26692;ms-received-cid=1D00
    Ms-Forking: Active
    Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting(Microsoft Lync Server 2010 4.0.7577.139)
    Message-Body: –
    $$end_record

    TL_INFO(TF_DIAG) [1]1E3C.0F84::06/09/2011-13:12:56.069.00006265 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
    LogType: diagnostic
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 500 The server encountered an unexpected internal error
    SIP-Call-ID: 9f6c871fe70d4b7f8bc51c05e434b126
    SIP-CSeq: 1 INVITE
    Peer: 10.3.60.73:26692
    Data: destination="user1@DOMAIN.com"
    $$end_record

    TL_INFO(TF_PROTOCOL) [1]1E3C.0F84::06/09/2011-13:12:56.069.00006273 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 3424051562
    Instance-Id: 000001BD
    Direction: outgoing;source="local"
    Peer: 10.3.60.73:26692
    Message-Type: response
    Start-Line: SIP/2.0 500 The server encountered an unexpected internal error
    From: "USER1";tag=5b80826305;epid=04e6604476
    To: ;tag=A514104DB850C11C0C4BC9EE2DBD2D2D
    CSeq: 1 INVITE
    Call-ID: 9f6c871fe70d4b7f8bc51c05e434b126
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="F2212B2E", srand="2043FCB1", snum="35", rspauth="040401ffffffffff00000000000000000d3683df253e6869b1161f13", targetname="sip/SV-CYLYNCINT.cy.DOMAIN.com", realm="SIP Communications Service", version=4
    Via: SIP/2.0/TLS 10.3.60.73:26692;ms-received-port=26692;ms-received-cid=1D00
    ms-diagnostics: 1;reason="Service Unavailable";AppUri="http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting";reason="Failed when constructing the outgoing request";source="SV-CYLYNCINT.cy.DOMAIN.com"
    Server: RTC/4.0
    Content-Length: 0
    Message-Body: –
    $$end_record

    TL_INFO(TF_PROTOCOL) [1]1E3C.0F84::06/09/2011-13:12:56.254.000062ff (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 3424051562
    Instance-Id: 000001BF
    Direction: incoming
    Peer: 10.3.60.73:26692
    Message-Type: request
    Start-Line: ACK sip:user1@DOMAIN.com;opaque=app:voicemail SIP/2.0
    From: ;tag=5b80826305;epid=04e6604476
    To: ;tag=A514104DB850C11C0C4BC9EE2DBD2D2D
    CSeq: 1 ACK
    Call-ID: 9f6c871fe70d4b7f8bc51c05e434b126
    Via: SIP/2.0/TLS 10.3.60.73:26692
    Max-Forwards: 70
    User-Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)
    Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="F2212B2E", targetname="sip/SV-CYLYNCINT.cy.DOMAIN.com", crand="07702b9d", cnum="30", response="040400ffffffffff0000000000000000d44a71096272b789f37203f5"
    Content-Length: 0
    Message-Body: –
    $$end_record

    TL_INFO(TF_PROTOCOL) [1]1E3C.09A0::06/09/2011-13:12:56.450.0000656a (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 731503335
    Instance-Id: 000001C0
    Direction: incoming
    Peer: 10.3.60.73:26692
    Message-Type: request
    Start-Line: SERVICE sip:user1@DOMAIN.com SIP/2.0
    From: ;tag=639b2919ca;epid=04e6604476
    To:
    CSeq: 1 SERVICE
    Call-ID: e4faad719cfd4c889f93ce0128f4360a
    Via: SIP/2.0/TLS 10.3.60.73:26692
    Max-Forwards: 70
    Contact:
    User-Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)
    Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="F2212B2E", targetname="sip/SV-CYLYNCINT.cy.DOMAIN.com", crand="0f16211b", cnum="31", response="040400ffffffffff0000000000000000aac130ea4c5b27919d0055d4"
    Content-Type: application/msrtc-reporterror+xml
    Content-Length: 797
    Message-Body: ">http://schemas.microsoft.com/2006/09/sip/error-reporting">1;reason="Service Unavailable";AppUri="http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting";reason="Failed when constructing the outgoing request";source="SV-CYLYNCINT.cy.DOMAIN.com";OriginalPresenceState="0";CurrentPresenceState="0";MeInsideUser="Yes";ConversationInitiatedBy="0";SourceNetwork="0";RemotePartyCanDoIM="No"
    $$end_record

    TL_INFO(TF_DIAG) [1]1E3C.09A0::06/09/2011-13:12:56.452.00006870 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
    LogType: diagnostic
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 400 Bad request
    SIP-Call-ID: e4faad719cfd4c889f93ce0128f4360a
    SIP-CSeq: 1 SERVICE
    Peer: 10.3.60.73:26692
    Data: destination="user1@DOMAIN.com"
    $$end_record

    TL_INFO(TF_PROTOCOL) [1]1E3C.09A0::06/09/2011-13:12:56.452.0000687e (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 731503335
    Instance-Id: 000001C1
    Direction: outgoing;source="local"
    Peer: 10.3.60.73:26692
    Message-Type: response
    Start-Line: SIP/2.0 400 Bad request
    From: "USER1";tag=639b2919ca;epid=04e6604476
    To: ;tag=A514104DB850C11C0C4BC9EE2DBD2D2D
    CSeq: 1 SERVICE
    Call-ID: e4faad719cfd4c889f93ce0128f4360a
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="F2212B2E", srand="C96F53B0", snum="36", rspauth="040401ffffffffff00000000000000008ac256f1ef342683b9f79bd7", targetname="sip/SV-CYLYNCINT.cy.DOMAIN.com", realm="SIP Communications Service", version=4
    Content-Length: 58
    Via: SIP/2.0/TLS 10.3.60.73:26692;ms-received-port=26692;ms-received-cid=1D00
    ms-diagnostics: 4001;reason="XML parse failure";source="SV-CYLYNCINT.cy.DOMAIN.com"
    Content-Type: application/msrtc-fault+xml
    Server: RTC/4.0
    Message-Body:
    Client.BadCall

    $$end_record


    CU2 applied on server-side.

     

    Can this be the result of an incorrectly created Subscriber Access object in AD? I had an issue to create the object from OCSUMUTIL.exe (Access denied, when trying to create the object), even though I have Domain Admin permission for the install, but no access to Exchange. I believe this activity does not WRITE exchange attributes.

    I had to pre-create the contact object by hand. After this activity, the OCSUMUTIL.exe was able to provision the previously created AD contact object for the SA purpose. Or at least it seemed so.

    However, I am not sure, if the pre-created AD contact object was a proper one, it may have additional attributes created by default, which may break the integration. The "otherIPphone" value properly contains the EXUM GRUU, other than that I have no idea, what else may be required for this contact object. It was obviously completely different from the contact object I have in another deployment (this pre-created one had home-pool, and sip address, while the other properly created one didnt).

    Wednesday, June 15, 2011 1:13 PM

Answers

  • Fixed, was a certificate issue: signature hash algorithm was not sha1RSA, but something else. Alsways make sure signature hash algorithm is sha1RSA, othwerwise you will suffer... literally!
    • Marked as answer by Rich.Pa Saturday, March 3, 2012 1:12 PM
    Saturday, March 3, 2012 1:12 PM

All replies

  • It is also important to use a certificate on the exchange um server from the root ca and not the self signed certificate. Look into the evenetlog of the Lync and Exchange UM server after you call the um server for more error information.

    Is the Exch UM dialplan configured right?


    regards Holger Technical Specialist UC
    Thursday, June 16, 2011 9:25 PM
  • Hi,Richard,

    There might be some misconfiguration on certificate,Exchange UM dial plan or DNS records.

    Would you please check your integrated configuration step-by-step with the guide written by Jeff Schertz?

    http://blog.schertz.name/2010/11/lync-and-exchange-um-integration/

    Regards,

    Sharon


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, June 17, 2011 6:48 AM
    Moderator
  • Hi,Richard,

    Have you fixed your issue?

    Any updates please kindly let us know.Thanks!

    Regards,

    Sharon


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, June 23, 2011 9:48 AM
    Moderator
  • Hi,

    unfortunately no good news: it still does not work!

    Core exchange and Lync infra is correct, all certificates are proven to be correct. (I can call the UM SA number via the deplyoed PSTN gateway: the call is routed to Lync, Lync recognizes the destination number as "Subscriber Access" and re-routes the call to Exchange UM, Exchange UM connects the Welcome greeting, so far so good).

    All the validation utilities I could find in Lync shows "green" light, still nobody can call the voicemail from Lync / calls forwarded to Exchange are dropped.

    "get-csexumcontact" --> all the output seems valid

    OCSUMUTIL --> no error, no red excalamation mark, I even resolved the non-identical Lync dialplan name and EXUM dialplan FQDN conflict as well.

    What I have experienced, that none of the 250 user has client certificate in the Lync system, get-csclientcertificate results with 0.. Can be related, or not, I have no idea.



    Friday, July 29, 2011 2:41 PM
  • Anybody, any ideas? That is #1 hit on Google for "Could not update referred-by header".. :) I am desperate
    Thursday, August 11, 2011 1:57 PM
  • Fixed, was a certificate issue: signature hash algorithm was not sha1RSA, but something else. Alsways make sure signature hash algorithm is sha1RSA, othwerwise you will suffer... literally!
    • Marked as answer by Rich.Pa Saturday, March 3, 2012 1:12 PM
    Saturday, March 3, 2012 1:12 PM
  • I found that on exchange server 2007 and 2010, after the ExchUcUtill script is run, the "1:1" gateway port has to be configured to use port 5061. this is done by using the command set-UmIpGateway -identity 1:1 -port 5061". Hope this helps people out!

    Supporting Article http://technet.microsoft.com/en-us/library/aa996577.aspx

    Tuesday, March 6, 2012 11:18 PM
  • I found that on exchange server 2007 and 2010, after the ExchUcUtill script is run, the "1:1" gateway port has to be configured to use port 5061. this is done by using the command set-UmIpGateway -identity 1:1 -port 5061". Hope this helps people out!

    Supporting Article http://technet.microsoft.com/en-us/library/aa996577.aspx

    I have never faced such an issue, to manually correct the work of the script.
    Wednesday, March 7, 2012 6:34 AM