Cant Forward Callsfrom external callers to external number.

Status
Not open for further replies.

jody7734

Joined
Oct 7, 2010
Messages
4
Reaction score
0
I'm trying to forward to cell phones when out off the office. External calls to the forwarded extension go to slow busy, works fine when calling from internal extensions. Here is the 3cx log:

11:25:32.828 [CM503020]: Normal call termination. Reason: Server Failure
11:25:32.828 [CM503016]: Call(12): Attempt to reach "5165"<sip:[email protected]:5060> failed. Reason: Not Implemented
11:25:32.828 [CM503003]: Call(12): Call to sip:[email protected]:5066 has failed; Cause: 488 Not Acceptable Here; from IP:127.0.0.1:5066
11:25:32.546 [CM503025]: Call(12): Calling Unknown:12107973044@(Ln.10000@Sangoma)@[Dev:sip:[email protected]:5066]
11:25:32.484 [CM503004]: Call(12): Route 1: Unknown:12107973044@(Ln.10000@Sangoma)@[Dev:sip:[email protected]:5066]
11:25:32.484 [CM503010]: Making route(s) to "5165"<sip:[email protected]:5060>
11:25:32.484 [CM505001]: Ext.2103088800: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Netborder Express Gateway/2.1.8] PBX contact: [sip:[email protected]:5060]
11:25:32.484 [CM503001]: Call(12): Incoming call from Sip.21037887700 to "5165"<sip:[email protected]:5060>
 
Re: Cant Forward Callsfrom external callers to external numb

I'm going to assume that the Sangoma is a card in the machine running 3CX, given that there is no separate IP shown for it.

jody7734 said:
11:25:32.828 [CM503003]: Call(12): Call to sip:[email protected]:5066 has failed; Cause: 488 Not Acceptable Here; from IP:127.0.0.1:5066

This would seem to indicate that the number, (or perhaps the SIP headers?) are not going to work. You do have a second trunk available for the call? How is the first call coming in, through the same card, or a direct SIP call? I've seen issues in the past, with the dealing of direct SIP calls.
 
Re: Cant Forward Callsfrom external callers to external numb

Yes the sangoma card is in the same server running netborder
 
Re: Cant Forward Callsfrom external callers to external numb

Sorry posted too quick.

Yes, I have a sangoma card int he same server and a full Pri (23 channels) connected to it. Calls are coming in through the sangoma.
 
Re: Cant Forward Callsfrom external callers to external numb

Off hand then, it would appear that the Sangoma is not happy with something (the number, or SIP header) and is telling you...
leejor said:
Cause: 488 Not Acceptable Here; from IP:127.0.0.1:5066

You may want to compare, a 3CX log of a call that completes (internal to external, and the one you posted. That may give you a clue as to the difference, but if it is a SIP header issue, then probably not.
 
Re: Cant Forward Callsfrom external callers to external numb

do you perhaps use a "dial 9" rule in your setup for outbound calls that are not being used in these that are not working?
 
Re: Cant Forward Callsfrom external callers to external numb

craigreilly said:
do you perhaps use a "dial 9" rule in your setup for outbound calls that are not being used in these that are not working?

I have a dial 9 rule and my forwarding number has a leading 9.
 
Re: Cant Forward Callsfrom external callers to external numb

Could it be something to do with the Caller ID difference (internal/external), being rejected by the PRI trunk provider, as passed to the gateway?
 
Status
Not open for further replies.

Forum statistics

Threads
111,851
Messages
589,359
Members
164,685
Latest member
Concorde