Vodia support
-
Posts
1,005 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Vodia support
-
-
1. Is there a way that they can do that from the phone? Yes this can done on the phone or on the User Web interface under "When caller reaches mailbox, play this greeting:"
http://wiki.snomone.com/index.php?title=Mailbox
2. Is there a way that this can be done automatically? No
-
Hi, Carlos Update the ticket with the IP of the box user/pass for ssh.
Best regards
-
You will have to .tar the whole directory.
here is example
sudo tar -zcvf snomONE.tar.gz /usr/local/snomONEyou can be in the root directory when you tar the file as well the tar will be stored there btw -
Hi, Tobymac
can you check if the certificates are available on the PBX?
-
The only way to call other ACD groups is by using the "Caller in queue" but it's not possible to call multiple ACD. Anymore specifics?
-
switch to admin---> scroll down to status general to check if the license has been activated
If the issue is that you don't see any of the domains or user please upgrade your chrome browser to the latest or firefox.
you can verify if your web browser support html5 or websocket as well.
-
Thanks for the info, We will test this item in our lab and see if it's reproducible.
Best regards
-
Can you PM us the log files usually there are some clues there.
Best regards
-
What do the phone logs say? if it's not fully provisioning then usually the phone will report an error code of 500 internal server error also check if there has been any changes on the snom templates this could also cause some issues.
-
GENE: means general
-
The best defense for these types of scenarios is using the access list on the PBX by allowing the users whom are tied to the system. The SIP scanners only send request to the PBX and if a SIP request is answer then they will start guessing sip password ect or just simply by sending a bogus invite to the PBX which result in the trunk provider trusting the source. The access list will automatically block these request by automatically blk listing these external IP.
-
Please check if the alert playback is turned off.
under advance-->audio--->Alert Info playback: on or off
if it's off then the phone will ignore the Alert-Info sent by the PBX.
http://wiki.snom.com/wiki/index.php/Settings/alert_info_playback
-
I have tried to reproduce this item and was unsuccessful
. Does the extension "Call forward all calls to" or "Call forward when not registered" set in the redirection? or perhaps there is a timeout on the AA that send the call elsewhere? Maybe you can post a log on the event or PM me a PCAP trace http://wiki.snomone.com/index.php?title=Trunk_PCAP_Generation -
Just for testing purpose can you create a new AA , I just tested here and it waits for me to input the extensions at 3?
-
Hi, Stefano here is an article on extension PCAP tracing.
http://wiki.snomone.com/index.php?title=Extension_PCAP
also are you incoming calls coming into a hunt group or agent group?
Best regards
-
Did you setup the "Extension input" for 3 Digits under the behavior section of the AA?
-
That could cause some confusion but have you tried creating the col lines for trunk 2? colines 7-8. The pbx should be able to determine the line parameter that will help determine which trunk is actually calling into the system.
-
Based on your question you want to know when a hunt group is being called by looking at the co-line button?
1. Add the DID to the hunt group
2. Create a coline1 account against the trunk you want to monitored.
3. Assign or create a button for that extension using the shared line option and name the parameter coline 1
the user should see the LED light up when an incoming call is coming into the hunt group.
-
We will re-test this item. Keep you updated.
-
This will also depend if the carrier as well, some will not show CID and will just advertise a number.
Not sure which one will work but it's worth a shot.
or
If non work you may want to try different combinations.
http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers
-
You will have to create that specific co-line on a button.
-
Can you post the full SIP trace?
Thx
-
Have you tried adding the Asterisk IP address in the trunk setting "Explicitly list addresses for inbound traffic" on the Vodia PBX?
-
Looks like the phone is remote? The phone send it's SDP with 192.168.1.182 and the PBX is sending it's SDP with 24.119.220.155. The PBX cannot send RTP traffic to a local IP.Check if you have a firewall set at the server level and on the router you can turn them off for testing services and try your the VM test.i this case if the phone was remote it would be sending SDP based on its Dynamic IP.INVITE sip:*97@voip.barrettsys.com;user=phone SIP/2.0Via: SIP/2.0/TLS 192.168.1.182:2066;branch=z9hG4bK-543qhk05dj5z;rportFrom: "Steve Butterfield" <sip:112@voip.barrettsys.com>;tag=fndlv64tazTo: <sip:*97@voip.barrettsys.com;user=phone>Call-ID: 52b0f3c5d925-dsalfsaxbvipCSeq: 1 INVITEMax-Forwards: 70Contact: <sip:112@192.168.1.182:2066;transport=tls;line=ihfiyuz5>;reg-id=1X-Serialnumber: 000413244C69P-Key-Flags: keys="3"User-Agent: snom320/8.7.3.25Accept: application/sdpAllow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATEAllow-Events: talk, hold, refer, call-infoSupported: timer, 100rel, replaces, from-changeSession-Expires: 3600;refresher=uasMin-SE: 90Proxy-Require: buttons-snom320Content-Type: application/sdpContent-Length: 502v=0o=root 584979493 584979493 IN IP4 192.168.1.182s=callc=IN IP4 192.168.1.182t=0 0m=audio 50780 RTP/AVP 0 8 3 9 99 18 101a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:6Dwq4Jkn2h+aiF4YkKmZnmu9wwiBVgl01psqpScwa=rtpmap:0 PCMU/8000a=rtpmap:8 PCMA/8000a=rtpmap:3 GSM/8000a=rtpmap:9 G722/8000a=rtpmap:99 G726-32/8000a=rtpmap:18 G729/8000a=fmtp:18 annexb=noa=rtpmap:101 telephone-event/8000a=fmtp:101 0-15a=ptime:20a=rtcp-xr:voip-metrics stat-summary=loss,dup,jitta=sendrecvSIP/2.0 100 TryingVia: SIP/2.0/TLS 192.168.1.182:2066;branch=z9hG4bK-543qhk05dj5z;rport=2066;received=24.119.220.154From: "Steve Butterfield" <sip:112@voip.barrettsys.com>;tag=fndlv64tazTo: <sip:*97@voip.barrettsys.com;user=phone>;tag=24b5840c7aCall-ID: 52b0f3c5d925-dsalfsaxbvipCSeq: 1 INVITEContent-Length: 0SIP/2.0 200 OkVia: SIP/2.0/TLS 192.168.1.182:2066;branch=z9hG4bK-543qhk05dj5z;rport=2066;received=24.119.220.154From: "Steve Butterfield" <sip:112@voip.barrettsys.com>;tag=fndlv64tazTo: <sip:*97@voip.barrettsys.com;user=phone>;tag=24b5840c7aCall-ID: 52b0f3c5d925-dsalfsaxbvipCSeq: 1 INVITEContact: <sip:112@24.119.220.155:5061;transport=tls>Supported: 100rel, replaces, norefersubAllow-Events: referAllow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATEAccept: application/sdpUser-Agent: Vodia-PBX/5.1.3Content-Type: application/sdpContent-Length: 348v=0o=- 677813057 677813057 IN IP4 24.119.220.155s=-c=IN IP4 24.119.220.155t=0 0m=audio 19170 RTP/AVP 9 0 8 101a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:KIovh3hlKqgGlVvULirklht4JS79+jXzdtOGGeMra=rtpmap:9 G722/8000a=rtpmap:0 PCMU/8000a=rtpmap:8 PCMA/8000a=rtpmap:101 telephone-event/8000a=fmtp:101 0-16a=ptime:20a=sendrecvACK sip:112@24.119.220.155:5061;transport=tls SIP/2.0Via: SIP/2.0/TLS 192.168.1.182:2066;branch=z9hG4bK-xbj4q151mgkb;rportFrom: "Steve Butterfield" <sip:112@voip.barrettsys.com>;tag=fndlv64tazTo: <sip:*97@voip.barrettsys.com;user=phone>;tag=24b5840c7aCall-ID: 52b0f3c5d925-dsalfsaxbvipCSeq: 1 ACKMax-Forwards: 70Contact: <sip:112@192.168.1.182:2066;transport=tls;line=ihfiyuz5>;reg-id=1Proxy-Require: buttons-snom320Content-Length: 0BYE sip:112@24.119.220.155:5061;transport=tls SIP/2.0Via: SIP/2.0/TLS 192.168.1.182:2066;branch=z9hG4bK-x0tq5z5vo8lp;rportFrom: "Steve Butterfield" <sip:112@voip.barrettsys.com>;tag=fndlv64tazTo: <sip:*97@voip.barrettsys.com;user=phone>;tag=24b5840c7aCall-ID: 52b0f3c5d925-dsalfsaxbvipCSeq: 2 BYEMax-Forwards: 70Contact: <sip:112@192.168.1.182:2066;transport=tls;line=ihfiyuz5>;reg-id=1User-Agent: snom320/8.7.3.25RTP-RxStat: Total_Rx_Pkts=0,Rx_Pkts=0,Rx_Pkts_Lost=0,Remote_Rx_Pkts_Lost=0RTP-TxStat: Total_Tx_Pkts=502,Tx_Pkts=502,Remote_Tx_Pkts=0Proxy-Require: buttons-snom320Content-Length: 0SIP/2.0 200 OkVia: SIP/2.0/TLS 192.168.1.182:2066;branch=z9hG4bK-x0tq5z5vo8lp;rport=2066;received=24.119.220.154From: "Steve Butterfield" <sip:112@voip.barrettsys.com>;tag=fndlv64tazTo: <sip:*97@voip.barrettsys.com;user=phone>;tag=24b5840c7aCall-ID: 52b0f3c5d925-dsalfsaxbvipCSeq: 2 BYEContact: <sip:112@24.119.220.155:5061;transport=tls>User-Agent: Vodia-PBX/5.1.3Content-Length: 0
TLS trunk
in Trunk Setup
Posted
it should resolve the DNS however TLS would require a certificate from the provider and I don't think this is implemented yet.
Please check this article.
http://www.informationweek.com/infrastructure/unified-communications/how-secure-are-sip-trunks/d/d-id/1080573?