Outbound calls on Broadvoice Fast busy call rejected

[pkothe]

I am able to get inbound calls no problem, Outbound calls are not working I get "Call (C:A) is rejected: Bad Request" and a fast busy on the phone which I am sure is a standard sip 404 message or something like that. Is there any special setting needed for the provider setup on the headers and invite messages with Broadvoice? I also have a VoIP line with "Voicestep" and it works fine in and out. I am using an outbound rule with a dial 6 for Broadvoice and a Dial 8 for Voicestep and a Dial 9 for my Audiocodes box with 4 PSTN lines. Checked the firewall logs and nothing is being dropped. I did a Wireshark packet capture on the server and I am getting rejected from Broadvice. Any config help on what they may be looking for would be helpful.

Thanks in advance,

Paul

 

[N_G]

Hi Paul,

Broadvoice works fine with 3Cx PHone System. Many of our users use it.

Ensure that you have followed the manual when configuring it. The next step is to review the server status log, the error will be listed there. Then post the server status log here.

 

[pkothe]

More information on the problem

After extensive testing I have found out some interesting information and I might be on to the possible solution. What I did not tell you in the first post was I already had another VoIP provider called Voicestep in the system and working perfectly, also my Sonicwall firewall firmware has some tricks of its own it can do to sip packets and to the NAT to make it consistent. After playing around with multiple settings on the firewall I found I still could not get both inbound and outbound on both VoIP providers. I finally deleted the Voicestep provider and like magic it works fine both inbound and outbound. Now I need a little help. If you have multiple and different VoIP providers do you need to use unique UDP ports for the registration? At one point, and it was late, I did manage to get 3 of the 4 channels working by changing one of the ports on the Broadvoice screen to 5061 but I did not get both in and out so I was baffled on that one. By the way I think I have 3 sold alerady and you have not even released it yet. I think we are right in the sweet spot for this market.

 

[dekatech]

Hi There!

I use Broadvoice, Junction, and a few other providers for testing all on the same 3CX system. It all works fine. What I did find to be a pain was one time I mistakenly typed the wrong password in for Broadvoice and after 3 registration attempts (it took me longer to relaize it was not registering), Broadvoice locked me out for 30 minutes, I have to remove broadvoice from my 3CX system and add it back after 30 minutes and all worked fine.

Travis

 

[pkothe]

VoIP Providers

Thanks for the information. I think my problem is how the firewall is configured. One provider likes setting a certain way and the other prover wants it the other way. I am going to mess with it some more later.

 

[Ralph]

I am having a very similar problem

I am having a very similar problem.

I have 2 BroadVoice Lines and a Vitelity line. I can send and receive calls fine on the Vitelity line but I can only receive calls on the Broadvoice lines.

Where you able to find a solution for this?

My network layout is as follows:

Internet -> Firewall -> 3CX Server -> Phones

The phones and the 3cx server are on the same subnet.

My server logs from the latest attempt at calling out are as follows:

10:15:18.179 CallConf::Rejected [CM103005] Call(7) is rejected: Unsupported Media Type
10:15:18.179 StratInOut:nCancel [CM104008] Call(7): Call from Ext.201 to xxxxxxx terminated; cause: 415 Unsupported Media Type; from IP:147.135.12.221
10:15:17.829 CallConf:nIncoming [CM103002] Call(7): Incoming call from 201 (Ext.201) to sip:[email protected]
10:15:03.633 ClientRegs:nSuccess [CM113005] Registration of sip:[email protected] is successful
10:15:03.233 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
10:15:03.233 ExtLine::Register [CM110001] Use External IP for device line registration DN='10000' device='BV1'
10:15:03.223 StunClient:rocess [CM115002] STUN resolved external IP=xxx.xxx.xxx.xxx:xxxxx by server 80.239.235.209

I have been beating my head against the wall on this for several days now.

I have another posting on this in the general forum.

http://www.3cx.com/forums/viewtopic.php?t=1787

Any help is greatly appreciated.

 

[pkothe]

My Settings that are working

On the Broadvoice line I have the internal address being used for the contact field for registration and on the Voicestep line I have External Stun selected and they both work fine. I also have one to one NAT setup to my PBX ad I think this has an affect on wether to use External or Internal address option. What firewall type do you have?

 

[nb]

Re: I am having a very similar problem

I have 2 BroadVoice Lines and a Vitelity line. I can send and receive calls fine on the Vitelity line but I can only receive calls on the Broadvoice lines.

10:15:18.179 CallConf::Rejected [CM103005] Call(7) is rejected: Unsupported Media Type
10:15:18.179 StratInOut:nCancel [CM104008] Call(7): Call from Ext.201 to xxxxxxx terminated; cause: 415 Unsupported Media Type; from IP:147.135.12.221

It looks that the call is being cancelled by Broadvoice VoIP provider. We have been working with Broadvoice for a very long time and it works perfectly. I will try and replicate this in our test network however I would try to check and see for the codecs used in the phone. The "Unsupported Media Type" is a codec issue. We are checking on this.

 

[nb]

Broadvoice works out of the box. Just tested - broadvoice works fine -

