News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Cannot Setup Cisco 7942 with Obi200

Started by voipnewuser, September 22, 2019, 12:17:56 AM

Previous topic - Next topic

voipnewuser

Can someone help me setup the correct configuration for the Cisco IP 7942 to work with Obi200?

I followed the setup of the guides on the Obi200 end, and using PhonerLite, it does seem to receive the call.

However, I cannot setup the configuration of the Cisco IP Phone to dial out or receive incoming calls. There is a dial tone but it does not go any further than that.

user = Obi200
pass = none

Obi200 IP = 192.168.0.68
Cisco Phone IP = 192.168.1.3
All ports going to 5063 configured on SP4.

Also, I've read somewhere that I can include a <flat-profile> which will auto update the configuration every soft reboot, can someone tell me how I can incorporate that into the conf.xml below. I am running a TFTPD64 server on 192.168.1.2. For now, I have been manually hard resetting, and re-uploading ALL of the firmware files every time I want to change a configuration in the SEP(MAC).conf.xml file. Thank you for any help.

Here is my SEP(MAC).conf.xml:

Quote
<device>
<deviceProtocol>SIP</deviceProtocol>
<sshUserId>cisco</sshUserId> 
<sshPassword>cisco</sshPassword>
<devicePool> 
<dateTimeSetting> 
    <dateTemplate>M/D/Ya</dateTemplate> 
    <timeZone>Pacific Standard/Daylight Time</timeZone>
    <ntps> 
         <ntp> 
             <name>10.1.2.3</name> 
             <ntpMode>Unicast</ntpMode> 
         </ntp> 
    </ntps> 
</dateTimeSetting> 
<callManagerGroup> 
    <members> 
       <member priority="0"> 
          <callManager> 
             <ports> 
                <ethernetPhonePort>2000</ethernetPhonePort> 
                <sipPort>5063</sipPort> 
                <securedSipPort>5063</securedSipPort> 
             </ports> 
             <processNodeName>192.168.0.68</processNodeName> 
          </callManager> 
       </member> 
    </members> 
</callManagerGroup> 
</devicePool> 
<sipProfile>
<sipProxies> 
    <backupProxy></backupProxy> 
    <backupProxyPort></backupProxyPort> 
    <emergencyProxy></emergencyProxy> 
    <emergencyProxyPort></emergencyProxyPort> 
    <outboundProxy>192.168.0.68</outboundProxy> 
    <outboundProxyPort>5063</outboundProxyPort> 
    <registerWithProxy>false</registerWithProxy> 
</sipProxies> 
<sipCallFeatures>
    <cnfJoinEnabled>true</cnfJoinEnabled> 
    <callForwardURI>x--serviceuri-cfwdall</callForwardURI> 
    <callPickupURI>x-cisco-serviceuri-pickup</callPickupURI> 
    <callPickupListURI>x-cisco-serviceuri-opickup</callPickupListURI> 
    <callPickupGroupURI>x-cisco-serviceuri-gpickup</callPickupGroupURI> 
    <meetMeServiceURI>x-cisco-serviceuri-meetme</meetMeServiceURI> 
    <abbreviatedDialURI>x-cisco-serviceuri-abbrdial</abbreviatedDialURI> 
    <rfc2543Hold>false</rfc2543Hold> 
    <callHoldRingback>2</callHoldRingback> 
    <localCfwdEnable>true</localCfwdEnable> 
    <semiAttendedTransfer>true</semiAttendedTransfer> 
    <anonymousCallBlock>2</anonymousCallBlock> 
    <callerIdBlocking>2</callerIdBlocking> 
    <dndControl>0</dndControl> 
    <remoteCcEnable>true</remoteCcEnable> 
</sipCallFeatures>
<sipStack> 
    <sipInviteRetx>6</sipInviteRetx> 
    <sipRetx>10</sipRetx> 
    <timerInviteExpires>180</timerInviteExpires> 
    <timerRegisterExpires>1200</timerRegisterExpires> 
    <timerRegisterDelta>5</timerRegisterDelta> 
    <timerKeepAliveExpires>120</timerKeepAliveExpires> 
    <timerSubscribeExpires>120</timerSubscribeExpires> 
    <timerSubscribeDelta>5</timerSubscribeDelta> 
    <timerT1>500</timerT1> 
    <timerT2>4000</timerT2> 
    <maxRedirects>70</maxRedirects> 
    <remotePartyID>false</remotePartyID> 
    <userInfo>None</userInfo> 
