Hi All... I'm trying to get the intercom feature working on some snom 190 phones but having no luck... As you can see from the SIP trace below (from the called phone), intercom=true is being appended to the To: header as per requirements. I've email'd snom a few days ago but have yet to get a response. On my 190s, im running snom190-SIP 3.57v. I am pulling the config for the phone from a web page. Im setting: intercom_enabled&: on Looking in the settings.htm page on the phone verifies this, as does the listing in the advanced.htm page. Any one have any ideas why I'm having this problem? Cheers, -Shaun <>====================Received from udp:203.30.X.Y:5060 at 17/3/2005 15:40:59:030 (987 bytes): INVITE sip:1011@192.168.10.150:2051;line=9avrmhew SIP/2.0 Via: SIP/2.0/UDP 203.30.X.Y:5060;branch=z9hG4bK02a02946;rport From: "Shaun" <sip:1010@203.30.X.Y>;tag=as1fc0080d To: <sip:1011@192.168.10.150:2051;line=9avrmhew>;intercom=true Contact: <sip:1010@203.30.X.Y> Call-ID: 5c6546c54487eeab5a0975524e62bae2@203.30.X.Y CSeq: 102 INVITE User-Agent: Asterisk PBX Date: Thu, 17 Mar 2005 07:40:59 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER Content-Type: application/sdp Content-Length: 467 v=0 o=root 8153 8153 IN IP4 203.30.X.Y s=session c=IN IP4 203.30.X.Y t=0 0 m=audio 10850 RTP/AVP 8 0 3 97 4 2 5 10 7 18 110 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:3 GSM/8000 a=rtpmap:97 iLBC/8000 a=rtpmap:4 G723/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:5 DVI4/8000 a=rtpmap:10 L16/8000 a=rtpmap:7 LPC/8000 a=rtpmap:18 G729/8000 a=rtpmap:110 speex/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - -
> As you can see from the SIP trace below (from the called phone), > intercom=true is being appended to the To: header as per requirements.The "intercom=true" needs to be appended to the request URI, not to the header as a whole -- your To: header should be: To: <sip:1011 at 192.168.10.150:2051;line=9avrmhew;intercom=true> Mind you, I didn't get the phone to respond to the intercom=true until I added it on the request line as well, so the INVITE line of your request would be: INVITE sip:1011 at 192.168.10.150:2051;line=9avrmhew;intercom=true SIP/2.0 I'm on a Snom 220 with SIP 3.56t, and I'm stuck on the very next step of the process -- answering the phone's challenge to the INVITE request. The wiki indicates that the Snom needs to challenge with realm=snom, but even if I add snom into our internal DNS so that I can set the registrar to snom (that being the only way I can see to change what the phone uses as realm), it still rejects the digest response. Anyone have this working with recent loads of SIP that can shed any light on this?> I've email'd snom a few days ago but have yet to get a response.According to their web page, they have a new office as of April 1, and I got a response to a support request (on this very issue) today saying that they'd likely not be able to respond until people are settled into the new offices, so you'll likely have to be patient with them. -- Joshua P. Dady -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3721 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20050317/cc998854/smime.bin
> As you can see from the SIP trace below (from the called phone), > intercom=true is being appended to the To: header as per requirements.The "intercom=true" needs to be appended to the request URI, not to the header as a whole -- your To: header should be: To: <sip:1011 at 192.168.10.150:2051;line=9avrmhew;intercom=true> Mind you, I didn't get the phone to respond to the intercom=true until I added it on the request line as well, so the INVITE line of your request would be: INVITE sip:1011 at 192.168.10.150:2051;line=9avrmhew;intercom=true SIP/2.0 I'm on a Snom 220 with SIP 3.56t, and I'm stuck on the very next step of the process -- answering the phone's challenge to the INVITE request. The wiki indicates that the Snom needs to challenge with realm=snom, but even if I add snom into our internal DNS so that I can set the registrar to snom (that being the only way I can see to change what the phone uses as realm), it still rejects the digest response. Anyone have this working with recent loads of SIP that can shed any light on this?> I've email'd snom a few days ago but have yet to get a response.According to their web page, they have a new office as of April 1, and I got a response to a support request (on this very issue) today saying that they'd likely not be able to respond until people are settled into the new offices, so you'll likely have to be patient with them. -- Joshua P. Dady