Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 06-08-2010, 12:28 AM
cdresen cdresen is offline
Member
 
Join Date: May 2010
Posts: 3
cdresen has 10 reputation points
Default one-X Mobile callback doesn't work

I have a problem with my one-X Mobile installation. Looks like the one-X mobile sets two zeros infront of my extension and the cm isn't recognizing any incoming invites from the one-X Mobile.

We have traced all communications with wireshark on the one-X Mobile server, and traced the incoming calls on the trunk from the CM. (We are using a Midsize Business Template as CM solution here.)



Thats what my Callcontrol.log says when I try to place a call.

Code:
From: <sip:00142@172.16.254.244>;tag=1505998205.1.mkpaop   dpdfhhobfadicpdimo
To:  <sip:00142@172.16.254.201;transport=TCP;lr;avaya-cm-fnu=off-hook>;tag=80a0789e5b84df1bc3b4c257ad00
Call-ID: -939698215565572436@172.16.254.244
CSeq: 1 INVITE
Via: SIP/2.0/TCP 172.16.254.244:5070;branch=z9hG4bKAC10FEF4BADF00D0   0000128F8E368238576
Via: SIP/2.0/UDP app.ubiquitysoftware.com;branch=z9hG4bKAC10FEF4BAD   F00D00000128F8E36823
Record-Route: <sip:172.16.254.201;lr;transport=tcp>
Server: Avaya CM/R015x.02.1.016.4
Contact: <sip:00142@172.16.254.201;transport=tcp>
Supported: timer, replaces, join, histinfo
Allow: INVITE, CANCEL, BYE, ACK, PRACK, SUBSCRIBE, NOTIFY, REFER,  OPTIONS, INFO, PUBLISH
Content-Length: 0
As you can see in the From and To Header, there is always a 00 infront of the actual extension. I tried to use the dial-plan to cut them off, but nothing that I configure seems to change anything. Is there some sort of trick to it or am I missing something?


This is what I see when I trace my trunk:

Code:
15:24:33     Calling party trunk-group 12 member 1  cid 0x226f
15:24:33     Calling Number & Name NO-CPNumber NO-CPName
15:24:33     active trunk-group 12 member 1  cid 0x226f
15:25:33     idle trunk-group 12 member 1  cid 0x226f
Here you see, no number or anything is recognized. The call simply drops after one minute of waiting.

Does anyone have a working solution installed?

I would really appreciate any help or idea I can get!

Regards
Chris
Reply With Quote
  #2  
Old 06-10-2010, 10:43 PM
ghao ghao is offline
Aspiring Member
.
 
Join Date: Jun 2010
Posts: 1
ghao has 10 reputation points
Default

Please provide the whole call flow when you encounter the fault with "list trace" result.Thanks
Reply With Quote
  #3  
Old 06-14-2010, 07:50 AM
cdresen cdresen is offline
Member
 
Join Date: May 2010
Posts: 3
cdresen has 10 reputation points
Default

Hello ghao,

you won't see anything more in the list trace of the trunk, even with a working installation of one-X Mobile. I already checked this with a colleague.

I recently figured out the following: when you license a user on the one-X Mobile, there is supposed to be an entry in the off-pbx-telephone station-mapping for his particular extension...its supposed to look like this:

(warning: This isn't a copy from my installation, it's supposed to give you an idea)

Station Application Dial CC Phone Number Trunk Config Dual
Extension Prefix Selection Set Mode
1020 ONE-X - 0001020 80


1020 is the extension
0001020 is the Phone Number the one-X Mobile it trys to create the calls for (here the extension 1020)
80 is the trunk number to the one-X Mobile

It seems to vary how many zero's are infront of the extension. But what you see here is some sort of loopback for the one-X Mobile to callback the extension through the particular trunk (in this case 80).

This entry, for some reason, won't be created in my CM installation. The only thing I get is a similar entry for mobilephones, but without an entry for the trunk. So I can't trick the one-X Mobile to send my station any calls.

I opened up a ticket for this case, since I can't see any error from my side. This is my second installation of the same system, and the same error occured again.
Reply With Quote
  #4  
Old 09-20-2010, 06:37 PM
michal michal is offline
Aspiring Member
 
Join Date: Sep 2010
Posts: 2
michal has 10 reputation points
Default Same Issue...

Hi,

I have the same issue.

Have you managed to resolve the issue where there is no entry in off-pbx and you are able to use Callback properley?

Thanks,
M
Reply With Quote
  #5  
Old 09-26-2010, 06:59 PM
michal michal is offline
Aspiring Member
 
Join Date: Sep 2010
Posts: 2
michal has 10 reputation points
Smile Issue Resolved - port 5060 - Bi-Directional

Issue was resolved by changing port 5060 to be bi-directional. it was blocked from One X Mobile Side as this was implemented using the DMZ configuration.

When implementing one x mobile solution 5.2, it is important to udnerstand that you should expect 2 entries in off-pbx station which are created for any ONE-X user.
One is created as soon as you license a user and the other one is created as soon as you administer the mobile via the End User Web. If the first one is not created, then you have an issue with ports being blocked.
Reply With Quote
  #6  
Old 09-29-2010, 06:47 AM
peternaaktgeb peternaaktgeb is offline
Aspiring Member
 
Join Date: Sep 2010
Posts: 2
peternaaktgeb has 10 reputation points
Default

Hi,

I have the same issue.

How can I change port 5060 to be bi-directional on the One-X Mobile Side?

Thanks,
Peter
Reply With Quote
  #7  
Old 09-29-2010, 04:23 PM
aktran aktran is offline
Aspiring Member
.
 
Join Date: Sep 2010
Posts: 1
aktran has 10 reputation points
Default

Check to see if you are running CM 5.2.1 or higher.
Reply With Quote
  #8  
Old 09-30-2010, 10:59 PM
djiang djiang is offline
Member
.
 
Join Date: Sep 2010
Posts: 8
djiang has 10 reputation points
Default

Please show me the display off-pbx-telephone station-mapping.

If the station number is 1234, there should be a mapped station 001234 in the from.

If the callback doesn't work. i believe there a additional 0 added at the begining.

so the CM recieved "0001234" which is not recognized by CM.

Here is the resolution plan:

Under Advanced Settings on user Page ' Dial Out Prefix.
This was set to '0' . this was getting prefixed for the test user Robert van Linden. Extension 31208081294

Also since the System was not set to use PSTN PREFIX defined as *0 on the COS on the Admin page.
When changing the dial Out Prefix it would use the default PSTN PREFIX defined in the Admin Page.
The PSTN Prefix was set to blank as it's not being used. And then the dial out Prefix was also allowed to be set as blan k.

After changing the Dial Out Prefix to blank for the above user and testing a call, we see that the 1XM is sending the correct SIP URI and diallable number for the CM as required.
Reply With Quote
  #9  
Old 10-01-2010, 09:29 AM
peternaaktgeb peternaaktgeb is offline
Aspiring Member
 
Join Date: Sep 2010
Posts: 2
peternaaktgeb has 10 reputation points
Default

I solve the problem.

We where using ars analysis location 1. And the One-x Mobile server dails out through the ars analysis default. We copy the rules from location 1 to default. And everything works.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 11:42 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.