locked
Caller ID OCS R2 RRS feed

  • Question

  • Is there anyway to strip the +1 from the originating caller number in the OCS?  Our PBX sees this as a private number sending out the main bill number on the caller id. Thanks
    Monday, August 24, 2009 3:52 PM

All replies

  • You can strip "+" on the Mediation server before it is send to the PBX/Gateway. Be advice that the procedure to enable this differs on both 2007 and 200 R2.

    To remove "1" you must use the manipulation table on your PBX/Gateway.

    Drago
    Monday, August 24, 2009 4:26 PM
  • Stripping off the + will change the originating number?

    Tuesday, August 25, 2009 11:45 AM
  • Here is an example of what hapens with "+" stripped on the mediation side:

    TL_INFO(TF_PROTOCOL) [2]0128.0ADC::08/25/2009-13:23:10.268.0000002f (MediationServer,GatewaySDP.GetOffer:gatewaysdp.cs(188))( 00000000037010CA )$$START-MEDIATIONSERVER
    MediationCall: 728b5376b67c4666890602cbf6d02d9d
    CallId: a9aa9099-9a3c-428c-9872-e3dcedf3f899
    From: sip:14783874390@milmed01.gmc.cc.ga.us;user=phone
    To: sip:14782512197@10.0.40.27;user=phone
    Direction: Outbound
    Start-Line: Send INVITE to Gateway with SDP: v=0
    o=- 5689 1 IN IP4 10.0.40.27
    s=session
    c=IN IP4 10.0.40.27
    b=CT:1000
    t=0 0
    m=audio 60960 RTP/AVP 97 101 13 0 8
    c=IN IP4 10.0.40.27
    a=rtcp:60961
    a=label:Audio
    a=rtpmap:97 RED/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=rtpmap:13 CN/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=ptime:20
    $$END-MEDIATIONSERVER

    Note FROM and TO fileds are not E.164 compilant.

    Any further manipulation must be done on the PBX/Gatew side.

    Drago
    Tuesday, August 25, 2009 2:04 PM
  • hi
    Any update for your issue?


    Regards!
    Friday, September 4, 2009 8:03 AM
    Moderator
  • Hi,
    The process for removing the + that Drago is talking about is only related to the "called" number - the number you are trying to reach. The "calling" number will not have the + stripped.

    If you want to manipulate the calling number, you'll either need to do that on your voice gateway (I've done this on NET, AudioCodes, Dialogic gateway). If you are doing a direct SIP connection to your PBX (like to call manager) you will need to use a translation pattern in CCM to change the "calling party transform mask" to XXXXXXXXXX (that's 10 xs - so it drops the leading +1 and leaves the rest of the number).

    I've had this same issue a few times, and solved it each time with either the gateway or PBX calling party transformations. Let me know what gateway you are using & I can point you in the right direction.

    Regards,
    Matt

    Matt McGillen, PointBridge - https://blogs.pointbridge.com/Blogs/mcgillen_matt/default.aspx
    Friday, September 4, 2009 6:13 PM
  • mmcgille

     

    There a many variations for number manipulation.

     

    The original question was about “originating caller number in the OCS”. Apparently zerodock’s PBX requires 10 digit number (NPA-NXX-XXX) in order to pass out the originating caller ID and if it is not this exact format, sends out the BTN instead. So the solution is to remove “+1”. This could be done either by stripping “+” on the mediation side AND “1” on PBX side before sending it to the trunk, or, by stripping “+1” on PBX on arrival.

     

    He must (or already does) adds “+1” when passing a number from PBX to Mediation or else OCS will return “404 Not Found”. This is in case OCS users are provisioned with E.164 number.

     

    However, there are some other possibilities J. If one populate TEL URI field with tel:+12345 and the PBX pass “+12345” to Mediation, the call will be connected. Furthermore, if Telephone Number property in AD is also populated with “+12345” and normalization rule is in place to add “+” to dialed “12345”, calls between two pure OCS endpoints are possible. Also, when an outbound call from an endpoint provisioned with “+12345” is placed in PSTN direction, the originating Caller ID is shown as …12345. I have tested this scenario.

    Drago

    Friday, September 4, 2009 10:50 PM
  • Hey Drago - I see what you're saying, now! Agreed, yeah: the mediation can strip the plus from both TO / FROM URIs, but the "1" needs to be handled by the gateway or PBX.  

    Regards,
    Matt


    Matt McGillen, PointBridge - https://blogs.pointbridge.com/Blogs/mcgillen_matt/default.aspx
    Saturday, September 5, 2009 3:11 PM
  • The recommeded way to strip the + within the OCS environment is to disable the WMI super class called “MSFT_SIPMediationServerConfigSetting”. Use the wbemtest.exe tool to enumerate the super class “MSFT_SIPMediationServerConfigSetting”, then selec the properties and select “RemovePlusFromRequestURI”. Change the value to True. 

    I have seen environments with Cisco 4.x where add a 'digit manipulation' rule in Audiocodes didnt strip the + from the number when it presented it to the CUCM.  I tried the WMI class and it worked.

    HTH

    J

    Sunday, September 6, 2009 2:23 AM
  • Hi all,

    If you have the OCS 2007 R2 Resource kit you can take a look at page 429 for an explanation around similar issues with "+" in phone numbers.

    /mk
    Monday, September 7, 2009 7:26 AM