Receptionist can not transfer to the ext.of unregistered ??

[kate]

Receptionist can not transfer to the ext.of unregistered ??

Extension 103 setting:If the ext103 is unregeistered that will forward to the extension 104.

The problem is When a caller calls into the system the digital receptionist answers the call and plays a welcome message.

The caller then dials Ext. 103 and is transferred to the extension.
But receptionsit said "call transfer failed" . why ??

 

[silentfun]

just to have you understand

incomming call to DR

DR play message
if caller dial 103 while messages is played
and 103 is unregistered and it is configured to forward to 104 if unregistered


1. Is 104 registered?
2. did the mediaserver recogniced the DTMF Tone? what does the log say?

3. try to config to the DR to forward to 103 if 1 is pressed and 104 if 2 is pressed. then try calling and press 1 instead of 103. and if failed press 2 to veryfy he send the call to 104.

Andy

 

[kate]

17:51:08.328 Call::RouteFailed :[CM503014]: Call(49): Attempt to reach [sip:[email protected]] failed. Reason: Not Registered
17:51:08.328 CallCtrl:nSelectRouteReq :[CM503015]: Call(49): Target is not registered: Ext:Ext.103
17:50:58.421 Call::RouteFailed :[CM503014]: Call(49): Attempt to reach [sip:[email protected]] failed. Reason: Not Registered
17:50:58.421 CallCtrl:nSelectRouteReq :[CM503015]: Call(49): Target is not registered: Ext:Ext.103

1. Ext 104 is registered.

2. 103 is unregistered and it is configured to forward to 104 . If caller dial 103 while messages is played "call transfer failed"

3.I pressed 1 (forward to 103) ==>I got "call transfer failed"
I pressed 2 (forward to 104) ==>It's no problem with the call

If I call the ext 103 form ext 102, It can be work well, the phone call will forwad to the ext 104 .

 

[Ricambi America]

I am experiencing the same problem on 5.0.3790.0.

 

[silentfun]

Re:

17:51:08.328 Call::RouteFailed :[CM503014]: Call(49): Attempt to reach [sip:[email protected]] failed. Reason: Not Registered
17:51:08.328 CallCtrl:nSelectRouteReq :[CM503015]: Call(49): Target is not registered: Ext:Ext.103
17:50:58.421 Call::RouteFailed :[CM503014]: Call(49): Attempt to reach [sip:[email protected]] failed. Reason: Not Registered
17:50:58.421 CallCtrl:nSelectRouteReq :[CM503015]: Call(49): Target is not registered: Ext:Ext.103

1. Ext 104 is registered.

2. 103 is unregistered and it is configured to forward to 104 . If caller dial 103 while messages is played "call transfer failed"

3.I pressed 1 (forward to 103) ==>I got "call transfer failed"
I pressed 2 (forward to 104) ==>It's no problem with the call

If I call the ext 103 form ext 102, It can be work well, the phone call will forwad to the ext 104 .

17:50:58.421 Call::RouteFailed :[CM503014]: Call(49): Attempt to reach [sip:[email protected]] failed. Reason: Not Registered

why is ext 106 also involved?

 

[Ricambi America]

In my case, the logs show:
15:52:07.656 Call::RouteFailed [CM503014]: Call(112): Attempt to reach [sip:[email protected]] failed. Reason: Not Found
15:52:07.656 CallCtrl:nSelectRouteReq [CM503013]: Call(112): No known route to target: [sip:[email protected]]

The phone is configured extremely simple:

Extension 201
Forward All Calls (regardless of registration) to x-xxx-xxx-xxxx (my external number)

I have also added extension 201 into a known working "outbound rule"


Any ideas?

 

[silentfun]

No known route to target: [sip:[email protected]]

this indicates the outbound rule is not ok

Andy

 

[kate]

Re: I tried it again, it still could not work ....

