mattlandis Posted November 3, 2010 Report Share Posted November 3, 2010 4.2.0.3958 (Win32) the problem is we can park a call using this new park orbit account and a park orbit button on a snom phone, (park orbit button on snom phone indicates fine) but we cannot retrieve the call using the button. If we type *86 <ext> we can retreive the parked call. If we use the park orbit button the snom phone it just drops the call. Also, and maybe related: in the new park orbit account type we can't seem to save a value in: "Extensions that may use this orbit:" Matt Quote Link to comment Share on other sites More sharing options...
pbx support Posted November 4, 2010 Report Share Posted November 4, 2010 4.2.0.3958 (Win32) the problem is we can park a call using this new park orbit account and a park orbit button on a snom phone, (park orbit button on snom phone indicates fine) but we cannot retrieve the call using the button. If we type *86 <ext> we can retreive the parked call. If we use the park orbit button the snom phone it just drops the call. Also, and maybe related: in the new park orbit account type we can't seem to save a value in: "Extensions that may use this orbit:" Matt Can you please let us know what is set on the button profile and star codes for park & retrieve? Just wanted to recreate the same here. Quote Link to comment Share on other sites More sharing options...
mattlandis Posted November 4, 2010 Author Report Share Posted November 4, 2010 Can you please let us know what is set on the button profile and star codes for park & retrieve? Just wanted to recreate the same here. very simple. the snom phone button is set to park orbit. (you can provision this from snom one or set it in snom phone) we cannot have a button to put calls into an orbit and a seperate one to take out. That's far too many buttons if we have more than one park orbit. thanks, Matt Quote Link to comment Share on other sites More sharing options...
Vodia support Posted November 4, 2010 Report Share Posted November 4, 2010 All you have to do is edit the "Call Park" and "Call Park Retrieve" with the same star code for example if the star code is *85 then both "Call Park" and "Call Park Retrieve" need the same star code. Then create a button profile with "Park orbit" and in the parameter field add the the park orbit account only no star code feature needed. You should be able to retrieve the call in and out with the buttons now. Quote Link to comment Share on other sites More sharing options...
mattlandis Posted November 4, 2010 Author Report Share Posted November 4, 2010 i shall test! ;-) Quote Link to comment Share on other sites More sharing options...
Vodia support Posted November 4, 2010 Report Share Posted November 4, 2010 4.2.0.3958 (Win32) the problem is we can park a call using this new park orbit account and a park orbit button on a snom phone, (park orbit button on snom phone indicates fine) but we cannot retrieve the call using the button. If we type *86 <ext> we can retreive the parked call. If we use the park orbit button the snom phone it just drops the call. Also, and maybe related: in the new park orbit account type we can't seem to save a value in: "Extensions that may use this orbit:" Matt "Extensions that may use this orbit" will be removed from the park orbit section. MR X Quote Link to comment Share on other sites More sharing options...
mattlandis Posted November 4, 2010 Author Report Share Posted November 4, 2010 thanks for headsup Quote Link to comment Share on other sites More sharing options...
mattlandis Posted November 4, 2010 Author Report Share Posted November 4, 2010 All you have to do is edit the "Call Park" and"Call Park Retrieve" with the same star code for example if the star code is *85 then both "Call Park" and "Call Park Retrieve" need the same star code. Then create a button profile with "Park orbit" and in the parameter field add the the park orbit account only no star code feature needed. You should be able to retrieve the call in and out with the buttons now. The above solution does not work. Did you test it? Matt Quote Link to comment Share on other sites More sharing options...
pbx support Posted November 5, 2010 Report Share Posted November 5, 2010 The above solution does not work. Did you test it? Matt Test this on 4.2.0.3961 Steps: 1. Create a park orbit account (this is the new account type), say 555 2. Domain->Settings->Star codes page - set both park and retrieve as the same star code, say *85 3. Create a button profile with "Name=7, Type=Park orbit, Parameter=555" 4. Assign this button profile to the snom phone/extension of your choice, say 200. 5. Log in to phone and see if the "Function Keys" page show this button set 6. Place a call to this extension 200 7. Answer the call 8. Put the call on hold and Press the park button 7. 9. You will hear the message that the call is parked on orbit 555 10. Caller will be hearing the music on hold 11. Press the retrieve button (same button 7) 12. You should be connected back to the call. Quote Link to comment Share on other sites More sharing options...
mattlandis Posted November 5, 2010 Author Report Share Posted November 5, 2010 we will test...that is what we think we test already...but will try again..tx Quote Link to comment Share on other sites More sharing options...
broz Posted April 22, 2011 Report Share Posted April 22, 2011 There is also another problem. The park orbit does not save the on hold selection. Will that be removed too? Quote Link to comment Share on other sites More sharing options...
broz Posted April 22, 2011 Report Share Posted April 22, 2011 Why remove extension that can use this Park Orbit option, I think it's a good field. Quote Link to comment Share on other sites More sharing options...
Brian Barr Posted August 19, 2011 Report Share Posted August 19, 2011 Has this issue been resolved? I am seeing this exact same problem on version 4.2.1 (4025) on Darwin. In Domain, create a Park Orbit (extension 50) In Domain Star Codes, set Call Park/Call Retrieve to same code (*85) In Domain Buttons, Set button #11 on all phones to be "park orbit" with parameter 50 Reboot snom 370 on extension 40; Person A places a call to an extension (40); Person B at extension 40 answers call, speaks to Person A, then pushes button #11 on snom 370. Call is placed on "hold" in Park Orbit 50, Person A hears music on hold. Person B at extension 40, 1 minute later, pushes button #11 again, and nothing happens. Call remains on hold in park orbit. Quote Link to comment Share on other sites More sharing options...
Vodia support Posted August 23, 2011 Report Share Posted August 23, 2011 I was not able to reproduce this issue, I was able to park/pick it after 2-3 mins using the same star code *85 and programmed virtual keys on the snom 870. I am using the latest pbx Version 4.2.1.4025. On the phones I used http://provisioning.snom.com/download/fw/snom870-8.4.32-SIP-r.bin http://provisioning.snom.com/download/fw/snom821-8.4.32-SIP-r.bin for users that are having the park/pick up issue post your log files for some clues. Here is the log file. [8] 2011/08/23 10:32:21: Last message repeated 5 times [7] 2011/08/23 10:32:21: SIP Rx tls:192.168.0.38:3742: INVITE sip:1061@192.168.0.22:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS 192.168.0.38:3742;branch=z9hG4bK-dqyulvpvvi60;rport From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=h6hcyr391w To: <sip:1000@snomone;user=phone>;tag=4832f336f0 Call-ID: 0372263cea42-sgo36dk7qizv CSeq: 3 INVITE Max-Forwards: 70 Contact: <sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x>;reg-id=1 X-Serialnumber: 00041341181A P-Key-Flags: resolution="31x13", keys="4" User-Agent: snom870/8.4.32 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, 100rel, replaces, from-change Session-Expires: 3600;refresher=uas Min-SE: 90 Proxy-Require: buttons Content-Type: application/sdp Content-Length: 522 v=0 o=root 618371818 618371819 IN IP4 192.168.0.38 s=call c=IN IP4 192.168.0.38 t=0 0 m=audio 60720 RTP/AVP 9 0 8 2 3 18 4 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:XlNGNz4n+15mlSPa+el8UMAZhzRxtzuXGllyjkC+ a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:3 GSM/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:4 G723/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:voip-metrics stat-summary=loss,dup,jitt a=sendonly [8] 2011/08/23 10:32:21: Packet authenticated by transport layer [7] 2011/08/23 10:32:21: SIP Tx tls:192.168.0.38:3742: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.0.38:3742;branch=z9hG4bK-dqyulvpvvi60;rport=3742 From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=h6hcyr391w To: <sip:1000@snomone;user=phone>;tag=4832f336f0 Call-ID: 0372263cea42-sgo36dk7qizv CSeq: 3 INVITE Contact: <sip:1061@192.168.0.22:5061;transport=tls> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snom-PBX/2011-4.2.1.4025 Content-Type: application/sdp Content-Length: 478 v=0 o=- 246072395 246072395 IN IP4 192.168.0.22 s=- c=IN IP4 192.168.0.22 t=0 0 m=audio 54566 RTP/AVP 0 8 9 18 2 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:K8VEaFvFEep15sglbF2RmNuTN+fhqRuav6O55vUH a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:rcvr-rtt=all voip-metrics a=recvonly [8] 2011/08/23 10:32:21: Packet authenticated by transport layer [7] 2011/08/23 10:32:21: SIP Rx tls:192.168.0.38:3742: INVITE sip:*851@snomone;user=phone SIP/2.0 Via: SIP/2.0/TLS 192.168.0.38:3742;branch=z9hG4bK-ikoq42s4omu4;rport From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=ia3k6fifiz To: <sip:*851@snomone;user=phone> Call-ID: 0772263ca8ec-o5bf48ckjuz8 CSeq: 1 INVITE Max-Forwards: 70 Contact: <sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x>;reg-id=1 X-Serialnumber: 00041341181A P-Key-Flags: resolution="31x13", keys="4" User-Agent: snom870/8.4.32 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, 100rel, replaces, from-change Session-Expires: 3600;refresher=uas Min-SE: 90 Proxy-Require: buttons Content-Type: application/sdp Content-Length: 522 v=0 o=root 990779771 990779771 IN IP4 192.168.0.38 s=call c=IN IP4 192.168.0.38 t=0 0 m=audio 49196 RTP/AVP 9 0 8 2 3 18 4 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:8ZuC41ytzd/Vf9GxYATW0TBRgtFMqZVhNWbAL4UM a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:3 GSM/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:4 G723/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:voip-metrics stat-summary=loss,dup,jitt a=sendrecv [8] 2011/08/23 10:32:21: Packet authenticated by transport layer [7] 2011/08/23 10:32:21: SIP Tx tls:192.168.0.38:3742: SIP/2.0 100 Trying Via: SIP/2.0/TLS 192.168.0.38:3742;branch=z9hG4bK-ikoq42s4omu4;rport=3742 From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=ia3k6fifiz To: <sip:*851@snomone;user=phone>;tag=8a1160d5d6 Call-ID: 0772263ca8ec-o5bf48ckjuz8 CSeq: 1 INVITE Content-Length: 0 [8] 2011/08/23 10:32:21: Incoming call: Request URI sip:*851@snomone;user=phone, To is <sip:*851@snomone;user=phone> [8] 2011/08/23 10:32:21: Set the To domain based on From user 1061@snomone [7] 2011/08/23 10:32:21: SIP Rx tls:192.168.0.38:3742: ACK sip:1061@192.168.0.22:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS 192.168.0.38:3742;branch=z9hG4bK-b7dgl5fjq5tt;rport From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=h6hcyr391w To: <sip:1000@snomone;user=phone>;tag=4832f336f0 Call-ID: 0372263cea42-sgo36dk7qizv CSeq: 3 ACK Max-Forwards: 70 Contact: <sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x>;reg-id=1 Proxy-Require: buttons Content-Length: 0 [8] 2011/08/23 10:32:21: Packet authenticated by transport layer [7] 2011/08/23 10:32:21: SIP Tx tls:192.168.0.38:3742: MESSAGE sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x SIP/2.0 Via: SIP/2.0/TLS 192.168.0.22:5061;branch=z9hG4bK-7a35c7901f94945a1c339e7909799bda;rport From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=1021856375 To: "Lonnie VELAZQUEZ" <sip:1061@snomone> Call-ID: 9p8epz32@pbx CSeq: 1153828748 MESSAGE Max-Forwards: 70 Contact: <sip:192.168.0.22:5061;transport=tls> Subject: buttons Content-Type: application/x-buttons Content-Length: 42 k=1 c=park n=*851 a=invite l=Park1 [7] 2011/08/23 10:32:21: SIP Tx tls:192.168.0.38:3742: BYE sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x SIP/2.0 Via: SIP/2.0/TLS 192.168.0.22:5061;branch=z9hG4bK-44b52d79e0b068bf68baad4b3da6adeb;rport From: <sip:1000@snomone;user=phone>;tag=4832f336f0 To: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=h6hcyr391w Call-ID: 0372263cea42-sgo36dk7qizv CSeq: 30230 BYE Max-Forwards: 70 Contact: <sip:1061@192.168.0.22:5061;transport=tls> Content-Length: 0 [7] 2011/08/23 10:32:21: SIP Tx tls:192.168.0.38:3742: MESSAGE sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x SIP/2.0 Via: SIP/2.0/TLS 192.168.0.22:5061;branch=z9hG4bK-4364bf8ccf063bedeb10df6f9190d9a0;rport From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=676167076 To: "Lonnie VELAZQUEZ" <sip:1061@snomone> Call-ID: 4jwn9igi@pbx CSeq: 1542464117 MESSAGE Max-Forwards: 70 Contact: <sip:192.168.0.22:5061;transport=tls> Subject: buttons Content-Type: application/x-buttons Content-Length: 42 k=1 c=park n=*851 a=invite l=Park1 [7] 2011/08/23 10:32:21: SIP Tx tls:192.168.0.38:3742: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.0.38:3742;branch=z9hG4bK-ikoq42s4omu4;rport=3742 From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=ia3k6fifiz To: <sip:*851@snomone;user=phone>;tag=8a1160d5d6 Call-ID: 0772263ca8ec-o5bf48ckjuz8 CSeq: 1 INVITE Contact: <sip:1061@192.168.0.22:5061;transport=tls> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snom-PBX/2011-4.2.1.4025 Content-Type: application/sdp Content-Length: 480 v=0 o=- 1541682606 1541682606 IN IP4 192.168.0.22 s=- c=IN IP4 192.168.0.22 t=0 0 m=audio 52500 RTP/AVP 0 8 9 18 2 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:Y/YdxETwq6W8TwBhWHB5h5i/wm45ORK0YQ5Zdf06 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [8] 2011/08/23 10:32:21: Packet authenticated by transport layer [7] 2011/08/23 10:32:21: SIP Rx tls:192.168.0.38:3742: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.0.22:5061;branch=z9hG4bK-7a35c7901f94945a1c339e7909799bda;rport=5061 From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=1021856375 To: "Lonnie VELAZQUEZ" <sip:1061@snomone> Call-ID: 9p8epz32@pbx CSeq: 1153828748 MESSAGE Content-Length: 0 [8] 2011/08/23 10:32:21: Packet authenticated by transport layer [8] 2011/08/23 10:32:22: Last message repeated 3 times [7] 2011/08/23 10:32:22: SIP Rx tls:192.168.0.38:3742: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.0.22:5061;branch=z9hG4bK-4364bf8ccf063bedeb10df6f9190d9a0;rport=5061 From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=676167076 To: "Lonnie VELAZQUEZ" <sip:1061@snomone> Call-ID: 4jwn9igi@pbx CSeq: 1542464117 MESSAGE Content-Length: 0 [7] 2011/08/23 10:32:22: SIP Rx tls:192.168.0.38:3742: ACK sip:1061@192.168.0.22:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS 192.168.0.38:3742;branch=z9hG4bK-mbloufbczzn3;rport From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=ia3k6fifiz To: <sip:*851@snomone;user=phone>;tag=8a1160d5d6 Call-ID: 0772263ca8ec-o5bf48ckjuz8 CSeq: 1 ACK Max-Forwards: 70 Contact: <sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x>;reg-id=1 Proxy-Require: buttons Content-Length: 0 [8] 2011/08/23 10:32:22: Packet authenticated by transport layer [7] 2011/08/23 10:32:22: SIP Rx tls:192.168.0.38:3742: SIP/2.0 200 OK Via: SIP/2.0/TLS 192.168.0.22:5061;branch=z9hG4bK-44b52d79e0b068bf68baad4b3da6adeb;rport=5061 From: <sip:1000@snomone;user=phone>;tag=4832f336f0 To: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=h6hcyr391w Call-ID: 0372263cea42-sgo36dk7qizv CSeq: 30230 BYE Contact: <sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x>;reg-id=1 User-Agent: snom870/8.4.32 RTP-RxStat: Total_Rx_Pkts=165,Rx_Pkts=42,Rx_Pkts_Lost=0,Remote_Rx_Pkts_Lost=0 RTP-TxStat: Total_Tx_Pkts=164,Tx_Pkts=52,Remote_Tx_Pkts=-739068640 Content-Length: 0 [7] 2011/08/23 10:32:22: Call 0372263cea42-sgo36dk7qizv: Clear last request [5] 2011/08/23 10:32:22: BYE Response: Terminate 0372263cea42-sgo36dk7qizv [8] 2011/08/23 10:32:22: Packet authenticated by transport layer [8] 2011/08/23 10:32:24: Last message repeated 7 times [7] 2011/08/23 10:32:24: SIP Tx tls:192.168.0.38:3742: BYE sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x SIP/2.0 Via: SIP/2.0/TLS 192.168.0.22:5061;branch=z9hG4bK-fb289f6f092dfce799f41ffc0ce3ad22;rport From: <sip:*851@snomone;user=phone>;tag=8a1160d5d6 To: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=ia3k6fifiz Call-ID: 0772263ca8ec-o5bf48ckjuz8 CSeq: 18728 BYE Max-Forwards: 70 Contact: <sip:1061@192.168.0.22:5061;transport=tls> Content-Length: 0 [7] 2011/08/23 10:32:24: SIP Rx tls:192.168.0.38:3742: SIP/2.0 200 OK Via: SIP/2.0/TLS 192.168.0.22:5061;branch=z9hG4bK-fb289f6f092dfce799f41ffc0ce3ad22;rport=5061 From: <sip:*851@snomone;user=phone>;tag=8a1160d5d6 To: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=ia3k6fifiz Call-ID: 0772263ca8ec-o5bf48ckjuz8 CSeq: 18728 BYE Contact: <sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x>;reg-id=1 User-Agent: snom870/8.4.32 RTP-RxStat: Total_Rx_Pkts=173,Rx_Pkts=173,Rx_Pkts_Lost=0,Remote_Rx_Pkts_Lost=0 RTP-TxStat: Total_Tx_Pkts=174,Tx_Pkts=183,Remote_Tx_Pkts=-739068640 Content-Length: 0 [7] 2011/08/23 10:32:24: Call 0772263ca8ec-o5bf48ckjuz8: Clear last request [5] 2011/08/23 10:32:24: BYE Response: Terminate 0772263ca8ec-o5bf48ckjuz8 [8] 2011/08/23 10:32:25: Packet authenticated by transport layer [8] 2011/08/23 10:32:36: Last message repeated 46 times [7] 2011/08/23 10:32:36: SIP Rx tls:192.168.0.38:3742: INVITE sip:*851@snomone;user=phone SIP/2.0 Via: SIP/2.0/TLS 192.168.0.38:3742;branch=z9hG4bK-wkspogud252s;rport From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=ev6kyo5omg To: <sip:*851@snomone;user=phone> Call-ID: 1672263cd9cb-503i6u1l0a6z CSeq: 1 INVITE Max-Forwards: 70 Contact: <sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x>;reg-id=1 X-Serialnumber: 00041341181A P-Key-Flags: resolution="31x13", keys="4" User-Agent: snom870/8.4.32 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, 100rel, replaces, from-change Session-Expires: 3600;refresher=uas Min-SE: 90 Proxy-Require: buttons Content-Type: application/sdp Content-Length: 522 v=0 o=root 425836819 425836819 IN IP4 192.168.0.38 s=call c=IN IP4 192.168.0.38 t=0 0 m=audio 65162 RTP/AVP 9 0 8 2 3 18 4 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:bWCb9ZI9UkZWe5FU7QiDzbiWfzXWFT/Qrsi4ndeX a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:3 GSM/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:4 G723/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:voip-metrics stat-summary=loss,dup,jitt a=sendrecv [8] 2011/08/23 10:32:36: Packet authenticated by transport layer [7] 2011/08/23 10:32:36: SIP Tx tls:192.168.0.38:3742: SIP/2.0 100 Trying Via: SIP/2.0/TLS 192.168.0.38:3742;branch=z9hG4bK-wkspogud252s;rport=3742 From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=ev6kyo5omg To: <sip:*851@snomone;user=phone>;tag=0c720f6875 Call-ID: 1672263cd9cb-503i6u1l0a6z CSeq: 1 INVITE Content-Length: 0 [8] 2011/08/23 10:32:36: Incoming call: Request URI sip:*851@snomone;user=phone, To is <sip:*851@snomone;user=phone> [8] 2011/08/23 10:32:36: Set the To domain based on From user 1061@snomone [7] 2011/08/23 10:32:36: SIP Tx tls:192.168.0.38:3742: MESSAGE sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x SIP/2.0 Via: SIP/2.0/TLS 192.168.0.22:5061;branch=z9hG4bK-1f09f1ec2e4789ce0e77caeabf29a425;rport From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=32243633 To: "Lonnie VELAZQUEZ" <sip:1061@snomone> Call-ID: m53djq79@pbx CSeq: 1965502478 MESSAGE Max-Forwards: 70 Contact: <sip:192.168.0.22:5061;transport=tls> Subject: buttons Content-Type: application/x-buttons Content-Length: 34 k=1 n=*851 a=invite l=Park1 [7] 2011/08/23 10:32:36: SIP Tx tls:192.168.0.38:3742: INFO sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x SIP/2.0 Via: SIP/2.0/TLS 192.168.0.22:5061;branch=z9hG4bK-592a0642fc824ac5b86c7b6dcb559d67;rport From: "Kurtis WHITFIELD" <sip:1000@snomone>;tag=0c720f6875 To: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=ev6kyo5omg Call-ID: 1672263cd9cb-503i6u1l0a6z CSeq: 19256 INFO Max-Forwards: 70 Contact: <sip:1061@192.168.0.22:5061;transport=tls> Content-Type: message/sipfrag Content-Length: 88 From: "Kurtis WHITFIELD" <sip:1000@snomone> To: "Lonnie VELAZQUEZ" <sip:1061@snomone> [7] 2011/08/23 10:32:36: SIP Tx tls:192.168.0.38:3742: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.0.38:3742;branch=z9hG4bK-wkspogud252s;rport=3742 From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=ev6kyo5omg To: <sip:*851@snomone;user=phone>;tag=0c720f6875 Call-ID: 1672263cd9cb-503i6u1l0a6z CSeq: 1 INVITE Contact: <sip:1061@192.168.0.22:5061;transport=tls> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snom-PBX/2011-4.2.1.4025 Content-Type: application/sdp Content-Length: 478 v=0 o=- 348350826 348350826 IN IP4 192.168.0.22 s=- c=IN IP4 192.168.0.22 t=0 0 m=audio 61236 RTP/AVP 0 8 9 18 2 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:xMRN1zT4P8aGSvKDwbcSK9bFR0lBims4wg5Y9yew a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [7] 2011/08/23 10:32:36: SIP Rx tls:192.168.0.38:3742: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.0.22:5061;branch=z9hG4bK-1f09f1ec2e4789ce0e77caeabf29a425;rport=5061 From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=32243633 To: "Lonnie VELAZQUEZ" <sip:1061@snomone> Call-ID: m53djq79@pbx CSeq: 1965502478 MESSAGE Content-Length: 0 [7] 2011/08/23 10:32:36: SIP Rx tls:192.168.0.38:3742: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.0.22:5061;branch=z9hG4bK-592a0642fc824ac5b86c7b6dcb559d67;rport=5061 From: "Kurtis WHITFIELD" <sip:1000@snomone>;tag=0c720f6875 To: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=ev6kyo5omg Call-ID: 1672263cd9cb-503i6u1l0a6z CSeq: 19256 INFO Contact: <sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x>;reg-id=1 Content-Length: 0 [7] 2011/08/23 10:32:36: Call 1672263cd9cb-503i6u1l0a6z: Clear last request [8] 2011/08/23 10:32:36: Packet authenticated by transport layer [7] 2011/08/23 10:32:36: SIP Rx tls:192.168.0.38:3742: ACK sip:1061@192.168.0.22:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS 192.168.0.38:3742;branch=z9hG4bK-y4a3eiziu8ra;rport From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=ev6kyo5omg To: "Kurtis WHITFIELD" <sip:1000@snomone>;tag=0c720f6875 Call-ID: 1672263cd9cb-503i6u1l0a6z CSeq: 1 ACK Max-Forwards: 70 Contact: <sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x>;reg-id=1 Proxy-Require: buttons Content-Length: 0 [8] 2011/08/23 10:32:36: Packet authenticated by transport layer [8] 2011/08/23 10:32:41: Last message repeated 24 times [7] 2011/08/23 10:32:41: SIP Rx tls:192.168.0.38:3742: BYE sip:1061@192.168.0.22:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS 192.168.0.38:3742;branch=z9hG4bK-tsvggs8qiih4;rport From: "Lonnie VELAZQUEZ" <sip:1061@snomone>;tag=ev6kyo5omg To: "Kurtis WHITFIELD" <sip:1000@snomone>;tag=0c720f6875 Call-ID: 1672263cd9cb-503i6u1l0a6z CSeq: 2 BYE Max-Forwards: 70 Contact: <sip:1061@192.168.0.38:3742;transport=tls;line=k3htv34x>;reg-id=1 User-Agent: snom870/8.4.32 RTP-RxStat: Total_Rx_Pkts=261,Rx_Pkts=261,Rx_Pkts_Lost=0,Remote_Rx_Pkts_Lost=0 RTP-TxStat: Total_Tx_Pkts=262,Tx_Pkts=262,Remote_Tx_Pkts=256 Proxy-Require: buttons Content-Length: 0 Quote Link to comment Share on other sites More sharing options...
reco Posted October 10, 2011 Report Share Posted October 10, 2011 i do have 4.2.1.4025 (Darwin) with snom 870. works fine even i have different codes for Call Park and Call Park Receive. one annoying thing though is the *85xx in the dialed numbers list. is there a way to exclude feature codes form that list? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 11, 2011 Report Share Posted October 11, 2011 one annoying thing though is the *85xx in the dialed numbers list. is there a way to exclude feature codes form that list? Well, we discussed that recently. Problem is that in the call center environment, people love to use such codes to trace when agents logged in and out. For me the answer was: Show star codes in the CDR, but dont show them in the web interface. We are moving things to JavaScript anyway here, so that at the end of the day this will be in the hands if the web code anyway and if neccessary, admins can change it. Quote Link to comment Share on other sites More sharing options...
djanjic Posted January 22, 2012 Report Share Posted January 22, 2012 Test this on 4.2.0.3961 Steps: 1. Create a park orbit account (this is the new account type), say 555 2. Domain->Settings->Star codes page - set both park and retrieve as the same star code, say *85 3. Create a button profile with "Name=7, Type=Park orbit, Parameter=555" 4. Assign this button profile to the snom phone/extension of your choice, say 200. 5. Log in to phone and see if the "Function Keys" page show this button set 6. Place a call to this extension 200 7. Answer the call 8. Put the call on hold and Press the park button 7. 9. You will hear the message that the call is parked on orbit 555 10. Caller will be hearing the music on hold 11. Press the retrieve button (same button 7) 12. You should be connected back to the call. I started a topic http://forum.snomone.com/index.php?/topic/5646-park-orbit-on-hosted-system/ which essentialy describes the same problem discussed in here. There are few differences: 1. We are using HOSTED VERSION 4.3.0.5021 (Win32). 2. We are using Snom's 320 and 370 with 8.4.32 firmware on them instead 870 which people are describing. We cannot make this work!!! If need be we can provide logs... Dusan Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.