ObiTalk Service Sevice Settings Digitmap Question

(1/1)

larrybob:
Here is the default Inbound Call Route:
{(290183615|200197212)>(xx.):SP1},{(290183615|200197212):aa},{ph}
I understand the second rule :if a call comes in from ObiTalk number 290183615, 0r ObiTalk number 200197212, pick up with AA, otherwise ring the PHONE.

The second rule confuses me?
I think it says if  a call comes in from ObiTalk number 290183615, 0r ObiTalk number 200197212
calling any number,(allow this call-the xx. part),andsend the call through sp1.

1)How would a call of this type originate where the call to number is  defined with the incoming call?
       The only thing I can think of is a call coming through from the soft phone app. or from the Obion App?

2) Why is xx. used and not @. I have  some confusion reading about the @ definition in the Admin guide. In the Call Route Configuration Section @ is defined as any number but anonymous. In the Digit Map section @ is defined as any single alphanumeric number except #.

RonR:
Quote from: larrybob on April 09, 2012, 11:52:34 am

The second rule confuses me?
I think it says if  a call comes in from ObiTalk number 290183615, 0r ObiTalk number 200197212
calling any number,(allow this call-the xx. part),andsend the call through sp1.

1)How would a call of this type originate where the call to number is  defined with the incoming call?
       The only thing I can think of is a call coming through from the soft phone app. or from the Obion App?


The OBiTALK Web Portal should only be creating rules with a Callee-list on the OBiTALK Service InboundCallRoute.  This is how single-stage dialing from an OBiON App is accomplished.  A Callee-list is also applicable on an SPx Service that's configured for SIP, using the SIP userid as the Caller-list, but I don't believe the OBiTALK Web Portal is capable of genereating any such rules.

Quote from: larrybob on April 09, 2012, 11:52:34 am

2) Why is xx. used and not @. I have  some confusion reading about the @ definition in the Admin guide. In the Call Route Configuration Section @ is defined as any number but anonymous. In the Digit Map section @ is defined as any single alphanumeric number except #.


Using (xx.) is very poor coding.  In most cases. the called number should be validated and possibly transformed using the DigitMap associated with the target trunk:

{(200123456|290123456)>(Msp1):sp1}

larrybob:
 
Ron you Stated :
The OBiTALK Web Portal should only be creating rules with a Callee-list on the OBiTALK Service Inbound.  This is how single-stage dialing from an OBiON App is accomplished.

I might not have been clear , this is from the  OBiTALK Service Inbound
 Again, Here is the default Inbound Call Route:
{(290183615|200197212)>(xx.):SP1},{(290183615|200197212):aa},{ph}
I did not create this , it is auto created by the OBiTalk Web Portal. I Understand what you are saying about the xx. and how (Msp1) would be a better to use. (I guess Obi should clean up their programing)

Larry

Navigation

[0] Message Index