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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Turret to cisco to IPO

Status
Not open for further replies.

ipowarrior

Programmer
Apr 5, 2011
52
GB
Hi

hopefully some one has this working and could advise...please!

I have a client that has decided to put trader turrets onto a cisco router connected via pri to an IPO localy.
I have set incomming call routes to extentions, eg; when you dial ext200 from a turret it goes through the cisco, over the pri and rings the ext.
the problem is that the turrets need to dial externaly and I cant seem to get the call to come in and bcak out to the isdn30?

many thanks in advanced
 
thanks for your reply,

when i look at the monitor trace i see the external number that they are dialing, ie 0207 123 4567,
I created an incoming call route of 9 that had a destination of short code 9N dial and I see in the trace "receive secondary dial tone".
the problem is that the turrets send all the digits en bloc
 
Try creating a call route with 9xxx and use as many X as you will get for digits and make the destination .

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries
 
ha your right. I am in the US and we use 9 for everything...

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries
 
I wonder if the IPO is seeing what they dial essentialy as the DDI number. Try set an incoming call route matching what the dial as the incoming digits and see if you can route it. then you need to work out how to make a route that transfers a DDI back to BT with it's own number!!! Make sense??

You might have more success if the link to the Cisco with set to QSIQ. That way it would be more like an internal call and use the short codes and away. Just a thought!!

It would mean some networking licenses though.

Jamie Green

Football is not a matter of life and death-It is far more important!!!!
 
I think you will need to put that PRI in its own Incoming line gp and create an Incoming call route as follows:

Incoming number: 0XXXXXXXXXX
Destination: .

This will route dial the entire number as recieved from the Cisco, so you need a system shortcode to handle it (not a 9N one) :)

If they sometimes dial local you will need to create routes with an incoming number that matches those e.g 5XXXXX etc or International 00XXXXXXXXXXXX etc :)

ACSS (SME)
APSS (SME)


"I'm just off to Hartlepool to buy some exploding trousers
 
cheers chaps,

Jamie,Armriddle01,qsig was a mission for the cisco freak to try and commission,
YES, of course! It makes perfect sense to route the incomming call routes like that, ill give it a go.

many thanks
 
Are you using QSIG or not?
QSIG does not use the incoming call route!!!


BAZINGA!

I'm not insane, my mother had me tested!
 
Assuming, the mother of all ........

BAZINGA!

I'm not insane, my mother had me tested!
 
hmmm, didnt make myslef clear,

Jaimie mentioned try using qsig,
the cisco muppet had a hard time of it so we are using pri,

the advice on 0xxxxxxx and local call routing to shortcodes rather than 9n (makes perfect sense)

cheers
 
I'd try inserting LINE shortcode

9N
N
Dial
ARS of outbound



Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
Or use a different incoming linegroup id.
Then try leaving the ddi field empty.
If that works then add some ddi's.

BAZINGA!

I'm not insane, my mother had me tested!
 
cheers matt already tried that,
amridlle01 suggestion is favourite me thinks
 
Look like Mr Riddle is correct.

F1 on ICR in Manager:
· Destination: Default = Blank, Software Level = Up to 4.0 only.
For IP Office 4.1+, this option has moved to the Incoming Call Route | Destinations tab. Select the destination for the call from the drop-down list box which contains all available extensions, users, groups, RAS services and voicemail. System short codes and dialing numbers can be entered manually. Once the incoming call is matched the call is passed to that destination.

· Drop-Down List Options
The following options appear in the drop-down in the following order:

· Voicemail allows remote mailbox access with Embedded Voicemail, Voicemail Lite or Voicemail Pro. Callers are asked to enter the extension ID of the mailbox required and then the mailbox access code.

· User Names

· Hunt Groups Names

· AA:Name directs calls to an Embedded Voicemail auto-attendant services.

· Manually Entered Options
The following options can be entered manually into the field.

· VM:Name Directs calls to the matching start point in Voicemail Pro.

· A . matches the Incoming Number field. This can be used even when X wildcards are being used in the Incoming Number field.

· A # matches all X wildcards in the Incoming Number field. For example, if the Incoming Number was -91XXXXXXXXXXX, the Destination would be XXXXXXXXXXX.

· Text and number strings entered here are passed through to system short codes, for example to direct calls into a conference. Note that not all short code features are supported.


Jamie Green

Football is not a matter of life and death-It is far more important!!!!
 
You may even get away with leaving the Incomng number field blank as long as it's in it's own line gp and set as any voice, it may still pass the incoming number through :)

ACSS (SME)
APSS (SME)


"I'm just off to Hartlepool to buy some exploding trousers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top