Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: sunspark on November 23, 2017, 02:49:46 PM
-
Hi ,
When internal number 1111 call 2222 ( and 2222 forward call to mobile ) : 1111 are able to join the 2222 mobile.
But when i call from outside with my mobile --> 2222 , i'm not able to join 2222 mobile
CRM/CIM 29
any idea ?
-
Hi ,
When internal number 1111 call 2222 ( and 2222 forward call to mobile ) : 1111 are able to join the 2222 mobile.
But when i call from outside with my mobile --> 2222 , i'm not able to join 2222 mobile
CRM/CIM 29
any idea ?
Test:
Remove call forwarding of 2222
Outside call to 2222, pick-up the Phone en do a blind transfer to your mobile Phone.
Is this working?
Verstuurd vanaf mijn SM-G935F met Tapatalk
-
Hi ,
When internal number 1111 call 2222 ( and 2222 forward call to mobile ) : 1111 are able to join the 2222 mobile.
But when i call from outside with my mobile --> 2222 , i'm not able to join 2222 mobile
CRM/CIM 29
any idea ?
Test:
Remove call forwarding of 2222
Outside call to 2222, pick-up the Phone en do a blind transfer to your mobile Phone.
Is this working?
Verstuurd vanaf mijn SM-G935F met Tapatalk
Hi bigsin ,
Yes , i'm able to pickup the call and forward it to mobile.
-
Class of restriction of the trunks would be first suspect, the trunk COR needs to be allowed to make the external call.
Also, depending on the type of trunk and carrier you might need to surpress the caller ID pass through.
You can always view the EDT (PRI/T1) or SIP trace and see why the call is failing.
-
Class of restriction of the trunks would be first suspect, the trunk COR needs to be allowed to make the external call.
Also, depending on the type of trunk and carrier you might need to surpress the caller ID pass through.
You can always view the EDT (PRI/T1) or SIP trace and see why the call is failing.
I checked my COR and all is OK.
with sip tcpdump i have 403 forbidden.
-
Class of restriction of the trunks would be first suspect, the trunk COR needs to be allowed to make the external call.
Also, depending on the type of trunk and carrier you might need to surpress the caller ID pass through.
You can always view the EDT (PRI/T1) or SIP trace and see why the call is failing.
I checked my COR and all is OK.
with sip tcpdump i have 403 forbidden.
I am assuming the From number in your Invite is the originating phone number... Your SIP provider is probably rejecting the call based on that since there isn't a valid Diversion or P-Asserted-Identity header being sent. In your SIP Peer Profile, Calling Line ID, change Public Calling Party Number Pass through to No and make sure that you have the Default CPN defined as your main billing number (SIP Pilot Number).
BTW, if you are using an Adtran Netvanta or Total Access 900e series router as your SIP SBC, I have a configuration to get around that and to properly send the original caller ID by adding a diversion header... It works with Broadsoft at least. I don't have a fix for MBG or other SBC's.
-
Class of restriction of the trunks would be first suspect, the trunk COR needs to be allowed to make the external call.
Also, depending on the type of trunk and carrier you might need to surpress the caller ID pass through.
You can always view the EDT (PRI/T1) or SIP trace and see why the call is failing.
I checked my COR and all is OK.
with sip tcpdump i have 403 forbidden.
I am assuming the From number in your Invite is the originating phone number... Your SIP provider is probably rejecting the call based on that since there isn't a valid Diversion or P-Asserted-Identity header being sent. In your SIP Peer Profile, Calling Line ID, change Public Calling Party Number Pass through to No and make sure that you have the Default CPN defined as your main billing number (SIP Pilot Number).
BTW, if you are using an Adtran Netvanta or Total Access 900e series router as your SIP SBC, I have a configuration to get around that and to properly send the original caller ID by adding a diversion header... It works with Broadsoft at least. I don't have a fix for MBG or other SBC's.
Hi,
Public Calling Party Number Pass through was already set to NO.
I added only SIP Pilot Number but still have the same issue.
About SBC , i have an MBG mut i dont use it for sip trunk.
-
Can we assume you are using a shortcode in the transfer? If so have you ticked override toll control on the short code?
-
Can we assume you are using a shortcode in the transfer? If so have you ticked override toll control on the short code?
I dont use transfert. But call forward from 6920 ip phone to mobile.
When i call from another dn (internal to internal) i m able to reach external destination. But when i call from external i doesn't works.
-
Do you have the external number direct in the call forward first alternative or is a call forward on the phone or does either forward to a shortcode first?
-
Do you have the external number direct in the call forward first alternative or is a call forward on the phone or does either forward to a shortcode first?
Hi xman
Call forword on the phone
-
Try call forward on the phone to a system shortcode containing the external number (not forgetting any access code such as 9) and tick overrides toll control.
-
Try call forward on the phone to a system shortcode containing the external number (not forgetting any access code such as 9) and tick overrides toll control.
You want me to make speedcall to my mobile?
-
Yes, system speedcall (sorry I still call them shortcodes; its my age) to your mobile then point your phone forward to the system speedcall (don't forget to enable overrides toll control in the speedcall).
-
Yes, system speedcall (sorry I still call them shortcodes; its my age) to your mobile then point your phone forward to the system speedcall (don't forget to enable overrides toll control in the speedcall).
OK :-)
I run this tests :
456 speedcall to my mobile 33123456789
Phone 2222 forwarded to 456
If i call from 1111 to 2222 i'm able to join the mobile 33123456789
If i call from outside 1111 i'm still able to join the mobile 33123456789
-
Sorted then?
-
Sorted then?
what do you mean ?
-
The problem you had in this post is now sorted. It is working as you wish?
-
The problem you had in this post is now sorted. It is working as you wish?
Oh sorry i did a mistake in my last post. In the second test if i call from outside 1111 im not able to join mobile.
-
But when i call from outside with my mobile --> 2222 , i'm not able to join 2222 mobile
If i call from outside 1111 i'm still [not] able to join the mobile 33123456789
Wel, no you won't as its 2222 that is forwarded...not 1111. Or are you saying that you have forwarded 1111 to 2222 and then want the call to forward to your mobile that is programmed into 2222?
Your posts are not clear. Can you give a definitive answer exactly what you want to happen?
-
But when i call from outside with my mobile --> 2222 , i'm not able to join 2222 mobile
If i call from outside 1111 i'm still [not] able to join the mobile 33123456789
Wel, no you won't as its 2222 that is forwarded...not 1111. Or are you saying that you have forwarded 1111 to 2222 and then want the call to forward to your mobile that is programmed into 2222?
Your posts are not clear. Can you give a definitive answer exactly what you want to happen?
Hi Xman ,
Extension 2222 forwarded to mobile.
When an internal extension (1111) call 2222 : --> 1111 able to join mobile
When external (DID) call 1111 : --> note able to join mobile.
It is clear ?
-
Yes. but why should a call to 1111 be able to use the transfer to your mobile on 2222? They are completely separate. If you want to reach your mobile on 1111 set up a transfer (just like 2222) to got to 456.
Or divert 1111 to 2222 ( which is set to divert) and make sure that the programming of number of hops for transfer is set to at least 3.
To be honest I am now really confused as to what you actually want to do?
-
Yes. but why should a call to 1111 be able to use the transfer to your mobile on 2222? They are completely separate. If you want to reach your mobile on 1111 set up a transfer (just like 2222) to got to 456.
Or divert 1111 to 2222 ( which is set to divert) and make sure that the programming of number of hops for transfer is set to at least 3.
To be honest I am now really confused as to what you actually want to do?
I don't now how can i be more clear .
In the morning you work in the office with extension 2222 . the afternoon you have an external appointement so you forward/transfert your extension 2222 to your mobile .
if someone from office call 2222 --> he is able to join u on your mobile.
if someone (Customer) outside office call your DID (2222) --> he is not able to join you on your mobile.
It is clear now ?
-
What does the external caller receive when phoning the DID of 2222 when its forwarded? You do realise it may take a while to connect; often more than you would imagine.... Are you using call forward all or just internal/external norply/busy? If the latter are you sure you have programmed BOTH types and enabled BOTH on the phone?
-
Odds are really good that it's one of three problems.
1) The COR of the incoming trunks does not allow it to call the cell.
To fix: forward to a system speed dial that has Override Toll Control ticked.
2) The COS does not allow trunk to trunk connections
To Fix: correct your COS of the incoming trunks.
3) Your outbound trunks are forwarding the incoming caller ID and your carrier will not allow that.
To Fix: change your SIP Peer or PRI to not forward the external Caller ID.
Ralph
-
Ralph;
"1) The COR of the incoming trunks does not allow it to call the cell.
To fix: forward to a system speed dial that has Override Toll Control ticked."
Done that.
2) The COS does not allow trunk to trunk connections
To Fix: correct your COS of the incoming trunks.
Done that; "Yes , i'm able to pickup the call and forward it to mobile."
3) Your outbound trunks are forwarding the incoming caller ID and your carrier will not allow that.
To Fix: change your SIP Peer or PRI to not forward the external Caller ID.
Done; not the problem
-
Hi Raph,
I think , i'm in the assumtion number 3 (Your outbound trunks are forwarding the incoming caller ID and your carrier will not allow that.)
i have already opened a case at my telco, I wait for the answer
-
id;
Hi, Public Calling Party Number Pass through was already set to NO.
I added only SIP Pilot Number but still have the same issue.
-
Solved :
It was the COR of trunk
Trunk Sip : COR 4
Users COR: 12
Ars rout : cor 30
In COR the ARS rout was set : 1-11,13-110
and now : 1-3,5-11,13-110
Thank u guys !