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!

Voicemail pro forwarding incoming call without CLI fails

Status
Not open for further replies.

geosat

Technical User
Feb 27, 2006
9
GB
Have had a problem where voicemail pro forwarding incoming call to external number using a SIP trunk fails when the incoming call has no CLI (anonymous)

The SIP trunk had all the SIP URI fields set to 'use internal data'. Incoming calls with CLI did not fail.

All simple outgoing calls were OK.

I set our CLI into all the fields for SIP URI to our main DDI and the problem disappeared - the downside is CLI is no longer passed for forwarded calls that have a CLI.

Below is the ARS info from the monitor application - this is a failing call that ARS then sends out on an ISDN trunk

Any ideas of a different fix that will not prevent passing CLI of forwarded calls??



592924mS CMARS: FindActiveARSByGroupID GroupID=58 - Found
592924mS CMARS: MakeCallTarget - Called Number: 0197836
592929mS CMARS: FORM: ANS IP MAG - Received Number: 0197836xxx
592929mS CMARS: FOUND A SHORT CODE - short_code: 0197836xxx - Tel: "44208xxxxxx@xxxxxx.net" - Called_Party: 442080991238@xxxxxxxxxxxxx.net - Line Group Id: 20
592930mS CMARS: FindActiveARSByGroupID GroupID=20 - Not Found
592935mS CMARS: FOUND LINE - Line Id: 20 - using line group id: 20 - Called Number: 44208xxxxxxxxx@xxxxxxxxxxxx.net - Calling Number:
592935mS CMARS: SEND Setup TO LINE
592937mS CMARS: LINE ep Received: CMReleaseComp - child->state = CMCSOffering - ARS Call State = CMCSOverlapRecv
592938mS CMARS: Target: Short_Code: 01978xxxxxxxx - Line_Group_ID: 20 has been set to: CMARS_OUTOFSERVICE
593938mS CMARS: MOVE TO ALTERNATE FORM: M Voip
593938mS CMARS: FORM: M Voip - Received Number: 0197xxxxxxx
593938mS CMARS: FOUND A SHORT CODE - short_code: 0N; - Tel: 44N"@xxxxxxxxnet" - Called_Party: 44197xxxxxxxx@xxxxxxxxxnet - Line Group Id: 20
593938mS CMARS: FindActiveARSByGroupID GroupID=20 - Not Found
593944mS CMARS: FOUND LINE - Line Id: 20 - using line group id: 20 - Called Number: 441xxxxxxxx@xxxxxxxxxxx.net - Calling Number:
593944mS CMARS: SEND Setup TO LINE - ARSTimeout
593945mS CMARS: LINE ep Received: CMReleaseComp - child->state = CMCSOffering - ARS Call State = CMCSRinging
593947mS CMARS: Target: Short_Code: 0N; - Line_Group_ID: 20 has been set to: CMARS_OUTOFSERVICE
594947mS CMARS: MOVE TO ALTERNATE FORM: Via 2n GSM Gate
594947mS CMARS: FORM: Via 2n GSM Gate - Received Number: 0197xxxxxxx
594947mS CMARS: FOUND A SHORT CODE - short_code: ? - Tel: . - Called_Party: 019xxxxxxx - Line Group Id: 10
594947mS CMARS: FindActiveARSByGroupID GroupID=10 - Not Found
594949mS CMARS: FOUND LINE - Line Id: 4 - using line group id: 10 - Called Number: 019xxxxxxxxx - Calling Number:
594949mS CMARS: SEND Setup TO LINE - ARSTimeout
595044mS CMARS: LINE ep Received: CMSetupAck - child->state = CMCSOffering - ARS Call State = CMCSRinging
595044mS CMARS: LINE IS NOW THE B END OF THE CALL - CMARSEndpoint::RequestEnd()
595044mS CMARS: CMARSEndpoint::CallLost(cause=124) - Address: 0.1061.0 10 ARS for Via 2n GSM Gate - Call State: CMCSRinging

 
You should have one URI of * * * (that is * in all three fields) that is used for incoming and one URI of Use Internal Data for your outgoing. You probably want to change the incoming URI's outgoing group ID to something other than what is targeted in your ARS table so it isn't used for outbound.

Kyle Holladay / IPOfficeHelp.com
ACSS & APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
 
Kyle,

Thanks - already have separate SIP lines (and group IDs) for incoming and outgoing.

The incoming line's URI already have the '*' as you suggest.

The problem occurs when outgoing lines URI set to internal data and a divert of a call with no CLI but not when the three URI fields of the outgoing sip line are manually set to a fixed CLI
 
Don't forget forwarded calls use system shortcodes, so set users to dial out a different line group to the system shortcodes by using user shortcodes to target a line group wih the * * * URI in, then add another URI with the correct data entered into he three SIP fields and add that to a unique line group and have system shortcodes use that line group :)

NTE-wave-logo-for-a4-header.jpg
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top