Quantcast
Channel: Asterisk Forums
Viewing all 7460 articles
Browse latest View live

Yealink phones with Switchvox- DND

$
0
0
The calls are sent to Voicemail only because the phone, when it's had DND enabled locally on the handset, returns a 486 SIP response to Switchvox, which then rolls over to voicemail because the phone's just rejected the inbound call.

Yealink phones don't provide any notification to Switchvox, or that Switchvox can understand, that they're in a "DND" presence state. BLF lights on phones correspond to device state, not user presence. DND is a user presence concept while Device States, as far as Switchvox and Asterisk understand it, are idle, in_use, ringing, on_hold, etc.

Presence integration between handsets and Switchvox is accomplished with Digium's handsets.

Statistics : Posted by phoneguy797 • on Wed Dec 10, 2014 1:28 pm • Replies 1 • Views 28

Do I use MeetMe or ConfBrirdge

$
0
0
I am currently using Asterisk 11 and want to know do I use MeetMe or ConfBrirdge? Also how do I configure? I do not have a fancy setup would like to just see a basic config.

Statistics : Posted by aristech • on Wed Dec 10, 2014 11:29 am • Replies 1 • Views 31

Do I use MeetMe or ConfBrirdge

Originate gets "404 Not Found"

$
0
0
You will need to provide us with your configuration and details of the incoming caller ID.

404 is not really an appropriate response.

Statistics : Posted by crs • on Tue Dec 09, 2014 4:34 pm • Replies 5 • Views 139

Originate gets "404 Not Found"

$
0
0
Asterisk Support (tag line: "Get help with installing, upgrading and running Asterisk".)

The tag line of Asterisk General is "General discussions about Asterisk".

Statistics : Posted by crs • on Tue Dec 09, 2014 4:34 pm • Replies 5 • Views 139

Originate gets "404 Not Found"

$
0
0
Thanks for the suggestion.
But a question - You mention "Also please note that Asterisk General is a discussion forum, not a support one."
I thought that the question was a general Asterisk issue. What would be a better forum for such a question?

Statistics : Posted by crs • on Tue Dec 09, 2014 4:34 pm • Replies 5 • Views 139

Originate gets "404 Not Found"

$
0
0
This is nothing to do with Originate, except that you have provided the wrong address information.

You will have to look at the remote system to find out why it thinks there is no resource with the URI sip:62021@192.168.90.50:5260

Also please note that Asterisk General is a discussion forum, not a support one.

Statistics : Posted by crs • on Tue Dec 09, 2014 4:34 pm • Replies 5 • Views 139

Originate gets "404 Not Found"

$
0
0
After looking at our registrars log iit appears that the problem is that the INVITE generated by our Asterisk originate command includes "From: "Anonymous" <sip:anonymous@anonymous.invalid>" as well as "Contact: <sip:anonymous@192.168.15.224:5060>".
Why is that? How can I avoid the "Anonymous" in the INVITE?

Thanks again for your attention and assistance.

The excerpt from the log follows.

16:27:13.074:(1) Received [11,UDP] 885 bytes from 192.168.15.224:5060 <<<<<
INVITE sip:62021@192.168.90.50:5260 SIP/2.0
Via: SIP/2.0/UDP 192.168.15.224:5060;branch=z9hG4bK1c0d0bf1
Max-Forwards: 70
From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=as5d3410a7
To: <sip:62021@192.168.90.50:5260>
Contact: <sip:anonymous@192.168.15.224:5060>
Call-ID: 2ab335f15deec5525a50158f7e2df117@192.168.15.224:5060
CSeq: 102 INVITE
User-Agent: Asterisk PBX 11.12.1
Date: Tue, 09 Dec 2014 21:27:13 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 285

v=0
o=root 513210126 513210126 IN IP4 192.168.15.224
s=Asterisk PBX 11.12.1
c=IN IP4 192.168.15.224
t=0 0
m=audio 10648 RTP/AVP 3 0 8 101
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

