I am attempting to use carrierroute for the first time, and the problem that I am having is that when I attempt to place a call, I see the following in stderror:
/usr/local/sbin/openser[32664]: New request - M=INVITE RURI= sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T= sip:1678XXXXXXX@domain.com IP=204.XXX.XXX.XXX ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C@192.168.5.147 /usr/local/sbin/openser[32664]: Callee is not local - M=INVITE RURI= sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T= sip:1678XXXXXXX@domain.com IP=204.XXX.XXX.XXX ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C@192.168.5.147 /usr/local/sbin/openser[32664]: Not normalized callee '1678XXXXXXX' to E.164format - M=INVITE RURI= sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T= sip:1678XXXXXXX@domain.com IP=204.XXX.XXX.XXX ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C@192.168.5.147 /usr/local/sbin/openser[32664]: carrierroute:carrier_rewrite_msg: Domain too big. (We only have 5 domains, you wanted 0.) /usr/local/sbin/openser[32664]: Request leaving server, D-URI='<null>' - M=INVITE RURI=sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T= sip:1678XXXXXXX@domain.com IP=204.XXX.XXX.XXX ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C@192.168.5.147 /usr/local/sbin/openser[32667]: New request - M=INVITE RURI= sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T= sip:1678XXXXXXX@domain.com IP=72.XXX.XXX.XXX ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C@192.168.5.147 /usr/local/sbin/openser[32660]: NAT-Reply - S=100 D=Trying F= sip:1404XXXXXXX@domain.com T=sip:1678XXXXXXX@domain.com IP=72.XXX.XXX.XXX ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C@192.168.5.147 /usr/local/sbin/openser[32667]: Proxy authentication failed - M=INVITE RURI= sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T= sip:1678XXXXXXX@domain.com IP=72.XXX.XXX.XXX ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C@192.168.5.147 /usr/local/sbin/openser[32663]: NAT-Reply - S=407 D=Proxy Authentication Required F=sip:1404XXXXXXX@domain.com T=sip:1678XXXXXXX@domain.com IP= 72.XXX.XXX.XXX ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C@192.168.5.147 /usr/local/sbin/openser[32663]: Failure route for PSTN entered - M=INVITE RURI=sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T= sip:1678XXXXXXX@domain.com IP=204.XXX.XXX.XXX ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C@192.168.5.147
Thanks for any direction!!
On Monday 12 November 2007, Mark Baker wrote:
I am attempting to use carrierroute for the first time, and the problem that I am having is that when I attempt to place a call, I see the following in stderror:
/usr/local/sbin/openser[32664]: carrierroute:carrier_rewrite_msg: Domain too big. (We only have 5 domains, you wanted 0.)
Hi Mark,
the error message you've qouted above is indeed wrong. I've made a fix for this in the trunk.
It means that the desired carrier does not exist. The cause could be an error in your script or in the route database.
Could you test again with the fix in r3118? This could give you more informations about the wanted carrier in this case.
Cheers,
Henning
I did as you suggested and updated to the latest head. The error I get is similar: carrierroute:carrier_rewrite_msg: desired carrier doesn't exist. (We only have 5 carriers, you wanted -1.)
Thanks for your time and assistance. - Mark Baker
On Nov 13, 2007 6:29 AM, Henning Westerholt henning.westerholt@1und1.de wrote:
On Monday 12 November 2007, Mark Baker wrote:
I am attempting to use carrierroute for the first time, and the problem that I am having is that when I attempt to place a call, I see the following in stderror:
/usr/local/sbin/openser[32664]: carrierroute:carrier_rewrite_msg: Domain too big. (We only have 5 domains, you wanted 0.)
Hi Mark,
the error message you've qouted above is indeed wrong. I've made a fix for this in the trunk.
It means that the desired carrier does not exist. The cause could be an error in your script or in the route database.
Could you test again with the fix in r3118? This could give you more informations about the wanted carrier in this case.
Cheers,
Henning
On Tuesday 13 November 2007, Mark Baker wrote:
I did as you suggested and updated to the latest head. The error I get is similar: carrierroute:carrier_rewrite_msg: desired carrier doesn't exist. (We only have 5 carriers, you wanted -1.)
Just for the archives:
"-1" is emitted if the carrier is not found, or not valid. There was a default carrier entry in the route_tree table missing.
Cheers,
Henning
-
Henning Westerholt -
Mark Baker