locked
Can not call from UCM6.1 via SIP trunk to MOC client, but MOC Client can call out. RRS feed

  • Question

  • I've just had this dropped onto me and am in over my head.  Any help would be appreciated.

    We have outbound calling from an MOC client to the PSTN via the SIP trunk working fine, but from a UCM phone we can not call into a MOC client.

    I am sending 10 digits across the SIP trunk from the UCM server, and am seeing them come in on a log file trace on the mediation server.

    Here is a trace from a failed call:
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.631.0000023e (OutboundRouting,OutboundRoutingTransaction.constructor:outboundroutingtransaction.cs(194))Creating a OutboundRoutingTransaction object (160)
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.631.0000023f (OutboundRouting,OutboundRouting.OnRequest:outboundrouting.cs(242))( 0000000000B38324 )Enter
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.631.00000240 (OutboundRouting,Settings.ProcessPendingWmiEvents:settings.cs(941))( 000000000004B0B6 )Enter.
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.631.00000241 (OutboundRouting,OutboundRoutingDispatcher.OnRequest:outboundroutingdispatcher.cs(124))( 0000000001C6F509 )From uri: 4164;phone-context=dialstring@info.customer.com
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.631.00000242 (OutboundRouting,OutboundRoutingDispatcher.OnRequest:outboundroutingdispatcher.cs(125))( 0000000001C6F509 )From User Uc Enabled: False
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.631.00000243 (OutboundRouting,OutboundRoutingDispatcher.OnRequest:outboundroutingdispatcher.cs(126))( 0000000001C6F509 )From User Policy: <null>
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.631.00000244 (OutboundRouting,OutboundRoutingDispatcher.OnRequest:outboundroutingdispatcher.cs(136))( 0000000001C6F509 )Referrer URI: <null>
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.631.00000245 (OutboundRouting,OutboundRoutingDispatcher.OnRequest:outboundroutingdispatcher.cs(138))( 0000000001C6F509 )IsAvMCUDialOut: False
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.631.00000246 (OutboundRouting,OutboundRoutingDispatcher.OnRequest:outboundroutingdispatcher.cs(206))( 0000000001C6F509 )Applying From URI's outbound policy
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.631.00000247 (OutboundRouting,OutboundRoutingDispatcher.ApplyCallerPolicyAndRouteRequest:outboundroutingdispatcher.cs(589))( 0000000001C6F509 )Routing request based on caller: 4164;phone-context=dialstring@info.customer.com
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.631.00000248 (OutboundRouting,OutboundRoutingDispatcher.ApplyCallerPolicyAndRouteRequest:outboundroutingdispatcher.cs(592))( 0000000001C6F509 )Caller not UC enabled.
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.631.00000249 (OutboundRouting,OutboundRoutingDispatcher.DoMessageStampingNotUcEnabled:outboundroutingdispatcher.cs(536))( 0000000001C6F509 )Stamping request from non UC enabled user
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.631.0000024a (OutboundRouting,OutboundRouting.OnRequest:outboundrouting.cs(246))( 0000000000B38324 )Exit
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.913.0000024b (OutboundRouting,OutboundRoutingTransaction.constructor:outboundroutingtransaction.cs(194))Creating a OutboundRoutingTransaction object (161)
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.913.0000024c (OutboundRouting,OutboundRouting.OnRequest:outboundrouting.cs(242))( 0000000000B38324 )Enter
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.913.0000024d (OutboundRouting,Settings.ProcessPendingWmiEvents:settings.cs(941))( 000000000004B0B6 )Enter.
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.913.0000024e (OutboundRouting,OutboundRoutingDispatcher.OnRequest:outboundroutingdispatcher.cs(124))( 0000000001C6F509 )From uri: 6185556101;phone-context=dialstring@info.customer.com
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.913.0000024f (OutboundRouting,OutboundRoutingDispatcher.OnRequest:outboundroutingdispatcher.cs(125))( 0000000001C6F509 )From User Uc Enabled: False
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.913.00000250 (OutboundRouting,OutboundRoutingDispatcher.OnRequest:outboundroutingdispatcher.cs(126))( 0000000001C6F509 )From User Policy: <null>
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.913.00000251 (OutboundRouting,OutboundRoutingDispatcher.OnRequest:outboundroutingdispatcher.cs(136))( 0000000001C6F509 )Referrer URI: <null>
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.913.00000252 (OutboundRouting,OutboundRoutingDispatcher.OnRequest:outboundroutingdispatcher.cs(138))( 0000000001C6F509 )IsAvMCUDialOut: False
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.913.00000253 (OutboundRouting,OutboundRoutingDispatcher.OnRequest:outboundroutingdispatcher.cs(206))( 0000000001C6F509 )Applying From URI's outbound policy
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.913.00000254 (OutboundRouting,OutboundRoutingDispatcher.ApplyCallerPolicyAndRouteRequest:outboundroutingdispatcher.cs(589))( 0000000001C6F509 )Routing request based on caller: 6185556101;phone-context=dialstring@info.customer.com
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.913.00000255 (OutboundRouting,OutboundRoutingDispatcher.ApplyCallerPolicyAndRouteRequest:outboundroutingdispatcher.cs(592))( 0000000001C6F509 )Caller not UC enabled.
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.913.00000256 (OutboundRouting,OutboundRoutingDispatcher.DoMessageStampingNotUcEnabled:outboundroutingdispatcher.cs(536))( 0000000001C6F509 )Stamping request from non UC enabled user
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:47.913.00000257 (OutboundRouting,OutboundRouting.OnRequest:outboundrouting.cs(246))( 0000000000B38324 )Exit
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:53.131.00000258 (OutboundRouting,OutboundRoutingTransaction.constructor:outboundroutingtransaction.cs(194))Creating a OutboundRoutingTransaction object (162)
    TL_INFO(TF_COMPONENT) [0]1A30.1AA4::03/12/2009-22:13:53.131.00000259 (OutboundRouting,OutboundRouting.OnRequest:outboundrouting.cs(242))( 0000000000B38324 )Enter

    Any ideas?



    Update:  Got it working.
    • Edited by InthePipe Thursday, March 12, 2009 10:21 PM added log excerpt
    Thursday, March 12, 2009 10:08 PM

All replies

  • How?? I have the same problems on a MITEL 3300 CXI.
    Got outbound working but cannot for the life of me get incoming calls to route to the client.

    I have the same issues in the log as you had.

    Cheers
    Dean
    Tuesday, July 7, 2009 3:22 AM
  • Hi,
    have you tried to do some tracing on the SIP Stack on your Front End server to see if incoming call requests are actually getting routed towards your OCS infrastructure? This might give us further info on the problem.

    However, I do not know your environment background, but Cisco generally sends from and to URI's in non E.164 format (i.e. the '+' sign is not included) and thus OCS is unable to match the called  URI to an OCS user tel URI. You should have a normalization rule applied to your default location profile so that the called number can be translated to an existing user tel URI like this : ^(\d{10})$ --> +$1

    Regards
    George
    Thursday, July 9, 2009 6:11 AM