:cry: 10:40:19.968 Call::Terminate :[CM503008]: Call(54): Call is terminated
10:40:19.953 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:800
10:40:17.843 Call::Terminate :[CM503008]: Call(53): Call is terminated
10:40:17.843 Call::Terminate :[CM503008]: Call(53): Call is terminated
10:40:10.687 Call::RouteFailed :[CM503014]: Call(54): Attempt to reach [sip:[email protected]] failed. Reason: Not Registered
10:40:10.687 CallCtrl:nSelectRouteReq :[CM503015]: Call(54): Target is not registered: Ext:Ext.100
10:39:57.750 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:800
10:39:57.734 CallCtrl:nLegConnected :[CM503007]: Call(54): Device joined: sip:[email protected]:5060
10:39:56.906 CallCtrl:nLegConnected :[CM503007]: Call(54): Device joined: sip:
10:39:56.906 CallCtrl:nSelectRouteReq :[CM503004]: Call(54): Calling: IVR:800@[Dev]
10:39:56.890 Line:rintEndpointInfo :[CM505002]: Gateway:[pstn] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [056 12-35-9983931] Transport: [sip:192.168.1.3:5060]
10:39:56.890 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:800
10:39:56.875 CallCtrl:nIncomingCall :[CM503001]: Call(54): Incoming call from 10000@(Ln.10000@pstn) to [sip:[email protected]:5060]
10:39:56.859 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:800
10:39:52.859 MediaServerReporting:TMFhandler :[MS211000] C:53.2: 220.228.58.89:25764 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.
10:39:52.578 CallCtrl:nLegConnected :[CM503007]: Call(53): Device joined: sip:[email protected]:5060
10:39:52.562 CallCtrl:nLegConnected :[CM503007]: Call(53): Device joined: sip:[email protected]:15001
10:39:52.484 Line:rintEndpointInfo :[CM505003]: Provider:[voip] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:192.168.1.3:5060]
10:39:51.781 CallCtrl:nSelectRouteReq :[CM503004]: Call(53): Calling: VoIPline:10001@[Dev:sip:[email protected]:5060]
10:39:51.734 CallCtrl:nIncomingCall :[CM503001]: Call(53): Incoming call from Ext.802 to [sip:[email protected]]
10:39:34.156 Call::Terminate :[CM503008]: Call(52): Call is terminated


:cry: 10:39:29.453 CallCtrl:nRerouteReq :[CM503005]: Call(52): Forwarding: Ext:103@[Dev:sip:[email protected]:5060]
10:39:29.453 Call::RouteFailed :[CM503014]: Call(52): Attempt to reach [sip:[email protected]] failed. Reason: Not Registered
10:39:29.453 CallCtrl:nSelectRouteReq :[CM503015]: Call(52): Target is not registered: Ext:Ext.100
10:39:29.437 CallCtrl:nIncomingCall :[CM503001]: Call(52): Incoming call from Ext.802 to [sip:[email protected]]

I tried it again ~ The called form ext 802 to ext 100, It's wroking flawlessly with internal calls. (Configure behavior if this extension is unregistered and a call is received for this ext 103)
But when I made a incoming calls , it could not forward to the ext 103 . (If caller dial 103 while messages is played "call transfer failed")

My version is v5. 3790 .
Thank you ~~

 

[silentfun]

i have set up this to test your needs:
10004 Line to ext. 203
rule for 203 on unregistered forward to 200 (and 203 is unregistered)
then i called the phone number associated with line 10004 and look what happens and 200 was ringing.

i have included the logfile

