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
in the CP that I sent you is not activated the All? option, only the rest of the options for in/out calls. But the call never goes to the coverage, I just hear rings... Never ends...
 
Upvote 0 Downvote
You say the calls are forwarded from another pbx, How are they getting to you? from a tie trunk maybe?
 
Upvote 0 Downvote
Ok, Then I would look at the SIP header.
I had a case last year where calls transferring from one company to use had Voice mail issue. They were sending a SIP header that was being rejected by voice mail.
ended up stripping those odd SIP headers and that fixed the issue.
 
Upvote 0 Downvote
joe2938 that is correct, the call is received in a Nortel PBX, then the pbx send the call to the AVAYA over a SIP trunk (service type tie)

DAVIDPAYNE, where can I check the SIP header? or Diversion Header? At the AVAYA PBX? or is this something that should be check at the Nortel side?

Thank you very much for all your support with the issue.
Regards
JC
 
Upvote 0 Downvote
You would need to capture a SIP trace of the call for one of those calls. It will show you the Diversion Header that is coming in for that call.
You voice mail may not like wants coming in. For me to fix our issue on the SBC we looks from any call with that Diversion Header, and then had the SBC strip that header out.
 
Upvote 0 Downvote
This is the trace I have from traceSM:

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

Do I need to run something different?
 
Upvote 0 Downvote
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
AZZZ_Irv_SBCE_As SM SM100 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
13:42:55.029 |--INVITE-->| | | (10) T:3029954xxx F:2148418xxx U:3029954xxx
13:42:55.034 | |--INVITE-->| | (10) T:3029954xxx F:2148418xxx U:3029954xxx
13:42:55.037 | |<--Trying--| | (10) 100 Trying
13:42:55.038 |<--Trying--| | | (10) 100 Trying
13:42:55.382 | |<--Ringing-| | (10) 180 Ringing
13:42:55.383 |<--Ringing-| | | (10) 180 Ringing
13:44:56.404 |--CANCEL-->| | | (10) sip:302995xxxx@10.202.xxx.xxx:5060
13:44:56.407 | |--CANCEL-->| | (10) sip:302995xxxx@10.202.xxx.xxx:5060
13:44:56.414 | |<--200 OK--| | (10) 200 OK (CANCEL)
13:44:56.415 |<--200 OK--| | | (10) 200 OK (CANCEL)
13:44:56.524 | |<--Request-| | (10) 487 Request Terminated
13:44:56.524 |<--Request-| | | (10) 487 Request Terminated
13:44:56.528 |----ACK--->| | | (10) sip:302995xxxx@10.202.xxx.xxx:5060
13:44:56.529 | |----ACK--->| | (10) sip:302995xxxx@10.202.xxx.xxx:5060
13:44:59.395 |--INVITE-->| | | (266) T:302995xxxx F:214841xxxx U:3029954xxx
13:44:59.396 | |--INVITE-->| | (266) T:302995xxxx F:214841xxxx U:3029954xxx
13:44:59.398 | |<--Trying--| | (266) 100 Trying
13:44:59.398 |<--Trying--| | | (266) 100 Trying
13:44:59.736 | |<--Ringing-| | (266) 180 Ringing
13:44:59.738 |<--Ringing-| | | (266) 180 Ringing
13:45:03.905 |--CANCEL-->| | | (266) sip:302995xxxx@10.202.xxx.xxx:5060
13:45:03.906 | |--CANCEL-->| | (266) sip:302995xxxx@10.202.xxx.xxx:5060
13:45:03.909 | |<--200 OK--| | (266) 200 OK (CANCEL)
13:45:03.910 |<--200 OK--| | | (266) 200 OK (CANCEL)
13:45:03.988 | |<--Request-| | (266) 487 Request Terminated
13:45:03.989 |<--Request-| | | (266) 487 Request Terminated
13:45:03.990 |----ACK--->| | | (266) sip:302995xxxx@10.202.xxx.xxx:5060
13:45:03.990 | |----ACK--->| | (266) sip:302995xxxx@10.202.xxx.xxx:5060


10.202.xxx.xxx:42267 --TCP-> 10.202.xxx.xxx:5060 |
13:4|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
13:4|INVITE sip:3029954xxx@10.202.xxx.xxx:5060 SIP/2.0 |
13:4|From: "XXSDD" <sip:214841xxxx@10.202.xxx.xxx>;tag=2044499835672996_c3b05.1.1.1526021647333.0_3664670_7280514 |
13:4|To: <sip:3029954xxx@10.202.xxx.xxx:5060> |
13:4|CSeq: 2 INVITE |
13:4|Call-ID: da24eb7f00e7187462c196412bac3d05 |
13:4|Contact: <sip:10.202.xxx.xxx:5060;transport=tcp> |
13:4|Record-Route: <sip:10.202.xxx.xxxx:5060;ipcs-line=1440247;lr;transport=tcp> |
13:4|Allow: INVITE,ACK,CANCEL,BYE,INFO,PRACK |
13:4|Supported: replaces |
13:4|Max-Forwards: 69 |
13:4|Via: SIP/2.0/TCP 10.202.xxx.xxx:5060;branch=z9hG4bK-s1632-000392866434-1--s1632- |
13:4|Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed |
13:4|P-Asserted-Identity: "XXSDD" <sip:214841xxxx@10.202.xxx.xxx> |
13:4|Content-Disposition: session; handling=required |
13:4|Content-Type: application/sdp |
13:4|Content-Length: 245 |
13:4| |
13:4|v=0 |
13:4|o=Sonus_UAC 18432 27073 IN IP4 10.202.xxx.xxx |
13:4|s=SIP |
13:4|c=IN IP4 10.202.xxx.xxx |
13:4|t=0 0 |
13:4|m=audio 39846 RTP/AVP 18 0 100 |
|a=rtpmap:18 G729/8000 |
|a=rtpmap:0 PCMU/8000 |
|a=rtpmap:100 telephone-event/8000 |
|a=fmtp:100 0-15 |
|a=sendrecv |
|a=maxptime:30

