Identify Cellular Calls in SIP Logs

[spend]

Hello Again,

I have another question.  I am wondering, is there is a attribute in SIP logs which identifies callers using a mobile phone?  I imagine it would be similar to ANI II digits...

/mg

[Fra]

You must be joking. There's nothing like that.

Fra

[spend]

Nope not joking.

http://www.nanpa.com/number_resource_info/ani_ii_assignments.html

We use these digits to identify calls originating from prison (Ani II assignment 29) at the carrier level.  It would be nice to lose the fees incurred by routing on their platform and move this functionality to Genesys.  Avaya can route based on these digits (noted in CM as 'ii-digits'), but I guess that is a piece of functionality Genesys lacks. 

[fnunezsa]

I believe what Fra meant is that there is no ANI II attribute in SIP Server logs and he's right.

But if you can elaborate more on what you're trying to achive maybe we can guide you to the right direction. For example, if you have a range of starting digits for cellular phones then you can enable some kind of routing decisions based on that.

Kind regards,
Franklin.

[Fra]

[quote author=fnunezsa link=topic=6155.msg26794#msg26794 date=1296846347]
I believe what Fra meant is that there is no ANI II attribute in SIP Server logs and he's right.

But if you can elaborate more on what you're trying to achive maybe we can guide you to the right direction. For example, if you have a range of starting digits for cellular phones then you can enable some kind of routing decisions based on that.

Kind regards,
Franklin.
[/quote]

Correct.

[Dave]

This generally won't be a function of SIP Server, but rather your media gateway.  If your gateway supports ANI II digits (for example the Cisco AS5400 will generally report them in the SIP header as isup-oli within the from: string), then it would be up to the gateway to parse that string, identify any call with a 61, 62 or 63, and send it to a unique target that would match up to a Genesys route point with a strategy designed to handle cellular calls.  Other calls would be targeted at a different strategy.

Some gateways will support these digits; most will not.  Even fewer will let you do the complex parsing necessary to accomplish what you're trying... The reason Avaya can do this and Genesys can't is because Avaya is a completely closed environment -- they control the switch and the routing platform all in one.  Genesys doesn't control the media platform -- despite its name, SIP Server is just the software, but it doesn't control the media interface to the PSTN.  If the majority of switch vendors and media gateways exposed ANI II through the CTI interface, I'm sure Genesys would support such data through the TServer (or SIP Server).

[bublepaw]

There is a simpler solution. If gateway supports ANI II digits it's enough to know in which SIP header this data is sent. Inside Genesys SIP Server we can extract value from any sip header and use it inside strategy to make decision - there is no need to do any manipulation on gateway side.

[Dave]

[quote author=bublepaw link=topic=6155.msg26826#msg26826 date=1297201634]
There is a simpler solution. If gateway supports ANI II digits it's enough to know in which SIP header this data is sent. Inside Genesys SIP Server we can extract value from any sip header and use it inside strategy to make decision - there is no need to do any manipulation on gateway side.
[/quote]
That would be true, except that in my experience, SIP Server has always rewritten the From header with a very limited set of data.  I would be very surprised to see isup-oli included in the From header that SIP Server carries forward from the media gateway, which is why I recommended having the gateway parse it out of that header and route based on the value.

[bublepaw]

Dave,

If You configure header mapping using INVITE section in SIP Server, From header will be extracted from initial INVITE and attached before any manipulation is done by SIPS so You can safely use this value later in strategy.

Pawel