>>>>>>>>>>>>>>>>>>>>>>>>>>
Time Function Message
06:48:16.019 Call::Terminate [CM503008]: Call(57): Call is terminated
06:48:15.988 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10004 forwards to DN:203
06:48:03.879 Extension:rintEndpointInfo [CM505001]: Ext.200: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXP2020 1.1.4.17] Transport: [sip:99.88.25.24:5060]
06:48:03.879 CallCtrl:nAnsweredCall [CM503002]: Call(57): Alerting sip:[email protected]:63466;transport=udp;user=phone
06:48:03.769 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10004 forwards to DN:203
06:48:03.754 MediaServerReporting::SetRemoteParty [MS210002] C:57.2:Offer provided. Connection(transcoding mode): 99.88.25.24:9014(9015)
06:48:03.488 CallCtrl:nRerouteReq [CM503005]: Call(57): Forwarding: Ext:200@[Dev:sip:[email protected]:63466;transport=udp;user=phone]
06:48:03.488 Call::RouteFailed [CM503014]: Call(57): Attempt to reach [sip:[email protected]:5060] failed. Reason: Not Registered
06:48:03.488 CallCtrl:nSelectRouteReq [CM503015]: Call(57): Target is not registered: Ext:Ext.203
06:48:03.488 CallCtrl:nSelectRouteReq [CM503010]: Making route(s) to [sip:[email protected]:5060]
06:48:03.488 MediaServerReporting::SetRemoteParty [MS210000] C:57.1:Offer received. RTP connection: 217.10.67.13:14606(14607)
06:48:03.488 CallLeg::setRemoteSdp Remote SDP is set for legC:57.1
06:48:03.488 Line:rintEndpointInfo [CM505003]: Provider:[0991580098012 SIPGATEde] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:99.88.25.24:5060]
06:48:03.488 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10004 forwards to DN:203
06:48:03.426 CallCtrl:nIncomingCall [CM503001]: Call(57): Incoming call from 09920792437@(Ln.10004@0991580098012 SIPGATEde) to [sip:[email protected]:5060]
06:48:03.191 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10004 forwards to DN:203
06:48:03.160 CallLeg:nNewCall [CM500002]: Info on incoming INVITE:
INVITE sip:[email protected]:5060;rinstance=12635708152e5859 SIP/2.0
Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK3dd1.a6d5bb44.0
Via: SIP/2.0/UDP 172.20.40.3;branch=z9hG4bK3dd1.a6d5bb44.0
Via: SIP/2.0/UDP 217.10.79.9:5060;received=217.10.68.222;branch=z9hG4bK6b870284
Via: SIP/2.0/UDP 217.10.67.13:5060;branch=z9hG4bK6b870284;rport=5060
Max-Forwards: 67
Record-Route: [sip:217.10.79.9;lr=on;ftag=as48ca2af7]
Record-Route: [sip:172.20.40.3;lr=on]
Record-Route: [sip:217.10.79.9;lr=on;ftag=as48ca2af7]
Contact: [sip:[email protected]]
To: [sip:[email protected]]
From: "09920792437"[sip:[email protected]];tag=as48ca2af7
Call-ID: [email protected]
CSeq: 102 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0
<<<<<<<<<<<<<<<<<<<<<<<<<<

this log is is very diferent to yours - it seems there is something not ok

it looks like 802 is one of your internal extensions.

what is about 800 is this DR or CallQueu or RingGroup?

Andy

 

[kate]

ext 800 is the DR ~~

when I called the ext 100 , I got the message "call transfer failed" , and then forward to the DR(800) again. (only in the incoming call)

I don't what's happening with my 3cx ??? shock >.<~~

 

[Ricambi America]

Sadly, we gave up on Version 5 and rolled back to 3 late last night, in order to have this functionality work properly. I'm sorry, but the V5 perhaps does work -- but it's either poorly documented, or an oddball configuration which kept it from working on our system.

Now, we use V3 DR's like this:

EXT 101, if busy go to VM
EXT 101, if no answer or unregistered go to DR 802
DR 802 is defined with message "Press 1 for xfer to external extension (201)", or stay on the line for VM
1-> Xfer to extension 201
no response, wait 2 second then -> Send to VM for 101

Seems like there are plenty of nice new features that I'm happy to pay for with V5 -- but not at the expense of crippling the business while we work through the oddities.

 

[kate]

Sadly, we gave up on Version 5 and rolled back to 3 late last night, in order to have this functionality work properly. I'm sorry, but the V5 perhaps does work -- but it's either poorly documented, or an oddball configuration which kept it from working on our system.

Now, we use V3 DR's like this:

EXT 101, if busy go to VM
EXT 101, if no answer or unregistered go to DR 802
DR 802 is defined with message "Press 1 for xfer to external extension (201)", or stay on the line for VM
1-> Xfer to extension 201
no response, wait 2 second then -> Send to VM for 101

Seems like there are plenty of nice new features that I'm happy to pay for with V5 -- but not at the expense of crippling the business while we work through the oddities.

By the way, If my configuration is that if ext101 is unregistered forward to VM , but I got a message "call tranfer failed " only, and then the call transfer to the DR(800) again .

Should I roll back to the v3 !!! :cry:

 

[Ricambi America]

Sadly, we gave up on Version 5 and rolled back to 3 late last night, in order to have this functionality work properly. I'm sorry, but the V5 perhaps does work -- but it's either poorly documented, or an oddball configuration which kept it from working on our system.

Now, we use V3 DR's like this:

EXT 101, if busy go to VM
EXT 101, if no answer or unregistered go to DR 802
DR 802 is defined with message "Press 1 for xfer to external extension (201)", or stay on the line for VM
1-> Xfer to extension 201
no response, wait 2 second then -> Send to VM for 101