/--------------------------------------------------------------------------------------------------------------------------------------------------------------13:4| 10.202.xxx.xxx:0 --TCP-> 10.202.xxx.xxx:15060 |
13:4|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
13:4|INVITE sip:302995xxxx@10.202.xxx.xxx:5060 SIP/2.0 |
13:4|Route: <sip:10.202.xxx.xxx:15060;transport=TCP;lr> |
13:4|From: "XXSDD" <sip:214841xxxx@10.202.xxx.xxx>;tag=2044499835672996_c3b05.1.1.1526021647333.0_3664670_7280514 |
13:4|To: <sip:302995xxxx@10.202.xxx.xxx:5060> |
13:4|CSeq: 2 INVITE |
13:4|Call-ID: da24eb7f00e7187462c196412bac3d05 |
13:4|Contact: <sip:10.202.xxx.xxx:5060;transport=tcp> |
13:4|Record-Route: <sip:785daa11@10.202.xxx.xxx;transport=tcp;lr> |
13:4|Record-Route: <sip:10.202.xxx.xxx:5060;ipcs-line=1440247;lr;transport=tcp> |
13:4|Allow: INVITE,ACK,CANCEL,BYE,INFO,PRACK |
13:4|Supported: replaces |
13:4|Max-Forwards: 68 |
13:4|P-Av-Transport: AP;fe=10.202.xxx.xxx:42267;ne=10.202.xxx.xxx:5060;tt=TCP;th |
13:4|Via: SIP/2.0/TCP 10.202.xxx.xxx;branch=z9hG4bK-s1632-000392866434-1--s1632--AP;ft=673442 |
13:4|Via: SIP/2.0/TCP 10.202.xxx.xxx:5060;branch=z9hG4bK-s1632-000392866434-1--s1632- |
13:4|Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed |
13:4|P-Asserted-Identity: "XXSDD" <sip:214841xxxx@10.202.xxx.xxx> |
13:4|Content-Disposition: session; handling=required |
13:4|Content-Type: application/sdp |
13:4|Content-Length: 245 |
13:4| |
13:4|v=0 |
13:4|o=Sonus_UAC 18432 27073 IN IP4 10.202.xxx.xxx |
13:4|s=SIP |
13:4|c=IN IP4 10.202.xxx.xxx |
|t=0 0 |
|m=audio 39846 RTP/AVP 18 0 100 |
|a=rtpmap:18 G729/8000 |
|a=rtpmap:0 PCMU/8000 |
|a=rtpmap:100 telephone-event/8000 |
|a=fmtp:100 0-15 |
|a=sendrecv |
|a=maxptime:30 |
\-------------------

/--------------------------------------------------------------------------------------------------------------------------------------------------------------13:4| 10.202.xxx.xxx:15060 --TCP-> 10.202.xxx.xxx:60327 |
13:4|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
13:4|SIP/2.0 100 Trying |
13:4|Call-ID: da24eb7f00e7187462c196412bac3d05 |
13:4|CSeq: 2 INVITE |
13:4|From: "XXSDD" <sip:214841xxxx@10.202.xxx.xxx>;tag=2044499835672996_c3b05.1.1.1526021647333.0_3664670_7280514 |
13:4|To: <sip:302995xxxx@10.202.xxx.xxx:5060> |
13:4|Via: SIP/2.0/TCP 10.202.xxx.xxx;branch=z9hG4bK-s1632-000392866434-1--s1632--AP;ft=673442;received=10.202.xxx.xxx;rport=60327 |
13:4|Via: SIP/2.0/TCP 10.202.xxx.xxx:5060;branch=z9hG4bK-s1632-000392866434-1--s1632- |
13:4|Content-Length: 0

/--------------------------------------------------------------------------------------------------------------------------------------------------------------13:4| 10.202.xxx.xxx:5060 --TCP-> 10.202.xxx.xxx:42267 |
13:4|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
13:4|SIP/2.0 100 Trying |
13:4|Call-ID: da24eb7f00e7187462c196412bac3d05 |
13:4|CSeq: 2 INVITE |
13:4|From: "XXSDD" <sip:214841xxxx@10.202.xxx.xxx>;tag=2044499835672996_c3b05.1.1.1526021647333.0_3664670_7280514 |
13:4|To: <sip:302995xxxx@10.202.xxx.xxx:5060> |
13:4|Via: SIP/2.0/TCP 10.202.xxx.xxx:5060;branch=z9hG4bK-s1632-000392866434-1--s1632- |
13:4|Content-Length: 0

Here is the latest trace, please let me know your comments,
Regards
JC
 
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