[cisco-voip] PIMG configs

[Pat Hayes]

A direct call to the pilot typically wouldn't have a redirecting
number, you'd only see that on a forwarded call. For a direct call to
get routed to sign-in, you need a calling party number (need to know
what mailbox you want to sign in to). Depending on what you see for
calling party, there are a few typical problems:

Receiving too many/not enough digits - you can setup some translations
on the PIMG side or add alternate extensions for each subscriber in
Unity

No digits - Either the PBX isn't sending them to the PIMG or the
parsing rules are screwed up. Try pulling one of the lines going to
the PIMG and plugging it into a digital set (unless of course you have
an analog PIMG). Make a call that will land on that port and see if
you get call info on the display

Totally wrong digits - Either something is up on the PBX (use above
method to see what it is sending) or the parsing rules on the PIMG are
incorrect.

On Wed, Jun 3, 2009 at 2:33 PM, Countryman, Edward
<Edward.Countryman at provena.org> wrote:
> Examining call logs shows that when the VM pilot is dialed by user directly the "redirected number" field is not filled in.
>
> My question however is, should I expect it work by tweaking the PIMG or is this a limitation on the TDM side??
>
> -----Original Message-----
> From: Pat Hayes [mailto:pat-cv at wcyv.com]
> Sent: Tuesday, June 02, 2009 5:27 PM
> To: Lelio Fulgenzi
> Cc: Countryman, Edward; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] PIMG configs
>
> Sounds more like Unity isn't getting the call info from the PIMG. Get
> a packet capture or look at the SIP traces (either from Unity or the
> PIMG), is there a calling party number or is it anonymous? Most likely
> culprit is a problem with the parsing rules on the PIMG, double check
> that you loaded the right config file during install.
>
> On Tue, Jun 2, 2009 at 5:38 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>> I just completed a PIMG integration with Unity Connection 7 and it went
>> fairly well. We get the appropriate sign-in process, i.e. enter your PIN,
>> rather than *.
>>
>> The only thing I can think of is partitions included in the search space of
>> the default routing rule.
>>
>> If you're using Unity (without partitions), not sure.
>>
>> I'd open a case with the TAC. They're usually pretty good.
>>
>>
>> ---
>> Lelio Fulgenzi, B.A.
>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> "Bad grammar makes me [sic]" - Tshirt
>>
>>
>> ----- Original Message -----
>> From: "Edward Countryman" <Edward.Countryman at provena.org>
>> To: cisco-voip at puck.nether.net
>> Sent: Tuesday, June 2, 2009 5:27:54 PM GMT -05:00 US/Canada Eastern
>> Subject: [cisco-voip] PIMG configs
>>
>> I've recently deployed PIMGs in my environment to enable users from our
>> Nortel and Avaya legacy systems to become unity users.
>>
>>
>>
>> Although working ok, (lamps and greetings) pbx users are not recognized when
>> they call into to check their messages.  When unity says "Hello" they are
>> required to press * then their 6 digit mail box id.
>>
>>
>>
>> While not the end of the world; I was curious to see if this could be
>> corrected.  Thoughts?
>>
>> _______________________________________________ cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>