Jump to content

870 message key not working


xy3
 Share

Recommended Posts

Newbie setting up snom ONE SoHo and struggling with the 'Message' key on an 870 set. Pressing the lit key after a message is left gives only a momentary '8200 calling' on the display, then almost immediately '8200 NOT FOUND', and a couple of seconds of fast busy tome (reorder). Suspect it's something dumb that we did.. but can't figure out what.

 

The 870 is running 8.4.33 and Soho is running 4.3.0.5021. Note we have snom Vision in use, so keeping 870 f/w at 8.4.32 or .33 is important for sensible BLF/LED behavior. Active identity of the set is extension 200.

 

I don't see anything in a SIP trace after pressing the message key. Dialing "8200" via the keypad does bring us to voicemail without problem (as will dialing 200 from the same extension, or dialing the *97 access code). But the 'message' hard key fails (as described above) every time. Suggestions? Ideas? Workarounds??

Link to comment
Share on other sites

Yes; the value was '8'. As noted, oddly, dialing '8200' from the set's keypad works fine. Pressing the 'Message' key fails every time, as described.

 

Here's a SIP trace following a couple of 'Message' key presses:

 

Sent to udp:192.168.0.100:5060 at 12/12/2011 12:11:00:701 (477 bytes):

 

SUBSCRIBE sip:192.168.0.100:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.0.5:3072;branch=z9hG4bK-b2jo2mcjmruq;rport

From: <sip:200@192.168.0.100>;tag=fmwxu9y0r9

To: <sip:300@192.168.0.100;user=phone>;tag=5ec0582220

Call-ID: f9ee283c919f-gw0mdp1y1fug

CSeq: 736 SUBSCRIBE

Max-Forwards: 70

Contact: <sip:200@192.168.0.5:3072;line=q9ppce6b>;reg-id=1

Event: dialog

Accept: application/dialog-info+xml

User-Agent: snom870/8.4.33

Expires: 3600

Content-Length: 0

 

Received from udp:192.168.0.100:5060 at 12/12/2011 12:11:00:709 (332 bytes):

 

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.0.5:3072;branch=z9hG4bK-b2jo2mcjmruq;rport=3072

From: <sip:200@192.168.0.100>;tag=fmwxu9y0r9

To: <sip:300@192.168.0.100;user=phone>;tag=5ec0582220

Call-ID: f9ee283c919f-gw0mdp1y1fug

CSeq: 736 SUBSCRIBE

Contact: <sip:192.168.0.100:5060;transport=udp>

Expires: 359

Content-Length: 0

 

Sent to udp:192.168.0.100:5060 at 12/12/2011 12:11:26:402 (693 bytes):

 

REGISTER sip:192.168.0.100 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.5:3072;branch=z9hG4bK-eu1trzpapx3h;rport

From: <sip:201@192.168.0.100>;tag=arn7wezmoe

To: <sip:201@192.168.0.100>

Call-ID: 2b70263c1ee5-pi9jlsjsjs67

CSeq: 3652 REGISTER

Max-Forwards: 70

Contact: <sip:201@192.168.0.5:3072;line=907rdkpu>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:d928a5d1-e017-44c8-8f44-000413410439>";audio;mobility="fixed";duplex="full";description="snom870";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"

User-Agent: snom870/8.4.33

Allow-Events: dialog

X-Real-IP: 192.168.0.5

Supported: path, gruu

Expires: 3600

Content-Length: 0

 

Received from udp:192.168.0.100:5060 at 12/12/2011 12:11:26:415 (338 bytes):

 

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.0.5:3072;branch=z9hG4bK-eu1trzpapx3h;rport=3072

From: <sip:201@192.168.0.100>;tag=arn7wezmoe

To: <sip:201@192.168.0.100>;tag=c80f3ed558

Call-ID: 2b70263c1ee5-pi9jlsjsjs67

CSeq: 3652 REGISTER

Contact: <sip:201@192.168.0.5:3072;line=907rdkpu>;expires=360

Supported: path

Content-Length: 0

Link to comment
Share on other sites

I guess the message key is programmed to be a Action URL, from a previous automatic provisioning. This is using HTTP, not SIP. What could be is that the HTTP port cannot be reached by the phone. If you can log in to the web interface of the phone, you can check what has been set for MWI.<br><br>The other thing is that 8.4.33 seems to stil have a couple of bugs, so if you can try moving to 8.4.31 or 8.4.34. Make sure that you factory reset the phone, so there is no leftover from previous configurations.

 

 

Link to comment
Share on other sites

Looking at 'function key's tab of 870 UI, that key just shows type = key event, number = retrieve. Tried clearing settings and downloaded 8.4.32. Same result; '8200 not found' when pressing they hard key. Works fine when I dial 8200 (or 200) from the keypad. Think you're onto something about http vs SIP; can you be a little more specific about what I should check in the 870's config? Also, where is 8.4.34 f/w? I did not spot it. Many thanks for your attention.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...