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!

Register Log in
  • 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!

Coverage path issue (Voice Mail is asking for the extension, instead of leave voicemail)

Status
Not open for further replies.
JuanCarman

JuanCarman

IS-IT--Management
May 30, 2016
73
0
0
MX
Hello folks,

I am receiving a call from a different PBX, that was was forwarded to the AVAYA phone system, so when the call is route to the extension in the PBX and the user dont answer the call, the call should be route it to the voicemail box of this user, but instead of that, the call is routed to the announcement (Please enter your mailbox), so the call is not routed to the Voice Mail Box.

Could you please let me know if there is something that is affecting this configuration?

The AVAYA PBX is version 7.1 with session manager using SIP phones.

Please let me know your comments,
Regards
 
Sort by date Sort by votes
is your dial plan 10 digits? If so you should look at adaptions

Incoming calls to session manager
Matching Pattern Min Max Delete Digits insert digits address to modify
xxxxxxxxxx 10 10 0 +1 destination


Outgoing calls from session manager
Matching Pattern Min Max Delete Digits insert digits address to modify
+ 12 12 2 +1 destination
 
Upvote 0 Downvote
Use traceSM to see what is being passed to the voicemail system.
 
Upvote 0 Downvote
Agree with Wanebo, please get the first invite message to the voicemail system.
 
Upvote 0 Downvote
Thank you for your comments, I will schedule some time for testing today, I will let you know more ASAP. Regards
 
Upvote 0 Downvote
I found the next info in the trace:

13:16:01 INVITE going via Sig Grp 250, ignoring called number routing

I think this is something that is affecting the call. Please let me know your comments,
regards
 
Upvote 0 Downvote
Again, use traceSM to see what information is being passed through to the voicemail system. A list trace isn't going to give you definitive answers but a traceSM will show you exactly what the voicemail system is getting and allow you to adjust whatever needs to be adjusted in the adaptation.
 
Upvote 0 Downvote
I would check the public-unknown add your extension len. to your voice mail trunk group.
example Ext.Len. 5, ext code 5, trk grps 99. (where ext 50000 going to voice mail Trunk group 99.)
 
Upvote 0 Downvote
I agree with David Payne above, I had same issue that was entries missing from public or private unknown numbering
 
Upvote 0 Downvote
Here is the trace from the CM, I am working in the traceSM as I dont have access at this moment, but maybe this trace can show what is happening. Please let me know your comments:

time data

13:15:55 TRACE STARTED 06/14/2018 CM Release String cold-00.0.441.0-23853
13:16:01 SIP<INVITE sip:2026169@domain.com SIP/2.0
13:16:01 Call-ID: 8b1e708-a13640a-13c4-55013-4ae408-5f6ff967-4ae
13:16:01 408
13:16:01 Calling party trunk-group 850 member 139 cid 0x2324
13:16:01 Calling Number & Name 2144812030 DOM
13:16:01 dial 2026169
13:16:01 term station 2026169 cid 0x2324
13:16:01 dial 2026169
13:16:01 term trunk-group 850 cid 0x2325
13:16:01 dial 2026169
13:16:01 route-pattern 850 preference 1 location ALL cid 0x2325
13:16:01 seize trunk-group 850 member 116 cid 0x2325
13:16:01 Calling Number & Name 2144812030 DOM
13:16:01 INVITE going via Sig Grp 850, ignoring called number routing



LIST TRACE

time data
13:16:01 SIP>INVITE sip:2026169@domain.com SIP/2.0
13:16:01 Call-ID: fe1a3f2c6ffe41e8b1a005056a570a2
13:16:01 Setup digits 2026169
13:16:01 Calling Number & Name 2144812030 DOM
13:16:01 SIP<SIP/2.0 100 Trying
13:16:01 Call-ID: fe1a3f2c6ffe41e8b1a005056a570a2
13:16:01 Proceed trunk-group 850 member 116 cid 0x2325
13:16:01 SIP<SIP/2.0 180 Ringing
13:16:01 Call-ID: fe1a3f2c6ffe41e8b1a005056a570a2
13:16:01 SIP>SIP/2.0 180 Ringing
13:16:01 Call-ID: 8b1e708-a13640a-13c4-55013-4ae408-5f6ff967-4ae
13:16:01 408
13:16:01 ring station 2026169 cid 0x2324
13:16:01 Alert trunk-group 850 member 116 cid 0x2325
13:16:01 Alerting party uses private-numbering
13:17:01 SIP>SIP/2.0 180 Ringing



LIST TRACE

time data
13:17:01 Call-ID: 8b1e708-a13640a-13c4-55013-4ae408-5f6ff967-4ae
13:17:01 408
13:18:01 SIP>SIP/2.0 180 Ringing
13:18:01 Call-ID: 8b1e708-a13640a-13c4-55013-4ae408-5f6ff967-4ae
13:18:01 408
13:18:59 SIP<CANCEL sip:2026169@dmain.com SIP/2.0
13:18:59 Call-ID: 8b1e708-a13640a-13c4-55013-4ae408-5f6ff967-4ae
13:18:59 408
13:18:59 SIP>SIP/2.0 200 OK
13:18:59 Call-ID: 8b1e708-a13640a-13c4-55013-4ae408-5f6ff967-4ae
13:18:59 408
13:18:59 SIP>SIP/2.0 487 Request Terminated
13:18:59 Call-ID: 8b1e708-a13640a-13c4-55013-4ae408-5f6ff967-4ae
13:18:59 408
13:18:59 SIP>PUBLISH sips:2026169@domain.com SIP/2.0
13:18:59 Call-ID: 683e77426fff41e8b8ce05056a570a2



