IPO 7.0(23) and incoming call route FYI

[mforrence]

FYI regarding ICR and wildcards in destination.

I'm configuring an IP500V2 w/7.0(23) as a "tandam" switch. Calls will come in on a T1 from a legacy PBX - some of which need to be routed back out via an H.323 trunk. All stations in the system use four-digit numbering plan beginning with the digit "3". The legacy PBX sends me the last three digits (i.e. if the destination is 3401, legacy PBX sends 401) and there is no way to change this. So, on ICR, I simply wanted to add a digit "3" in front of whatever arrived from legacy PBX. So on group 6 I have received digits XXX with destination of 3. - manager gave an error and said that I must put the . inside quotes. Did so, but system then passed 3. for shortcode match as if the . were a character not representing the digits 401 or whatever legacy PBX sent. I found that if I don't put the . in quotes, it works like a champ, but still shows the evil red X and warns me every time I send config.
Tried using 3# as destination (# is supposed to match all wildcards) - same "must be in quotes" error. When I used 3"#", system passed the # as if it were a character instead of the digits received from legacy PBX. So, same result. FYI

 

[mattKnight]

XXX ->3XXX

XXX ->3N



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.

 

[hairlessupportmonkey]

I did a similar thing from Lync to IPO - trunk to trunk. Lync to dial off the IPO.

ICR +XXXXXXXXXX Dest #

# simply redials the numbers in the ICR Incoming number.

If you want to route calls over different routes, then 8# will match a short code 8N

I ignored the errors about having the # in quotes.

ACSS - SME
General Geek

 

[mforrence]

@Matt - I'm not sure what you're indicating
@HSM - yup - that's my point. Put # in quotes and it doesn't work, but Manager is happy. Don't put # in quotes and it works, but Manager is peeved.
Mike