16:27:13.074:(1) Unable to resolve number for DN:anonymous
16:27:13.074:(1) Unable to resolve number for DN:anonymous
16:27:13.074:(1) trunk ip addr 192.168.15.224
16:27:13.074 Std 52002 Gateway for address '192.168.15.224', number 'anonymous' is not found.
16:27:13.074:(1) CallMatcher: no call match attributes found
16:27:13.075:(1) Unable to resolve number for DN:anonymous
16:27:13.075:(1) Unable to resolve number for DN:anonymous
16:27:13.075:(1) trunk ip addr 192.168.15.224
16:27:13.075 Std 52002 Gateway for address '192.168.15.224', number 'anonymous' is not found.
16:27:13.075:(1) ERROR: 10000002, GetDeviceManager().ResolveOriginationDevice(inviteMsg, from), SipCallManager.cpp,1297
16:27:13.075:(1) Sending [11,UDP] 362 bytes to 192.168.15.224:5060 >>>>>
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.15.224:5060;branch=z9hG4bK1c0d0bf1;received=192.168.15.224
From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=as5d3410a7
To: <sip:62021@192.168.90.50:5260>;tag=00955CA4-2A7B-145D-AA6D-325AA8C0AA77-6158

Statistics : Posted by crs • on Tue Dec 09, 2014 4:34 pm • Replies 5 • Views 139

Originate gets "404 Not Found"

$
0
0
Why the "404 Not found" from SIP INVITE generated from "channel originate"?
The phone seems to register OK. I have "senrpid = yes" in sip.conf
as was suggested by another user.

I'm guessing the problem is with the INVITE generated by the "channel originate" call.
1. I'm not sure what's incorrect, if anything, with the INVITE generated.
2. If that is true, I don't know how to configure Asterisk to generate the correct INVITE.

The general difference between these originate examples which fail with the "404 Not Found" response and the originate examples which I've gotten to work successfully is that the failed cases have user phones which have a more complicated registration process: chalange - authentication and they also use a different registration port "5260" instead of the default "5060".

I would certainly appreciate any suggestions / ideas - I'm stumped?

From CLI output:
channel originate SIP/62021@192.168.90.50:5260 extension 51207
== Using SIP RTP CoS mark 5
Audio is at 10648
Adding codec 100002 (gsm) to SDP
Adding codec 100003 (ulaw) to SDP
Adding codec 100004 (alaw) to SDP
Adding codec 100017 (testlaw) to SDP
Adding non-codec 0x1 (telephone-event) to SDP
Reliably Transmitting (no NAT) to 192.168.90.50:5260:
INVITE sip:62021@192.168.90.50:5260 SIP/2.0
Via: SIP/2.0/UDP 192.168.15.224:5060;branch=z9hG4bK1c0d0bf1
Max-Forwards: 70
From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=as5d3410a7
To: <sip:62021@192.168.90.50:5260>
Contact: <sip:anonymous@192.168.15.224:5060>
Call-ID: 2ab335f15deec5525a50158f7e2df117@192.168.15.224:5060
CSeq: 102 INVITE
User-Agent: Asterisk PBX 11.12.1
Date: Tue, 09 Dec 2014 21:27:13 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 285

v=0
o=root 513210126 513210126 IN IP4 192.168.15.224
s=Asterisk PBX 11.12.1
c=IN IP4 192.168.15.224
t=0 0
m=audio 10648 RTP/AVP 3 0 8 101
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

---
*CLI>
<--- SIP read from UDP:192.168.90.50:5260 --->
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.15.224:5060;branch=z9hG4bK1c0d0bf1;received=192.168.15.224
From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=as5d3410a7
To: <sip:62021@192.168.90.50:5260>;tag=00955CA4-2A7B-145D-AA6D-325AA8C0AA77-615809
Call-ID: 2ab335f15deec5525a50158f7e2df117@192.168.15.224:5060
CSeq: 102 INVITE
Content-Length: 0


