Call Transfer Failed

Status
Not open for further replies.

cpinero

Joined
Apr 26, 2008
Messages
12
Reaction score
0
I am trying to setup virtual extension that will forward a call to an external number. Every time I dial the number I get a "Call Transfer Failed" message.

From suggestions in other posts I have added an outbound rule by adding a prefix to the external number but I still cannot get it to work. In the extension settings I have:

Forward All -> All Hours -> All Calls -> Forward to External Number 9xxxxxxxxx

The nine (9) is the prefix for the outbound rule.

If calls are forwarded using the cfwd feature of the phone, the forwarding of calls works perfectly, but I need virtual extension for different external numbers.

Any ideas of what could be wrong??
 
Hi

if you call the Virtual extension internally does it work...and connect you to the external number?

Are you sure that you do not have an Outbound rule based on extension making the call? If you have outbound rules based on extension making the call remove them temporarily OR create a catch all Outbound rule at the bottom of the list.

Can you reproduce the issue and attach the Verbose logs of such a call?
 
If the extension is dialed internally the transfer works with no problems.

All outbound rules are based on prefix numbers, none have extensions associated with them.

This is the log when the call fails:

16:26:30.609 [CM503008]: Call(144): Call is terminated
16:26:30.609 [CM503008]: Call(144): Call is terminated
16:26:27.562 [MS210005] C:144.2:Answer provided. Connection(proxy mode):127.0.0.1:7104(7105)
16:26:27.562 [MS210001] C:144.1:Answer received. RTP connection: 192.168.1.160:5012(5013)
16:26:27.562 Remote SDP is set for legC:144.1
16:26:27.453 [MS210004] C:144.1:Offer provided. Connection(proxy mode): 192.168.1.180:7102(7103)
16:26:27.453 [MS210000] C:144.2:Offer received. RTP connection: 127.0.0.1:40708(40709)
16:26:27.453 Remote SDP is set for legC:144.2
16:26:27.125 [CM503015]: Call(144): Attempt to reach <sip:[email protected]:5060> failed. Reason: Reason Unknown
16:26:27.125 [CM503003]: Call(144): Call to sip:[email protected]:5060 has failed; Cause: 400 Bad request; from IP:194.221.62.198:5060
16:26:26.781 [CM503004]: Call(144): Calling: VoIPline:1305xxxxxxx@(Ln.10008@Poivy)@[Dev:sip:[email protected]:5060]
16:26:26.625 [CM503010]: Making route(s) to <sip:[email protected]:5060>
16:26:26.625 Refer: from="DR800:"<sip:[email protected]:5060>;tag=15420b21; to="WIRELESS CALLER"<sip:[email protected]:5060>;tag=d0363c51; RefTo=<sip:[email protected]:5060>
16:26:26.296 [MS210003] C:144.2:Answer provided. Connection(transcoding mode):127.0.0.1:7104(7105)
16:26:26.296 [MS210001] C:144.1:Answer received. RTP connection: 192.168.1.160:5012(5013)
16:26:26.296 Remote SDP is set for legC:144.1
16:26:26.187 [MS210002] C:144.1:Offer provided. Connection(transcoding mode): 192.168.1.180:7102(7103)
16:26:26.187 [MS210000] C:144.2:Offer received. RTP connection: 127.0.0.1:40708(40709)
16:26:26.187 Remote SDP is set for legC:144.2
16:26:17.109 Session 50801 of leg C:144.1 is confirmed
16:26:17.031 [CM503007]: Call(144): Device joined: sip:[email protected]:40600;rinstance=b8779f494d3c9131
16:26:17.015 [CM503007]: Call(144): Device joined: sip:[email protected]:5064
16:26:17.015 [CM505001]: Ext.800: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] Transport: [sip:127.0.0.1:5060]
16:26:17.015 [MS210005] C:144.1:Answer provided. Connection(proxy mode):192.168.1.180:7102(7103)
16:26:17.015 [MS210001] C:144.2:Answer received. RTP connection: 127.0.0.1:40708(40709)
16:26:17.000 Remote SDP is set for legC:144.2
16:26:17.000 [CM503002]: Call(144): Alerting sip:[email protected]:40600;rinstance=b8779f494d3c9131
16:26:16.500 [MS210004] C:144.2:Offer provided. Connection(proxy mode): 127.0.0.1:7104(7105)
16:26:16.500 [CM503004]: Call(144): Calling: Ext:Ext.800@[Dev:sip:[email protected]:40600;rinstance=b8779f494d3c9131]
16:26:16.500 [CM503010]: Making route(s) to <sip:[email protected]:5060>
16:26:16.500 [MS210000] C:144.1:Offer received. RTP connection: 192.168.1.160:5012(5013)
16:26:16.500 Remote SDP is set for legC:144.1
16:26:16.500 [CM505002]: Gateway:[GXW4104 Miami] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW4104 (HW 1.0, Ch:2) 1.0.1.10] Transport: [sip:192.168.1.180:5060]
16:26:16.484 [CM503001]: Call(144): Incoming call from 305xxxxxxx@(Ln.10002@GXW4104 Miami) to <sip:[email protected]:5060>
16:26:16.484 [CM503012]: Inbound office hours rule for 10002 forwards to DN:800
16:26:16.484 Looking for inbound target: called=10000+; caller=305xxxxxxx
16:26:16.453 [CM500002]: Info on incoming INVITE:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 192.168.1.160:5064;branch=z9hG4bK71b3cbf5cdc6d231
Max-Forwards: 70
Contact: <sip:[email protected]:5064>
To: <sip:[email protected]>
From: "WIRELESS CALLER"<sip:[email protected]>;tag=f624849411a03d97
Call-ID: [email protected]
CSeq: 18920 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE, PRACK
Proxy-Authorization: Digest username="10002",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:[email protected]",nonce="12878169976:47c4ce69bfc8cdd373b2f42a846e3f7f",response="d3b05ac2a769f9ddbc2e77692a63fd53"
Supported: replaces, timer, path
User-Agent: Grandstream GXW4104 (HW 1.0, Ch:2) 1.0.1.10
Content-Length: 0

