none
Forward a DID to an outside line

    Question

  • I have a L3 SIP trunk.  We are porting over a toll-free number from another carrier.  We and L3 map that TF number to a DID on the SIP trunk.  We have a request to forward that TF number to an outside line.  So this isn't like a user going in a setting link to forward calls.  I wanted to know if I can somehow in Lync say this DID forwards to an outside (different) number?

    This is Lync 2013.

    Wednesday, July 24, 2013 8:21 PM

Answers

  • Hi Bez825,

    Since you have Direct SIP, the DID would have to terminate to a Response Group within Lync.  Then, you have the flexibility to do a number of tasks for an ingress call (open/closed actions, forward to another number, forward to another SIP URI, forward to another PSTN number, etc.)


    Please “Vote As Helpful” and/or “Mark As Answer” if this post helped you. Thanks!
    Adam Curry, UC Consultant, Unify Square Inc. (Blog, Twitter)
    Looking for Lync Users Groups in your area? Check out Lync Users Group

    Saturday, July 27, 2013 8:01 PM

All replies

  • Hi Bez825,

    So, there is a couple ways to go about this:

    1. If you have a SBC:

    Create a transformation of the incoming DID and send back out the SIP Trunk. This would need to be manually enabled/disabled when you would want the DID to be forwarded to an external number.

    2. If you are using Direct SIP integration or have a SBC:

    You will need to create a Response Group which the DID will terminate, then create a call forward based on a schedule. 


    Please “Vote As Helpful” and/or “Mark As Answer” if this post helped you. Thanks!
    Adam Curry, UC Consultant, Unify Square Inc. (Blog, Twitter)
    Looking for Lync Users Groups in your area? Check out Lync Users Group

    Thursday, July 25, 2013 4:39 PM
  • We have direct SIP....so how would you set up to use an outside # not defined to Lync?
    Friday, July 26, 2013 3:30 PM
  • Hi Bez825,

    Since you have Direct SIP, the DID would have to terminate to a Response Group within Lync.  Then, you have the flexibility to do a number of tasks for an ingress call (open/closed actions, forward to another number, forward to another SIP URI, forward to another PSTN number, etc.)


    Please “Vote As Helpful” and/or “Mark As Answer” if this post helped you. Thanks!
    Adam Curry, UC Consultant, Unify Square Inc. (Blog, Twitter)
    Looking for Lync Users Groups in your area? Check out Lync Users Group

    Saturday, July 27, 2013 8:01 PM
  • Depending on your SIP trunk provider you might be able to setup forwarding at the carrier level.
    Saturday, July 27, 2013 9:27 PM
  • Understood...however going thru the response group workflow seems tedious.  I have to create a group, a queue then the workflow.  I don't know what I need to put in there.  All I want is 1 DID that is defined with a SIP address to a PSTN #.  Even the PSTN # in the workflow is looking for a domain @something.  Can that be anything?
    Wednesday, July 31, 2013 3:58 PM
  • We are, working with the carrier though is not a overnight thing, it's taking a week to do this so I'd rather just handle it thru Lync.
    Wednesday, July 31, 2013 4:00 PM
  • Since you're on Lync 2013, you should be able to use inter-trunk routing to accomplish this.  Let's assume you want to forward 15552227777 to 15552228888:

    1. Create a PSTN usage/route combination that maps to 15552227777 and uses the SIP trunk for the route.
    2. Assign the PSTN usage to your incoming trunk
    3. On the same incoming trunk, create a called number translation to translate 15552227777 to 15552228888.

    What should happen is that calls to 15552227777 should get routed back out to the PSTN as 15552228888.  

    For an overview on setting up inter-trunk routing, look at my blog post on the subject: http://ucken.blogspot.ca/2013/06/inter-trunk-routing-in-lync-2013.html


    Ken Lasko | Lync MVP | http://UCKen.blogspot.com | http://LyncOptimizer.com


    • Edited by KenLaskoMVP Wednesday, July 31, 2013 6:22 PM
    Wednesday, July 31, 2013 5:48 PM
  • Thanks Ken but the destination is not a DID on the SIP trunk.  So it's like this :

    outside caller -> (carrier SIP with DID 571111111 into our Lync 2013 system) forwards to outside carrier # not on the SIP trunk 44311111111.

    We own the 571#, we do not own the 443#.


    • Edited by bez825 Wednesday, July 31, 2013 6:20 PM
    Wednesday, July 31, 2013 6:20 PM
  • Yeah, I get that.  But you'll be forwarding the call to the 443 number via the SIP trunk, correct?  I've clarified my original post to say that the usage/route combo should use the SIP trunk for the outbound call route.


    Ken Lasko | Lync MVP | http://UCKen.blogspot.com | http://LyncOptimizer.com


    • Edited by KenLaskoMVP Wednesday, July 31, 2013 6:23 PM
    Wednesday, July 31, 2013 6:21 PM
  • Right...comes in on the SIP trunk into Lync and Lync sends it back out the same SIP trunk, or another if I want, to the carrier.

    So I have a route match for the inbound DID being called (the 571 #).  I can route it out to the gateway.  But where do I tell it to forward to the 443#?

    Sorry if I'm not following you 100%...this is new to me....confusing as you can see.  I do appreciate ur help.

    Wednesday, July 31, 2013 6:33 PM
  • You create a trunk translation rule that changes the called number from the 571 number to the 443 number.  Haven't tried it myself specifically for this circumstance, but I don't see any reason why it wouldn't work.

    Ken Lasko | Lync MVP | http://UCKen.blogspot.com | http://LyncOptimizer.com

    Wednesday, July 31, 2013 6:38 PM
  • Oh boy Ken, now you got me interested  in seeing if inter-trunk hairpin routing on Lync Server 2013 will work.


    Please “Vote As Helpful” and/or “Mark As Answer” if this post helped you. Thanks!
    Adam Curry, UC Consultant, Unify Square Inc. (Blog, Twitter)
    Looking for Lync Users Groups in your area? Check out Lync Users Group


    • Edited by Adam Curry Thursday, August 01, 2013 2:25 AM spelling
    Thursday, August 01, 2013 2:25 AM
  • Yep, works like a charm.  I just tried it out myself.  Forwarded my office number to my mobile via inter-trunk routing.


    Ken Lasko | Lync MVP | http://UCKen.blogspot.com | http://LyncOptimizer.com

    • Proposed as answer by Adam Curry Monday, August 05, 2013 4:49 PM
    Thursday, August 01, 2013 3:08 AM
  • Ken...can you post screenshots of each piece that u need to set up?  Or my email me directly if possible.  I'd like to see this.
    Thursday, August 01, 2013 2:48 PM
  • I just created a blog post on the subject, with screenshots.

    http://ucken.blogspot.ca/2013/08/forwarding-calls-using-inter-trunk.html


    Ken Lasko | Lync MVP | http://UCKen.blogspot.com | http://LyncOptimizer.com

    Thursday, August 01, 2013 3:25 PM