OBiTALK Community

General Support => Installation and Set-Up (Devices) => Topic started by: RonR on May 15, 2011, 12:30:11 PM

Title: pli Expansion in InboundCallRoute : Bug or Omission
Post by: RonR on May 15, 2011, 12:30:11 PM
Obihai,

The following rules are all valid in an InboundCallRoute:


{pap2>(Msp1):sp1}
{pap2>(Msp2):sp2}
{pap2>(Mpp):pp}
{pap2>(Mli):li}
{pap2>(Mtg1):tg1}

PrimaryLine may be set to sp1, sp2, pp, li, or tg1.

The following rule is ignored in an InboundCallRoute:

{pap2>(Mpli):pli}

I don't know if this is a bug or simply an inadvertent omission (you forgot to expand pli in InboundCallRoutes), but it needs to be supported so that changes to PrimarlyLine don't also require editing to InboundCallRoute rules.

Can we please get this fixed/added in the next firmware release?
Title: Re: pli Expansion in InboundCallRoute : Bug or Omission
Post by: obi-support2 on May 15, 2011, 01:11:13 PM
primary line only applies to Phone Port and AA
Title: Re: pli Expansion in InboundCallRoute : Bug or Omission
Post by: RonR on May 15, 2011, 01:26:55 PM
Quote from: obi-support2 on May 15, 2011, 01:11:13 PM
primary line only applies to Phone Port and AA

pli is expanded in DigitMaps and OutboundCallRoutes.  Why is there a problem with expanding it in InboundCallRoutes also?  It's a simple replacement of 'pli' with 'sp1', 'sp2', 'pp', 'li', or 'tg1' from the PrimaryLine variable.  I'm sure you already have a function to do this.  I don't see a downside, but there is a big upside.