Seems like there are plenty of nice new features that I'm happy to pay for with V5 -- but not at the expense of crippling the business while we work through the oddities.

By the way, If my configuration is that if ext101 is unregistered forward to VM , but I got a message "call tranfer failed " only, and then the call transfer to the DR(800) again .

Should I roll back to the v3 !!! :cry:

That's very similar to the problem we had. We're back on V3 now, and life has returned to normal.

 

[SY]

Thanks a lot for information.
Could you please specify, which of VoIP providers cannot handle such scenarios(transfer from the DR)?

Thanks

 

[kate]

Thanks a lot for information.
Could you please specify, which of VoIP providers cannot handle such scenarios(transfer from the DR)?

Thanks

I used the line of PSTN.....

 

[camdeal]

I have the same problem after upgrading from the latest v3.1 to latest v5.
DR will not transfer calls to extensions (registered or not). Deliver a "transfer failed" message with same logs as above.
Call from one ext to another (registered or not) displays a "no known route to target"

Called from 2145551212 in to POTS line on POTS Gateway
DR picks up and plays message and then I press 289 (to call Ext 289 which is registered and can dial out fine)
Here is the non-verbose logs...
-----------------------------------
15:33:30.306 Call::Terminate :[CM503008]: Call(4): Call is terminated
15:33:30.276 Call::Terminate :[CM503008]: Call(4): Call is terminated
15:33:30.226 LineCfg::getInboundTarget :[CM503011]: Inbound out-of-office hours' rule for LN:10011 forwards to DN:405
15:33:23.266 Call::RouteFailed :[CM503014]: Call(4): Attempt to reach [sip:[email protected]] failed. Reason: Busy
15:33:23.266 CallCtrl:nSelectRouteReq :[CM503013]: Call(4): No known route to target: [sip:[email protected]]
15:33:19.690 MediaServerReporting:TMFhandler :[MS211000] C:4.1: 172.31.255.85:6000 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.
15:33:12.941 LineCfg::getInboundTarget :[CM503011]: Inbound out-of-office hours' rule for LN:10011 forwards to DN:405
15:33:12.901 CallCtrl:nLegConnected :[CM503007]: Call(4): Device joined: sip:[email protected]:5060
15:33:12.260 CallCtrl:nLegConnected :[CM503007]: Call(4): Device joined: sip:
15:33:12.230 CallCtrl:nSelectRouteReq :[CM503004]: Call(4): Calling: IVR:405@[Dev]
15:33:12.200 Line:rintEndpointInfo :[CM505002]: Gateway:[WF POTS BANK B] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Audiocodes-Sip-Gateway-MP-118 FXO/v.5.00A.035.003] Transport: [sip:172.31.255.81:5060]
15:33:12.200 LineCfg::getInboundTarget :[CM503011]: Inbound out-of-office hours' rule for LN:10011 forwards to DN:405
15:33:12.150 CallCtrl:nIncomingCall :[CM503001]: Call(4): Incoming call from 2145551212@(Ln.10011@WF POTS BANK B) to [sip:[email protected]:5060]
15:33:12.130 LineCfg::getInboundTarget :[CM503011]: Inbound out-of-office hours' rule for LN:10011 forwards to DN:405
-----------------------------------
In addition, DIDs and incoming calls on Nexvortex work on the first call, then subsequent calls don't come through. Have to "reregister" the line.

After working all weekend on this, I also gave up and reverted back to v3.1 install so we can work properly Monday morning.

 

[blabla]

Any information when this bug was or will be fixed ?

 

[wtl]

Same problem here - digital receptionist will not transfer a call to voicemail when the extension is unregistered (5.0.3790).

I do note that if you configure "Forward all calls" for the extension to forward to voicemail, that works fine. This suggests to me that it's a bug, and not a misconfiguration.

 

[archie]

This bug is already found and exterminated. Update will be available quite soon (we're in test phase now)

 

[Ricambi America]

Bug? That's for dang sure. Here's the fix:

Add the extension of the Digital Receptionist (in my case '800') into one of the outbound rules. Bingo, it works.

Now, if DR gets a call, it tries to ring 101, 102, 103, etc. If no answer, it forwards to ext 500 -- which is our always 'unregistered' general mailbox. The outbound rule was needed for DR to get the call into 500. We struggled for a long time on this one, but seems to work now just perfectly.