</sipStack>
<autoAnswerTimer>1</autoAnswerTimer> 
<autoAnswerAltBehavior>false</autoAnswerAltBehavior> 
<autoAnswerOverride>true</autoAnswerOverride> 
<transferOnhookEnabled>false</transferOnhookEnabled> 
<enableVad>false</enableVad>
<preferredCodec>g711ulaw</preferredCodec> 
<dtmfAvtPayload>101</dtmfAvtPayload> 
<dtmfDbLevel>3</dtmfDbLevel> 
<dtmfOutofBand>avt</dtmfOutofBand> 
<alwaysUsePrimeLine>false</alwaysUsePrimeLine> 
<alwaysUsePrimeLineVoiceMail>false</alwaysUsePrimeLineVoiceMail> 
<kpml>3</kpml>
<natReceivedProcessing>false</natReceivedProcessing> 
<natEnabled>false</natEnabled> 
<natAddress></natAddress> 
<phoneLabel>Obi200</phoneLabel>
<stutterMsgWaiting>1</stutterMsgWaiting>
<callStats>false</callStats> 
<silentPeriodBetweenCallWaitingBursts>10</silentPeriodBetweenCallWaitingBursts> 
<disableLocalSpeedDialConfig>false</disableLocalSpeedDialConfig>
<startMediaPort>16384</startMediaPort> 
<stopMediaPort>32766</stopMediaPort>
<sipLines>
  <line button="1">
       <featureID>9</featureID> 
       <featureLabel>Obi200</featureLabel> 
       <proxy>192.168.0.68</proxy> 
       <port>5063</port>
       <name>Obi200</name>
       <displayName>MY VOIP</displayName> 
       <autoAnswer>
          <autoAnswerEnabled>2</autoAnswerEnabled>
       </autoAnswer> 
       <callWaiting>3</callWaiting>
       <authName>Obi200</authName> 
       <authPassword></authPassword> 
       <sharedLine>false</sharedLine>
       <messageWaitingLampPolicy>1</messageWaitingLampPolicy> 
       <messagesNumber>*97</messagesNumber> 
       <ringSettingIdle>4</ringSettingIdle> 
       <ringSettingActive>5</ringSettingActive>
       <contact>Obi200</contact> 
       <forwardCallInfoDisplay> 
          <callerName>true</callerName> 
          <callerNumber>false</callerNumber> 
          <redirectedNumber>false</redirectedNumber> 
          <dialedNumber>true</dialedNumber> 
       </forwardCallInfoDisplay> 
    </line>
</sipLines>
<voipControlPort>5063</voipControlPort> 
<dscpForAudio>184</dscpForAudio> 
<ringSettingBusyStationPolicy>0</ringSettingBusyStationPolicy> 
<dialTemplate>dialplan.xml</dialTemplate> 
</sipProfile>
<commonProfile> 
<phonePassword></phonePassword>
<backgroundImageAccess>true</backgroundImageAccess> 
<callLogBlfEnabled>2</callLogBlfEnabled> 
</commonProfile>
<loadInformation>SIP42.8-5-3SR1S</loadInformation>
<vendorConfig>
<disableSpeaker>false</disableSpeaker>
<disableSpeakerAndHeadset>false</disableSpeakerAndHeadset>
<pcPort>0</pcPort>
<settingsAccess>1</settingsAccess>
<garp>0</garp>
<voiceVlanAccess>0</voiceVlanAccess>
<videoCapability>0</videoCapability> 
<autoSelectLineEnable>0</autoSelectLineEnable>
<webAccess>1</webAccess> 
<spanToPCPort>1</spanToPCPort> 
<loggingDisplay>1</loggingDisplay> 
<loadServer></loadServer> 
</vendorConfig>
<versionStamp></versionStamp>
<userLocale>
<name>United_States</name>
<uid>64</uid>
<langCode>en_US</langCode>
<version>1.0.0.0-1</version>
<winCharSet>iso-8859-1</winCharSet>
</userLocale>
<deviceSecurityMode>1</deviceSecurityMode>
<authenticationURL></authenticationURL> 
<directoryURL></directoryURL> 
<idleURL></idleURL> 
<informationURL></informationURL>
<messagesURL></messagesURL> 
<proxyServerURL></proxyServerURL> 
<servicesURL></servicesURL>
<dscpForSCCPPhoneConfig>96</dscpForSCCPPhoneConfig> 
<dscpForSCCPPhoneServices>0</dscpForSCCPPhoneServices> 
<dscpForCm2Dvce>96</dscpForCm2Dvce>
<transportLayerProtocol>4</transportLayerProtocol>

