No audio when dialing 1300 xxx xxx & 13 xx xx numbers

[moore]

Hello,

I have recently installed 3CX v9 on a virtual win 7 box, and i can not hear the audio when i call 1300 and 13 numbers.
We have 2 accounts one with ISPhone and the other for Internode both in Australia.
We have has a older version of 3CX installed with the same providers and it worked, is there something i have to do to activate 1300 ect calls, mobile/ call phone calls work fine.

This is what my service activity log reads>>>>

14:42:08.311 [CM503007]: Call(27): Device joined: sip:[email protected]:5060
14:42:07.138 [CM505001]: Ext.101: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA525G-7.4.6] PBX contact: [sip:[email protected]:5060]
14:42:07.138 [CM503002]: Call(27): Alerting sip:[email protected]:5060
14:42:07.059 [CM503025]: Call(27): Calling Ext:Ext.101@[Dev:sip:[email protected]:5060]
14:42:06.996 [CM503004]: Call(27): Route 1: Ext:Ext.101@[Dev:sip:[email protected]:5060]
14:42:06.994 [CM503010]: Making route(s) to <sip:[email protected]:5060>
14:42:06.990 [CM505003]: Provider:[Internode] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]:5060]
14:42:04.112 [CM503003]: Call(28): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:10.10.2.201:5060
14:42:04.004 [CM503008]: Call(28): Call is terminated
14:42:02.278 Currently active calls - 2: [27,28]

Thankyou.
Darren

 

[leejor]

I see a call to ext 101 but no call attempt to a 1300... number. If some numbers, through the same providers, work, and other are having issues, then...be sure you are , in fact, sending the correct digits. If you are, then it sounds like an issue with your provider, or, something that they may be able to shed some light on, by looking at the call logs, from their end. You can try re posting an outgoing call attempt by one of your extensions to both a working number and a non-working 1300 number.

 

[will]

I have a ticket open on a similar issue. In the mean time I wanted to engage the user community.

My installation was a v8 (tested extensively) then upgraded to v9 (also tested extensively) problem started after last night's v9 SP3 upgrade.

No Audio on 800 or 888 outbound calls after upgrade to v9 SP3 - can't complete a toll free call.

Voip or PSTN - does not matter.

Other outbound calls are working without issue - no issue with inbound.

I also noticed the IVR Services pegging some high cpu (and then calming) - the install is on a Server 2003 R2 SP2 w/ IIS.

Any ideas?

-Will

 

[moore]

Hey all again, ok i have tried tweeking some things in Cisco but still same ol, this is now the complete call log i just made to Telstra 132203 number. i chose telstra because you will always have a long Hold time LOL.

10:52:53.439 [MS105000] C:12.2: No RTP packets were received:remoteAddr=203.2.134.1:18008,extAddr=121.223.223.130:9014,localAddr=121.223.223.130:9014
10:52:52.462 [CM503008]: Call(12): Call is terminated
10:52:36.454 Currently active calls - 1: [12]
10:52:36.119 Session 1642 of leg C:12.1 is confirmed
10:52:36.054 [CM503007]: Call(12): Device joined: sip:[email protected]:5060
10:52:36.036 [CM503007]: Call(12): Device joined: sip:[email protected]:5060
10:52:36.014 [MS210001] C:12.2:Answer received. RTP connection[unsecure]: 203.2.134.1:18008(18009)
10:52:36.011 Remote SDP is set for legC:12.2
10:52:35.949 [MS210003] C:12.1:Answer provided. Connection(transcoding mode[unsecure]):10.10.2.6:7034(7035)
10:52:35.946 [MS210001] C:12.2:Answer received. RTP connection[unsecure]: 203.2.134.1:18008(18009)
10:52:35.944 Remote SDP is set for legC:12.2
10:52:35.941 [CM505003]: Provider:[Internode] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]:5060]
10:52:35.940 [CM503002]: Call(12): Alerting sip:[email protected]:5060
10:52:31.801 [CM503025]: Call(12): Calling VoIPline:132203@(Ln.10000@Internode)@[Dev:sip:[email protected]:5060]
10:52:31.764 [MS210002] C:12.2:Offer provided. Connection(transcoding mode): 121.223.223.130:9014(9015)
10:52:31.380 [CM503004]: Call(12): Route 1: VoIPline:132203@(Ln.10000@Internode)@[Dev:sip:[email protected]:5060]
10:52:31.374 [CM503010]: Making route(s) to <sip:[email protected]>
10:52:31.374 [MS210000] C:12.1:Offer received. RTP connection: 10.10.2.202:16438(16439)
10:52:31.371 Remote SDP is set for legC:12.1
10:52:31.370 [CM505001]: Ext.102: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA525G-7.4.6] PBX contact: [sip:[email protected]:5060]
10:52:31.342 [CM503001]: Call(12): Incoming call from Ext.102 to <sip:[email protected]>
10:52:31.295 [CM500002]: Info on incoming INVITE:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.2.202:5060;branch=z9hG4bK-1c0afb0a
Max-Forwards: 70
Contact: "Darren Geyer"<sip:[email protected]:5060>
To: <sip:[email protected]>
From: "Darren Geyer"<sip:[email protected]>;tag=92fe3733857af89eo0
Call-ID: [email protected]
CSeq: 102 INVITE
Expires: 240
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE
Proxy-Authorization: Digest username="102",realm="3CXPhoneSystem",nonce="414d535c02d011bf44:19832e0b21fcd972728ce936e9d32376",uri="sip:[email protected]:5060",algorithm=MD5,response="71328d7c25ba87ef5b248d8247b03244"
Supported: replaces
User-Agent: Cisco/SPA525G-7.4.6
Content-Length: 0

 

