Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem with mobile twinning on IP Office IP500v2

Status
Not open for further replies.

vfonseca76

IS-IT--Management
Feb 24, 2012
16
PT
Hi everyone.

First a litle insight on the problem:
A customer has a group of mobile phones that can call each other using a reduced number (GSM group). When they call numbers outside the group, the 9 digit number is the CLI, when they call within the group, a 4 digit CLI is used, is this case 5xxx.
The operator has a PRI trunk that makes possible for fixed extn connected to the IP500 to call the mobile phones the same way and vice-versa:
Ex. extn 4255 (fixed IP extn from IP500) can call extn 5160 (mobile phone) directly and vice-versa, and the CLI presented to the visor of the phones is the respective extn number.

The problem is this:
when I tried to install a mobile twinning for some of the mobile phones, I can't get a match for the user, since the CLI for the mobile phone is only 4 digits, and the IP500 expects at least 6 to make the match.

All needed licenses are OK, have 40 Mobile User licenses.

I need to add 2 digits to the CLI before routing the call to the corresponding FNE service, or else it won't work.

Changing the numbering plan for the mobile phones is not an option at this point.

I've tried using VMPro to change the CLI, tried using an 's' on the short code to force the CLI, no success so far...

IP500V2 running R6.0.18
VMPro 6.0.22

Does anybody have some ideas on this ?
Can it be done?

Thanks for your time.
Vasco
 
Add the following to NoUser source numbers and reboot:

oneXdigits2match=4

That should make it match against 4 digits :)

 
amriddle01 : didn't work...

But...

I'm going to do some more tests with that tomorrow.. it's been a long day and I could be missing something..

Anyway, thanks for the help.

Vasco
 
BTW, it needs to be a reboot not a merge, I have only seen this used set at 6 but don't see why 4 wouldn't work, someone tried 3 but that didn't so fingers crossed :)

 
Sorry, posted that last without havng seen your response, oh well :-(

 
You could do this by using loop back into the ipo


See the bottom of this thread, although I didn't make it very clear:)

Basically you need 2 line isdn card per 2 simultaneous call. You can also use the example to create multiple outgoing cli entries and still have the call tagged to the relevant user.

Post back if you need clarification on it

TT
 
TT:
Let me see if I got the picture...
I do have 2 BRI cards unused for the job, so:
- I configure one or both to S-bus and configure them for outgoing trunk 99
- I create a line shortcode using 's' to change the CLI for the call
- I define the TG 99 as the TG for that short code

That does a loop on the BRI card.

After that, I create a ICR routing the CLI I configured for the FNE feature.

How about the original call ? How do I route it to the S-bus trunk ?
Doesn't this affect all the calls comming in on the incoming TG ?

Anyway, you gave me a HUGE helkp on this, I will do some tests with this tomorrow... Thanks a lot :)

Vasco
 
You do need a end resistor otherwise it won't work!!!!


BAZINGA!

I'm not insane, my mother had me tested!

 
@amriddle01
@tlpeter

Do you know any more codes like "oneXdigits2match = 4" and "ProgressEndsOverlapSend"?

Some would facilitate the work.
 
I'm not in a position to test this again but I think this is what you need:

Trunk settings:
Customer Lines
TGX In (assume 0)

Loop ISDN port:
TG out 98 (Not used)
TG In 97 (Unique TG used just for FNE One-X)

Loop S-Bus port:
TG Out 99 (Used only by S-Bus)
TG In 98 (Not used)

Connect ISDN port to S-Bus Port using Resistor or €30 avaya cable!)

User Settings:
User 1 Ext 201 Mobility Number 201201201

User 2 Ext202 Mobility Number 202202202

User 1 CLI Received = 087123456
User 2 CLI Received = 086123123
Replace with your user's cli


Short Code Settings:
**XXX
Dial NsNNN (so caller id sent is ext/ext/ext giving match on mobility above)
TG99 (s-bus out)

FNE00 *8888 (you can mix and match here depending on what Fne services you want to offer)

ICR Settings:
TG97 (Loop ISDN In)
Any Number
FNE Short Code (*8888 in my example)
----so any call in on this TG will be sent to the FNE service


TGX (assume 0)
CLI 087123456 (User 1 Mobile Number)
DDI (Optional if you want a dedicated incoming number for this)
Destination s/c **201

TGX
CLI 086123123 (User 2 Mobile Number)
DDI (Optional)
Destination s/c **202

so in summary, a user of 201 with mobile number 087123456 dials in on the main customer line or a dedicated ddi. The ICR picks up their caller id, sends it to a short code, which in turn sends a caller id out the s-bus back into the isdn. this isdn is dedicated to FNE service, the caller id (201201201 or 202202202, etc) sent is matched against the user so they get dial tone. if you want to get more elaborate read up on the fne services I'm sure there would be easy ways to get all the features working on just 1 ddi using this method.

Have fun!
TT



 
Hello boys and girls.

Sorry for such a late feedback on this subject... honestly I forgot... :(

Thank's to everyone for the great advice, but unfortunately I was unable to used them. 2 simultaneous calls was not an option in this case, so I just forced a prefix on the trunk and adjusted the configuration accordingly. It's a bit sloppy, but I didn't see any other way...

But I learned a lot from your input, so thanks again to all of you.

Take care.
Vasco
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top