<capfAuthMode>0</capfAuthMode> 
<capfList> 
<capf> 
    <phonePort>3804</phonePort> 
</capf> 
</capfList>
<certHash></certHash> 
<encrConfig>false</encrConfig> 
</device>

drgeoff

Is there a good reason the OBi has a 192.168.0 address and the Cisco has 192.168.1? Have you got routeing between them?

voipnewuser

Quote from: drgeoff on September 22, 2019, 01:39:44 AM
Is there a good reason the OBi has a 192.168.0 address and the Cisco has 192.168.1? Have you got routeing between them?

Yes, the Cisco IP Phone => POE Switch => Asus Router => Obi200 => Modem => Internet

Sheffield_Steve

That's not good.  To have the Obi out on the internet.

Move it the same POE switch as the phone.

voipnewuser

Quote from: Sheffield_Steve on September 22, 2019, 08:07:50 AM
That's not good.  To have the Obi out on the internet.

Move it the same POE switch as the phone.

Obi200 is connected to the internet. I can make and receive calls using a traditional phone on Phone jack 1.

Sheffield_Steve

#5
What I'm saying is that it should NOT be connected directly to the modem (internet), but should be connected to the same switch as the phone.

You setup means it's not secure.

drgeoff

Quote from: voipnewuser on September 22, 2019, 07:44:17 AM
Quote from: drgeoff on September 22, 2019, 01:39:44 AM
Is there a good reason the OBi has a 192.168.0 address and the Cisco has 192.168.1? Have you got routeing between them?

Yes, the Cisco IP Phone => POE Switch => Asus Router => Obi200 => Modem => Internet
I do not understand that.  An OBi200 has one ethernet port.  Yet you show it as between modem and Asus router.

The original Obihai document is attached.

voipnewuser

#7
Quote from: drgeoff on September 22, 2019, 09:24:02 AM
Quote from: voipnewuser on September 22, 2019, 07:44:17 AM
Quote from: drgeoff on September 22, 2019, 01:39:44 AM
Is there a good reason the OBi has a 192.168.0 address and the Cisco has 192.168.1? Have you got routeing between them?

Yes, the Cisco IP Phone => POE Switch => Asus Router => Obi200 => Modem => Internet
I do not understand that.  An OBi200 has one ethernet port.  Yet you show it as between modem and Asus router.

The original Obihai document is attached.

Sorry, let me further clarify, and thank you for the quick response.

Cisco IP phone is connected to port 1 of the POE switch (containing 5 ports all together).
Obi200 ethernet/internet port connected to port 2 of POE switch
POE switch port 3 (LAN only, no POE) connected to ASUS Router LAN port 1
ASUS router internet port connected to Internet Modem

And yes, Ive spent several hours configuring ITSP D, SP2, SP4 based on that document.

drgeoff

#8
Quote from: voipnewuser on September 22, 2019, 09:41:06 AM
Quote from: drgeoff on September 22, 2019, 09:24:02 AM
Quote from: voipnewuser on September 22, 2019, 07:44:17 AM
Quote from: drgeoff on September 22, 2019, 01:39:44 AM
Is there a good reason the OBi has a 192.168.0 address and the Cisco has 192.168.1? Have you got routeing between them?

Yes, the Cisco IP Phone => POE Switch => Asus Router => Obi200 => Modem => Internet
I do not understand that.  An OBi200 has one ethernet port.  Yet you show it as between modem and Asus router.

The original Obihai document is attached.

Sorry, let me further clarify, and thank you for the quick response.

Cisco IP phone is connected to port 1 of the POE switch (containing 5 ports all together).
Obi200 ethernet/internet port connected to port 2 of POE switch
POE switch port 3 (LAN only, no POE) connected to ASUS Router LAN port 1
ASUS router internet port connected to Internet Modem

And yes, Ive spent several hours configuring ITSP D, SP2, SP4 based on that document.
1.  Given that description of how the OBi and Cisco are both on the LAN side of the Asus router, I repeat the question I asked in my first post in this thread.

2.  I have no first hand experience of this but there were reports that at some point a firmware version caused some IP phones to be unable to register to the OBi.  I do not know if subsequent firmwares still cause this.  Search for post(s) by azrobert which mention a workaround of setting the IP phone to be able to call without being registered.