This is the log if dialed internally:

16:24:45.656 [CM503008]: Call(143): Call is terminated
16:24:35.125 [CM505003]: Provider:[Poivy] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:192.168.1.180:5060]
16:24:35.125 [MS210005] C:143.1:Answer provided. Connection(proxy mode):192.168.1.180:7100(7101)
16:24:35.125 [MS210001] C:143.2:Answer received. RTP connection: 195.219.64.173:25504(25505)
16:24:35.125 Remote SDP is set for legC:143.2
16:24:35.125 [CM503002]: Call(143): Alerting sip:[email protected]:5060
16:24:34.578 [MS210004] C:143.2:Offer provided. Connection(proxy mode): 70.148.132.248:9042(9043)
16:24:34.500 [CM503004]: Call(143): Calling: VoIPline:1305xxxxxx@(Ln.10008@Poivy)@[Dev:sip:[email protected]:5060]
16:24:34.343 [CM503010]: Making route(s) to <sip:[email protected]>
16:24:34.343 [MS210000] C:143.1:Offer received. RTP connection: 192.168.1.101:16476(16477)
16:24:34.343 Remote SDP is set for legC:143.1
16:24:34.343 [CM505001]: Ext.100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA922-6.1.3(a)] Transport: [sip:192.168.1.180:5060]
16:24:34.328 [CM503001]: Call(143): Incoming call from Ext.100 to <sip:[email protected]>
16:24:34.328 [CM500002]: Info on incoming INVITE:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK-9d55fe09
Max-Forwards: 70
Contact: "Carlos Pinero"<sip:[email protected]:5060>
To: <sip:[email protected]>
From: "Carlos Pinero"<sip:[email protected]>;tag=686688f8fe0f019o0
Call-ID: [email protected]
CSeq: 102 INVITE
Expires: 240
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Proxy-Authorization: Digest username="100",realm="3CXPhoneSystem",nonce="12878169874:19ec284e2751976f0e2c291e9c978a59",uri="sip:[email protected]",algorithm=MD5,response="2700ba51d3d87db87bde9966d844b24f"
Supported: replaces
User-Agent: Linksys/SPA922-6.1.3(a)
Content-Length: 0

Thanks,

Carlos Pinero
 
I had the same issue.

my outbound rule was from ext201 to my voip provider
I added a secound outbound rule for number starting with "1" and I select to don't stip any digit.
then in the unregistred ext, I forward call to: 1 xxx xxx xxxx (without spaces)
 
cpinero said:
If the extension is dialed internally the transfer works with no problems.

All outbound rules are based on prefix numbers, none have extensions associated with them.

This is the log when the call fails:

16:26:30.609 [CM503008]: Call(144): Call is terminated
16:26:30.609 [CM503008]: Call(144): Call is terminated
16:26:27.562 [MS210005] C:144.2:Answer provided. Connection(proxy mode):127.0.0.1:7104(7105)
16:26:27.562 [MS210001] C:144.1:Answer received. RTP connection: 192.168.1.160:5012(5013)
16:26:27.562 Remote SDP is set for legC:144.1
16:26:27.453 [MS210004] C:144.1:Offer provided. Connection(proxy mode): 192.168.1.180:7102(7103)
16:26:27.453 [MS210000] C:144.2:Offer received. RTP connection: 127.0.0.1:40708(40709)
16:26:27.453 Remote SDP is set for legC:144.2
16:26:27.125 [CM503015]: Call(144): Attempt to reach <sip:[email protected]:5060> failed. Reason: Reason Unknown
16:26:27.125 [CM503003]: Call(144): Call to sip:[email protected]:5060 has failed; Cause: 400 Bad request; from IP:194.221.62.198:5060
16:26:26.781 [CM503004]: Call(144): Calling: VoIPline:1305xxxxxxx@(Ln.10008@Poivy)@[Dev:sip:[email protected]:5060]
16:26:26.625 [CM503010]: Making route(s) to <sip:[email protected]:5060>

This is the log if dialed internally:

16:24:45.656 [CM503008]: Call(143): Call is terminated
16:24:35.125 [CM505003]: Provider:[Poivy] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:192.168.1.180:5060]
16:24:35.125 [MS210005] C:143.1:Answer provided. Connection(proxy mode):192.168.1.180:7100(7101)
16:24:35.125 [MS210001] C:143.2:Answer received. RTP connection: 195.219.64.173:25504(25505)
16:24:35.125 Remote SDP is set for legC:143.2
16:24:35.125 [CM503002]: Call(143): Alerting sip:[email protected]:5060
16:24:34.578 [MS210004] C:143.2:Offer provided. Connection(proxy mode): 70.148.132.248:9042(9043)
16:24:34.500 [CM503004]: Call(143): Calling: VoIPline:1305xxxxxx@(Ln.10008@Poivy)@[Dev:sip:[email protected]:5060]
16:24:34.343 [CM503010]: Making route(s) to <sip:[email protected]>

Thanks,

Carlos Pinero

It looks as though the outbound call is going through a proxy from internal when it succeeds, but there is no proxy involved when coming from external through the Vegastream.
 
discovery1 said:
It looks as though the outbound call is going through a proxy from internal when it succeeds, but there is no proxy involved when coming from external through the Vegastream.

If the problem is using the proxy how can I force to use the proxy on external calls through the Grandstream??
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,885
Messages
589,547
Members
164,744
Latest member
johnblackwood1