locked
Inbound calls from header user is not a valid number. RRS feed

  • Question

  • I am configuring Lync with a DMG 1000 Gateway, I have outbound calls working
    but for inbound im seeing something odd, iv never seen with SIP Trunks before.

    When the call comes into the Lync server, I see this in the Snooper

    TL_INFO(TF_COMPONENT) [2]24BC.2B34::10/28/2011-02:29:28.171.0022c25d (MediationServer,SessionCommon.GetOutgoingFromHeaderInfoInbound:sessioncommon.cs(1129))$$START-MEDIATIONSERVER
    MediationCall: 7af88e4d15234a4898765f345f03637f
    CallId: 01B2275B917900210000001B@pbxgw.domain.local
    From: sip:Anonymous@10.200.200.1:5060;user=phone
    To: sip:Anonymous@10.200.200.2:5060;transport=tcp
    Direction: Inbound
    Start-Line:  inbound call's from header user part is not valid number, use anonymous instead.
    $$END-MEDIATIONSERVER

    Then just below that i get this,

    TL_INFO(TF_COMPONENT) [2]24BC.2B34::10/28/2011-02:29:28.171.0022c260 (MediationServer,SessionCommon.ApplyOutgoingRequestURIRules:sessioncommon.cs(1204))$$START-MEDIATIONSERVER
    MediationCall: 7af88e4d15234a4898765f345f03637f
    CallId: 01B2275B917900210000001B@pbxgw.domain.local
    From: sip:Anonymous@10.200.200.1:5060;user=phone
    To: sip:Anonymous@10.200.200.2:5060;transport=tcp
    Direction: Inbound
    Start-Line: Invalid phone number for inbound call, pass it along.
    $$END-MEDIATIONSERVER


    Im not sure why the Dialogic is not passing the CID,

    I know this is more of a Dialogic issue then Lync, But i know there are some Dialogic Gurus around here, as the dialogic forums are no help.

    Thank you


    • Edited by Tim_MCP Friday, October 28, 2011 1:27 PM
    Friday, October 28, 2011 1:27 PM

Answers

  • Its actually an issue with Bell Canada, they are not forwarding the information correctly. So as a bypass i just set the destination caller ID number in the routing table as the clients primary number. everything is working.

     

    Thanks!

    • Marked as answer by Tim_MCP Tuesday, December 6, 2011 2:39 PM
    Tuesday, December 6, 2011 2:38 PM

All replies

  • Dear friend,

       i think your correct you have to match the configuration gateway side and also SIP Trunk Provider. If i explain  this to you, gateway should identify the Signalling from ISP Side and it pass to Mediation Server.

       Better to check with Dialogic Engineer and trace the dialogic In/Out then you can find the problem. 


    Madushka Dias : MCITP(Lync Server 2010 Administrator) & MCTS - Active Directory) - http://uctechi.blogspot.com/ | Live - madushka@live.com | If got your answer don't forget to Rate as an Answer
    Saturday, October 29, 2011 5:40 PM
  • Hi,

    From: sip:Anonymous@10.200.200.1:5060;user=phone
    To: sip:Anonymous@10.200.200.2:5060;transport=tcp

    is this how you see in the trace? it does not carry the source number and the destination number at all. 

    Run a trace from the Gateway and check whether the PSTN Provider pass the information. If so then run a Wireshark on the mediation server and check whether the Gateway is passing the information. i believe this is due to some mis-configuration in the Gateway.

    Thamara.

    Saturday, October 29, 2011 5:50 PM
  • Hi,

    how have you configure the sipcontrol software in the dmg. It looks like you have not configure the conversion from normal numbers to E.164.

    Have you setup the dialplan or addresmaps on the DMG?


    regards Holger Technical Specialist UC
    Monday, October 31, 2011 7:32 AM
  • Thanks for the reply's. I have got it mostly working. Now i can see the Caller's Caller ID show up int the Dialogic logs. had to change the Central Office CID Alert Type, but the destination dialed number is still not being displayed, when i look in the Dialogic Logs, it shows no other information other then the Caller ID Number and Name. I have spoken with Bell Canada, and they confirmed they are passing the info.

    For a device that is on the Lync OIP list it shure doesent have much documentation on configuring it with Lync.

    Monday, October 31, 2011 1:08 PM
  • Run the wireshark in Mediation server and check whether your able to see the Invite message To Lync user Line URI. if you able to see that, make sure it's in E.164 fromat and also you have populated the Telephone number Field of the users AD Account.

    Thamara.

    Monday, October 31, 2011 1:30 PM
  • Hi Tim,

    You could get more info from here.

    In addition, provide some Lync and Dialogic Troubleshooting Tips for reference. Hope it’s useful.

    Tuesday, November 1, 2011 5:54 AM
  • Its actually an issue with Bell Canada, they are not forwarding the information correctly. So as a bypass i just set the destination caller ID number in the routing table as the clients primary number. everything is working.

     

    Thanks!

    • Marked as answer by Tim_MCP Tuesday, December 6, 2011 2:39 PM
    Tuesday, December 6, 2011 2:38 PM