Have you added any codecs or changed any settings?
What SIP phone are you using? Have you tried from other phones?
Can you enable verbose loggings and post the relevant logs here. I would recommend that you restart the PBX services so that there won't be a lot of logs to go through making it more difficult to read and generate the logs exactly after.

 

[Ralph]

Logs and additional information

Good morning,

I have not added any codecs or modified 3CX in any way.
We are using Polycom Soundpoint IP 501 phones.
I have attempted to call out with X-Lite and a Grandstream GXP 2000 with the same results. I have also built an identical server and had the same results. The server has its own public IP address and the firewall is wide open to the server.

I changed logging to verbose and restarted the server. I then attempted to make some calls using one of the Polycom phones. The following are log entries from the 3CXPhoneSystem.trace.log file:

CSeq: 1 REGISTER
User-Agent: 3CXPhoneSystem
Content-Length: 0


08:24:33.213|SipStack.cxx(278)|Debug8|Resip|>>:SEND: SipResp: 404 tid=c251e1af9435E338 cseq=REGISTER / 1

from(tu)
08:24:33.213|ServerAuthManager.cxx(50)|Trace5|Resip|>>:ServerAuth rejected request SipReq:

REGISTER xxx.xxx.xxx.xxx:5060 tid=c251e1af9435E338 cseq=REGISTER [email protected] / 1

from(wire)
08:24:33.303|TimerQueue.cxx(85)|Debug8|Resip|>>:Adding timer: Timer J tid=c251e1af9435E338

ms=32000
08:24:33.303|TransportSelector.cxx(525)|Debug8|Resip|>>:Looked up source for destination: [ V4

xxx.xxx.xxx.xxx:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target

domain=unspecified connectionId=0 ] connectionId=0 ] -> [ V4 xxx.xxx.xxx.xxx:0 UDP target

domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0

] connectionId=0 ] sent-by=xxx.xxx.xxx.xxx sent-port=0
08:24:33.303|TransportSelector.cxx(766)|Debug8|Resip|>>:Transmitting to [ V4 xxx.xxx.xxx.xxx:5060 UDP

target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified

connectionId=0 ] connectionId=0 ] tlsDomain= via [ V4 xxx.xxx.xxx.xxx:5060 UDP target domain=unspecified

received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0

]SIP/2.0 404 User Not Found
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx;branch=z9hG4bKc251e1af9435E338
To: <sip:[email protected]>;tag=7e26236f
From: "303"<sip:[email protected]>;tag=100ADF1-7E837B44
Call-ID: [email protected]
CSeq: 1 REGISTER
User-Agent: 3CXPhoneSystem
Content-Length: 0


08:24:33.303|Transport.cxx(209)|Debug8|Resip|>>:Adding message to tx buffer to: [ V4 xxx.xxx.xxx.xxx:5060

UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified

connectionId=0 ] connectionId=0 ]
08:24:39.822|ClientRegistration.cxx(234)|Trace5|Resip|>>:requesting

refresh of ClientRegistration sip:[email protected]
08:24:39.822|DialogUsageManager.cxx(800)|Debug8|Resip|>>:SEND: REGISTER sip:sip.broadvoice.com SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-d87543-1404ec424e6a7123-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:[email protected]:5060;rinstance=401c1f35fb3e4250>
To: <sip:[email protected]>
From: <sip:[email protected]>;tag=ef3c0a33
Call-ID: MDU2Nzc3M2I0OGJhNWU2YTAxMTAwNjY2YWFlMjM5MTk.
CSeq: 24 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
User-Agent: 3CXPhoneSystem
Content-Length: 0


08:24:39.822|DialogId.cxx(50)|Debug8|Resip|>>ialogId:ialogId:

MDU2Nzc3M2I0OGJhNWU2YTAxMTAwNjY2YWFlMjM5MTk.-ef3c0a33-
08:24:39.822|DialogUsageManager.cxx(912)|Debug8|Resip|>>:Using outbound proxy:

sip:[email protected]:5060;lr -> SipReq: REGISTER sip.broadvoice.com tid=1404ec424e6a7123

cseq=REGISTER [email protected]:5060 / 24 from(tu)
08:24:39.912|TimerQueue.cxx(85)|Debug8|Resip|>>:Adding timer: Timer F tid=1404ec424e6a7123 ms=32000
08:24:39.912|DnsResult.cxx(186)|Debug8|Resip|>>nsResult::lookup

sip:[email protected]:5060;lr
08:24:39.912|TimerQueue.cxx(85)|Debug8|Resip|>>:Adding timer:

Timer E1 tid=1404ec424e6a7123 ms=500
08:24:39.912|TransportSelector.cxx(525)|Debug8|Resip|>>:Looked up

source for destination: [ V4 147.135.12.221:5060 UDP target domain=sip.broadvoice.com connectionId=0 ] ->