From sip.conf:
; sip.conf 04dec2014
;
[general]

registertimeout => 3600
defaultexpiry => 3600
allowexternaldomains = yes
sendrpid = yes
; rpid_update = no ; In certain cases, the only method by which a connected line chg ...

;
; ICM
;
register=>62021:password@192.168.90.50:5260/62021
; OXE
;
register=>51206:password@152.148.200.236:5060/51206
register=>51207:password@152.148.200.236:5060/51207




From CLI output (earlier) - The Registration:
[Dec 9 16:24:32] NOTICE[32535]: chan_sip.c:14991 sip_reregister: -- Re-registration for 62021@192.168.90.50
REGISTER 11 headers, 0 lines
Reliably Transmitting (no NAT) to 192.168.90.50:5260:
REGISTER sip:192.168.90.50:5260 SIP/2.0
Via: SIP/2.0/UDP 192.168.15.224:5060;branch=z9hG4bK4c99839e
Max-Forwards: 70
From: <sip:62021@192.168.90.50>;tag=as5767814a
To: <sip:62021@192.168.90.50>
Call-ID: 39cb26c54a84669a2c61731e26e499d7@192.168.15.224
CSeq: 104 REGISTER
User-Agent: Asterisk PBX 11.12.1
Authorization: Digest username="62021", realm="switch", algorithm=MD5, uri="sip:192.168.90.50:5260", nonce="008475F6-6879-1487-AA6D-325AA8C0AA77", response="f222e74872d8a0af2b81c3011f7ed353", opaque="737769746368", qop=auth, cnonce="015f1404", nc=00000002
Expires: 3600
Contact: <sip:62021@192.168.15.224:5060>
Content-Length: 0


---

<--- SIP read from UDP:192.168.90.50:5260 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.224:5060;branch=z9hG4bK4c99839e;received=192.168.15.224
From: <sip:62021@192.168.90.50>;tag=as5767814a
To: <sip:62021@192.168.90.50>;tag=00955CA4-2A7B-145D-AA6D-325AA8C0AA77-615767
Call-ID: 39cb26c54a84669a2c61731e26e499d7@192.168.15.224
CSeq: 104 REGISTER
Server: SIP Server, 2.0.044.01
Expires: 1800
Contact: <sip:62021@192.168.15.224:5060>;expires=1800
Content-Length: 0

<------------->
--- (10 headers 0 lines) ---
[Dec 9 16:24:32] NOTICE[32535]: chan_sip.c:23504 handle_response_register: Outbound Registration: Expiry for 192.168.90.50 is 1800 sec (Scheduling reregistration in 1785 s)
Really destroying SIP dialog '39cb26c54a84669a2c61731e26e499d7@192.168.15.224' Method: REGISTER







































-UUU:----F1 originate_no_ip_in_from.txt

Statistics : Posted by crs • on Tue Dec 09, 2014 4:34 pm • Replies 5 • Views 139

Get Switchboard To Hangup/Disconnect the Phone on Transfer

$
0
0
Am I missing something -- he said with tongue firmly planted in cheek. Is there a way to get Switchboard to hang up/drop dial tone upon blind transfer of a call. Why in the heck do I still want dial tone on my phone after I drag-and-drop blind transfer a call using Switchboard. That does not seem in any way, shape or form to me to be intuitive. Perhaps there is a logical reason why Switchboard does it that way. The physical phone doesn't do that when I transfer a call from it. It disconnects. Just wondering if there is any way around it. Makes Switchboard somewhat of a pain for our receptionist types to use when they have to hang up their phone after every transfer. Suppose they could just let it sit there at dial tone and then go to reorder tone and then eventually hang up itself but that's a little annoying. Thank You for listening.

Statistics : Posted by jreed1949 • on Thu Dec 11, 2014 5:31 pm • Replies 1 • Views 37

"Outgoing call rule is incomplete" Error message

