Session Manager to Lync Routing question 1

[heathersuzanne]

Hi everyone,

Lets say I have an inbound call from Belgium coming to my CM 6.2 enviornment/SM 6.2 (to my DID number). My DID number is call forwarded over to Lync via a SIP trunk set up between the two systems. The call from Belgium routes through my CM, to SM, to Lync and completes fine on Lync. However, the number in the Lync call log is 32xxxxxxxx (10 digits). I can't redial the nubmer because its not in E.164 format.

I can't really modify this to E.164 format, because of overlaps in the dialplan that prevent me. 32xxxxxxxx (again, ten digits) is also a number that we would receive in the inbound if someone calls me from lets say a town in Texas (325 area code) or Arizona (327). Has anyone else dealt with this and if so, how did you get around it so that you can deliver your calling numbers to Lync in E.164 format so that your redial function worked?

Thanks,
HeatherSue.

 

[kyle555]

I would think it might depend on what Lync looks at in the SIP headers to determine what number to put in the call logs, but consider an adaptation in SM.

Call it the "Lync" adapter, module "DigitConversionAdapter" and apply that adaptation to your Lync SIP entity.

You can match and manipulate digits on calls coming into SM from that entity, or going to that entity from SM, and you can modify the origination or destination or both addresses.

Matching your pattern, adding a + and only modifying the originating number might be what you're looking for.

 

[heathersuzanne]

Hi Kyle,
Thank you for your reply!
We do have a DigitConversionAdapter adaptation is SM on the Lync SIP entity. However, I'm not sure how to handle 10 digit inbound numbers that can be EITHER international or domestic.

So if I take an example, looking at an inbound 10 digit number right now - 3253721110. This is the number that the carrier routes to me, it hits CM, CM routes the call to my extension, my extension is call- forwarded to the SM so it can be taken from there over to Lync. How to I enter a adaptation for this number if I dont knwo if this inbound number is from a caller in the 325 area code in the US, or if its from a vendor in Belgium, where the country code is 32?

I would want to either send the call to Lync with a +1 in front (if inbound call is Domestic), or just with the + (if its international). It seems its too variable for me to wrap my heard around how to make the adaptation if the calling number can really go either way - domestic or international.

What do you think?

Thanks again!
Heather

 

[kyle555]

I think the answer might be with PSTN SIP trunks!

But just to make sure I understand...
-You have DS1 trunks on CM
-You want to send calls coming in on those trunks to Lync
-You have different possible 10 digit numbers beginning with "32" that could indicate a NANP 3 digit NPA, or +32 country
-You don't know how to separate those 2 possible "32X" strings to know whether to send +1-32?-NXX-XXXX or +32-BELGIUM to Lync.


I think you need the telco to send 1-32X-NXX-XXXX or 011-32-BELGIUM as CLID for you to make the distinction. You'll eventually have the same problem with another country and it would seem to be easier to trigger on 011, strip 3 leading digits, add +, and go. Else, if 11 digits beginning with a 1, I know you're North America.

 

[kyle555]

Another solution I suppose could be to make a very specific exception for Belgium if you know what numbers they're coming in with.

For example, 325-654, and just deal with the fallout of not calling San Angelo, TX back properly!

 

[heathersuzanne]

Hi,

Yes, you are understanding it exactly. DS1 trunks on CM (not SIP) routing inbound to our Avaya enviornment. This is connected to Lync via SM and Sip trunks 'in the middle'.

I sent a message to the carrier a couple days ago to inquire whether they can send me the digit 1 on inbound Domestic calls (right now they do not send us the 1). I'm waiting to find out what they will say. But I wasn't sure if there was another way that we could do without the carrier getting involved (lord knows I wont hear back from them for a while on this one...)

Thanks so much!

Heather

 

[kyle555]

I know that on your SIP trunks that you can add a + to your outgoing, and you can remove a + on your incoming.

You also (at least at 6.3) trigger on a + on your incoming call-handling treatment form on DS1s.

To say, if telco sends 32X-XXX-XXXX from the US and +32 X XXX XXXX from Belgium, you could be able to work with that.

But if telco sends 10 digits beginning with 32 with the only difference being where the hyphens are, then you're kinda stuck with using 1 and 011 to know the difference.