Tapi Problems

[jlumby]

I have the same version of PBXnSIP running on 2 different independant servers. If I setup the tapi client on my laptop to connect to one of them, everything works fine, however if I set it up to connect to the other one, then when my extension rings, I pick it up, and the call immediately terminates. The PBX logs the following

 

[5] 2008/07/09 17:02:20: Not setting dialog state of non-existing call port (call-id=b9578b47@pbx#4049)

[5] 2008/07/09 17:02:22: BYE Response: Terminate 86837862@pbx

 

Can you tell me what I might have configured wrong/different on the second system.

[Vodia PBX]

I have the same version of PBXnSIP running on 2 different independant servers. If I setup the tapi client on my laptop to connect to one of them, everything works fine, however if I set it up to connect to the other one, then when my extension rings, I pick it up, and the call immediately terminates. The PBX logs the following

 

[5] 2008/07/09 17:02:20: Not setting dialog state of non-existing call port (call-id=b9578b47@pbx#4049)

[5] 2008/07/09 17:02:22: BYE Response: Terminate 86837862@pbx

 

Can you tell me what I might have configured wrong/different on the second system.

 

At first glance that does not sound like a TAPI problem to me. Can you check if click to dial behaves correctly? Maybe something "stupid" like a missing dial plan entry for that route or some stange characters that cannot be dialled.

[jlumby]

You were correct, it was in the dialplan. The problem was the number that outlook was showing me matched the dialplan, however if I looked at the packet capture, it was sending a 1 infront of the number that outlook was displaying.

Thanks for the help