$
0
0
Until you can get deeper into the firewall with your ITSP, not much you can do, but if they're both SIP trunks and with the same provider no less, I'd bet that whatever is affecting your primary SIP trunk will also affect your secondary.

You could throw an Analog line into the system with a few copper lines for backup... or perhaps get an inexpensive secondary SIP provider from another company.

I'm 99% percent sure this is not a Switchvox issue, but rather a Firewall/ITSP issue. Image

Good luck!

Statistics : Posted by pzimmerle • on Tue Dec 09, 2014 12:57 pm • Replies 5 • Views 222

"Outgoing call rule is incomplete" Error message

$
0
0
It is a SIP trunk. The Wholesale server does not accept OPTIONS requests so it's difficult to tell if they're registered at any given time.
I'll ask my SIP provider about a failover. (Edit: They have a failover IP address I can use so I'll try that out and see how it goes.)

Further Edit: Looks like the Failover is working some of the time (here's an example of a successful failover just for contrast):
Outgoing 11:42:50 AM Dialed number (1727394XXXX)
Provider 11:42:50 AM Sent call over SIP Provider ( Vitelity SBC ) with number 727394XXXX
Status 11:42:50 AM Received status of CONGESTION with a cause code of 19
Provider 11:42:50 AM Sent call over SIP Provider ( Vitelity Failover ) with number 727394XXXX
Talking 11:42:58 AM Talked to <1727394XXXX> for 41 seconds
Hang up 11:43:40 AM Call was hung up by Timothy X <231>

However, I notice I'm still getting a lot of Congestion statuses even with the failover (here's an example of a failed failover):

Outgoing 11:45:13 AM Dialed number (1209745XXXX)
Provider 11:45:13 AM Sent call over SIP Provider ( Vitelity SBC ) with number 209745XXXX
Status 11:45:17 AM Received status of CONGESTION with a cause code of 19
Provider 11:45:17 AM Sent call over SIP Provider ( Vitelity Failover ) with number 209745XXXX
Status 11:45:23 AM Received status of CONGESTION with a cause code of 19
Hang up 11:45:27 AM Call was hung up by Bob X <340>

Is there anything we can do to reduce the frequency of these further, or is that something I'll need to bring up with my ITSP?

~

We're using a ZyXel ZyWall USG 50 as a firewall.

Statistics : Posted by pzimmerle • on Tue Dec 09, 2014 12:57 pm • Replies 5 • Views 222

"Outgoing call rule is incomplete" Error message

$
0
0
Is this a SIP trunk, perhaps?

I'm guessing that registration with the SIP provider has timed out, or needs to be resent. Either that or the firewall SIP session times out and during the re-connect time, it fails. When the SIP session re-authorizes with your provider, the calls go through.

So, is this a SIP provider? If so, I might start with them and see what they have for recommendations.

What firewall do you have?

Most of the "playback" tones that are played to callers when placing a call that fails occur due to a connectivity issue with the provider... i.e., Switchvox is doing everything right - the rules are right - the number matches a pattern - but the Switchvox received some error code from the provider (or the provider didn't respond).

Also, do you have any failover trunks in the system (analog or another provider)? Try adding that as a failover route for this rule and I bet you could see 100% calls complete, but you'll see they're failing over to the secondary provider.

Statistics : Posted by pzimmerle • on Tue Dec 09, 2014 12:57 pm • Replies 5 • Views 222

"Outgoing call rule is incomplete" Error message

$
0
0
1) Current Version: 5.10 (70448)

2) I deleted and redid the rules last night.

Unfortunately, I'm told that dialers this morning are still hearing this error: "Rule 4, Error 89" on calls that are failing to go through.

On the plus, I don't see "Outgoing call rule is incomplete" in the error messages right now.

There seems to be no pattern in the failed calls - indeed, they can keep re-dialing that number until suddenly it works.

Statistics : Posted by pzimmerle • on Tue Dec 09, 2014 12:57 pm • Replies 5 • Views 222

"Outgoing call rule is incomplete" Error message

