Jump to content
Vodia PBX forum

Ganesh

Members
  • Content Count

    47
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ganesh

  • Rank
    Advanced Member

Recent Profile Visitors

4,580 profile views
  1. Hello, I would like to know if there is a possibility of this feature being included in the new release. Ganesh
  2. Hello, I would like to know if there is a possibility of this feature being included in the new release. Ganesh
  3. Hi, One of our customer using snomONE is looking for having the recorded call information tab under "Call Logs". By clicking on the tab, they should be able to play/download the audio file. Currently they are accessing the recorded calls from c:\program files\snomone\recording but it is very difficult to search for a specific call in the available files. Hope this feature would be avaialble in the next release. Regards Ganesh
  4. Hi, Any further progress on this please? We hope to see this feature in the next release. Regards Ganesh
  5. Thanks. Let me know how we can increase this value (max_udp_invite). Is this value in the snomONE configuration settings? Regards, Ganesh
  6. Hi, Our customer is using snomONE version 4.2.0.3958 (Linux)and everthing was working fine. Today they are unable to call between the extensions. The snom phone displays the message as "Temporarily unavailable". In the PBX logs we see "DoS protection: Not accepting more calls" Let me know how we can fix this problem. We are using version 4.2.0.3958 (Linux. Regards Ganesh
  7. Hi Support, Our customer using the snomONE PBX is receiving the daily CDR to the email ID configured. It is a screen shot of call logs and these CDRs are not in editable format and it is difficult to search for specific numbers in the CDR. It would be nice if we could receive the CDR in MS-Excel/CSV file format. If you could include a tab in the "Call Logs" for downloading the CDR in CSV format, it would be a great option! Hope this feature can be included in the next release Cheers Ganesh
  8. This is the startup file that we are using for CentOS and this is working with older versions and not working with version 4025. The error displayed while starting the service is "[root@sip3 ~]# service pbxnsip start Starting PBX:/etc/init.d/pbxnsip: line 19: 4471 Segmentation fault $PBX --dir $INSTALLDIR" Let me know the changes needed in the file to run version 4025. #!/bin/bash # # Init file for pbxnsip PBX # # Copyright © 2006 pbxnsip Inc., USA # # chkconfig: 2345 20 80 # description: SIP-based PBX # # processname: pbxctrl # pidfile: /var/run/pbxctrl.pid # source function library . /etc/rc.d/init.d/functions RETVAL=0 # Installation location INSTALLDIR=/usr/local/pbxnsip PBX=$INSTALLDIR/pbxctrl start() { echo -n "Starting PBX:" $PBX --dir $INSTALLDIR echo RETVAL=1 } stop() { echo -n "Stopping PBX:" killproc $PBX -TERM echo RETVAL=1 } case "$1" in start) start ;; stop) stop ;; restart) stop start ;; status) status $PBX RETVAL=$? ;; *) echo $"Usage: $0 {start|stop|restart|status}" RETVAL=1 esac exit $RETVAL
  9. Hello, We are using Cent OS and upgraded the pbxnsip to version 4.2.1.4025. After upgrade while I try to start the service I see the error as "[root@sip3 ~]# service pbxnsip start Starting PBX:/etc/init.d/pbxnsip: line 19: 4471 Segmentation fault $PBX --dir $INSTALLDIR" The start up script file works fine with the older version and not with version 4025. Can you please tell me what changes we need to make in start up file? I have checked the installation directory. It is as per the path in the start up file. Regards Ganesh
  10. Hello, We are using Cent OS and upgraded the pbxnsip to version 4.2.1.4025. After upgrade while I try to start the service I see the error as "[root@sip3 ~]# service pbxnsip start Starting PBX:/etc/init.d/pbxnsip: line 19: 4471 Segmentation fault $PBX --dir $INSTALLDIR" The start up script file works fine with the older version and not with version 4025. Can you please tell me what changes we need to make in start up file? I have checked the installation directory. It is as per the path in the start up file. Regards Ganesh
  11. We have two SIP registration trunk setup to two different service providers and both trunks are registered to service provider. The failover behaviour on both trunks is configured to "on all error codes". The dial plan is configured with first preference to trunk A and then same dial plan number to second preference to trunk B. Now if the Trunk A registration fails then snomONE trunk status shows "408 request timed out". At this state if any user makes a call, the call is not redirected to Trunk B as trunk A is in failed state. We have seen that the snomONE is still trying to route the call only to the failed trunk. It never tries to re-route the same call to the other trunk. Why does the PBX try routing call to a trunk that is in failed state? How do we setup the server to try route call to trunk B when A is in failed state? Is it possible to first route the call to trunk A and wait for a while (few seconds) and if no response is received from far end then re-route a new Invite to trunk B? Regards Ganesh
  12. Thanks for your reply. When 10.10.11.9 fails, the call routing is happening with 10.10.11.10. The problem observed is only when 10.10.11.10 fails while 10.10.11.9 is in working state. Ideally it should continue to work with 10.10.11.9 but it does not. Let me try the option of adding one more dial plan. Regards Ganesh
  13. We have 2 snom one servers at a central location on IP address 10.10.11.9 and 10.10.11.10. The remote location snom one server has 2 SIP gateway trunks configured to the central location servers. In the trunk 1 we have specified the domain as 10.10.11.9 and outbound proxy as 10.10.11.10. Similarly on trunk 2 we have specified the domain as 10.10.11.10 and outbound proxy as 10.10.11.9. The failover on both the trunks is set to "Always except when busy". In the dial plan of the remote location server the first preference is set to 10.10.11.9 and second is 10.10.11.10. When the remote location users call the central site the call is well handled by the server 10.10.11.9. During a failover of the server 10.10.11.9 at central site, the remote location snom one server is automatically routing calls to 10.10.11.10 and this is working fine. But during the failover of server 10.10.11.10, the remote location server stops routing calls even to 10.10.11.9. Why is it so? The server 10.10.11.9 works only if the other server is connected and working. Else this stops responding. Whereas the server 10.10.11.10 works fine even if the first server becomes unavailable. Has someone tried this? Regards Ganesh
  14. Thanks. This is now working after the upgrade.
  15. The PBX has a single domain (localhost) and the server has single IP address (10.10.71.10). Attached is the SIP registration and calls traces of the snom phones with snomONE server. There is no outbound proxy configured in the snom phone. We are using only the Registrar as 10.10.71.10. If we use the same registrar in the outbound proxy, still the same problem is observed. If we use the outbound proxy as 172.21.11.x (as seen in the SIP registration traces of snomONE) then the phones does not register.No plug and play is used, the phones are manually configured with snomONE. Factory reset was done before registering the phones. The phones (ext 111 and 112) at location B can call to phones (203 and 204) at location A whereas the reverse is not working. The phones (111 and 112) at location B cannot call each other. The phones (203 and 204) at location A can call each other. The "route print" of snomONE network is C:\Users\Snom Technology>route print =========================================================================== Interface List 16...1c 65 9d 25 ea c3 ......Microsoft Virtual WiFi Miniport Adapter 14...1c 65 9d 25 ea c3 ......Realtek RTL8191SE 802.11b/g/n WiFi Adapter 11...1c c1 de 9e 41 84 ......Realtek PCIe FE Family Controller 1...........................Software Loopback Interface 1 19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 37...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3 15...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.10.71.1 10.10.71.10 276 10.10.71.0 255.255.255.0 On-link 10.10.71.10 276 10.10.71.10 255.255.255.255 On-link 10.10.71.10 276 10.10.71.255 255.255.255.255 On-link 10.10.71.10 276 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 10.10.71.10 274 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 10.10.71.10 276 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 10.10.71.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 11 276 fe80::/64 On-link 11 276 fe80::d991:e426:3991:9937/128 On-link 1 306 ff00::/8 On-link 11 276 ff00::/8 On-link =========================================================================== Persistent Routes: None C:\Users\Snom Technology> The "route print" of phone at location B is Microsoft Windows [Version 6.1.7600] Copyright © 2009 Microsoft Corporation. All rights reserved. C:\Users\Snom Technology>route print =========================================================================== Interface List 16...1c 65 9d 25 ea c3 ......Microsoft Virtual WiFi Miniport Adapter 14...1c 65 9d 25 ea c3 ......Realtek RTL8191SE 802.11b/g/n WiFi Adapter 11...1c c1 de 9e 41 84 ......Realtek PCIe FE Family Controller 1...........................Software Loopback Interface 1 19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 37...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3 15...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.11.51.1 10.11.51.10 276 10.11.51.0 255.255.255.0 On-link 10.11.51.10 276 10.11.51.10 255.255.255.255 On-link 10.11.51.10 276 10.11.51.255 255.255.255.255 On-link 10.11.51.10 276 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 10.11.51.10 274 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 10.11.51.10 276 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 10.11.51.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 11 276 fe80::/64 On-link 11 276 fe80::d991:e426:3991:9937/128 On-link 1 306 ff00::/8 On-link 11 276 ff00::/8 On-link =========================================================================== Persistent Routes: None C:\Users\Snom Technology> SIP registration traces of snomONE.txt SIP logs for calls using snomONE.txt Wireshark traces of calls using snomONE.zip
×
×
  • Create New...