• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Call failing one way to extension

Status
Not open for further replies.

andrew_h

Joined
Apr 28, 2010
Messages
3
Reaction score
0
Ok, so i have 3cx installed working with a SPA-3102 as a gateway and an Engin SIP account.

I have 2 phones, one is a Avaya desk phone (x500), the other is a Nokia E51 (x501) connected wirelessly as a SIP client.

Incoming calls via both Voip and PSTN are routed through to both phones in a group - Works fine
The E51 can call the Desk phone no problems but for some reason the desk phone can not call the E51 and i have no idea why.

Log entries:
Code:
09:30:42.095  [CM503008]: Call(231): Call is terminated
09:30:42.033  [CM503020]: Normal call termination. Reason: No answer
09:30:42.033  [CM503016]: Call(231): Attempt to reach "501"<sip:[email protected]> failed. Reason: No Answer
09:30:42.033  [CM503003]: Call(231): Call to sip:[email protected] has failed; Cause: 408 Request Timeout; internal
09:30:09.923  [CM503025]: Call(231): Calling Ext:Ext.501@[Dev:sip:[email protected]:5060;transport=UDP]
09:30:09.861  [CM503004]: Call(231): Route 1: Ext:Ext.501@[Dev:sip:[email protected]:5060;transport=UDP]
09:30:09.861  [CM503010]: Making route(s) to "501"<sip:[email protected]>
09:30:09.861  [CM505001]: Ext.500: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Avaya SIP R2.2 Endpoint Brcm Callctrl/1.5.1.0 MxSF/v3.2.6.26] PBX contact: [sip:[email protected]:5060]
09:30:09.861  [CM503001]: Call(231): Incoming call from Ext.500 to "501"<sip:[email protected]>

Can somone explain this?

One thing that might have something to do with it is in the initial setup, i set the extension range to start at 100. As it turns out, this was no good so i have manually changed the extensions to 500, 501 etc. I could not find a 'propper' way to change the start of the range other than to re-install the whole lot.
 
Hi,

try to change spa-3102 port on line1 config admin and sip port to 5065.

try this and said result
 
Thankyou for your response but i am not having problems with the 3102 or any external calls. It is working fine for incoming and outgoing calls from/to both extensions. The problem i am having is local calls between the extensions.

For some reason 501 -> 500 works (E51 to Avaya) but 500 -> 501 does not work (avaya to E51), it produces the error i have above in the logs.
 
It looks like 3CX can't find Ext 501....

andrew_h said:
09:30:42.033 [CM503016]: Call(231): Attempt to reach "501"<sip:[email protected]> failed. Reason: No Answer

So, I would think that 501 either isn't registered (properly?) or is not responding to the call. Does it show in 3CX as being registered?

What does the 3CX log look like when you turn on Nokia and it first registers?
 
Code:
22:14:19.127  [CM504001]: Ext.501: new contact is registered. Contact(s): [sip:[email protected]:5060;transport=UDP/501]
It appears to be registered fine - green light etc. I would have thought that if it was not, then it would not work for incoming calls from external sources but it is. That is what has me baffled.
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,635
Messages
749,001
Members
144,754
Latest member
deanhbs
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.