LIST TRACE

time data
13:18:59 idle trunk-group 850 member 139 cid 0x2324
13:18:59 SIP>CANCEL sip:2026169@domain.com SIP/2.0
13:18:59 Call-ID: fe1a3f2c6ffe41e8b1a005056a570a2
13:18:59 idle trunk-group 850 cid 0x2325
13:20:46 TRACE COMPLETE station 2026169 cid 0x0
 
Upvote 0 Downvote
Here is the trace from traceSM that you requested, please let me know if something in the trace shows the issue:

09:33:43.452 |--INVITE-->| | | (119) T:3029954xxx F:2148418xxx U:3029954xxx
09:33:43.454 |<--Trying--| | | (119) 100 Trying
09:33:43.461 | |--INVITE-->| | (119) T:4131;phone-context=cdp.voice F:2148418xxx U:4xxx;phone-context=cdp.voice P:terminating
09:33:43.513 | |<--Trying--| | (119) 100 Trying
09:33:43.545 | |<--INVITE--| | (120) T:2026169;phone-context=voice F:2148418xxx;phone-context=UnknownUnknown U:2026169;phone-context=voice
09:33:43.547 | |--Trying-->| | (120) 100 Trying
09:33:43.552 | |--------INVITE-------->| (120) T:2026169 F:2148418492;phone-context=UnknownUnknown U:2026169 P:internal_terminating
09:33:43.554 | |<--------Trying--------| (120) 100 Trying
09:33:43.677 | |<--------Ringing-------| (120) 180 Ringing
09:33:43.681 | |--Ringing->| | (120) 180 Ringing
09:33:43.744 | |<--Ringing-| | (119) 180 Ringing
09:33:43.749 |<--Ringing-| | | (119) 180 Ringing
09:34:29.851 |--CANCEL-->| | | (119) sip:3029954xxx@10.202.xxx.xxx:5060
09:34:29.862 |<--200 OK--| | | (119) 200 OK (CANCEL)
09:34:29.863 | |--CANCEL-->| | (119) sip:4131
09:34:29.913 | |<--200 OK--| | (119) 200 OK (CANCEL)
09:34:29.913 | |<--Request-| | (119) 487 Request Terminated
09:34:29.915 | |----ACK--->| | (119) sip:4131
09:34:29.918 |<--Request-| | | (119) 487 Request Terminated
09:34:29.918 |----ACK--->| | | (119) sip:3029954xxx@10.202.xxx.xxx:5060
09:34:29.925 | |<--CANCEL--| | (120) sip:2026169
09:34:29.960 | |--200 OK-->| | (120) 200 OK (CANCEL)
09:34:29.961 | |--------CANCEL-------->| (120) sip:2026169@domain.com
09:34:29.963 | |<--------200 OK--------| (120) 200 OK (CANCEL)
09:34:29.967 | |<--Request Terminated--| (120) 487 Request Terminated
09:34:30.005 | |----------ACK--------->| (120) sip:2026169@domain.com
09:34:30.007 | |--Request->| | (120) 487 Request Terminated
09:34:30.053 | |<----ACK---| | (120) sip:2026169

Regards
JC
 
Upvote 0 Downvote
Yes I did, but I was not able to fix the issue, I added the extension lenght with the trunk groups related to the Voice mail service, but the issue is the same...
 
Upvote 0 Downvote
I worked in public, do you think the change should be in private?
 
Upvote 0 Downvote
Depends on how the trunk group is configured, most likely it is set to private so make an entry in that table and retest.
 
Upvote 0 Downvote
Same results, at this moment I am working in the adaptation section in SM, hope that helps...
 
Upvote 0 Downvote
Same results, if I configure all in the coverage path the call is send directly to the voicemail, if I used the other options in the cov path, the call only rings in the phone, the call is never send to the Cov Path.

I added an adaptation path in SM, but that one is not helping at all.

Any other idea how to solve the issue?

Thank you very much in advance!!
Regards
JC
 
Upvote 0 Downvote
COVERAGE PATH

Coverage Path Number: 100
Cvg Enabled for VDN Route-To Party? n Hunt after Coverage? n
Next Path Number: Linkage

COVERAGE CRITERIA
Station/Group Status Inside Call Outside Call
Active? y y
Busy? y y
Don't Answer? y y Number of Rings: 4
All? n n
DND/SAC/Goto Cover? y y
Holiday Coverage? n n


COVERAGE POINTS
Terminate to Coverage Pts. with Bridged Appearances? n
Point1: h97 Rng: 4 Point2:
Point3: Point4:
Point5: Point6:
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

W
  • Question
CMS Reporting Avail -> Other -> ACD instead of Ring. Calls not counting for Summary reports
Replies
4
Views
317
Weslee
W
Traveler74
  • Locked
  • Question
Coverage Path not forwarding call
Replies
0
Views
108
Traveler74
Traveler74
DTechNation
  • Question
Display call is coming from a Coverage Answer Group on J179s
Replies
0
Views
117
DTechNation
DTechNation
JPidliskey
  • Locked
  • Question
coverage answer 1
Replies
2
Views
139
JPidliskey
JPidliskey
Wolfdzn
  • Locked
  • Question
Extension name display instead of agent id
Replies
0
Views
111
Wolfdzn
Wolfdzn

Part and Inventory Search

Sponsor

Back
Top