Jump to content

Chappo

Members
  • Posts

    48
  • Joined

  • Last visited

Posts posted by Chappo

  1. The setting you need to adjust is the following -

     

    http://wiki.snom.com/Settings/always_show_active_call

     

    This setting is used to configure the default behaviour in call waiting scenarios. Default value on will keep the active call on the display, regardless of any incoming calls. All user actions such as hold or transfer will effect the active call. Disabling this setting will display the latest incoming call (all actions will be applied to the call displayed)

  2. Just installed 5.2.0 - the caller ID works as expected which is great, however the received caller list is still showing the internal callers name and ext number.

     

    Should the Caller ID also show the internal party that transferred the call? At the moment it shows both the 0423 XXX XXX and +61 423 XXX XXX numbers.

  3. Well, as for the call pick up CDR on the phone. If you tell me how we can write the phones CDR, we could take a look at this! But the call pickup is a star code.

     

    But to the end user the star code is irrelevant.

     

    My main issue with this revision is that the phones are not updating the Caller ID of an external party when the call is picked up via star pickup. Previously on 5.1.2 this worked ok. Currently the screen will only display the current logged in users name and extension on the line below.

     

    See: https://dl.dropboxusercontent.com/u/56065335/screen%20external%20call%20no%20clid.bmp

     

    I have gone back to 5.1.2v and this is what you get when you answer a call via star code - https://dl.dropboxusercontent.com/u/56065335/CLIDcorrect_screen.bmp

     

    The dialled / received behaviour is still the same other than the received list would show the internal party that transferred the call and next to it display the caller ID of the external call. Now it only shows the internal extension.

     

    Edit:

    5.1.2v - Outgoing CLID broken

    5.1.2w - Incoming CLID broken

    5.1.3 - Incoming CLID broken

  4. Caller ID appears to be broken yet again?

     

    Any phones that are answering a shared line (through line hunt) are only showing their own name and extension number? Received calls are showing outbound calls which have been made to other users.

     

    Dialed numbers is showing incoming calls - just the star code entry for the pickup.

     

    Snomone server user login is not showing any call history.

     

    Phone settings are as follows (Using Firmware-Version: snom821-SIP 8.7.3.25) - (Phone is extension 45) -

     

    <callrecord_received_local idx="0" perm="">45@pbx.domain.com.au</callrecord_received_local>
    <callrecord_received_local idx="1" perm="">45@pbx.domain.com.au</callrecord_received_local>
    <callrecord_received_local idx="2" perm="">45@pbx.domain.com.au</callrecord_received_local>
    <callrecord_received_local idx="3" perm="">45@pbx.domain.com.au</callrecord_received_local>
    <callrecord_received_local idx="4" perm="">45@pbx.domain.com.au</callrecord_received_local>
    <callrecord_received_remote idx="0" perm="">sip:44@pbx.domain.com.au</callrecord_received_remote>
    <callrecord_received_remote idx="1" perm="">sip:40@pbx.domain.com.au</callrecord_received_remote>
    <callrecord_received_remote idx="2" perm="">sip:40@pbx.domain.com.au</callrecord_received_remote>
    <callrecord_received_remote idx="3" perm="">sip:40@pbx.domain.com.au</callrecord_received_remote>
    <callrecord_received_remote idx="4" perm="">sip:40@pbx.domain.com.au</callrecord_received_remote>
    <callrecord_dialed_local idx="0" perm="">45@pbx.domain.com.au</callrecord_dialed_local>
    <callrecord_dialed_local idx="1" perm="">45@pbx.domain.com.au</callrecord_dialed_local>
    <callrecord_dialed_local idx="2" perm="">45@pbx.domain.com.au</callrecord_dialed_local>
    <callrecord_dialed_local idx="3" perm="">45@pbx.domain.com.au</callrecord_dialed_local>
    <callrecord_dialed_local idx="4" perm="">45@pbx.domain.com.au</callrecord_dialed_local>
    <callrecord_dialed_remote idx="0" perm="">sip:*601236@pbx.domain.com.au</callrecord_dialed_remote>
    <callrecord_dialed_remote idx="1" perm="">sip:*9044@pbx.domain.com.au</callrecord_dialed_remote>
    <callrecord_dialed_remote idx="2" perm="">sip:*601223@pbx.domain.com.au</callrecord_dialed_remote>
    <callrecord_dialed_remote idx="3" perm="">sip:*601134@pbx.domain.com.au</callrecord_dialed_remote>
    <callrecord_dialed_remote idx="4" perm="">sip:*9048@pbx.domain.com.au</callrecord_dialed_remote>
  5. Some devices have no valid certificate. It seems that there are good and bad devices... If you get a message like this, open the account for provisioning from the web interface. 5.1 also contains a new setting (admin/provisioning/settings) where you can set how long an extension should be open for provisioning. The default of 10 minutes was in many cases too short, especially in LAN environments where the risk of getting hacked is relatively low. Also make sure that you have the right MAC set for the extension.

     

    Changing back to 5.0.10m resolved the issue instantly.

  6. Looks like the provisioning bug has been reintroduced.

     

    Did not write snom_821.xml to file system because there is no user associated with this file [5] 2013/07/24 10:13:22: Alert(1, 0) [5] 2013/07/24 10:13:22: Did not write snom_3xx_fw.xml to file system because there is no user associated with this file [5] 2013/07/24 10:13:22: Alert(1, 0) [5] 2013/07/24 10:13:22: Last message repeated 3 times [5] 2013/07/24 10:13:22: Did not write snom_web_lang.xml to file system because there is no user associated with this file [5] 2013/07/24 10:13:22: Alert(1, 0) [5] 2013/07/24 10:13:23: Did not write snom_gui_lang.xml to file system because there is no user associated with this file [5] 2013/07/24 10:13:23: Alert(1, 0) [5] 2013/07/24 10:13:25: Did not write snom_3xx_fs.xml to file system because there is no user associated with this file
  7. Any one else seeing errors with dial plans on 5.10?

     

    When CO line 4 is in use and you attempt to dial without pre-selecting a line (ie via softphone dialer - flexor) it will give you a Not Found error from the pbx. As you can see from the logs it is selecting the in use line and not the next available.

     

    90;MNF 4 0940XXX9;;*;;;

    91;MNF 3 0940XXX8;;*;;;

    92;MNF 2 0940XXX7;;*;;;

    93;MNF 1 0940XXX6;;*;;;

     

    [5] 2013/05/21 11:33:50: Dialplan "Standard Dialplan": Match 9380XXXX@pbx.company.com.au to sip:9380XXXX@sip00.mynetfone.com.au;user=phone on trunk MNF 4 0940XXX9

    [5] 2013/05/21 11:33:50: SIP Tx tls:172.28.1.82:4166:

    SIP/2.0 404 Not Found

    Via: SIP/2.0/TLS 172.28.1.82:4166;branch=z9hG4bK-764esf4o6slq;rport=4166

    From: "Name" <sip:45@pbx.company.com.au>;tag=7t82c4lsu0

    To: <sip:9380XXXX@pbx.company.com.au;user=phone>;tag=82798b75e5

    Call-ID: 1deb9a51c8c6-mt3yzia6j9ne

    CSeq: 1 INVITE

    Contact: <sip:45@172.28.1.5:5061;transport=tls>

    Supported: 100rel, replaces, norefersub

    Allow-Events: refer

    Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

    Accept: application/sdp

    User-Agent: snomONE/5.0.10

    Content-Length: 0

     

    [5] 2013/05/21 11:33:50: SIP Rx tls:172.28.1.82:4166:

    ACK sip:9380XXXX@pbx.company.com.au;user=phone SIP/2.0

    Via: SIP/2.0/TLS 172.28.1.82:4166;branch=z9hG4bK-764esf4o6slq;rport

    From: "Name" <sip:45@pbx.company.com.au>;tag=7t82c4lsu0

    To: <sip:9380XXXX@pbx.company.com.au;user=phone>;tag=82798b75e5

    Call-ID: 1deb9a51c8c6-mt3yzia6j9ne

    CSeq: 1 ACK

    Max-Forwards: 70

    Contact: <sip:45@172.28.1.82:4166;transport=tls;line=bkwxc3sx>;reg-id=1

    Proxy-Require: buttons-snom821

    Content-Length: 0

  8. CDR email broken since 5.0.8?

     

    It seems that the new format email is not working correctly? The email I receive is all random characters.

     

    ٥杙뚆۩z*'魏*^rm{ ٥r 뮵&z֡ڞ诊Kjx.j{^קɞm+¢{^ԭʗʗ{^۞Ɵܲ˭ʗʗ{ r˜M쭾ޗjq)ޅ蠆ݺ 螗ښ)r w뢱 ˞'ܢZ+뮺몚uاک✡y^dކרۢͭ| b螊 m۪q~

    +Gz[޶' 챪⽊%v+骘w+m{ l7v;z'{-ʗٞ eӏW杮rܥyʥ4Ӎ4m$.רߥ_榫)x4"*'隶+޶+췩^~ޖ\Z+bZʺ'x&ʧۍwN?׿݊ K-ʗbZɹhrF{ ]yʫj

    ب靺b櫲W--ʗ؟幺+u괱饥]x4q饲x4§m]4]b{h Z+ ܺ{^֛樭׫ѩbw ׫q饥]x4q饲x4§m

  9. This is what has been provided by the VSP.

     

    INVITE sip:1300887899@sip10.mynetfone.com.au:5060 SIP/2.0

    Via: SIP/2.0/UDP 192.168.5.150:5060;branch=z9hG4bK-d8754z-591caa70b8520754-1---d8754z-;rport=61973;received=xxx.xxx.xxx.xxx

    Max-Forwards: 70

    Contact: <sip:09123456@xxx.xxx.xxx.xxx:5060>

    To: <sip:1300887899@sip10.mynetfone.com.au:5060>

    From: "0280088000"<sip: 09123456@sip10.mynetfone.com.au:5060>;tag=e53ba10d

    Call-ID: MTY4YTMxOTE2MDk4ZTAzMThkYmFlY2QwY2MxZTE4MDE.

    CSeq: 1 INVITE

    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE

    Content-Type: application/sdp

    Supported: replaces

    User-Agent:

    Content-Length: 332

    Remote-Party-ID: "0280088000"<sip: 0280088000@sip10.mynetfone.com.au:5060>;party=calling

     

    ^ Please ensure that your remote party ID or P asserted identity string is exactly the same as the "from" string – The above example would fail because it is not the same.

     

    Typically the P Asserted Identity would be your internal extension number OR your DID.

  10. Can confirm the issues with provisioning.

     

    2013/05/02 15:24:55: Received SUBSCRIBE for plug and play. SIP multicast support is set to handle plug and play.

    [5] 2013/05/02 15:27:05: Did not write snom_redirect.xml to file system because there is no user associated with this file

    [5] 2013/05/02 15:27:05: Alert(2, 0)

    [5] 2013/05/02 15:27:05: Did not write snom_821.xml to file system because there is no user associated with this file

    [5] 2013/05/02 15:27:05: Alert(2, 0)

    [5] 2013/05/02 15:27:06: Did not write snom_3xx_fw.xml to file system because there is no user associated with this file

    [5] 2013/05/02 15:27:06: Alert(2, 0)

    [5] 2013/05/02 15:27:07: Last message repeated 3 times

    [5] 2013/05/02 15:27:07: Did not write snom_web_lang.xml to file system because there is no user associated with this file

    [5] 2013/05/02 15:27:07: Alert(2, 0)

    [5] 2013/05/02 15:27:07: Did not write snom_gui_lang.xml to file system because there is no user associated with this file

    [5] 2013/05/02 15:27:07: Alert(2, 0)

    [5] 2013/05/02 15:27:10: Did not write snom_3xx_fs.xml to file system because there is no user associated with this file

     

    And the log from the phone -

     

    /1/1970 00:01:21 [NOTICE] PHN: last prov successful:1; uri: >http://172.28.1.5:443/prov/prov/snom821-{mac}.htm<; default uri: >http://provisioning.snom.com/snom821/snom821.php?mac={mac}<

    1/1/1970 00:01:21 [NOTICE] PHN: Fetching URL: http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm

    1/1/1970 00:01:51 [ALERT ] PHN: WEBCLIENT: request http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm stopped due to no response from server for con_id:6

    1/1/1970 00:01:51 [NOTICE] PHN: Config setup: return code 408; requeueing >http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm<; attempt: 1, state: 30

    1/1/1970 00:01:54 [NOTICE] PHN: Fetching URL: http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm

    1/1/1970 00:02:24 [ALERT ] PHN: WEBCLIENT: request http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm stopped due to no response from server for con_id:7

    1/1/1970 00:02:24 [NOTICE] PHN: Config setup: return code 408; requeueing >http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm<; attempt: 2, state: 30

    1/1/1970 00:02:27 [NOTICE] PHN: Fetching URL: http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm

    1/1/1970 00:02:57 [ALERT ] PHN: WEBCLIENT: request http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm stopped due to no response from server for con_id:8

    1/1/1970 00:02:57 [NOTICE] PHN: Config setup: return code 408; requeueing >http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm<; attempt: 3, state: 30

    1/1/1970 00:03:00 [NOTICE] PHN: Fetching URL: http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm

    1/1/1970 00:03:30 [ALERT ] PHN: WEBCLIENT: request http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm stopped due to no response from server for con_id:9

    1/1/1970 00:03:30 [NOTICE] PHN: Config setup: return code 408; requeueing >http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm<; attempt: 4, state: 30

    1/1/1970 00:03:33 [NOTICE] PHN: Fetching URL: http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm

    1/1/1970 00:04:03 [ALERT ] PHN: WEBCLIENT: request http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm stopped due to no response from server for con_id:10

    1/1/1970 00:04:03 [NOTICE] PHN: Config setup: return code 408; requeueing >http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm<; attempt: 5, state: 30

    1/1/1970 00:04:06 [NOTICE] PHN: Fetching URL: http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm

    1/1/1970 00:04:36 [ALERT ] PHN: WEBCLIENT: request http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm stopped due to no response from server for con_id:11

    1/1/1970 00:04:36 [NOTICE] PHN: Config setup: return code 408; giving up on >http://172.28.1.5:443/prov/prov/snom821-00041345B328.htm<

    1/1/1970 00:04:36 [NOTICE] PHN: SetProvisioningDone

    1/1/1970 00:04:36 [NOTICE] PHN: Setting server prio 3, type dhcp, url: >newforma<

    1/1/1970 00:04:36 [NOTICE] PHN: Fetching URL: tftp://newforma:69/snom821.htm

    1/1/1970 00:04:36 [NOTICE] PHN: Config setup: return code 500; giving up on >tftp://172.28.1.5:69/snom821.htm<

    1/1/1970 00:04:36 [NOTICE] PHN: SetProvisioningDone

  11. Guys,

     

    As the topic suggests I would like to change the LED colour on the fixed buttons when used with Shared Line. Is it possible to have the local extension LED colour change to green instead of the default red LED? This will prevent confusion and allow the local user to see which line they are currently using.

     

    It does seem possible based on - http://wiki.snom.com/Features/LED_Remote_Control but I am not sure how we make the changes on the pbx?

  12. Guys,

     

    As the title states I am having some issues with how the internal phones register the incoming calls.

     

     

    The phones on an attended transfer or even picking up an external trunk directly will register either the star code or the person who performed the attended transfer.

     

    Is there a way to override this on the pbx side of things?

     

    callrecord_received_local0!: 45@pbx.domain.com.au

    callrecord_received_local1!: 45@pbx.domain.com.au

    callrecord_received_local2!: 45@pbx.domain.com.au

    callrecord_received_local3!: 45@pbx.domain.com.au

    callrecord_received_local4!: 45@pbx.domain.com.au

    callrecord_received_remote0!: sip:40@pbx.domain.com.au

    callrecord_received_remote1!: sip:47@pbx.domain.com.au

    callrecord_received_remote2!: sip:40@pbx.domain.com.au

    callrecord_received_remote3!: sip:61@pbx.domain.com.au

    callrecord_received_remote4!: sip:*6011273@pbx.domain.com.au

     

    Trunk Settings:

    Request-URI Let the System Decide

    From: Based on trunk account info

    To: Same as request-URI

    P-Asserted-Identity: Don't use Header

    P-Preferred-Identity: Don't use Header

    Remote-Party-ID: Don't use Header

    Privacy Indication: Other: id

     

    The problem I have is modifying any of these values results in a 502 Bad Gateway error as shown below:

     

     

    [5] 2013/04/19 12:04:41: SIP Rx udp:125.213.160.81:5060:

    SIP/2.0 502 Bad Gateway

    Via: SIP/2.0/UDP 172.28.1.5:5060;branch=z9hG4bK-a6f55ac37452f8b6bbc0f28e35179a25;rport

    To: <sip:947180000@sip00.mynetfone.com.au>

    From: "JR"<sip:OurPhoneNo@pbx.domain.com.au;user=phone>;tag=13990

    Call-ID: 08b383d5@pbx

    CSeq: 5001 INVITE

    User-Agent: ENSR3.0.66.41-IS1

    Content-Length: 0

     

    [5] 2013/04/19 12:04:41: SIP Tx udp:125.213.160.81:5060:

    ACK sip:947180000@sip00.mynetfone.com.au;user=phone SIP/2.0

    Via: SIP/2.0/UDP 172.28.1.5:5060;branch=z9hG4bK-a6f55ac37452f8b6bbc0f28e35179a25;rport

    From: "JR" <sip:OurPhoneNo@pbx.domain.com.au;user=phone>;tag=13990

    To: <sip:947180000@sip00.mynetfone.com.au>

    Call-ID: 08b383d5@pbx

    CSeq: 5001 ACK

    Max-Forwards: 70

    Contact: <sip:09406157@172.28.1.5:5060;transport=udp>

    Privacy: id

    Content-Length: 0

     

    [5] 2013/04/19 12:04:41: INVITE Response 502 Bad Gateway: Terminate 08b383d5@pbx

    [5] 2013/04/19 12:04:41: SIP Tx tls:172.28.1.84:3629:

    SIP/2.0 502 Bad Gateway

    Via: SIP/2.0/TLS 172.28.1.84:3629;branch=z9hG4bK-66fvzg68v8or;rport=3629

    From: "JR" <sip:48@pbx.domain.com.au>;tag=9q3f1xp4xm

    To: <sip:947180000@pbx.domain.com.au;user=phone>;tag=a7fad5b5fd

    Call-ID: 49c270511180-6ninip39wyuz

    CSeq: 1 INVITE

    Contact: <sip:48@172.28.1.5:5061;transport=tls>

    Supported: 100rel, replaces, norefersub

    Allow-Events: refer

    Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

    Accept: application/sdp

    User-Agent: snomONE/5.0.8

  13. The issue has always been around- even previously to version 5. If you press the button again on any phone the co light will go off.

     

    I also had some pretty major issues with 8.7.4.7 - The phones which were upgraded over night were not responsive to any incoming calls on the co lines in the morning (BlF not working, not picking any calls up on the virtual blf or didn't register any calls on the call monitor page). Placed a call which came in on line two. Pressing the CO line 1 on one of the non-responsive phones answered the call on the other line.

×
×
  • Create New...