Calling obi to obi or transferring call from 1 obi to another.
azrobert:
In the OBi200 definition the user defined digit map is missing a verticle bar before "(200|201)". It should be like this:
DigitMap: ((100|101)<:@192.168.1.100:5062>|(200|201)<:@192.168.1.101:5062>|202<:@192.168.1.111:5060>|301<:@192.168.1.112:5060>)
Please check the call history of the OBi202 you dialing from.
Log directly into the OBi using the local interface.
Key the IP address of the OBi into a Web Browser.
Hit Enter
The UserID and default Password are both "admin".
Click Status on the left column.
Then click Call History.
The right column should show the outbound call like this:
sp3(200@xx.xx.xx.xx)
For security reasons this forum recommends changing the X_UserAgentPort.
Voice Services -> SP3 Service -> X_UserAgentPort
Did you change the user agent port on the receiving OBi202?
In the User Defined DigitMap the port ":5062" must match the X_UserAgentPort of SP3 on the receiving OBi2xx.
You register the IP Phone to SP4. Correct?
I didn't change anything on SP4, so the changes should not affect the IP Phone from registering.
Dranon2:
VERY strange for some reason I can login to the OBi200 but not into either 202 I just get a big REQUESTED URL NOT FOUND So I hooked a laptop right into its lan port keyed in the same url and was able to login..
The right column shows: ph1
ringing
azrobert:
Since you could only login to the OBi200 I assume this is the call history for the OBi200.
It shows the Phone Port is ringing.
Is it actually ringing?
Check the time stamp.
Is this entry from a previous call?
What did you dial and from which OBi did you dial from to get this result?
What does the left column show?
drgeoff:
Quote from: Dranon2 on October 27, 2014, 08:22:18 am
VERY strange for some reason I can login to the OBi200 but not into either 202 I just get a big REQUESTED URL NOT FOUND So I hooked a laptop right into its lan port keyed in the same url and was able to login..
The right column shows: ph1
ringing
Not strange at all. The 202 contains a router. There is a parameter 'AccessFromWAN' (on the page System Management - Device Admin) which has default setting 'No'. The Device Admin Guide describes it thus:
_____________________________________________________________
Allow access the OBi device management web pages from the WAN side
Note: Option available on OBi202/OBi302 only
_____________________________________________________________
(Unfortunately the missing 'to' in the above extract is not the only case of poor English and careless proof-reading in that document.)
azrobert:
I tried the OBi200 config on my OBi200 and OBi110.
It worked.
My Phone Port DigitMap was already setup to accept 3 digit dialed numbers, so I didn't change anything.
I copied the above p2p User Defined DigitMap and changed the IP addresses and port numbers.
I added {(Mp2p):sp4}, to the beginning of my Phone Port OutboundCallRoute.
That's all the changes I made.
The rest of the config is for inbound calls.
SP4 is where I defined my dummy trunk.
The call history left column showed:
From PH1
The call history right column showed:
To SP4(100@192.168.1.110:5061)
Ringing
Call Ended (486 Busy Here)
I got a Busy because my OBi110 was not configured correctly.
I just wanted to see if the call would go out with my config.
You should see similar entries in your OBi200 call history.
If not, please log into your OBi200 via the local interface and post the following:
Phone Port DigitMap and OutboundCallRoute
p2p User Defined DigitMap
I want you to use the Local Interface because I want to know if the code is getting to the OBi200 correctly.
You navigate the configuration similar to OBiTalk.
Don't make any changes using the local interface because they will be overlayed by OBiTalk.
Navigation
[0] Message Index
[#] Next page
[*] Previous page