Update: see http://www.obitalk.com/forum/index.php?topic=14002 and links therein.

voipnewuser

#9
Quote from: drgeoff on September 22, 2019, 09:54:09 AM
Quote from: voipnewuser on September 22, 2019, 09:41:06 AM
Quote from: drgeoff on September 22, 2019, 09:24:02 AM
Quote from: voipnewuser on September 22, 2019, 07:44:17 AM
Quote from: drgeoff on September 22, 2019, 01:39:44 AM
Is there a good reason the OBi has a 192.168.0 address and the Cisco has 192.168.1? Have you got routeing between them?

Yes, the Cisco IP Phone => POE Switch => Asus Router => Obi200 => Modem => Internet
I do not understand that.  An OBi200 has one ethernet port.  Yet you show it as between modem and Asus router.

The original Obihai document is attached.

Sorry, let me further clarify, and thank you for the quick response.

Cisco IP phone is connected to port 1 of the POE switch (containing 5 ports all together).
Obi200 ethernet/internet port connected to port 2 of POE switch
POE switch port 3 (LAN only, no POE) connected to ASUS Router LAN port 1
ASUS router internet port connected to Internet Modem

And yes, Ive spent several hours configuring ITSP D, SP2, SP4 based on that document.
1.  Given that description of how the OBi and Cisco are both on the LAN side of the Asus router, I repeat the question I asked in my first post in this thread.

2.  I have no first hand experience of this but there were reports that at some point a firmware version caused some IP phones to be unable to register to the OBi.  I do not know if subsequent firmwares still cause this.  Search for post(s) by azrobert which mention a workaround of setting the IP phone to be able to call without being registered.

Update: see http://www.obitalk.com/forum/index.php?topic=14002 and links therein.

1. I tried to change IP of cisco phone to 192.168.0, but phone won't take firmware if it's not assigned 192.168.1.XX. I can't change the Obi200 IP to 192.168.1.XX?

2. I know of the registering issue, which was why I set register to false in the xml config file. The phone has a dial tone and ready to make calls, but it does not go through or receive any calls.

drgeoff

Until the OBi and the Cisco are on the same subnet, how are you expecting them to communicate? Your Asus router does not route between its LAN ports.

If your phone must be on 192.168.1 then you'll need to change everything else to be on 192.168.1 too.  I'm sure your router can be changed so that its DHCP server will allocate addresses in the 192.168.1 subnet.


voipnewuser

#11
Quote from: drgeoff on September 22, 2019, 11:52:05 AM
Until the OBi and the Cisco are on the same subnet, how are you expecting them to communicate? Your Asus router does not route between its LAN ports.

If your phone must be on 192.168.1 then you'll need to change everything else to be on 192.168.1 too.  I'm sure your router can be changed so that its DHCP server will allocate addresses in the 192.168.1 subnet.



Thank you again for the quick responses, I've spent so many hours on trying to get this to work :(

It seems 192.168.1.XX is the most logical gateway. How would I go about to changing/assigning the Obi200 to 192.168.1.XX? I tried to delete the device and add it back again, but everytime it goes back to 192.168.0.XX, I even have another Obi202, and even with a fresh install, it assigns 192.168.0.XX. I'm currently working right now so I can't test it out, but do you think plugging the Obi200 directly to the back of ASUS router LAN port #2 for example and re-adding in the device might change the IP to 192.168.1.XX?