[ V4 xxx.xxx.xxx.xxx:0 UDP target domain=sip.broadvoice.com connectionId=0 ] sent-by= sent-port=0
08:24:39.912|TransportSelector.cxx(971)|Debug8|Resip|>>:findTransportBySource([ V4 xxx.xxx.xxx.xxx:0 UDP

target domain=sip.broadvoice.com connectionId=0 ])
08:24:39.912|TransportSelector.cxx(1083)|Debug8|Resip|>>:findTransport (any port, any interface) =>

Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ]
08:24:39.912|TransportSelector.cxx(766)|Debug8|Resip|>>:Transmitting to [ V4 147.135.12.221:5060 UDP

target domain=sip.broadvoice.com received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified

connectionId=0 ] connectionId=0 ] tlsDomain= via [ V4 xxx.xxx.xxx.xxx:5060 UDP target

domain=sip.broadvoice.com connectionId=0 ]REGISTER sip:sip.broadvoice.com SIP/2.0
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK-d87543-1404ec424e6a7123-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:[email protected]:5060;rinstance=401c1f35fb3e4250>
To: <sip:[email protected]>
From: <sip:[email protected]>;tag=ef3c0a33
Call-ID: MDU2Nzc3M2I0OGJhNWU2YTAxMTAwNjY2YWFlMjM5MTk.
CSeq: 24 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
User-Agent: 3CXPhoneSystem
Content-Length: 0


08:24:39.912|Transport.cxx(209)|Debug8|Resip|>>:Adding message to tx buffer to: [ V4 147.135.12.221:5060

UDP target domain=sip.broadvoice.com received on: Transport: [ V4 0.0.0.0:5060 UDP target

domain=unspecified connectionId=0 ] connectionId=0 ]
08:24:39.972|Transport.cxx(259)|Debug8|Resip|>>:incoming from: [ V4 147.135.12.221:5060 UDP target

domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0

] connectionId=0 ]
08:24:39.972|DnsResult.cxx(177)|Debug8|Resip|>>:Whitelisting sip.broadvoice.com(1):

147.135.12.221
08:24:39.972|dns\RRVip.cxx(129)|Debug8|Resip|>>:updating an existing vip: 147.135.12.221

with 147.135.12.221
08:24:39.972|TransactionState.cxx(1721)|Debug8|Resip|>>:Send to TU: TU:

DialogUsageManager size=0 SIP/2.0 200 OK
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx;branch=z9hG4bK-d87543-1404ec424e6a7123-1--d87543-
Contact: <sip:[email protected]>
To: <sip:[email protected]>
From: <sip:[email protected]>;tag=ef3c0a33
Call-ID: MDU2Nzc3M2I0OGJhNWU2YTAxMTAwNjY2YWFlMjM5MTk.
CSeq: 24 REGISTER
Expires: 30
Content-Length: 0


08:24:39.972|TimerQueue.cxx(85)|Debug8|Resip|>>:Adding timer: Timer K tid=1404ec424e6a7123 ms=5000
08:24:39.972|DialogUsageManager.cxx(1190)|Trace5|Resip|>>:Got: SipResp: 200 tid=1404ec424e6a7123

cseq=REGISTER [email protected] / 24 from(wire)
08:24:39.972|DialogUsageManager.cxx(1646)|Debug8|Resip|>>ialogUsageManager:rocessResponse: SipResp:

200 tid=1404ec424e6a7123 cseq=REGISTER [email protected] / 24 from(wire)
08:24:39.972|DialogId.cxx(50)|Debug8|Resip|>>ialogId:ialogId:

MDU2Nzc3M2I0OGJhNWU2YTAxMTAwNjY2YWFlMjM5MTk.-ef3c0a33-
08:24:39.972|ClientRegistration.cxx(327)|Trace5|Resip|>>:Clearing service route ([])
08:24:39.972|TimerQueue.cxx(105)|Debug8|Resip|>>:Adding application timer: DumTimeout::Registration

ClientRegistration sip:[email protected]: duration=25 seq=24


If you need additional information or different logs please let me know.

Thanks again,

 

[Ralph]

Any ideas??

Just wanted to check in and see if anyone had any ideas about how to fix this??? :?

Thanks again

 

[SY]

Re: Any ideas??

Just wanted to check in and see if anyone had any ideas about how to fix this??? :?

Thanks again

PBX doesn't control decisions of other side. If they tell - "Unsupported Media Type", so... media Type is not supported. It seems the only one way to find ideas is to ask support of BroadVoice, why their's software made such decision...

Thanks,
Stepan

 

[Ralph]

Solution Found!!!!

Good afternoon,

After many days and untold hours on the phone with a variety of techs from BroadVoice, Firewall manufacturer, phone manufacturer, etc. I finally got to a higher level tech at the firewall manufacturer.

It turns out that the firewall has a small daemon called "SIP Helper" (you gotta believe this) :roll: and sometimes "SIP Helper" doesn't actually "help" much since it modifies the SIP packets (go figure) :shock: .

Anyhow, to make a long story short we disabled "SIP Helper" in the Firewall and everything works great now with BroadVoice.

To bad its not Friday yet, otherwise I could start celebrating immediately :wink:

Thanks again everyone I appreciate all the effort. BTW I am loving this 3CX software so far

Take care