$
0
0
Everything looks okay and I haven't seen this error in the logs, when it was still working.

1) What version of Switchvox are you running?
2) Perhaps delete the rule and re-create and see if that resolves the issue?

Statistics : Posted by pzimmerle • on Tue Dec 09, 2014 12:57 pm • Replies 5 • Views 222

"Outgoing call rule is incomplete" Error message

$
0
0
In the last couple weeks, I've been receiving the following error message:
100 12/9/2014 10:01 AM Call to 3082840173 failed because the 'Long Distance' outgoing call rule is incomplete.

Here are screenshots of our dial rules:

Attachments
LongDist.PNG
LongDist.PNG (121.24 KiB) Viewed 222 times

Attachments
LongDistno1.PNG
LongDistno1.PNG (143.81 KiB) Viewed 222 times


The thing, though, is that for the most part we seem to be dialing out fine using these rules - our provider has not requested a 1 with outbound calls and in practice the rules work just fine - I'm able to use them in isolation on a test extension and never seem to run into problems.

We have been having sporadic issues with our remote office where every few calls will have an error and the message "Error 85."

Statistics : Posted by pzimmerle • on Tue Dec 09, 2014 12:57 pm • Replies 5 • Views 222

WiFi adapter with Polycom Phones

$
0
0
As a general rule, I run far-far away from WiFi phones. They tend to be VERY picky about connectivity, latency, etc., and so you end up with a lot more call-quality related issues than just a regular hard-wired set. That not withstanding, most wireless networks are generally not well set up or configured for VOICE, so that exacerbates the issue(s) before you even get to the VOICE part of the call.

That being said, haven't used these sets or the WiFi Adapter, so I can't comment specifically on the question at hand.

Also, FWIW, it appears according to that doc, the WiFi Adapter is meant only for the VVX Series IP Soundpoint phones. So when they reference "Any IP Soundpoint phone", I think they really mean the VVX series.

Another point would be that if you're going to use the Switchvox to provision the IP 650 through a feature pack, even IF the 650 could support that WiFi Adapter, I'm not sure the firmware from the Switchvox is new enough, so you'd likely need to scrap the Switchvox Feature Pack and roll your own config to the 650. Seems like an awful lot of work for minimal return.

I might push them towards the new Digium Softphone App for IOS 8 iPhone5+, or even to a Digium desk set with a wireless plantronics headset. Or also maybe a DECT (PANASONIC TGP500) phone if they need to be truly cordless.

Just me two (well, more like 2000) cents.

Statistics : Posted by SS-306 Tang • on Thu Dec 11, 2014 7:35 am • Replies 2 • Views 75

WiFi adapter with Polycom Phones

WiFi adapter with Polycom Phones

$
0
0
A customer has asked about the Polycom WiFi adapter for use with Polycom phones. In the Polycom documentation there is the following note:

Supported Polycom Phones
The use of a WiFi adapter is supported for all Polycom SoundPoint® IP phones with USB ports (though not tested by Polycom at this time). The use of a WiFi adapter with the external power supply is supported for all SoundPoint IP phones without USB ports and all SoundStation IP phones (though not tested by Polycom at this time).

Has anyone used one of these adapters with the Polycom SoundPoint IP 650?

This will be used in an office with a couple of land-wired phones, computers, and printers. The customer wants to use one phone and one computer with the wireless link.

Comments?

Statistics : Posted by SS-306 Tang • on Thu Dec 11, 2014 7:35 am • Replies 2 • Views 75

PJSIP IPV6 Transport does not bind to ::

$
0
0
There's a note on there reading:

Enabling IPV6 Support
IPv6 support in pjproject is, by default, disabled. To enable it, add CFLAGS='-DPJ_HAS_IPV6=1' to your http://forums.asterisk.org/configure command.

That should help.

Cheers

Statistics : Posted by rbasche • on Fri Dec 12, 2014 10:53 am • Replies 8 • Views 191
Viewing all 7460 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>