Using ISDN Shortcodes on SIP

[NLPeterK]

We always assumed it couldn't be done, so for years we all struggled with SIP URI's.

So I did a GRIP request for it... Guess what? It's been possible since release 5!

Here's the response:
"This GRIP is declined as the following capability should address the requirement. IP Office 5.0+: If the wildcard * is used in the SIP trunk's Local URI, Contact and Display fields, that SIP trunk will accept any incoming SIP call. The incoming call routing is still performed by the system incoming call routes based on matching the values received with the call or the URI's incoming group setting. If outgoing calls are using this SIP URI, all valid short code CLI manipulations are used (transforming calling party number to isdn will be ignored)."

It actually works, with one "but": IPO will send "Anonymous" in the name field, although the number is correct. Our provider immediately responds to that and blocks the number.

ARS-entry:
N;/NS123456789Z"Some text or just a space"/Line ID

Bottomline, you only need one URI, with the stars. Use it like and ISDN line.

 

[Bas1234]

Don't think it work in R5 according to the docs.

NS123456789Z
Z - Calling Party Name (IP Office Release 6.0+)
This option can be used with trunks that support the sending of name information. The Z character should be followed by the name enclosed in " " quotation marks. Note that their may be name length restrictions that vary between line providers. The changing of name information on calls being forwarded or twinned may also not be supported by the line provider.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[intrigrant]

I am very sure it does not work on R5 nor on R6.

If it ain't dutch it ain't much

 

[NLPeterK]

Well, it does on R7 and R8. Haven't gotten around to testing the other two.

Hurray for the undocumented features

 

[tlpeter]

I think it was 7.0 where the "@123.123.123.123" was not needed anymore in the ARS or shortcode.
Although this is not documented (they still say you need to add the @123.123.123.123) this works.
I still add them because it is not documented and i do not want to be fouled when still "bug" is fixed one day.


BAZINGA!

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

 

[NLPeterK]

I do believe I did read it somewhere.. can't remember where though A co-worker pointed it out (and he's the one with the least amount of Avaya knowledge in our company ), after that I stopped using it.

 

[amriddle01]

There are some things that should be written into programming, this is one of those things, why they didn't from the start I don't know. I would like them to adopt the Mitel way of sending caller ID on SIP though....you enter the number the user sends into a box labelled "send number" no pissing about wih extra URI's/ARS forms etc

 

[NLPeterK]

At least you can now do it the "old-fashioned" way again

 

[tlpeter]

We always put it in because it is different than the IP address of the providers.

BAZINGA!

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