Avaya CM7 with DuVoice voicemail 1

[Bonker1974]

Hi All,
I have an issue we have a CM 7 with system and session manager. we are using Duvoice for guess room. the Duvoice is connected via SIP. we can call the DuVoice HG 1005 and it answer, the problem we are having it getting the MWI to turn on. DuVoice send the code back to SM but we get the below message. *04 to send MWI 7430 is the exten 1005 is the HG


11:28:25.609 | |<--INVITE--| | (5) T:*047430 F:1005 U:*047430
11:28:25.610 | |--Trying-->| | (5) 100 Trying
11:28:25.611 | |--Not Fou->| | (5) 404 Not Found (cannot determine routing domain, check SM ports)
11:28:25.611 | |<----ACK---| | (5) sip:*047430@192.168.200.15



SIP/2.0 404 Not Found (cannot determine routing domain, check SM ports) |
11:2|Call-ID: 38670e8-1fc8a8c0-13c4-65014-22ba9-62a597dd-22ba9 |2.16
11:2|CSeq: 1 INVITE |
11:2|From: "1005" <sip:1005@192.168.200.15>;tag=3848768-1fc8a8c0-13c4-65014-22ba9-1ab9864b-22ba9 |
11:2|To: <sip:*047430@192.168.200.15>;tag=73546582825077_local.1483802258051_241370_241824 |
11:2|Via: SIP/2.0/UDP 192.168.200.31:5060;branch=z9hG4bK-22ba9-87a8ec8-71ce4741-38331e8 |
11:2|Av-Global-Session-ID: 2464aea0-d8e4-11e6-be46-000c29a1ca57 |
11:2|Server: AVAYA-SM-7.0.0.0.700007 |
11:2|Content-Length: 0

 

[kyle555]

in the SM entity I think you can define a default domain for a port 5060 or 5061 that should sort you out.

 

[Bonker1974]

Thanks Kyle555 That fix that problem
but now i am getting no route available

13:05:02.637 | |<--INVITE--| | (6) T:*047430 F:1005 U:*047430
13:05:02.638 | |--Trying-->| | (6) 100 Trying
13:05:02.638 | |--Not Fou->| | (6) 404 Not Found (No route available)
13:05:02.639 | |<----ACK---| | (6) sip:*047430@192.168.200.15

 

[kyle555]

So, look at the programming you did to send calls to DuVoice. You need the return path back also programmed.
Consider that DuVoice will send a SIP Notify of the extn@domain.com, so your whole CM dial plan ranges have to have Dial Patterns in SM that "when matched on domain:ALL go to routing policy-->myCM

 

[Bonker1974]

@ Kyle555
I did that it now sends the process it However,it still not sending the MWI if you can see it keep trying until request time out.


13:37:35.952 | |<--INVITE--| | (69) T:*047430 F:1005 U:*047430
13:37:35.953 | |--Trying-->| | (69) 100 Trying
13:37:35.955 | |--INVITE-->| | (69) T:*047430 F:1005 U:*047430 P:terminating
13:37:35.957 | |<--Trying--| | (69) 100 Trying
13:37:36.016 | |<--Ringing-| | (69) 180 Ringing
13:37:36.016 | |<--200 OK--| | (69) 200 OK (INVITE)
13:37:36.017 | |--Ringing->| | (69) 180 Ringing
13:37:36.018 | |--200 OK-->| | (69) 200 OK (INVITE)
13:37:36.018 | |<----ACK---| | (69) sip:*047430@192.168.200.31
13:37:36.019 | |----ACK--->| | (69) sip:*047430@192.168.200.31
13:37:36.183 | |<----BYE---| | (69) sip:*047430@192.168.200.31
13:37:36.184 | |----BYE--->| | (69) sip:*047430@192.168.200.31
13:37:37.185 | |<----BYE---| | (69) sip:*047430@192.168.200.31
13:37:39.199 | |<----BYE---| | (69) sip:*047430@192.168.200.31
13:37:43.211 | |<----BYE---| | (69) sip:*047430@192.168.200.31
13:37:51.225 | |<----BYE---| | (69) sip:*047430@192.168.200.31
13:37:59.228 | |<----BYE---| | (69) sip:*047430@192.168.200.31
13:38:08.184 | |--Request->| | (69) 408 Request Timeout
13:38:26.628 |<--OPTIONS-| | | (75) sip:192.168.200.10

 

[kyle555]

Somethings wrong with that many BYEs at the end not being answered or processed from the right to the left. Check the thing on the left why it doesn't like the BYE


And after the call once DuVoice decides if you need a light lit, it ought to send a NOTIFY to the extension with some message in the body like "MWI=ON" or something

 

[Bonker1974]

I believe the issue is coming from the CM take a look at the trace..


10:14:52.424| +4082| 1005| sip:1005@192.168.200.31| Terminated - BYE (calling)| 1/7/30|CM[term]->SM100(200)[term]->DuVoic>
10:15:16.340| 1005| *047248| sip:*047248@192.168.200.31| Terminated - BYE (calling)| 2/10/19| DuVoice->SM100(200)[term]->DuVoice(200)
10:22:22.964| +4204| 1005| sip:1005@bchilton.com| Terminated - BYE (calling)| 5/56/46|-CM[term]->SM100(200)[term]->CM>
10:22:22.972| +4204| 1005| sip:1005@bchilton.com| Terminated - BYE (calling)| 5/57/48|CM[term]->SM100(200)[term]->CM>
[term]->DuVoic>

 

[kyle555]

Would I be correct in assuming 7430 is the guest room? Do you have a document that indicates how DuVoice does MWI over SIP for Avaya CM?

Would I be correct in assuming *04 is the Leave Word Calling activation code in your CM feature codes? Because I've only seen leave word calling used in integrations with analog or digital set emulation (say, with a Dialogic card in your DuVoice that emulates Avaya 8434 phones).

Generally, leave word calling is a feature invoked by stations - not over a trunk. Over a trunk, you'd use a QSIG message in ISDN/H323 or NOTIFY in SIP and the "message center" would be "sip-adjunct" as would "MWI server type" in the station form.

I suppose I don't see why your DuVoice couldn't have a trunk, as well as register a SIP station to SM with console permissions and use the feature code to light the lamp, but I've never seen it, it would be far easier to use SIP notify, and it might need to invite:*04, wait for CM to return dial tone, and then pass DTMF 7430 and not be able to get it all in one go.

Is this what you're trying to do?

http://www.devconnectprogram.com/fileMedia/download/8298cf89-24b2-4200-b6fd-ed2f17c2d0d3

 

[Bonker1974]

@ kyle555
Yes the link is correct. That's what I am trying to do.

 

[kyle555]

Then I'm not sure why it isn't sending a SIP NOTIFY and trying with the * code

 

[Bonker1974]

@Kyle555
Thanks for your help I got the problem resolved. The DuVoice guy was sending me the *04 when he should of been sending SIP NOTIFY like you said.

You have been a great help.