Another thing is I've tried using WhireShark, and filtering for SIP, I've noticed that the cisco ip phone does show when I attempt to dial out: Source: 192.168.1.3, Destination: SIP 5555555555@192.168.0.68 (example phone# replaced with a real working #), which seems it does attempt to reach out to 192.168.0 at the correct port 5603?? but then again I'm a complete newbie when it comes to networking, so I don't know if that means anything useful.

I've scoured the forum and every thread relating to the cisco ip phone with obitalk and I can't still find a solution!:(

drgeoff

If the OBi is getting its IP parameters by DHCP (which is its default mode) then it will, on powerup, automatically get an 192.168.1 address if and only if you configure the Asus router.  RTFM for it.

voipnewuser

Quote from: drgeoff on September 22, 2019, 12:20:15 PM
If the OBi is getting its IP parameters by DHCP (which is its default mode) then it will, on powerup, automatically get an 192.168.1 address if and only if you configure the Asus router.  RTFM for it.

Ok I will do that when I get back tonight and will post update if this is resolved. Does my IP phone config file looks correct though? Seems like all the Outbound ports are pointed to 5603, and proxy is ip address of Obi200. On Obi200, SP4 is set to receive incoming from Port 5603, and IP is the Cisco IP phone, not 127.0.0.1.

Basically, everything was done according to that document you attached with setup being Option 2 for Obi200 device.

voipnewuser

Quote from: drgeoff on September 22, 2019, 12:20:15 PM
If the OBi is getting its IP parameters by DHCP (which is its default mode) then it will, on powerup, automatically get an 192.168.1 address if and only if you configure the Asus router.  RTFM for it.

I managed to change the Obi200 IP address to 192.168.1.140 by manually assigning it...Now when I got to place a call from the Cisco IP phone, after dialing the #s, there is a busy dial tone...it was silent before, but now looks like there's a busy dial tone? Still not able to receive or make the actual call though...

azrobert

Try routing inbound calls to the Cisco like this:
SP1/X_InboundCallRoute = {SP4(1001@xx.xx.xx.xx:pppp),ph,ph2}

Replace xx.xx.xx.xx:pppp with the IP address and port of your IP Phone.

voipnewuser

Quote from: azrobert on September 22, 2019, 09:45:06 PM
Try routing inbound calls to the Cisco like this:
SP1/X_InboundCallRoute = {SP4(1001@xx.xx.xx.xx:pppp),ph,ph2}

Replace xx.xx.xx.xx:pppp with the IP address and port of your IP Phone.


Yes, I did try that... and I just re-tested it now and I seem to be having the exact problem as this previous thread, which you took part in: http://www.obitalk.com/forum/index.php?topic=8729.0

Now for some reason, after restarting the Obi200 and Cisco 7942, I am able to receive calls...but I cannot dial out...there is a dial tone, but after dialing, it goes to a busy dial tone...It looks like the original user managed to resolve it by defaulting to the 8.3.5 Firmware, but I do not have a service contract with Cisco to obtain these files. Cisco only offers >8.4 for free...Any suggestions?

drgeoff

I'm not familiar with the Cisco xml file stuff but the one in your opening post contains some occurences of 192.168.0.68. Did you change those after changing the OBi's IP address?

Furthermore, what exactly did you do about the  subnet issue? Changing only the IP address of the OBi could result in it having gateway and DNS problems. You really ought to have the Asus on 192.168.1 subnet.

voipnewuser

Quote from: drgeoff on September 22, 2019, 11:52:54 PM
I'm not familiar with the Cisco xml file stuff but the one in your opening post contains some occurences of 192.168.0.68. Did you change those after changing the OBi's IP address?

Furthermore, what exactly did you do about the  subnet issue? Changing only the IP address of the OBi could result in it having gateway and DNS problems. You really ought to have the Asus on 192.168.1 subnet.

Sorry, let me explain where I am at now. After changing the IP of the Obi200 to 192.168.1.140, and changing everything in the conf.xml to the corresponding IP 192.168.1.140 with port 5063, I am able to successfully receive calls through the Cisco IP Phone (yay!). So it was due to the wrong subnet. However, I still cannot make outbound calls, which I suspect has something to do with the SP4 configuration?

Obi200 WAN Status:
IPAddress   192.168.1.140   
SubnetMask   255.255.255.0   
DefaultGateway   192.168.1.1   
DNSServer1   192.168.1.1

X_InboundCallRoute = {Obi200>(Msp1):SP1} (also tried with {>(Msp1):SP1})
X_RegisterEnable = Unchecked
X_UserAgentPort = 5060 (tried also with 5063)
X_Proxy = Checked
AuthUserName = Obi200
AuthPassword = none

IP Phone Setup:
<sipProxies>  
   <backupProxy></backupProxy>  
   <backupProxyPort></backupProxyPort>  
   <emergencyProxy></emergencyProxy>  
   <emergencyProxyPort></emergencyProxyPort>
   <outboundProxy>192.168.1.140</outboundProxy>  
   <outboundProxyPort>5060</outboundProxyPort>  
   <registerWithProxy>false</registerWithProxy>  

When dialing out on Cisco IP phone, it goes straight to a busy dial tone. I even tried changing X_InboundCallRoute = ph, to test if it would ring my handset, and it does not, just goes straight to a busy dial tone.

Asus router IS 192.168.1.1.

zapattack

OBi DNS server is same as gateway!!!!
Hope that is a typo.
Are you sure you can dial out from the OBi phone port?