[moore]

Hey all

I have now just added ISPhone to our 3CX box and tested it with 132203 (a known working Telstra number) now i get a lady stating that "the number is incomplete or incorrect" with the following numbers O2TD11 Thirty.

so maybe 3CX is adding or deleting numbers when we dial 13 xx xx 1300 xxx xxx numbers

 

[leejor]

10:52:31.342 [CM503001]: Call(12): Incoming call from Ext.102 to <sip:1132203@10.10.2.6>

This what you are dialling (1132203)

10:52:31.374 [CM503010]: Making route(s) to <sip:1132203@10.10.2.6>

This is what the outbound rules are routing the call on (1132203)

10:52:31.380 [CM503004]: Call(12): Route 1: VoIPline:132203@(Ln.10000@Internode)@[Dev:sip:[email protected]:5060]

This is what 3CX is going to send out after passing through your outbound rules (132203)

10:52:31.801 [CM503025]: Call(12): Calling VoIPline:132203@(Ln.10000@Internode)@[Dev:sip:[email protected]:5060]

This is the actual call being placed sending out 132203, is this number the correct one that you want to send out? More importantly, is this the number your provider wants to see? If not, then you need to correct your outbound rules.

 

[moore]

This is the actual call being placed sending out 132203, is this number the correct one that you want to send out? More importantly, is this the number your provider wants to see? If not, then you need to correct your outbound rules.

Yes this is a Telstra Number (just a test).
Ok this is the set up... Internode is on prefix 1, ISPhone is on prefix 2...
so to dial out number "132202" using internode you will have to type "1" to select internode and then the phone number "132202" in total it will be "1132202" then in the out bound rule we strip the first digit so the number becomes "132202" yeah! so this is correct, we have tested the number on our cell phones it all works well.

Now news to hand... 13/1300 number sometimes work with internode and now any number sometimes fail. when this happens next i will attach the call log.

 

[leejor]

Well...this is what i would suggest. If call problems are intermittent (I hate that type of problem), before pointing fingers at your provider, and it may very well be their problem, use Wireshark and collect a record of some failed calls. Record the times/dates as your provider may have logs that they can check as well. You will then have documentation showing that you sent the correct digits, but the calls still failed. You also have something you can email to them when you confront them. Just be certain that the Wireshark logs back you up.

 

[Discovery Technology]

My money is on it being the provider, however you may want to workshop your wireshark results with them to see if you need to adjust your outbound SIP field matching in your trunks.

I have done this before with Internode and after a while achieved some success, however you'll need to be patient as you work through this with them.

We are using Nexvoice (in Australia also) and dialling the 132203 number works no problems otherwise - I suspect most other VoIP providers would probably work just as well.